[Ht Davis]

The QT Player will convert them to a format it can recognize. It’s a 64bit application trying to run a video file built to view in a 32 bit memory space, in a format that’s no longer playable in the new codec. It can reconfigure the video to a new format, which takes time, but it will match it as best it can, and play it without much alteration. The two formats are highly similar. But some of the header is very different, and the numbering of certain values is calculated differently ( or at least represented by different memory sizes). While it cannot play, it can be converted to a newer format that will play. I wouldn’t count on that for long, though.
By the way, PRO RES is quicktime, they’re not abandoning it, their just upgrading it so you don’t have to buy another program to work with these codecs. Before you had to have Quicktime, Compressor, Final cut. Now if you have compressor or final cut, you can use the codecs to encode. If you have quicktime player, it will convert the video to pro-res or mp4 and play back either one. However, the older codecs are not supported for playback, as their trying to keep the playback code small, but because those codecs are so similar to the new, it only takes a single pass to convert videos. If you can find the old codecs and put them in their old locations, you might get back the quick look. It’s iffy. I use several versions of CS and CC so I have to have both sets to work with prores across them. I also have to have compressor. If I want to output dolby properly, I use logic and Final cut.
You have to be able to function in a cross compatible workflow world. Some things you’ll have to do yourself instead of moving right into another app. Get used to it.

Also, In light of recent problems found with audition, consider the following:
Make a Batch file in windows that will
1. take a dropped file as input(your session file will do)
2. get the parent folder (the whole structure is important)–this is the folder where your session is, along with the folder containing your audio files that you record.
3. periodically non-destructively (as in not deleting files that are no longer in the first folder) Mirror the contents of the parent folder to another location anywhere on any drive (every 2-5 minutes works) and make sure you set this folder, or you can simply use the parent folder of the original file and add a Backup folder inside,
4. then just continually make backups using a forever loop (Condition is always true like While 1==1). You can close it when you close audition by simply closing the Command prompt window. You won\’t lose everything even if you crash, after all, audition cannot delete what it knows nothing about.

On mac open automator:
start by making an application–call it BackupStart. create 2 Path variables: SessionFile, ParentFolder. These will be what you use to grab your files. Create more Path variables with names similar to BackupFolder#, where # is the number of which backup folder. You can now Set Variable Value (in actions library) for the path Session file as your first action (this will catch the path of the file you drop on the app). Next, run a shell script in Bash (an action in utilities or system), and set STDIN to Arguments. Clear everything in the shell, and type: dirname \”$1\” Exactly as shown (don\’t replace dirname, it\’s a command that grabs the name of the parent folder of the file you just dropped in. Add another Set Variable action for ParentFolder. Now use an ASK for finder items action, and look in it\’s options to \”Ignore this items input\” and check the box. Add a Set Variable for BackupFolder1. Repeat for each BackupFolder variable you have (ask for folder, set variable). Now add a GET VARIABLE action, go to options and select \”Ignore input\” again, make sure you are GETting the ParentFolder variable. Now another GET Variable for Backupfolder1, but DONT ignore input (you want the two to pass into one another and continue on). Repeat this last op for each BackupFolder variable, leaving the ignore input unchecked to group them all together. Now add a RUN WORKFLOW action and turn off \”Wait for workflow to finish\”. Save this file, leave it open, and go to file Duplicate. Rename the duplicate BackupLoop1. File >Convert this doc to a Workflow. Delete the variable SessionFile from this document and all but the very last of the actions(Run Workflow). The other variables are still necessary. Everything we add should be above the RUN WorkFlow action. Use a Get Variable on your ParentFolder, and as before, do not check ignore input. You need this to run straight through from the first document. Add the GET Variable for your backups. Add a Shell Script in Bash, with STDIN set to Arguments. Clear the script box, and type:
rsync -vau \”$1/\” \”$2/\” (enter)
rsync -vau \”$2/\” \”$3/\” (enter)
The first line copies your parent folder\’s contents, the second copies the first backup to the second. You can continue this until you have handled every backup in the script. Apply a PAUSE action for a few seconds. Now add a Loop Action, and set it to run 50 or more times (applies a wait time until finish) and set it to use the same input. This will continually backup all your data as you record, and when you hit stop, you should get a copy of your audio almost immediately after, done by your system, and making the RAW file data into a finished file set. Now add the GET VARIABLE set again for all your variables, ignoring the input of the first one, but keeping it for the others. Point them into the last action of RUN WorkFlow. Again, Duplicate the document, call it BackupLoop2. Change the Run Workflow in this file so it points to where you saved BackupLoop1. Change the RUN WorkFlow in BackupLoop1 to point to BackupLoop2. Change the Run Workflow in BackupStart to point to BackupLoop1 and place BackupStart in your DOCK. When you get ready to record, drop the session file onto your dock icon, pick your backup folder(s), and then let it go. Hit record, and when you hit stop, wait a few seconds for it to end the raw file tags. Now check your backup folder. You should have a perfect WAV capture there.

