Trahald
2nd March 2004, 05:10
Im taking this from something I put in the knowledgebase for dif4u. the question comes up alot so i thought id bring up some of my findings. I also wanted to open up a dialogue to maybe get it squished once and for all. Here it is --
Question: What is this 'The number(0.0) of frame in a VOBU is less than 11.99/10.00' error scenarist is giving me and how do i fix it!?!
Answer: Basic definition of the error is.. there is a scene that is less than legal duration (0.4 seconds.) This occurs for many reasons, here are the main ones I have seen.
1. The scenarist script has 2 scene times very close to each other. This isnt really the scripts fault, it just goes by the ifo. The problem is that scenarist is programmed to put any scene time to the closest I frame it can find. If the closest I-frame happens to be the same as the scene before it used, so be it. The normal GOP structure has the I-frames 15 frames apart so there could be up to about a 14 frame difference that could still cause scenes to end up on the same I-frame. A quick way to fix this is to manually fix the script so that the next scene time is 15 frames away from the previous.
Now you may ask how did the origional publisher do it? Well it goes back to the encoding step.. whats supposed to happen is there should be forced I-frames placed by CCE during the encode. BatchCCEWS/DoCCE4u does place I-frames at chapter points.. but does not force them at cell points.. and its the cell points that tend to be very close together. Hopefully use of the CCE Cell-Point file that DVD Decrypter generates will be added to a future version of BatchCCEWS.. you can load that file manually if you wish before encoding.
2. A scene time is placed after the end of the film. Again its because of the scene time is gotten from the ifo. If the video is encoded a little short or the last I-frame is too close to the end of the film this may occur. Without prescanning the file, this may be harder to fix in advance. This may be helped with batchccews using cellpoints instead of chapter points for CCE. Or for sceneaid to maybe disregaurding dummy length scenes at the end of pgcs and replacing them with dummies. To fix it yourself, hand editing your script so that the length of film truely reflects the true time of your assett. And also making sure no scene times are past the end of the film time in your script.
Errors 1 and 2 can also be overcome by importing/processing of the assetts in scenarist obviously.
3. Really short files. These are nocce files that are too long for Scenarist to make into still shows, but also fall below the 0.4 second minimum for a VOBU. These genarate other errors as well. The way to deal with these? Usually only replacing them with a dummy helps.. Also sometimes they are slide shows that were origionally put together as cells (so legal still length as single cells) You can split by cell id and import as Still Shows then put the still shows back together.. but usually these files arent directly linked for playback. They are mostly test parterns or images that the authoring company put in but arent referenced directly by the menus. So usually replacing with a dummy is the best way to go. Review them in PowerDVD to see.
Hopefully these issues can be worked around/fixed with newer versions of Scenaid and BatchCCE.
Question: What is this 'The number(0.0) of frame in a VOBU is less than 11.99/10.00' error scenarist is giving me and how do i fix it!?!
Answer: Basic definition of the error is.. there is a scene that is less than legal duration (0.4 seconds.) This occurs for many reasons, here are the main ones I have seen.
1. The scenarist script has 2 scene times very close to each other. This isnt really the scripts fault, it just goes by the ifo. The problem is that scenarist is programmed to put any scene time to the closest I frame it can find. If the closest I-frame happens to be the same as the scene before it used, so be it. The normal GOP structure has the I-frames 15 frames apart so there could be up to about a 14 frame difference that could still cause scenes to end up on the same I-frame. A quick way to fix this is to manually fix the script so that the next scene time is 15 frames away from the previous.
Now you may ask how did the origional publisher do it? Well it goes back to the encoding step.. whats supposed to happen is there should be forced I-frames placed by CCE during the encode. BatchCCEWS/DoCCE4u does place I-frames at chapter points.. but does not force them at cell points.. and its the cell points that tend to be very close together. Hopefully use of the CCE Cell-Point file that DVD Decrypter generates will be added to a future version of BatchCCEWS.. you can load that file manually if you wish before encoding.
2. A scene time is placed after the end of the film. Again its because of the scene time is gotten from the ifo. If the video is encoded a little short or the last I-frame is too close to the end of the film this may occur. Without prescanning the file, this may be harder to fix in advance. This may be helped with batchccews using cellpoints instead of chapter points for CCE. Or for sceneaid to maybe disregaurding dummy length scenes at the end of pgcs and replacing them with dummies. To fix it yourself, hand editing your script so that the length of film truely reflects the true time of your assett. And also making sure no scene times are past the end of the film time in your script.
Errors 1 and 2 can also be overcome by importing/processing of the assetts in scenarist obviously.
3. Really short files. These are nocce files that are too long for Scenarist to make into still shows, but also fall below the 0.4 second minimum for a VOBU. These genarate other errors as well. The way to deal with these? Usually only replacing them with a dummy helps.. Also sometimes they are slide shows that were origionally put together as cells (so legal still length as single cells) You can split by cell id and import as Still Shows then put the still shows back together.. but usually these files arent directly linked for playback. They are mostly test parterns or images that the authoring company put in but arent referenced directly by the menus. So usually replacing with a dummy is the best way to go. Review them in PowerDVD to see.
Hopefully these issues can be worked around/fixed with newer versions of Scenaid and BatchCCE.