Blu-ray authoring problem

_Angus_

Senior Member Joined: Feb 19, 2011 19:59 Messages: 180 Offline

Solved by

Dec 10, 2017 13:59

Hi guys,

This is going to be slightly vague so apologies in advance. My retired friend has been spending a lot of time travelling and shooting video with his wife (who takes stills). Somebody told him to buy an editing program which he didn't get on with. He mentioned this to me, and I said get Power Director, 'cos it just works.

Well, he's got on with it very well, and burnt a dvd of part 1 of his recent US trip. He realsied his pc didn't have a blu-ray drive so bought an external one from Amazon. He used Windows 10 and after a few minutes it recognised the drive, but called it CD/DVD I think. We produced his masterpiece and then wemt to burn it.

Power Director started the authoring pricess but ay 98% stopped and sayed there for a couple of hours till he aborted it.

We're unsure how to proceed, he has 12 GBs memory.....

We checked the driver and asked Windows to download the latest, but after looking it said it already had the correct driver.

PD saw the drive as Blu-ray, not 100% windows does. :-/

Any thoughts?

I will encourage him to sort out his forum membership!

This message was edited 1 time. Last update was at Dec 10. 2017 14:01

Fenman

Senior Contributor Location: Cambridge, UK Joined: Nov 24, 2011 04:44 Messages: 731 Offline

Dec 10, 2017 15:38

When you say "started the authoring process" do you mean he was burning direct to a disc? The authoring process starts by compiling the disc structure, menus, video files etc. then enters the burning phase. This might be the point at which the process failed. Under 'Final output' try unchecking 'Burn to disc' and instead check 'Create a folder', selecting a suitable destination on the hard drive. Also uncheck ' Enable hardware video encoder' if this is checked. This will create a folder and file structure on the hard drive identical to what would be on the final DVD/Blu-ray which can then be played on a software player to test the compilation.

If that works that would imply the problem lies in the Blu-ray burner. If this came with a disc with bespoke drivers on it you could try uninstalling the driver that Windows installed then, with the drive unplugged, install the driver from the disc then plug the drive in and try again. I think when Windows detects new hardware the drivers that it installs may not always have the full functionality of the manufacturers own drivers.

Personally I never try to burn my discs with Power Director. I always use the 'Save to disc image' option. This creates a disc image .ISO file which I then burn using a free stand-alone burning program (Imgburn) as I feel this is less likely to produce excessive numbers of 'coasters'. So far I've had a 100% success rate using this method. It has the additional advantage of allowing the burning of multiple copies without needing to re-author each time.

This message was edited 2 times. Last update was at Dec 10. 2017 15:46

Regards,
Mike

Home-build system:
Intel Core i5 Quad Core 3.3GHz, 2 x 4GB DDR3 1333MHz,
Asus Nvidia GT440 1GB, 2 x Western Digital WD10EARS 1TB, 1 x Seagate ST1000DM010 1TB,
Windows 7 Prof 64-bit, PD 9 Ultra 64, PD 13 Ultimate 64

PepsiMan

Senior Contributor Location: Clarksville, TN Joined: Dec 29, 2010 01:20 Messages: 1054 Offline

Dec 10, 2017 15:40

welcome back.

you didn't give a lot of required info so, first -> probably a software compatibility issue??? Check the Windows 10 Compatibility of CyberLink Products on Your PC. if it's good to go, then disable all HA. use CPU only rendering and use lower writing speed to finish your so called masterpiece. remember if it doesn't come out as you've expected, then remember 'garbage in garbage out'

last resort -> see if you can burn to a folder, then use ImgBurn to finish... here's the ImgBurn 2.5.8 - without OpenCandy!

there are few things that are broke in PD 15/16, GPGPU is one of them. you gotta have that lucky GPU driver version in order to work...

happy happy joy joy

PepsiMan
'garbage in garbage out' 'no bridge too far'

Yashica Electro 8 LD-6 Super 8mm
Asrock TaiChi X470, AMD R7 2700X, W7P 64, MSI GTX1060 6GB, Corsair 16GB/RAM
Dell XPS L702X i7-2860QM, W7P / W10P 64, Intel HD3000/nVidia GT 550M 1GB, Micron 16GB/RAM
Samsung Galaxy Note3/NX1

_Angus_

Senior Member Joined: Feb 19, 2011 19:59 Messages: 180 Offline

Dec 11, 2017 14:45

Thanks guys.

We did burn an image to disk and that was successful. After that I deleted a couple of files my friend had installed when first connectiing the drive, some driver update program which should probably be avoided. Then we disconnected the drive rebooted and then reconnected, this time windows saw it as BD-something or other, as it should do, we tried burning from Power Director and everything worked okay.

By the way, I always wite the disk from Power Director and never seem (touch wood) to have a problem. Apart from if I do a compilation it seems to ignore my request for PAL and go for NTSC. :-/

Thanks for your help, much appreciated.