[John Mitchell]

Hi Jeff – no I hid the DVD columns as I find them distracting when working in a Blu-Ray project. Encore definitely did not re-transocde the assets. These were 1920×1080 50i assets so if the DVD clumns had been there they would have been saying “untranscoded“.

On the final burn/iso you can see there was some 500MB of free space on the disc which is another issue I have with Encore and Blu-ray. It does not report either the size or free space correctly.

cheers mate

John

[John Mitchell]

You can try 🙂 Some blu-ray players work, some don’t. You can use a tool called tsMuxeR to create the right file structure from your AVCHD file. Don’t make your data rate too high tho, remember the DVD spec maxes out at about 9.8MB/s so even compatible players will tend to fall over at high data rates. I’d paste a link over to another forum but don’t think that’s allowed around here, but maybe if you Google “blu-ray file structure on DVD?” you might find some helpful info.

It is a bit trial and error by the looks of the stuff I’ve read.

[John Mitchell]

OK – just wanted to clarify that this is definitely a bug. This project consistently built to a 33GB image within Encore. Here’s a look at the check project window that confirms that Encore knows it is the right size:

This shot confirms there is roughly 22GB (real) of assets:

Here’s the build window (that as per usual Encore incorrectly reports the build size as 26.25GB – I’ve learnt to ignore this!):

Here’s the flow chart that confirms each asset is only used once (not that this should affect disc size):

Here’s the screen shot of two .iso files of the same project – note the one that Encore built is from the project, the other correctly sized iso is built from a folder using the Encore Blu-ray folder option in combination with ImageBurn:

So basically everytime Encore built an image it somehow manage to shove an extra 11GB into it! When it built a folder it did it correctly. Deleting caches etc made no difference and I have no way of determining exactly what the 33GB ISO from Encore contains because it won’t mount. I might add that I have successfully built images from Encore for BD before so I don’t know why this particular project decided to behave this way. I like ot build and burn images as a way of ensuring that all that is happening at burn time with expensive BD media is the actual burning as I’ve had Encore crash before towards the end of a burn.

This kind of random stuff is enough to drive you nuts. It killed one BD on me when the iimage built successfully and I never checked the size and just went to burn it.

Beware check you ISO sizes before burn – HTH someone else

JOhn

[John Mitchell]

Hi Jon

The point is – it isn’t too big. Encore doesn’t report it as being too large it just fails with some arcane size error towards the end of the build iso command.

I ended up building to a folder and this folder burnt successfully to a disc.

YAEB – yet another Encore bug.

On the subject of Blu-ray and size I had another iso which built an ISO at a size of 36GB! The assets are 23GB only – I guarantee when I rebuild to a folder it will fit. Encore has some serious bugs with Blu-ray.

[John Mitchell]

Hi Jeff

I respect your opinion but I’m confused (mind you – I’ve authored only a few BDs)- all my reading of the spec says BluRay players are “better” at branching than DVD players and should be able to do it seamlessly using “the contents playlist file, which allows for high speed access to virtual playlists.” Hasn’t this part of the spec been implemented? I wouldn’t know but I’d be very surprised if Blu-ray was taking such a backward step. Of course using BDJ even more interactivity is achievable than straight BDMV authoring but I felt sure that even with BDMV (or HDMV) branching is supported.

And what I meant about making it clear wasn’t something buried on Pg 152 of the help file, but a warning that comes up in the interface when your trying to build a BD with chapter playlists. They have a project error checking process immediately prior to build, so Encore “knows” that it is building a blu-ray but no error pops up in the interface? Huh? Sorry – epic fail for me.

cheers

John

[John Mitchell]

Sorry to dredge up such an old thread but guess what – still doesn’t work in CS5. First of all zero out of 10 for Adobe for not documenting this and zero out of 10 for not addressing it for 2 years. Encore ain’t exactly cheap and this stuff should just work.

When Joe talks about Adobe addressing this I wonder if they can? I believe the core of Encore is the Sonic authoring engine so i think Adobe just addresses the interface etc.. not sure though.

[John Mitchell]

I’ve used BorisRED for this before (logo needs to be vector, but then it would for ProAnimator as well). I think Zaxwerks may give superior lighting and material interaction as well as some handy presets.

RED’s expensive as well but a lot of folks already have it, as either the original or AvidFX (which is just band labelled version of RED as a plug in and standalone) which comes with Avid.

You should also check out this link

https://www.videocopilot.net/tutorials/energetic_titles/

for a dummy 3D effect in AE – still a bit flat but might work for you and it’s free 🙂

[John Mitchell]

Thanks again Stephen.

I like Compressor 🙂 I just don’t like the fact that my Motion projects kept crashing it! (Quartz plug in I think)

And I’m not unhappy with the solution (I’m actually glad for any solution) – so thankyou.

Probably at the heart of all these problems is Quicktime – which I guess is being used as the interpreter for the Motion project within Compressor.

Perhaops if someone went through my workflow and told me why I was crashing and a way around it it might help…

My workflow was to drag the 35 motion projects into Compressor. I then highlighted all the individual source files and went to add a destination – this crashed Compressor after about 2 – 3 minutes. So I tried adding a custom preset to every file – XDCAM, native to the original Motion file for frame rate and raster. That crashed Compressor. So eventually I had to add a destination and preset individually to each source file. This took a while because everytime I highlighted a source file or dragged anything to it there was a noticeable delay. I saved each time and eventually got there with only one more crash.

Is there a better way and can anyone explain why it kept crashing with multiple projects?

This is the workflow I’d like to adopt to batch out Motion projects…

[John Mitchell]

Thanks for ths Stephen – I will give it a go. Wish I had two monitors for this…(most of my systems have two but the Mac only has one.)

As I have many more of these projects being able to adjust the template will be a big help. Still think it is a copnvoluted way of doing things that should be as simple as accessing the project preferences…

BTW – any tips on batch rendering? My experience with Motion project files interacting with Compressor was not good.

[John Mitchell]

Walter – that would be exactly my plan.