IF audition crashes, you can drag the files in your backup folder to the original place and continue.

[Ht Davis]

Another option is to get lists of the music (artist, album, etc) for the event. You can then find the music, and the copyright holder. If there is a DJ however, they’ve already bought the rights to display the music. Also, if your audio contains other audio besides the music, it’s not usually considered infringement, as it is simply a sound in the room that you are capturing. Another thing you can do is make a cut just as the song ends, and have it fade into other sound from another clip, which makes it so you haven’t “Stolen” the entire song, only part of it is legible. It doesn’t degrade the value of the song itself as a commercial work, as the song is not what is being used commercially. It is only a sound in the room, and has probably been paid for. This is Reasonable Fair Use. If there isn’t a DJ, it’s not on you to ensure the audio isn’t a stolen work. If they are playing the sound in the room when you’re shooting, and you don’t control the music, you aren’t responsible for any copyright infringement. Again, if I record a video of my family trip while I’m in the car, and a song comes on the radio, it becomes a part of the sound of the vehicle or the space I’m in.
Here’s a quick rendition of fair use:

You’re not making money off the music itself
You’re not diminishing the marketability of the work (in this case, you’re making it more marketable, as they might want to buy a cd to remember the moment)
You’re educating or documenting
You’re not diminishing the artwork (by showing something completely opposite the work or otherwise putting it down)

If some of these apply, you’re golden. I wouldn’t worry.

[Ht Davis]

Do you have Adobe Media Encoder installed? Try Queuing the video out to media encoder. Also, you might start a clean project, import your old project into it, save it new, clear the cache, save again, close, open again and then export the sequences. Sometimes the cache files get too big or too heavy for it to process correctly, and in trying to call up more room or more memory start points, it fails. Check how much ram you allocated to the program in your preferences.
Also, without adobe media encoder, some video formats will look okay in projects, but never render out.

[Ht Davis]

Always keep the same frame rates in proxies. Just the quality of the data in the images used for frames will be different. That said, if you plan on speeding or slowing video, you want to work with the original frame rate. 60 drops to 24 easily. 60 drops to 30 easily. 30 Drops to 24 easily. Vice versa. For 60->24, it’s 40% exactly (even in drop frame). For 30->24 it’s 80%. For vice versa, 24->30 is +25% (so 125% to speed up). For 24->60 it’s +150% (set to 250% to speed up).

[Ht Davis]

First, what kind of edits will be done? Pan\zooming? Speeding up\slowing down?

If you pan\zoom, you’ll lose quality fast. If you zoom to 115, you’ll be okay, but beyond that, you’ll really notice a problem from 1080p or 720p video. If you were to make your own sequence, I’d go with a widescreen 720×480 size (480i usually, but 480p for our purposes). If you want to keep a 1:1 square pixel size and pixel aspect ratio of 16×9, use 853×480. You can zoom out unit you’re just bigger than your frame (don’t have the video auto resize, you won’t be able to keep quality when pan\zooming; drop the video in and size it down until its just right). You can then zoom in without loss in quality, and move around a little. This works great for TV screens, or external screens that are better at upsizing. For standard computing however, don’t pan\zoom if you want Sharp picture. Or only do it lightly using the 720p setting. Also, I recommend a max bit-rate of 10-12mbps. That’s standard internet speed anymore, and won’t lose much for quality. Set your low to 4 if you have sections where only 1 or 2 objects move slower, and 6 if you have more sections of action. Set the target to 8-10.

