New Scenaid question

[hoops10]

With the newest Scenaid being released, is the method of using the big 3 different now? I have always used this method, in this order: DIF4U -> ReAuthorist (sometimes used RA, only when DIF4U messed up the bitrate) -> BATCHCCEWS. I would then have Scenaid scan the demux dir and create the script for Scenarist. First of all, please tell me if this method is flawed and what I need to do to fix it. Second, I have looked around in the newest Scenaid and noticed BATCHCCE integration. So am I right in thinking that, Scenaid could be plugged into where RA is in the above method, send BATCHCCE the bitrate numbers, and then when BATCHCCE is done encoding, I can create a script for scenarist with it? Thanks.

[influenza]

You can still follow your method if you want. You can also go from scenaid to batchccews. In that case the nitrates from ccedata.txt produced by dif4u are used. If you so it this way you can fully automate encoding and scenarist processing.

[hoops10]

Does the new scenaid use the bitrate numbers from DIF or does it generate it's own? If it does generate its own, how good are it's calculations to getting the movie to the magic 4.35 gigs mark?

[influenza]

In that case the nitrates from ccedata.txt produced by dif4u are used.

It uses the dif4u bitrates......

[Zeul]

You should run batchcce from scenaid as the ccedata.txt file is recreated by scenaid to update it to version 1.0.1.5; this adds all the cell locations so that the 'I' frame placement and therefore the cell / chapter boundaries in Scenarist are created as accurately as possible. The bitrates calculated by DIF4U are used.
So my procedure would be DIF4U -> NuMenu4u (Optional) -> Scenaid -> Batchcce -> Scenarist -> Batchifoupdate.

[Staz]

I have always used the programs in this order:

1. Dvd Decrypter
2. Doitfast4u
-Which I get to open numenu if my menu is too big.
3. Batchccews
4. Scenaid
5. Scenarist
6. Ifoupdate
7. Ifoedit
8. Dvd Decrypter to burn Ifoedit's image file.

Is this order OK or would it be better to do it differently?
Cheers :D

[jel]

@Staz

well given zuels detailed response a to why it is a really good idea to run batchcce from scenaid, then yes, the answer to your question would be:
do it differently!
:rolleyes:
..oh and if you use ImgTool Classic to create the iso image for you, the latest versions also automate DVD Decrypter to burn the image for you.

[D3s7]

You can still run BatchCCE first however, on certain movies it DOES make a difference. For example, with Insomnia, if you run BatchCCE/DoCCE using the ccedata.txt file from DoItFast4U! you will more then likely receive the .4sec scene duration errors. This particular title has very close scene locations and I-frame locations are critical.

I wanted to give people the simplest path for getting the most accurate data which is why there is ALWAYS a Scenaid-ccedata.txt file created (whether or not you launch BatchCCE from ScenAid). This takes the DoItFast4U! ccedata.txt file and using it's bitrates, adds the I-frame/cell locations for CCE (like the ccedata_new file ReAuthorist creates).. As an added bonus, when the new BatchCCE version (.6) is released (.5 has this ability but there is a bug in it) ScenAid will also flag angle assets as such. No more manually having to check these in BatchCCE :)

In my tests, with proper i-frame placement, the cells in the Authored IFO files are within 0-2 frames from the original IFO

[Staz]

I'll definitely start doing things differently!
Thanks