I have a 9 minute video; personal/consumer use; 1280x720; 59.94; source video from a Contour+ helmet camera that stores .mov, H.264; audio is on a separate track from my own selection of mp3 files (it is a music video). I have three intended playback targets: Blu-ray disc, Sony PS3 native, and PC/Windows Media Player. Is there a big downside on video or audio quality in this case using multiplexing to produce a single .m2t file imported into Encore to produce the BD vs. separate .m4v/.wav files? Not a huge deal, but having to maintain one production files vs. three is a minor plus if it makes little to no difference on the BD front.
Depending on the answer, If I use the H.264 Blu-ray format/preset in PP to produce the .m2t file does Encore have to re-encode? I am assuming Encore does not reencode if I am using separate .m4v/.wav files.
Sanity checking here ... I noticed that if I import a separate .m4v (and audio file) into Encore it does some thinking ("pending ...") and eventually comes back with "Don't transcode". However, if I produce a .m2t file using exactly the same settings other than TS multiplexing Encore comes back with untranscoded/Automatic.
Is the above to be expected or not? If yes, is Encore saying it needs to transcode simply to demux the audio, or is it going to transcode the video stream as reported?
If the audio stream is muxed, to the best of my knowledge Encore will re-transcode both video and audio if the audio stream doesn't match the project audio settings. Yet another reason to use elementary audio and video streams whenever possible.
Hi Jeff - I am using the defaults for H.264 Blu-ray and the 720p 59.94 preset within PP which has Dolby Digital for the audio format, which in turn matches the default transcoding settings in Encore. If I export with separate .m4v and .ac3 files Encore reports "don't transcode". If I go back and export with the only change being TS multiplexing Encore reports that it will transcode (I assume that is what untranscoded and automatic mean).
I wasn't sure exactly what you meant by match the project audio settings, so let me know if I missed something here.
Understood on separate being better. I was trying to kill two birds with one stone by having a playable .m2t file that I could also burn to BD. It's not a huge deal, worst case I will just have to deal with multiple exported variants when I complete a movie.
the defaults for H.264 Blu-ray and the 720p 59.94 preset within PP which has Dolby Digital for the audio format
The default for all H.264 Blu-ray presets is actually PCM audio. If it's set to DD, then you must have changed it. This happens when you change the default Multiplexer from None to TS.
Best to leave it at None and create two exports, one for BD and one for computer playback.
I see the default audio format for H.264 Blu-ray presets is PCM. What is odd is that if I turn on TS multiplexing not only is the format changed to Dolby Digital, but that is the only option. PCM as an audio option dissappears from the user interface. Is that to be expected?
Further, if I change the default transcode settings in Encore to be Dolby Digital, my .m2t file stills says it needs transcoding. Earlier Jeff thought that if the audio project settings matched Encore would not need to transcode.
Jim - undertsood. I'm just grappling with export file overload. Every time I put together a home or bicycle video I have to create a .m2t file to playback on PS3 and computer, separate audio/video for making BD's, project archive using the project manager feature, and then a master file using a less lossy codec in case of a future backwards compatibility issue with reloading old projects. I will do what it takes here, but am admittedly confused as to why Encore (apparently) needs to transcode the video stream here.
am admittedly confused as to why Encore (apparently) needs to transcode the video stream here.
I don't understand it either, I just know that is the way it works. There are more variables than you may think on how the audio stream is formed, and some variations are not bd legal. Also, when you mux, Encore must demux before it can build. We don't know if Encore is takingthe easy way out and declaring anything muxed to be illegal, or whether Encore predicts what it has once demuxed and finds that that demuxed product is illegal.
It seems illogical for a mux to work and a demux not, if they are really the same streams. But muxing/demuxing is really not that simple.
I have not tested dynamic link in CS6. Many users believe it does not work well enough, but the combination of adobe media encoder and dynamic link would be one of the best ways for these multiple export formats to work.