To answer your question, if you want to apply some slight zoom or reduction of shake, use a 720p 24fps sequence and size your video down manually to start. Then apply your other effects. When you output, start with the 720p setting and then adjust your bit-rate (leave it as Constant Frame rate CFR, but VBR for Variable bit rate) as mentioned above. You’ll get outstanding quality.
If you don’t need all the pan\zoom, use the 1080P and set the bit-rates as stated above. You’ll get a larger frame size, more compression, but it will only hurt if your action is really intense. If you have some super awesome action, up the values by 3-5mb\s.
Either way, turn on frame blending. Sometimes one or two frames will be dropped by a camera and need to be rebuilt at the end. You can enable this by turning it on at export. If your audio slips out, Export your video only with the same formatting as the original, do not carry audio with it, turn on frame blending. This will build a useable video clip. Place it in the same sequence, unlink the audio from the original video, and link it to the new video. Delete the old video. Carry on.

Also, In light of recent problems found with audition, consider the following:
Make a Batch file in windows that will
1. take a dropped file as input(your session file will do)
2. get the parent folder (the whole structure is important)–this is the folder where your session is, along with the folder containing your audio files that you record.
3. periodically non-destructively (as in not deleting files that are no longer in the first folder) Mirror the contents of the parent folder to another location anywhere on any drive (every 2-5 minutes works) and make sure you set this folder, or you can simply use the parent folder of the original file and add a Backup folder inside,
4. then just continually make backups using a forever loop (Condition is always true like While 1==1). You can close it when you close audition by simply closing the Command prompt window. You won\’t lose everything even if you crash, after all, audition cannot delete what it knows nothing about.

On mac open automator:
start by making an application–call it BackupStart. create 2 Path variables: SessionFile, ParentFolder. These will be what you use to grab your files. Create more Path variables with names similar to BackupFolder#, where # is the number of which backup folder. You can now Set Variable Value (in actions library) for the path Session file as your first action (this will catch the path of the file you drop on the app). Next, run a shell script in Bash (an action in utilities or system), and set STDIN to Arguments. Clear everything in the shell, and type: dirname \”$1\” Exactly as shown (don\’t replace dirname, it\’s a command that grabs the name of the parent folder of the file you just dropped in. Add another Set Variable action for ParentFolder. Now use an ASK for finder items action, and look in it\’s options to \”Ignore this items input\” and check the box. Add a Set Variable for BackupFolder1. Repeat for each BackupFolder variable you have (ask for folder, set variable). Now add a GET VARIABLE action, go to options and select \”Ignore input\” again, make sure you are GETting the ParentFolder variable. Now another GET Variable for Backupfolder1, but DONT ignore input (you want the two to pass into one another and continue on). Repeat this last op for each BackupFolder variable, leaving the ignore input unchecked to group them all together. Now add a RUN WORKFLOW action and turn off \”Wait for workflow to finish\”. Save this file, leave it open, and go to file Duplicate. Rename the duplicate BackupLoop1. File >Convert this doc to a Workflow. Delete the variable SessionFile from this document and all but the very last of the actions(Run Workflow). The other variables are still necessary. Everything we add should be above the RUN WorkFlow action. Use a Get Variable on your ParentFolder, and as before, do not check ignore input. You need this to run straight through from the first document. Add the GET Variable for your backups. Add a Shell Script in Bash, with STDIN set to Arguments. Clear the script box, and type:
rsync -vau \”$1/\” \”$2/\” (enter)
rsync -vau \”$2/\” \”$3/\” (enter)
The first line copies your parent folder\’s contents, the second copies the first backup to the second. You can continue this until you have handled every backup in the script. Apply a PAUSE action for a few seconds. Now add a Loop Action, and set it to run 50 or more times (applies a wait time until finish) and set it to use the same input. This will continually backup all your data as you record, and when you hit stop, you should get a copy of your audio almost immediately after, done by your system, and making the RAW file data into a finished file set. Now add the GET VARIABLE set again for all your variables, ignoring the input of the first one, but keeping it for the others. Point them into the last action of RUN WorkFlow. Again, Duplicate the document, call it BackupLoop2. Change the Run Workflow in this file so it points to where you saved BackupLoop1. Change the RUN WorkFlow in BackupLoop1 to point to BackupLoop2. Change the Run Workflow in BackupStart to point to BackupLoop1 and place BackupStart in your DOCK. When you get ready to record, drop the session file onto your dock icon, pick your backup folder(s), and then let it go. Hit record, and when you hit stop, wait a few seconds for it to end the raw file tags. Now check your backup folder. You should have a perfect WAV capture there.

