-
1. Re: A couple of questions about burning Blu-rays in Encore
MobyTrix Jul 25, 2011 8:51 AM (in response to Webshark2000)Webshark2000 wrote:
2. Why does Encore have to retranscode all of my motion menus every time I build the project, even if I haven't made any changes to the menus? Because my motion menus are quite numerous, this process takes over an hour each time. Doesn't Encore normally keep transcoded files so you can reburn the project quickly if you come back to it?
3. When I tell Encore to automatically transcode my video files using H.264, it shows the final Disc info as 25GB used and 7.005MB free, with 0 bytes used for BD-ROM content. But if I try to build the project straight to a disc it transcodes everything (taking several hours) then fails saying the project exceeds disc capacity. If I build it to an image, the image ends up being like 27GB and fails because of size if I try to burn it using ImgBurner. What should I do?
Thanks.
These two issues are bugs that I reported for CS5 and to my knowledge are still not fixed in CS5.5.
For #2, there is no workaround so you should build the time into your workflow (ie. work on something else while it's building). I found that even properly transcoded assets are STILL re-transcoded, so for those assets, I feed Encore the original master files to avoid two generational losses.
For #3, the Image build sometimes pads too much and creates an invalid .ISO for the size requested. Thankfully, I've found this is a padding issue only with building an image file and/or burning to disc directly from Encore. The workaround is to build a BMDV folder instead, which has always been correct in my experience, and then use a program like IMGBURN (Windows; not sure of a mac equivalent) to burn to Blu-ray.
-
2. Re: A couple of questions about burning Blu-rays in Encore
Webshark2000 Jul 25, 2011 10:25 AM (in response to MobyTrix)MobyTrix wrote:
The workaround is to build a BMDV folder instead, which has always been correct in my experience, and then use a program like IMGBURN (Windows; not sure of a mac equivalent) to burn to Blu-ray.This is exactly what I did and it fixed the problem. I ended up building to a Blu-ray folder and burning the contents to a BD-R 25GB using imgBurn. It worked perfectly.
I hope Adobe fixes these issues in a future update, but at least it's good to know there's a workaround.
Thanks!

