BatchCCEWS 0.9.1.4

[Trahald]

BBWoof has released BatchCCEWS version 0.9.1.4 available for download at www.woofsoft.com.</edit>

Basic whats new list -

It updates to ECLCCE's corrected create_new_vaf setting. so VAFFIX is no longer needed for use with batchccews

Prepares for future expansion of options

Many other changes.

*TFF/BFF issues will be addressed in the next version

[mookieguy]

Originally posted by Trahald
*TFF/BFF issues will be addressed in the next version
from www.woofsoft.com: The TFF/BFF issue corrected for all versions of CCE.

Does this mean we no longer need to check "invert field order in filenames" in DIF4U?

[BBWoof]

Originally posted by mookieguy
from www.woofsoft.com: The TFF/BFF issue corrected for all versions of CCE.

Does this mean we no longer need to check "invert field order in filenames" in DIF4U?

Well, I thought it was. But I screwed up. The next version, which I'll have out in a few days, really, really, really fixes it.

But on the good side, VafFix=1 should no longer be required for eclcce.

BBWoof

[fourtyfour]

servus...

Trahald, your link doesn´t work.

There is a dot too much :)

[Nonstop]

Mark all frames progressive doesn't seem to be working. Thanks alot for putting that feature in the new betas.

[arlsair]

Thanks for the new version.

I don`t want to hurry, just want to ask if I can help you further with "auto check angles" option for PAL ?

And it would be kind of you, if BatchCCE pick up the filenaming of DoItFast4U! for interlaced / progressive correctly.

Since now BatchCCE ignores the filenaming and uses what is defined in the registry (default is progressive IMO).
But it would be correct, if BatchCCE use progressiv ("progressive" checked, "alternate scan" unchecked") when the filename is "P-..." and interlaced ("progressive" unchecked, "alternate scan" checked") when the filename is "I-...".

[BBWoof]

Originally posted by arlsair
I don`t want to hurry, just want to ask if I can help you further with "auto check angles" option for PAL ?

I forgot to add to the other thread that the CCEData.txt you posted doesn't have any angles marked in the file name. The angles are vobid extracted. There is a vobid indicator V001, but no angle A1. That's why its not checking for them.

And it would be kind of you, if BatchCCE pick up the filenaming of DoItFast4U! for interlaced / progressive correctly.

Since now BatchCCE ignores the filenaming and uses what is defined in the registry (default is progressive IMO).
But it would be correct, if BatchCCE use progressiv ("progressive" checked, "alternate scan" unchecked") when the filename is "P-..." and interlaced ("progressive" unchecked, "alternate scan" checked") when the filename is "I-...".

Here's the problem I have with automating this part of the process. I backup NTSC disks. When I rip the assets with DIF4U (the only asset ripper as far as I'm concerned) I have material that ends up as either Interlaced (usually, but not always extras) and Progressive (Main Movie). But they're all marked as I-TFF, there isn't any P-TFF anywhere. If I'm wrong and have a setting wrong somewhere in DIF4U, please correct me. I think I want to test this. I'm not sure I have all the settings right

Also correct me if I'm wrong on this. If I have material that starts out as interlaced, but I use DVD2AVI Force Film, or decomb.dll with Telecide() and Decimate() the material I'm feeding to CCE is now Progressive and should be marked as progressive.

I don't have a way within my program to check for Progressive/Interlaced. If someone knows how I can I'd be more than willing to implement it.

BBWoof

[BBWoof]

I've added "Close All GOPs" and "GOP (N/M)" to the next release. I'm still looking for other options that people would like added. If you have suggestions, please let me know here.

BBWoof

[arlsair]

Originally posted by BBWoof
I forgot to add to the other thread that the CCEData.txt you posted doesn't have any angles marked in the file name. The angles are vobid extracted. There is a vobid indicator V001, but no angle A1. That's why its not checking for them.
That`s the way, the Auto Check Angles Option works ?
For me DoItFast4U! never named a file that way, but it seems to be a good suggestion for DoItFast4U!.

Originally posted by BBWoof
Here's the problem I have with automating this part of the process. I backup NTSC disks. When I rip the assets with DIF4U (the only asset ripper as far as I'm concerned) I have material that ends up as either Interlaced (usually, but not always extras) and Progressive (Main Movie). But they're all marked as I-TFF, there isn't any P-TFF anywhere. If I'm wrong and have a setting wrong somewhere in DIF4U, please correct me. I think I want to test this. I'm not sure I have all the settings right

Also correct me if I'm wrong on this. If I have material that starts out as interlaced, but I use DVD2AVI Force Film, or decomb.dll with Telecide() and Decimate() the material I'm feeding to CCE is now Progressive and should be marked as progressive.

I don't have a way within my program to check for Progressive/Interlaced. If someone knows how I can I'd be more than willing to implement it.

BBWoof
Hmm, but is this not the "fault" of DoItFast4U! ?
For me, it would be better, if DoItFast4U! analyse the source (I heard from influenza, that there will be also a proper analysis for PAL soon), post-process it and then give it the correct name.

I emailed Eyes`Only to have a look at this thread.

[BBWoof]

It appears I have not been using the proper settings in DIF4U or at least not paying enough attention.

If material is changed to progressive, it adds .P. to the filename.

If it's interlaced it includes the I-TFF or I-BFF.

BBWoof

[Trahald]

Originally posted by fourtyfour
servus...

Trahald, your link doesn´t work.

There is a dot too much :)

oopies.. thank you

