eEB191789. FAQ = http://www.cyberlink.com/support/product-faq-content.do?id=14960&prodId=4

e80D00002, maybe burn to a folder/instead/as well.

Quote: eEB191789. FAQ = http://www.cyberlink.com/support/product-faq-content.do?id=14960&prodId=4

e80D00002, maybe burn to a folder/instead/as well.

The FAQ refers to eEB191087; I had looked for both e80D00002 and eEB191789 without success.

Most EB errors that I've looked at refer to compatibility or damaged media, which I don't think is the case here since I'm writing to hard disk, SSD actually. eEB191087 did mention a lack of free space, but I have 106GB free on the drive I'm creating to and 13GB on my 'C'.

I sure welcome any other suggestions. I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

In addition to the previous post, I'd ask you to heed this request from that link;
Empty the contents of the C:\Windows\temp folder and C:\temp folder, if you have one. Then empty the Recycle Bin.

Get back to us with your results, please. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Quote: In addition to the previous post, I'd ask you to heed this request from that link;
Empty the contents of the C:\Windows\temp folder and C:\temp folder, if you have one. Then empty the Recycle Bin.

Get back to us with your results, please.

Already done. Are you hinting at a lack of space issue when suggesting clearing out TEMP folders, or a conflict with their contents? Look at the issue I've submitted to CL:

I have a movie that I'm trying to create with 'save as disc image', but it aborts at 98% completion with error e80D00002 (or eEB191789 if burning directly to blue ray). See 'PD13-1...' attachment.

The attached file 'pd13-2...' show that an ISO is created sized at around 20GB, which is about right given I did a Produce of it at close to that size.

When I mount that non functional ISO, attachment 'PD13-3... ' shows it has an allocation of 119GB, which exceeds the free space of 80GB on that drive, but all directories are empty.This is repeatable. I have Created several other movies of even greater size with no issue. All were created H.264, 1920x1080x60FPS.Also attached is... I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

Lack of free space was where I was heading, it was also an easy exercise for you to do, and may have helped with minimal effort. Oh well, it was worth a try. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Just throwing this stuff out in case it triggers something from someone...

I did another test last night. Did a Create 'create a folder' as well as a 'save as disc image'.

The Create 'create a folder' completed ok, playable, all fine, with separate .m2ts for movie, intro and menus.

The Create 'save as disc image' terminated again with e80D00002. Like before, a ISO was created, albeit this time sized at 3GB, and when mounted again shows an allocation of 119GB with empty folders throughout.

I had initially thought that CL couldn't (erroneously) find 119GB of available space to write the ISO and that this triggered the error code. But, after looking at other functional ISO's, I realize now that once mounted they all show an allocation of 119GB, with actual size varying according to the movie.

So I've come to the conclusion that the issue is not really available space, there's lots of that. I've created other movie ISO's with CL that were successful, so it would appear not to be an issue with CL logic creating an ISO.

The issue seems to be around a combination of preparing output material for ISO (or burning direct to BD) -and- this particular movie.

Peeking into the created ISO shows that it's populated, but obviously missing some structural elements. I'll try to find a utility that can check the integrity of an ISO.

Any suggestions welcome as to where to investigate next.

P.S. I was thinking of falling back to PD12, but that involves hours of uncertain work. I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

I have a movie that I'm trying to create with 'save as disc image', but it aborts at 98% completion with error e80D00002 (or eEB191789 if burning directly to blue ray). See 'PD13-1...' attachment. The attached file 'pd13-2...' show that an ISO is created sized at around 20GB, which is about right given I did a Produce of it at close to that size. When I mount that non functional ISO, attachment 'PD13-3... ' shows it has an allocation of 119GB, which exceeds the free space of 80GB on that drive, but all directories are empty.This is repeatable. I have Created several other movies of even greater size with no issue. All were created H.264, 1920x1080x60FPS.Also attached is...

CV 27

I think you may have an illegal character in the file name that's stopping the file being completed. Try changing PD13-1 to PD13_1 and so on.

I hope this works for you Panny TM10, GH2, GH4,

Quote: I think you may have an illegal character in the file name that's stopping the file being completed. Try changing PD13-1 to PD13_1 and so on.

I hope this works for you

The file names 'PD13..." actually refer to attachments to my bug submission.

I just want to make sure I understand your post though. A dash '-' is a legal character in a file name, even on a volume name, under WIndows. Did I miss your point? I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

It was just a thought - If I send a PD file wirelessly to my HD player and there is a "-" in the file name. It just stops at 98% with no explanation. Took me ages to discover why Panny TM10, GH2, GH4,

Quote: It was just a thought - If I send a PD file wirelessly to my HD player and there is a "-" in the file name. It just stops at 98% with no explanation. Took me ages to discover why

I'll keep that in mind for the next set of problems I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

Here's an update to my saga.

I did several tests: cut out accelerated clips, use another menu template, uncheck "include root menu" and "include opening menu video", etc. All unsuccessful.

After reading other posts I thought related to my issue, I tried what one of the posters said "worked" for him: specify "no menu".

Doing so, my project successfully completed a Create of an ISO. Having "no menu" defeats the purpose of a 1.5hr Blue Ray with 8 chapters, but at least this test sort of points me to a next step in debugging this issue.

I have long chapter text fields that overlap somewhat the thumbnail (World Monopoly template). So I'll try shorter text not overlapping and fewer chapters per page.

I believe there is a great opportunity for CL to clean up code logic: throughout these numerous tests, I've seen all sorts of strange behaviors. Why loading a project that has not changed a bit now throws CL into a 'not responding' state, while killing the process and reloading the project works perfectly well? Why do I get an error immediately at the start of a Create when that Create goes just fine after restarting CL?

CL has put in a tremendous set of functionality into PD over time. I think it's now time to clean up by coding for the exceptions.

I've often read that corruption in a movie can produce all kinds of strange behaviors. If this is what prevents me from completing my project, then I would recommend (already addressed to CL development)

1- more robust coding so that specifics are provided as to what is corrupted thus facilitating corrections; when PD13 aborts giving a cryptic error code, surely it has specifics as to what it didn't like

2- better yet, even more robust code that circumvents the corruption with a warning and completes the project

3- some utility that scans a project and its time line to detect corruptions I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

I did tests with chapter text overlapping thumbnail: still competed Create OK.

Then, while I was preparing for a second test, reducing the number of chapters per page, this caught my eye: even though I had initially set the nb of chapters per page at 5, the top righ corner showed 1, but the menu structure was showing 5 chapters under 1 title. I reset the number of chapters to 5, ran the Create and it completed OK.

I'm not sure how I got into this situation, but here's my theory, although I could not reproduce it.

I initially had a 3hr movie which had 14 chapters. I decided to split it in 2 parts. For part 1, I chopped off the tail end, so that apparently went well. But for part 2, I needed to chop the front end and at some point I believe PD13 got confused with reorganizing chapters. I should also mention that I was using specific frames for chapter thumbnails as opposed to the default.

P.S. I'm posting this here as I don't have a 'reply' button on my case# since the last exchange. Hope CL is reading... I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

Hi CV27,
I've been monitoring your posts and have advised CyberLink of your observations.
Dafydd

Quote: Hi CV27,
I've been monitoring your posts and have advised CyberLink of your observations.
Dafydd

Thanks! I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB