I'm finally seeing some continuity in results!

This applies ONLY if you are making 3D AVCHD BD using externally created 3D MVC avi files, but may be a good rule of thumb if you are experiencing freezes in your rendered streams, or failed burn cycles.

1) Make sure you clean out all tempory files before you try to burn anything.

2) Make sure "shadow copies" is turned off for HD material in settings, if you are working with HD footage.

3) Make sure any source material which is MVC avi has a total data rate of less than 120mbs for any 50P content.

4) Make sure any source material which is MVC avi has a total data rate of less than 180mbs for 50i content.

5) Author your 3DBD folder first, check the streams are good after creation and then copy to BDR.

6) I suggest trying to create intermediate mp4 files from you edit material in Produce, and use these to create your disc, as mp4 is less demanding than AVCHD, this may help in certain cases.

7) I obtain the most reliable processing with the source files on one drive, and the output files created onto a seperate drive - despite other opinions, neither of the media drives I use are my system C drive - I follow fundamental NLE guidlines which suggest that the system drive is best for system files only, whilst huge media files are best kept on dedicated, seperate, fast drives, with Indexing turned off.

Finaly, disable or remove any Anti Virus software you may have running on your system, it can cause fatal errors with file interrogation during processing.

It is preferable to have no internet connection on Editing Systems.

I'm now succeeding in creating 60 minute BDR streams without errors, from externally sourced high data rate MVC avi's using a variety of codecs - and very good they look too.

Paul

Quote: I'm finally seeing some continuity in results!

This applies ONLY if you are making 3D AVCHD BD using externally created 3D MVC avi files, but may be a good rule of thumb if you are experiencing freezes in your rendered streams, or failed burn cycles.

1) Make sure you clean out all tempory files before you try to burn anything.
2) Make sure "shadow copies" is turned off for HD material in settings, if you are working with HD footage.
3) Make sure any source material which is MVC avi has a total data rate of less than 120mbs for any 50P content.
4) Make sure any source material which is MVC avi has a total data rate of less than 180mbs for 50i content.
5) Author your 3DBD folder first, check the streams are good after creation and then copy to BDR.
6) I get best reliable processing with the source files on one drive, and the output files created onto a seperate drive -
despite other opinions, neither of the media drives I use are my system C drive - I follow sound guidlines which suggest that the system drive is best for system files only, whilst huge media files are best kept on dedicated fast drives.

I'm now succeeding in creating 60 minute BDR streams without errors, from externally sourced high data rate MVC avi's using a variety of codecs - and very good they look too.

Paul

Well done Paul ! I'm sure we all have learned a great deal from this exercise,, certainly I have a will make a note of this as a reference... Intel Core i7 3770K 3.6 Ghz,
GTX 680, 2 X Benq23 3D monitors,
6G DDR3, Win 7 64, Win 10 (Insider) 64
PCIE SSD, Intel Sata SSD 2 500 Gbyte Seagate,
Minoru 3D WebCam, NVIDIA 3D Vision-Ready

well done Paul.
I have passed your findings onto CyberLink.
Dafydd

Just a quick update:

All my work with PD10 is 3D - assets made in other software, final files are avi high data rate 3D MVC files.

My goal is to find a reliable workflow to create 3D BD from these files - its not been easy.

Basic system is Gigabyte X58 UDR3 i7 920 water cooled oc@ 4Ghz internal raid 0 4TB external Raid 5 4TB Nvidia GTX 285 6 gb ram. Samsung 500gb system drive. No Anti Virus Software.

If you follow this thread you can see I've had issues with the high data rate files I've been trying to use. As the render proceeds, the RAM is swallowed up until the OS stalls. The result is either, and, or a crash, a freeze in the video being created, or a tempory system panic creating a truncated file.

I've had moderate success with limiting the data rates in my master files, as well as the fame rates. 50P is a lot more intensive in data terms with MVC files, to cut a long story short, I found optimum data rates that produced a pretty high success rate.

All this time I've been running the OS and PD10 on the C drive. All my source data files are on the raid 5 and I've been outputting everything to the Raid 0.

I've juggled all this around too, using the C drive as suggested by some, turned off the over clocking - but the one thing that did help was turn off Shadow copies and the auto save. I Also clean out all tempory files before I try to do anything.

I recently added an OCZ 100gb SSD to a spare sata 2 port on my motherboard. I'm using this as a destination drive for renders in Produce and Folder output in Create Disc for 3D BD - I never burn directly to disc, I prefer to create a folder and check the streams are good. I also run Windows Task manager to keep an eye on the performance as it is very obvious when things go wrong.

Since fitting the OCZ I've not experienced a single failure, I've just created a 3D BD folder from an uncompressed MVC avi file with a data rate of 600mbs.

Maybe my experiences will help Cyberlink improve the data handling of PD10, as I do feel something is a little bit odd somewhere, and also help other users, I see many people on the forum having related issues.

I just attempted to create a new 3D BD folder to my Raid 0 instead of the OCZ, same 600mbs 3D MVC as above which worked perfectly: This is what happened, I've added a shot of the task manager showing the point at which things go nuts, all the ram is used and the CPU is shut down, the computer needs a hard restart and the folder is... gone

Paul

Quote: Just a quick update:

All my work with PD10 is 3D - assets made in other software, final files are avi high data rate 3D MVC files.

Since fitting the OCZ I've not experienced a single failure, I've just created a 3D BD folder from an uncompressed MVC avi file with a data rate of 600mbs.

Paul

I am interested to know how much of a difference 600mbs makes to the viewer ? Also I cannot find a way to achieve those rates..my created 3D-BD have a fixed rate of 15500K, I have found no way of changing that. I would very much like to. Intel Core i7 3770K 3.6 Ghz,
GTX 680, 2 X Benq23 3D monitors,
6G DDR3, Win 7 64, Win 10 (Insider) 64
PCIE SSD, Intel Sata SSD 2 500 Gbyte Seagate,
Minoru 3D WebCam, NVIDIA 3D Vision-Ready

Oh dear,

everything written is so ambiguous - let me try and be clear!

My workflow:

Edit my source files in another NLE, not PD10, including some After Effects work, titling etc.

Output my final edit to an uncompressed or high data rate compressed avi MVC file ( anything from 140mbs to 600mbs or above ) as 1280x720 50P (3D Bluray standard)

Import this file to PD10, make menu's and create 3DBD.

The data rate you mention for the AVCHD 3D blu ray is correct, the only way to up this is to utilise BluRay profile 5 which requires an expensive MVC encoder which produces two streams, a Base and Dependant stream which can have a maximum combined data rate of 60mbs.

All other 3D BD writers of a non professional nature will allow you to make AVCHD 3D discs with a maximum of 25mbs (vbr) so an average of 16mbs or there abouts.

Sonic Scenarist will do the real thing at about £20,000 as will DoStudio at £7,000 for the MVC coder alone!
Sony make Blueprint which I've asked for a trial copy of, but I guess it will cost a fortune too!

Paul