The need for the wavs is a Netflix delivery requirement. Even though we were able to spit out a ProResHQ of the final sequence to send to the facility creating the IMF master, which has already aired, or should I say streamed on Netflix? We now have to deliver archival masters ungraded and textless. While the aforementioned master was under 600 GB and afforded audio included in the file now we have to deliver DPX files which do not have audio so I must generate .wav files. We have generated ProTools stems but because on these archival masters I added some clean cover / Textless Elements to the end the ProTools stems would only work for the actual program content. In order to have audio on the additional end material I had to pull the stem elements from the actual show and add them at the end for the additional elements. Some networks want clean covers want clean cover/Textless Elements with sound and others MOS. As a result of this I made new audio only QT .movs which match the archival sequences then using VideoToolShed's Audio Map created individual .wav files for each stem. This is what Netflix wants so I'm going to give them both the .mov of audio only and the wav files to comply with their delivery requirements.
The whole DPX archival master delivery is complete overkill given our initial Camera Original is AVC-Intra 422 YUV 10bit BT.709. Originally we delivered DNxHRHQX files thinking that should meet the "DI" archival master delivery requirement. Initially we were told that would be sufficient but subsequently someone else at Netflix said that is not sufficient. After all why do in 600 GB what you can redo in 4.51 TB with separate audio files? There really seems to be a disconnect between these delivery requirements and technical reality but my job is to find a way to meet the demands even if they seem silly and overkill.
All this so it can be streamed and choked down to nothingness to the viewer. But hey it's 4K and "Every Pixel Counts, Every Pixel Counts, Every Pixel Counts..." Ahhhh now I will comply, now I will comply.... Just can't wait for 8K to be shoved up my art hole. ;-(
---In Avid-L2@yahoogroups.com, <cutandcover@...> wrote :
On Fri, Aug 5, 2016 at 8:18 PM, John Moore bigfish@... [Editing-List] <Editing-List@yahoogroups.com> wrote:I received what look to by typical mono mix stems .wav files from a Protools mix session. When I go to import a single stem I end up with a stereo track that appears to be to mono stems with the same name as the original mono mix stem. It gets weirder when the tracks for say the full mix which are named the same for both channels with the difference being the suffix.To be specific when the "Auto Detect Broadcast Wave Mono Groups" is checked on if I import "Santa Rosa ST MIX.L.wav" I end up with a stereo track where both tracks are labeled "Santa Rosa ST Mix.L.wav" If I do the same with the "Santa Rosa ST MIX.R.wav" I end up with a stereo track with both tracks also labeled "Santa Rosa ST Mix.L.wav". Turning off the feature and I get the normal mono tracks I would expect to get. I'm not sure how Avid detects these Broadcast Wave mono groups, is it based on the tracks names and why would both the right and left stems come in as stereo tracks with both tracks labeled Left.That was the issue I first noticed then today on a different project at work I exported an audio only .mov using direct out of an standard 8 channel 5.1 LtRt mix stems. I ended up with a .mov with 8 discrete tracks that I used QT Pro 7 to change the track assignments from mono to their corresponding proper assignents of L,R,C,Lfe,Ls,Rs,Lt,Rt. Then I ran Videotoolshed's Audio Map program, which I think I called QT Map in a thread earlier this week, and that produced 8 .wav stems each with a suffix of _1 thru _8 which correspond to the individual tracks from the audio only 8 channel QT .mov. When I ama link media to any one of the individual clips I end up with an 8 channel clip. I went and made sure to uncheck the autodetect broadcast wave mono groups in the import settings but that seems to have no effect on ama linking.As was suggested a few weeks back in order to change the time code on the wav files to match the sequence time code I downloaded the free Wave Agent program. When I changed the time code on the first "_1" file it actually changed the time code on all the individual wav files. When I bring any one of the 8 wav file into wave agent they show the correct modified time code and the Channels Column shows "8(MONO). I'm curious how these wav files are all linked. Is it based on file name or is there something in Audio Map when it strips the 8 discrete channels from the .mov to create 8 .wav files that creates metadata embedded in each of the files that links them together. I haven't had a chance to check much with the resulting files but they do import and link back into Avid with the correct starting time code I modified using Wave Agent so everything is working but I'm curious if Avid has a bug detecting Broadcast Wave Mono Groups and does it base it's imports and linking on just the file names or some other metadata present in the wav files?When I originally stripped out the wav files using Audio Map the files all show a 10 hour something time code when brought into Wave Agent. That's where I changed the start time code to match the sequence start of 00:59:00:00 24 frame code. I have no idea where the original 10 hour something code came from as the QT 8 channel .mov that was used by Audio Map had matching time code to the sequence.So many little metadata devils to line up. It would really be nice if Avid would just export direct to .wav with matching timecode to the sequence. It does export but all the .wavs start at zero time code in my experience. Does anybody know of a way to make Avid do what I need?From the thread a few weeks back here is the link Jim F. posted for Wave Agent:Mac and Windows. More info, link to app and manual here:John Moore Barking Trout Productions Studio City, CA bigfish@...
Posted by: bigfish@pacbell.net
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
No comments:
Post a Comment