Quote: Matt, have you ever tried making a DVD folder using PD and using another program like Power2Go or Imgburn (free) to burn the disk?

James... take a look on .. http://forum.cyberlink.com/forum/posts/list/11592.page it maybe helps you on your question.. Read it all and you find your answer.

Nicolas, I wasn't asking a question for myself since I use Imgburn all the time to create my DVDs which I produced from PD using a DVD folder. I was just asking Matt if he ever tried that approach to solve his problem. My thought was that PD may think the produced file would not fit on a 4.7GB DVD, but if the DVD folder was smaller than 4.7 GB then Imgburn may be a way to get around PD's error message.

Q9300 2.5 GHz
4 GB Ram
Nvidia 9800 GT

Hi James,

the project weights in at 9.2GB according to PD8 but is actually only 6.4GB.

Does anyone know why Cyberlink wouldn't disable the disc restriction message?

Matt

Quote: Matt, have you ever tried making a DVD folder using PD and using another program like Power2Go or Imgburn (free) to burn the disk?

Can I chip in and reply to that. When I first got PD, I just couldn't get it to record to a DVD. CL made all sorts of noises but the bottom line was that they thought it was another DVD burning software getting in the way - Nero or Pinnacle... Anyway, to cut a long story short, I bought in to Power2Go and forever since I have created the DVD in PD and then burned with P2Go. Never had a problem. However, I have not pushed the limits as I am only producing small stuff.

Perhaps the reason for the disparity in estimate vs actual is due to the variable bit rate used in the video? The estimate would use the maximum bit rate multiplied by the timeline time, but why it wouldn't replace that with the 'actuality' after the video had been produced is beyond me. Perhaps they have to create a container on the disc, which would use estimate, but the container cannot be (easily) resized after production? i7 980x; W7 Pro; 12GB; Nvidia GTX 285; 2x300G Velociraptors in Raid 0; 2x1.5TB Barracuda in Raid 1; 2TB WD Studio Ed.II (eSATA); NEC SpectraView Reference 2690 + MultiSync EA232

Hi all,

Disc Summary accuracy is caused by different algorithms.
That is, different file formats may need different algorithms to get the most accurate estimation. However, PD can use only one algorithm at a time to work out the disc summary. CL/PD chooses the one that has most tolerance. This is the reason why an editor sees a difference between the real size and estimation.

I have edited an explanation on the disc summary issue.

Dafydd

Quote: Disc Summary accuracy is caused by different algorithms.
That is, different file formats may need different algorithms to get the most accurate estimation. However, PD can use only one algorithm at a time to work out the disc summary. CL/PD chooses the one that has most tolerance. This is the reason why an editor sees a difference between the real size and estimation.
Dafydd

That is the main reason that CL should have never put in the hard restriction on DVD folder size limits when creating a DVD folder. If the coding can't estimate it correctly because of varied footage formats, how can one justify putting a hard limit on folder size creation? Let the user create the DVD folder and deal with it. Obviously other DVD folder issue will occur if the size is too big as the DVD format specification can't deal with that.

Quote: PD8 put some new wrinkles in folder creation. PD7 allowed folders larger than DVD, or DVD DL and you could compress (smart fit) with a 3rd party utility if you wish. PD8 no longer allows that, they check for size, very annoying as smart fit is not nearly as good as some other products.

http://forum.cyberlink.com/forum/posts/list/8401.page#35149

This is not a new issue, http://forum.cyberlink.com/forum/posts/list/4262.page PD7 was the same. The new issue in my opinion is that PD8 won't create the DVD folder, that is an issue that hopefully will be addressed by CL in PD9.

Jeff

Hi Jeff,
Thank you for your input - excellent.
I've passed on your observations.
Dafydd

21st July 2010

received a reply from head office after posting my complaint to them. Just the same old. Getting very frustrated

Hi everyone,

A funny thing just happened! I've just completed a 4 hour project in PD. PD estimated the project to be 49826mb which is over the 49202mb limit for 50gb blu-ray discs.

However, when I attempted to burn to folders, no warning message appeared telling me the project was too big and it went through no problem!

I have the latest build 3022. Can anyone else replicate this?

Cheers,

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

Hi Andrew,

I am assembling some vacation footage to be placed on a Blu-Ray disc today. It should be a FULL disc...I'll post my results.

Kevin
Check out PDtoots. PowerDirector Tutorials and more! Over 5,000 Subscribers.

Cheers Kevin!

It's worth mentioning that the actual folder size after burning to folders was 40.97GB so it was just under 18% out!!

The 'Refuse to Burn' feature does kick back in if attempting to write to DVD folders with a project that is too large. Maybe it's because writing to blu-ray folders is activated by a workaround and is exempt from the same restrictions.

Cheers.

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

Once you have the AUDIO_TS & VIDEO_TS folders on your hard drive to the correct size, you can burn the DVD disk as a data disk using any burner program.

I recommend refusing the 'make compatible' option because this causes reprocessing of the video that will cause some degradation and can affect the menu behavior of your production.

Agreed, the point here is that PD won't even burn the folders to your hard drive if it deems the project too big for a DVD.

Cheers,

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

Quote: This is not so important, but maybe helps at burning time! to add more clips to the media. I observe that the “used disk” space on “Create Disk” always shows about 8 to 10% more that the real created DVD size (the time it’s pretty much close to real).

This was my grand opening in PD forum time ago and earns me a lot of points (without any modesty), but this topic has moved around without any object and there is only one solution… as Jeff say:

Quote: That is the main reason that CL should have never put in the hard restriction on DVD folder size limits when creating a DVD folder.

I still think that it would be much easier if CL R&D remove the restriction, don’t you think?

cheers,
Nicolas

Hello all,

I've been away a while. Back in July, I got an email from HQ suggesting to select 'burn project to DVD' and not to 'folder'.

On selecting this, I got a PD message saying my project was too big for the media, BUT....it allowed me to continue burning! Yay I thought, finally the answer (hmm, did this come with update 3022).

Alas, I was never able to burn my (in reality 6.4GB) project still, as I got a PD message in the menu stage of burning stating the usual 'not enough room to burn the project' (it messed my discs up too!)

After uninstalling my Roxio easy CD and any other media software that might interfere, and making loads of space on my HDD, I still wasn't able to burn onto disc.

So seven months on, I'm back to try again. Has anyone had this problem at this stage and any fix?

I still have an unused Dual Layer burner I bought for my project here and a pack of expensive Dual layer discs getting corrupted on each try.

Hi,

Take a look at this 'refuse to burn' workaround:

http://forum.cyberlink.com/forum/posts/list/15324.page

It works for PD9, definately worth a go on PD8.

Cheers,

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530