Rendering Blu-Ray folders VS6pro/ult - stalled?

[PCFlyer]

I have a file that is 31gb, have attempted to render to Blu-Ray 4 times. It keeps stalling at 6% - no change in the slider bar for the last hour, currently at hour 06:39 and counting. Any recommendations? Is he dead Jim?

[Ken Berry]

Hi Jim... and welcome to the forums.

Unfortunately, though, we need rather more information than what you have provided. For a start, we need to know the Properties of the 31 Gb file. So please right click on it and copy ALL its Properties here, or else take a screen grab of it and upload it here as an Attachment.

Moreover, when you say you attempt to render it to Blu-Ray, do you mean a Blu-Ray file or a Blu-Ray disc? Can you identify what is at that 6% point? Is it different from the rest of the project?

[PCFlyer]

It is set to "create Blu-Ray folders". Also set for DL blu-ray.

The timeline consists of a short 15 minute segment. When the menu was created, 4 other longer VS project files, ranging from 20 min to 40 min were added.

Chapter points were added to each segment, though a sub menu was not desired, just a main menu.

The preview menu worked fine.

Where would I find the "properties" of the file? Since it didn't render - I assume it doesn't exist.

Thank you.

Attached is a snap of the screen, after 14 hours.

[PCFlyer]

I have narrowed the problem down to one project. In rendering it to a Blu-ray file separately from the others it hangs at 99%.

Any troubleshooting tips?

Thank you.

[Ken Berry]

That's one of the reasons we normally recommend NOT inserting vsp project files into the burning module. Rather, we recommend any project first be rendered to a new video in the format you intend to burn to disc -- as you have now attempted to do.

Unfortunately, there are no real tips for troubleshooting in situations like this -- apart from the obvious one of checking what is in the project at about the point that the rendering fails... But again, it would be helpful to know what format video is in the problem project. As I said in my first post above, you get the properties by right clicking on a clip either in the timeline or library window. If you have more than one type of format in the project, then do the same for the other format(s)... I notice from the image you uploaded that your overall project appears to be a slideshow. So is the problem project also a slideshow? If so, what are the formats of the images involved in it?

[PCFlyer]

The noted slideshow was from a previous iso burn.

Even though the problem file rendered to 99%, upon review it seemed fine. All others were rendered to Blu-ray files, then pre-rendered when added to the menu. Not sure if that will help.

I am getting some green horizontal bars across the first few frames of the clips. I trimmed them but wonder why they are shown or do not they not show up in the final?

We'll see if this works.

[PCFlyer]

You mention "We recommend" ... Is there another guide for using VSP?
If so, I would like to review it so I don't have to waste multiple days in trial and error mode.

If it doesn't work then maybe it shouldn't be an option?

All files began as AVCHD, 1080 60i.

[Ken Berry]

There is no other guide. It is simply a recommendation we make in cases like this. It developed in much earlier versions of Video Studio. I, for instance, started off with VS7. In those days, computers were far less powerful, and many users had trouble when they added a vsp project file to the burning module. This appeared to be because the computers did not appear to have enough grunt to be able to do the rendering and the burning all in the same process. (A vsp file is not a video file. It is only a text file telling the program what video was in it, where it was stored and what editing was done. It would still have to be converted to video either in the editing module or as part of the burning process.)

Our recommendation flowed from a workflow that others -- including myself -- tended to use anyway, namely finishing editing then, still in the editing module, going first to Share > Create Video File > and choosing the appropriate output format. If we were making a DVD, say, we would produce a DVD-compatible mpeg-2. When the new file was produced, we would then start a New Project. No need to give it a name since the objective was simply to empty the editing timeline. Then we would choose Share > Create Disc (and then the appropriate type of disc such as DVD or Blu-Ray). The burning module would open, and it should have an empty timeline. If by chance there was something in that timeline, we would delete it, then manually add the video clip or clips made in the editing module. Note that we would add the actual clips and not the vsp files from which they were made. Then we would check in the Options cogwheel icon in the bottom left of the burning screen and make sure that the box beside 'Do not convert compliant mpeg files' was ticked. We could then build the menu and burn. If on the final page of the burning module we got a message saying 'Converting Title', we would know something was wrong since the title in this case was the actual video we had insert, not the words we assigned to the DVD's 'title' or name. In other words, if you follow this, you should not get the 'Converting Title' message which appears in your image above.

As for not making an option available, well, the workflow of using vsp files in the burning module does in fact work for many users. It's just that in some cases it doesn't. That's when we make our recommendation to use our workflow instead.

You said "All files began as AVCHD, 1080 60i". That's fine as such files would be Blu-Ray compliant. If they were 1080/60p, they would not comply with the international Blu-Ray standard as it currently stands. But again you would need to check that that 'Do not convert compliant mpeg files' is ticked. Otherwise, the program would attempt to convert the AVCHD files (which are mpeg-4) into Blu-Ray standard mpeg-2, and could account for that 'Converting title' message.

My point, though, wasn't about what format the slideshow was in. Rather, it was about the format of the images used to make the slideshow in the first place.

[PCFlyer]

I am getting the "Convert title ..." message, and then it hangs. How is this fixed? The "Do not convert compliant..." is has a check mark.

[Ken Berry]

If that box is ticked and you are getting the 'Convert Title' message, then somehow or other the actual video file is not fully Blu-Ray compatible -- or else you have inadvertently included a vsp file. If you are sure that all your files in the burning module are truly video files and not vsp's, and if all have the same properties, then right click on one *within Video Studio* (either in the timeline/burning timeline or the editing library window). Then copy ALL the Properties here, please or take a screen grab and attach it here.

Slideshows can be tricky. They are tailor made for frame-based/progessive mode. But as it said, unless they are 1280 x 720p, then if one of them happens to be p instead of i, that could be your problem. Normally, the Properties should show Upper Field First if they are truly i. If that is not there, then almost undoubtedly they are p.

[PCFlyer]

All 5 clips have similar properties as the attached. A blank edit timeline was used and I went directly to share, then added all clips.

Has anyone had problems with adding chapter points to clips - and then not using a submenu?
I would like to have the chap points for ease of navigation without the overhead of a submenu. Wonder if this is the problem. I burned a DVD iso from same files, but removed all chapter points.

? I changed the background photo of the menu - but it is 1920x1080.

[PCFlyer]

There is a slideshow at the end of the 2nd clip, but it is stalling on the 1st clip. Would that matter?

[PCFlyer]

Ended up using AVS to master it. It had no problems taking the 5 clips made in VSP and creating a BD. Yes, the menu system is not as fancy, but it works. It would be nice nice if VSP did as well in creating BDs as it does DVDs.

Thanks for your help, in the end it was taking too long to trouble shoot.