IF audition crashes, you can drag the files in your backup folder to the original place and continue.

[Ht Davis]

I’ve had that happen. For some reason, this feature seems to be built for MULTICAM modes, not just multi audio. You have to make sure each audio track has a corresponding video track, even if it doesn’t have any video on it. I’ve had the menu grey out with 6 cams (with their own audio) and an audio track of my own mix, when the last audio track didn’t have a video track number to connect with. Once I added the video track, saved, closed, and reopened, everything worked. It’s looking for a timecode to use, which is usually defined by a video track, not audio, at least in premiere.

[Ht Davis]

When working with a lot of clips, sometimes editors will set the starting timecode to an offset value that represents the section of the video they’ll be working with. This isn’t done to the video, it’s done in premiere. It keeps a record of this. Crossed out lines means that perhaps the files didn’t import properly, so relinking fixes the problem with the video. Maybe the name of the clip has changed or something about the clip has been altered\linked differently. Either way, a relink should fix it. When you replace it completely, you rip out anything the other editor has done. I’ve had the problem with video when the two copies of the shot are encoded in a similar format with slightly different settings. Maybe your other editor has their own compressed version of the video or transcoded it for use for whatever reason.

In multi-editor workflows, I’ve often found that working in the same OS is only part of the needs to be met. Working from the same set of files is another. I use DISK IMAGES to store the file data. These carry common formats and can be used easily. When formatted properly, the OS isn’t a limitation. Disk Images with the original file data can be split and burned to optical media for later re-use. You can also catalogue the contents for searching. It makes everything easier to work with the same set of files in the same folder structure.
If you are within the same compound or campus, a shared NAS will also allow you to mount the disk image so file linkage is the same across the systems (URLS are common structure), and it will grab the files from the same link. With a fast fiber channel connection, you’ll never want for speed. Just my experience there… Old ways kept everybody on top of the work and there was a ton of it to go around. New ways are cutting down how many are needed, but are making it a little more complex in other ways.

[Ht Davis]

VLC is tough to encode with if you’ve never done it before. Even pros have trouble with the settings, and it’s not always successful when it comes to outputting new files. That said, it might work. Give it a try.

Another you can try is MPEG STREAMCLIP. It’s old… ..I know. You might need to download some old code packages to use it and look up how to install it. But lemme tell ya… …I’ve had similar issues… …and it saved my butt.
Handbrake works sometimes too. I’ve had 1 or 2 instances to use it. Grab a default setting and whiz bang…

VLC and Handbrake rely on the FFMPEG code mostly. But Handbrake can make use of mac native packages if you get the right version. Streamclip is native mac, but can be pointed to other packages. Streamclip isn’t free.

Also, In light of recent problems found with audition, consider the following:
Make a Batch file in windows that will
1. take a dropped file as input(your session file will do)
2. get the parent folder (the whole structure is important)–this is the folder where your session is, along with the folder containing your audio files that you record.
3. periodically non-destructively (as in not deleting files that are no longer in the first folder) Mirror the contents of the parent folder to another location anywhere on any drive (every 2-5 minutes works) and make sure you set this folder, or you can simply use the parent folder of the original file and add a Backup folder inside,
4. then just continually make backups using a forever loop (Condition is always true like While 1==1). You can close it when you close audition by simply closing the Command prompt window. You won\’t lose everything even if you crash, after all, audition cannot delete what it knows nothing about.

