-
Adobe Encore Bluray says its burning blank bd-r to full capacity mbps specs but disc looks partway burned???
What I’m using:
Windows 7
Adobe Cloude Encore CS 6
Samsung Portable Bluray Writer SE-506
Verbatim BD-R recordable hard coat (not re-writable)Problem Backstory:
Fan film director who spent a fair amount of time developing a dream project into a reality. Unfortunately I didn’t have the high tech equipment of the time to make this project the full specs I wanted it to have so essentially the best I could manage was to edit and finalize it to a standard 640×480 mov file off of final cut express on an old Imac 10.5.8.I’m defintiely happy with how the file itself came out for not being 720 or 1080p. However regardless of being the specs it was, this file totaled out to 13.2 GB being a 92 minute film.
I never had a problem getting it on standard DVDs or DVD+DL, and their presentations were fine but I was always curious if Bluray (Since they hold 25GB of space) would have a better result.
Problem itself:
After a long time of transfering source mov files over to my PC computer, I was finally able to burn some test copies with some slightly better results. Now I’m in the process of maximizing specs. However as I was testing things with trial and error, I noticed something.Despite what Encore tells me of a 720×480 Max Quality preset (which I manually determined) maxed my mov file to the disc at just 33.33 mpbs target rate; I burned a first play disc with what I was told was that amount, look at the back and notice that only “25%” of the disc looked burned. I checked things out further and then noticed the FileSession m4v file that had been created from that burn was only 5.8GB big.
That is starting to make me question:
A- If the file session from that specific burn was 5.8 GB big, does that corelate to why the back of the bluray disc looked partway burn when the build section stated otherwise?
B-And if so, why would that occur like that and what would I need to do to fix that issue to guarantee a full max spec result like I had planned on doing. (Would encoding the file through Media Encoder to a m4v/ac3 and then dumping that into encore solve the issue?)