[Eyes`Only]

BBWoof: actually the intent was to have the source's type analyzed, not the output. Which in retrospect seems wrong, as you would need the output type. If it's instead showing the output type, I'm amazed because I don't remember coding that! LOL

There's 2 things we can do to make this work with our apps:

1) I can modify my app to change the I in the filenames to a P if deinterlacing is selected.
Advantages: You don't have anything to do.
Disadvantages: Users have to have 1.4.8+ to use this feature.

2) You can detect the file type from the filename, but then if it's "I", also parse the AVS for "decomb.dll", and encode at progressive if it's found. I would not recommend testing for fps because you can use decomb and still keep NTSC at 29.97, and PAL is 25fps no matter if you deinterlace or not.
Advantages: More compatible if changes are made in DIF4U.
Disadvantages: You have stuff to do. hehe

I'm open to both, lemme know how you want to proceed, OK? And thanks for the "only asset ripper" remark above :D

[Eyes`Only]

arlsair: That feature you're requesting is a toughie, I'll see what I can do.

[arlsair]

Originally posted by Eyes`Only
2) You can detect the file type from the filename, but then if it's "I", also parse the AVS for "decomb.dll", and encode at progressive if it's found. I would not recommend testing for fps because you can use decomb and still keep NTSC at 29.97, and PAL is 25fps no matter if you deinterlace or not.
Advantages: More compatible if changes are made in DIF4U.
Disadvantages: You have stuff to do. hehe
Speaking for PAL Decomb is not the only deinterlacer. So method 1 seems to me the better way.

Originally posted by Eyes`Only
arlsair: That feature you're requesting is a toughie, I'll see what I can do.
Do you meen the thing with the angles ? Then you can probably get some code from ScenAid, as it detects the angles correctly in the script.

[D3s7]

Originally posted by arlsair
That`s the way, the Auto Check Angles Option works ?
For me DoItFast4U! never named a file that way, but it seems to be a good suggestion for DoItFast4U!.


Doitfast4u only flags Angles on PGC Demux you are correct. I'm currently working with BBWoof on a fix for VOBID and PGC demux that will address the problem of the flags not being set automatically. This will be part of the next version of ScenAid (as well as proper chapter/i-frame markers in the ccedata file for Scene alignment)

[seewen]

Originally posted by arlsair
Speaking for PAL Decomb is not the only deinterlacer. So method 1 seems to me the better way.
.

That's right. People are allowed to tweak the AVS options in DIF4U.
So if someone change Decomb for ... GreedyHMA for example, it will miss it.

So maybe DIF4U should add a comment in the AVS:
#Interlaced
or
#Normal
etc..
Depending of the method/script used.

This way user can tweak the AVS option like they want, and Batchccews will always catch the comment.

Bye

[BBWoof]

Originally posted by Eyes`Only
BBWoof: actually the intent was to have the source's type analyzed, not the output. Which in retrospect seems wrong, as you would need the output type. If it's instead showing the output type, I'm amazed because I don't remember coding that! LOL

I don't think it's exactly right. The only files that were marked with the .P. are those that are 23.976 after avisynth processing.

There's 2 things we can do to make this work with our apps:

1) I can modify my app to change the I in the filenames to a P if deinterlacing is selected.
Advantages: You don't have anything to do.
Disadvantages: Users have to have 1.4.8+ to use this feature.

2) You can detect the file type from the filename, but then if it's "I", also parse the AVS for "decomb.dll", and encode at progressive if it's found. I would not recommend testing for fps because you can use decomb and still keep NTSC at 29.97, and PAL is 25fps no matter if you deinterlace or not.
Advantages: More compatible if changes are made in DIF4U.
Disadvantages: You have stuff to do. hehe


I have to agree that arlsair that option #1 is probably the best. I can search the avs files for common deinterlace commands, but there are alot out there and will definitely miss a few.

How does the field diagnosis work for DIF4U, maybe it could be applied to BatchCCE as well.

And thanks for the "only asset ripper" remark above :D

Hey, DIF4U has saved me many hours of work :) And now ScenAid is saving me more also. I'm happy!!

BBWoof

[arlsair]

There is an issue with the cell informations:
I have here an DVD which is an InfiniFilm (you can watch the movie with some extras included). Because the extras are in the same vts as the movie there are dublicated vobids. So DoItFast4U! demuxed only the pgc including the movie and the extras. And for this pgc there are at all 174 cells. But CCE can only set 128 chapters, so the rest is left out.

I think because of this BatchCCE don`t import the cell informations. Also if I try to manually import them, they will not be stored.

I know this is not usual, but it would be great if BatchCCE can check the amount of cells and if there are to many, write a hint into the log (probably with the red error symbol, it`s more conspicuously) and import the chapter informations (better than nothing).

[BBWoof]

Originally posted by arlsair
I know this is not usual, but it would be great if BatchCCE can check the amount of cells and if there are to many, write a hint into the log (probably with the red error symbol, it`s more conspicuously) and import the chapter informations (better than nothing).

This feature was added in 0.9.1.4. Go to File -> Setting and select the check box for it.

BBWoof

[arlsair]

Originally posted by BBWoof
This feature was added in 0.9.1.4. Go to File -> Setting and select the check box for it.

BBWoof
No,no. Normally I prefer the cell-informations. Only when there are to many cell, I want an automatic fallback to the chapter-infos, because you only realise that there is an issue if you check the jobs in BatchCCE. And newbies will never realise the issue however.

[arlsair]

Originally posted by BBWoof
This feature was added in 0.9.1.4. Go to File -> Setting and select the check box for it.

BBWoof
No,no. Normally I prefer the cell-informations. Only when there are to many cell, I want an automatic fallback to the chapter-infos, because you only realise that there is an issue if you check the jobs in BatchCCE. And newbies will never realise the issue however.