On mac open automator:
start by making an application–call it BackupStart. create 2 Path variables: SessionFile, ParentFolder. These will be what you use to grab your files. Create more Path variables with names similar to BackupFolder#, where # is the number of which backup folder. You can now Set Variable Value (in actions library) for the path Session file as your first action (this will catch the path of the file you drop on the app). Next, run a shell script in Bash (an action in utilities or system), and set STDIN to Arguments. Clear everything in the shell, and type: dirname \”$1\” Exactly as shown (don\’t replace dirname, it\’s a command that grabs the name of the parent folder of the file you just dropped in. Add another Set Variable action for ParentFolder. Now use an ASK for finder items action, and look in it\’s options to \”Ignore this items input\” and check the box. Add a Set Variable for BackupFolder1. Repeat for each BackupFolder variable you have (ask for folder, set variable). Now add a GET VARIABLE action, go to options and select \”Ignore input\” again, make sure you are GETting the ParentFolder variable. Now another GET Variable for Backupfolder1, but DONT ignore input (you want the two to pass into one another and continue on). Repeat this last op for each BackupFolder variable, leaving the ignore input unchecked to group them all together. Now add a RUN WORKFLOW action and turn off \”Wait for workflow to finish\”. Save this file, leave it open, and go to file Duplicate. Rename the duplicate BackupLoop1. File >Convert this doc to a Workflow. Delete the variable SessionFile from this document and all but the very last of the actions(Run Workflow). The other variables are still necessary. Everything we add should be above the RUN WorkFlow action. Use a Get Variable on your ParentFolder, and as before, do not check ignore input. You need this to run straight through from the first document. Add the GET Variable for your backups. Add a Shell Script in Bash, with STDIN set to Arguments. Clear the script box, and type:
rsync -vau \”$1/\” \”$2/\” (enter)
rsync -vau \”$2/\” \”$3/\” (enter)
The first line copies your parent folder\’s contents, the second copies the first backup to the second. You can continue this until you have handled every backup in the script. Apply a PAUSE action for a few seconds. Now add a Loop Action, and set it to run 50 or more times (applies a wait time until finish) and set it to use the same input. This will continually backup all your data as you record, and when you hit stop, you should get a copy of your audio almost immediately after, done by your system, and making the RAW file data into a finished file set. Now add the GET VARIABLE set again for all your variables, ignoring the input of the first one, but keeping it for the others. Point them into the last action of RUN WorkFlow. Again, Duplicate the document, call it BackupLoop2. Change the Run Workflow in this file so it points to where you saved BackupLoop1. Change the RUN WorkFlow in BackupLoop1 to point to BackupLoop2. Change the Run Workflow in BackupStart to point to BackupLoop1 and place BackupStart in your DOCK. When you get ready to record, drop the session file onto your dock icon, pick your backup folder(s), and then let it go. Hit record, and when you hit stop, wait a few seconds for it to end the raw file tags. Now check your backup folder. You should have a perfect WAV capture there.

IF audition crashes, you can drag the files in your backup folder to the original place and continue.

[Ht Davis]

1. NEVER TURN LFE ALL THE WAY UP!!!!! Unless of course, you plan to kill somebody when you light their whole house on fire when the SubWoofer explodes… …In that case, you know, sure.
2. You don’t want to go changing encoders back and forth. Output your video, send it to final cut, and mix it in there. You can get great quality video encoding from Compressor, and it will mix the streams as you see fit. Finally, when you want to encode the audio for stereo output as well, the dolby from your final cut will mix down for a standard mixed stereo if you tell it to encode that way. In stereo, the LSRS will be delayed and phased, so they create dimension, and the LFE will be fed much the same by delays to all speakers, both in phase and out, so it will play normal on stereo. The Stereo channels will be WAV encoded, but compressed data, and the rest will be the differential analysis of the delays, Phase and db drops from those channels. That’s why the files are kept so small. The compression is just the mathematical representation of the differential from the main speakers. Fun in’t it?
3. If you can only use PREMIERE, then you’ll be in a mess. You’ll have to strike a balance. I’d dump the wavs into premiere, then start LFE at 15% and play with it there, watching it close. Don’t let it go above about 1\3 of the phase meter when you set it for 94-96db width. That will allow you to get the full safe range. At about 1\3 of the meter, you’re at 30dbu (sound pressure), which is enough to feel an earthquake in your calves. Try staying below the 1\3. If you can keep it to that, you shouldn’t have a problem with general use. -6dbV on that meter is a max value for other speakers. It gives you enough headroom to allow them to attenuate their own volume levels.

Good luck.

Also, In light of recent problems found with audition, consider the following:
Make a Batch file in windows that will
1. take a dropped file as input(your session file will do)
2. get the parent folder (the whole structure is important)–this is the folder where your session is, along with the folder containing your audio files that you record.
3. periodically non-destructively (as in not deleting files that are no longer in the first folder) Mirror the contents of the parent folder to another location anywhere on any drive (every 2-5 minutes works) and make sure you set this folder, or you can simply use the parent folder of the original file and add a Backup folder inside,
4. then just continually make backups using a forever loop (Condition is always true like While 1==1). You can close it when you close audition by simply closing the Command prompt window. You won\’t lose everything even if you crash, after all, audition cannot delete what it knows nothing about.

On mac open automator:
start by making an application–call it BackupStart. create 2 Path variables: SessionFile, ParentFolder. These will be what you use to grab your files. Create more Path variables with names similar to BackupFolder#, where # is the number of which backup folder. You can now Set Variable Value (in actions library) for the path Session file as your first action (this will catch the path of the file you drop on the app). Next, run a shell script in Bash (an action in utilities or system), and set STDIN to Arguments. Clear everything in the shell, and type: dirname \”$1\” Exactly as shown (don\’t replace dirname, it\’s a command that grabs the name of the parent folder of the file you just dropped in. Add another Set Variable action for ParentFolder. Now use an ASK for finder items action, and look in it\’s options to \”Ignore this items input\” and check the box. Add a Set Variable for BackupFolder1. Repeat for each BackupFolder variable you have (ask for folder, set variable). Now add a GET VARIABLE action, go to options and select \”Ignore input\” again, make sure you are GETting the ParentFolder variable. Now another GET Variable for Backupfolder1, but DONT ignore input (you want the two to pass into one another and continue on). Repeat this last op for each BackupFolder variable, leaving the ignore input unchecked to group them all together. Now add a RUN WORKFLOW action and turn off \”Wait for workflow to finish\”. Save this file, leave it open, and go to file Duplicate. Rename the duplicate BackupLoop1. File >Convert this doc to a Workflow. Delete the variable SessionFile from this document and all but the very last of the actions(Run Workflow). The other variables are still necessary. Everything we add should be above the RUN WorkFlow action. Use a Get Variable on your ParentFolder, and as before, do not check ignore input. You need this to run straight through from the first document. Add the GET Variable for your backups. Add a Shell Script in Bash, with STDIN set to Arguments. Clear the script box, and type:
rsync -vau \”$1/\” \”$2/\” (enter)
rsync -vau \”$2/\” \”$3/\” (enter)
The first line copies your parent folder\’s contents, the second copies the first backup to the second. You can continue this until you have handled every backup in the script. Apply a PAUSE action for a few seconds. Now add a Loop Action, and set it to run 50 or more times (applies a wait time until finish) and set it to use the same input. This will continually backup all your data as you record, and when you hit stop, you should get a copy of your audio almost immediately after, done by your system, and making the RAW file data into a finished file set. Now add the GET VARIABLE set again for all your variables, ignoring the input of the first one, but keeping it for the others. Point them into the last action of RUN WorkFlow. Again, Duplicate the document, call it BackupLoop2. Change the Run Workflow in this file so it points to where you saved BackupLoop1. Change the RUN WorkFlow in BackupLoop1 to point to BackupLoop2. Change the Run Workflow in BackupStart to point to BackupLoop1 and place BackupStart in your DOCK. When you get ready to record, drop the session file onto your dock icon, pick your backup folder(s), and then let it go. Hit record, and when you hit stop, wait a few seconds for it to end the raw file tags. Now check your backup folder. You should have a perfect WAV capture there.

IF audition crashes, you can drag the files in your backup folder to the original place and continue.

[Ht Davis]

It would seem that this is in fact a problem with the link not recognizing data carried from older versions. To explain: IF you started with an older version of Premiere and AE, even the first CC version, and updated to a later one mid project, before or after creating a dynamic link to AE or other apps, something with the link engine is trying to interpret it as if an older project file and not a newer one. Open your saved AE project files, save them and close. Now go to Premiere and unlink them, then relink them (like any other clip). They will relink and update the version of AE being used. If that doesn’t fix it, try dropping the clip from premiere project panel or sequence to AE while AE is open, then save the comp, import to PPro and “Replace from BIN”.