Log in

View Full Version : VobBlanker 1.6.0.6 is out


Pages : [1] 2 3 4 5 6

jsoto
8th December 2004, 03:04
I'm starting a new thread because the old one is too long...

Vers 1.6.0.1 (08-12-2004)
Added: New integrated preview using jeanl DVDPreview class: Resizeable, with DAR management and with “real” playback speed
Change: All internal arrays are now allocated in run time, so maximums have been changed to the official DVD ones: MaxPGCs=32768 and MaxMenuPGCs=32768. Also the maximum of IFO size is now 10 MB.
BugFix: Cell still time was not clear when blanking.

Special thanks to jeanl for his support and DVDpreview class.

jsoto
EDIT: Download problems solved.
Versions <= 1.5 discussion thread:
http://forum.doom9.org/showthread.php?s=&threadid=73145
Versions = 2.0 discussion thread:
http://forum.doom9.org/showthread.php?s=&threadid=92481

Links to announcement posts
VobBlanker 1.6.0.2 (http://forum.doom9.org/showthread.php?s=&postid=580695#post580695)
VobBlanker 1.6.0.3 (http://forum.doom9.org/showthread.php?s=&postid=583163#post583163)
VobBlanker 1.6.0.4 (http://forum.doom9.org/showthread.php?s=&postid=603948#post603948)
VobBlanker 1.6.0.5 (http://forum.doom9.org/showthread.php?s=&postid=615692#post615692)
VobBlanker 1.6.0.6 (http://forum.doom9.org/showthread.php?s=&postid=627264#post627264)

mrslacker
8th December 2004, 03:58
Congrats jsoto on overcoming the dynamic allocation hurdle. jsoto & jeanl: I hope to learn to program as well as you guys! Can't wait to try it out.

DMagic1
8th December 2004, 05:25
Great work.

G_
8th December 2004, 18:46
Really good job guys! Many thx again :)

sweetness
8th December 2004, 21:30
great job jsoto and jeanl too.
wow, last year we didn't have all these tools to work with. i was always looking at 2cool guides(that's not a bad thing :) ) on how to do things.
well, the people in this forum are the best.

Grave
9th December 2004, 02:39
did i miss explanation for this:
is there a reason why it does rearrange vobids so they are no longer sorted properly? (in menu vts. eg no longer consecutive 1-2-3-4-5-6 but unsorted 1-3-5-4-6-2)
it's a real pain in the ass finding certain vobids in vobs with tens of vobids :(

jsoto
9th December 2004, 19:59
Seems nobody likes VobBlanker reordering...

Well, no special reason, this is because how VobBlanker works and because I never thought it can be a problem when I started the development. (In fact I've never seen a problem in a settop due this).

As I said in other threads, changing this now is not easy, I've to rewrite a lot of code (with the risk of introducing bugs, lately I'm a little heavy..).

May be I can address it in a future (I can feel the pressure pushing me... :) ), but, by now, it is not in my TODO.

If you don't like your VOBids unordered or may be with gaps, you always can use VIDChanger as a post process. I've never use it, and I've backed up a lot of DVDs with VobBlanker.

jsoto

CoNS
9th December 2004, 20:14
Originally posted by jsoto
Seems nobody likes VobBlanker reordering...:p Well, cheer up, jsoto, it's just that the program is so great in every other respect... But I can understand that you don't want to redo the whole code as long as noone has reported the reordering issue to be a real problem when playing the disc.

blutach
9th December 2004, 21:32
If you have a look at my original posting in the PgcEdit thread (http://forum.doom9.org/showthread.php?s=&postid=576996#post576996), I did say the disk plays OK in a set top!

I was just reporting something strange that PgcEdit couldn't parse.

Regards to all

sweetness
9th December 2004, 21:55
went i preview a VMGM menu VobBlanker crashes. in the VTSM the preview is ok.

jsoto
10th December 2004, 00:25
@CoNS, blutach
Don't worry, I can live with it :p Currently I'm seeing it as a challenge, so who knows.... :)

@sweetness
Weird!. Yes, you are right. But it is not a bug. In fact, I needed to fix three before be able to preview. They are old (wrong, but not really used) references to the title domain memory (which do not exist any more in Video Manager due the new memory allocation system). May be there are more...The good thing is that you will experience a crash if I'm accessing to a non allocated memory.

BTW, There is other bug (potential crash) in memory deallocation (done when you load the second time a VIDEO_TS.IFO, when loading a project or when exiting the program)

I'm going to release a fix on these issues soon.

jsoto

blutach
10th December 2004, 00:27
Originally posted by jsoto
@CoNS, blutach
Don't worry, I can live with it :p Currently I'm seeing it as a challenge, so who knows.... :) The way I understand you program works, by going through in PGC order, I guess it will end up with VOBIDs out of order, if the VOBIDs aren't in a nice sequence.

So long as it plays, I don't give a rat's.... :):):)

jeanl
10th December 2004, 09:04
Jsoto,
Here's a stupid little request: I love the drag/drop feature in vobblanker, but you know how it is, given them a finger, they'll want the arm!
Could you possibly make it so we can drag/drop any file (not just VIDEO_TS.IFO)? Or even the directory itself?
Shrink does not have drag/drop but it lets you open a DVD by selecting the entire folder (even the folder above the VIDEO_TS subfolder!). PgcEdit is the same, very very convenient.
I don't think that would be very hard to add...

But maybe I'm too damn lazy!
Jeanl

jsoto
10th December 2004, 19:18
Yes, it can be done.
Currently I'm accepting "any" file as project file, except VIDEO_TS.IFO which is recognized as the DVD index. I can change and accept a folder or any VOB/BUP/IFO file and try to find the VIDEO_TS.IFO in the same folder. Any other extension (different *.VOB , *,BUP or *,IFO) will be managed as a "project file". Is it OK?

jsoto

jeanl
10th December 2004, 19:22
Originally posted by jsoto
Yes, it can be done.
Currently I'm accepting "any" file as project file, except VIDEO_TS.IFO which is recognized as the DVD index. I can change and accept a folder or any VOB/BUP/IFO file and try to find the VIDEO_TS.IFO in the same folder. Any other extension (different *.VOB , *,BUP or *,IFO) will be managed as a "project file". Is it OK?

jsoto
oh, OK I get it, I forgot you had your own "project" file type. I see. What you suggest sounds like a good solution... I hope it isn't too much work!
Jeanl

sweetness
10th December 2004, 19:53
hi,jsoto
can you explain to me what this warning is? and is it a big deal?

WARNING: nuPGCs mismatch between VTS_TMAPTI and VTS_PGCI 0
WARNING: nuPGCs mismatch between VTS_TMAPTI and VTS_PGCI 1
thanks

jsoto
10th December 2004, 21:09
This warning means a mismatch between the number of Program Chains in the VTS stored in the table VTS_PGCI and the one stored in the table VTS_TMAPTI . AFAIK it should be the same.

VobBlanker quits TMAPTI processing and keep this table as it was.

So, TMAPTI table is wrong and the consecuence is that the player will not be able to do the "Goto" function, i.e. powerDVD you will not allow you to drag the navigation slider to advance/rewind in the title.

But (unless there was a VobBlanker bug) the original DVD should have the same problem. It is not a big deal in the case of a short PGC and obviously you can forget it if you are blanking the PGC.

BTW, because how VobBlanker works (PGC by PGC) the warning is outputted once per PGC in the VTS. In your case, seems you have two PGCs in the VTS.

jsoto

PS: Mmmm, I've to review what happens if the original TMAPTI table does not exist....

sweetness
10th December 2004, 21:34
it might not be a bug. i had some trouble ripping that dvd.
thanks.

jsoto
10th December 2004, 22:03
PS: Mmmm, I've to review what happens if the original TMAPTI table does not exist.... It's OK, the code does not process the table in this case, but without any warning.

jsoto

jsoto
13th December 2004, 02:06
Vers 1.6.0.2 (13-12-2004)
Added: Drag & drop of folder or any VOB/IFO/BUP file
Added: Option to process files in input folder, (using a backup subfolder)
BugFix: Bug when deallocating memory
BugFix: Crash due unused references to title part of Video Manager
BugFix: PGC still time (0xa3) was not cleared when blanking PGCs
BugFix: Replaced/Blanked Cell and the following one is now marked as system clock discontinuity.
BugFix: Now marks as system clock discontinuity the appropiate cells when cutting PGCs
BugFix: A couple of bugs in slider management in preview, but I'm going to rewrite this code...


I'm releasing this version mainly because the memory crashes fixes, but I did not have time to test the other fixes/additions in deep, so be careful...

jsoto

jeanl
13th December 2004, 05:54
thanks a bunch jsoto!!
Jeanl

CoNS
13th December 2004, 14:05
Nice! :)

I can see that you replaced the option "Correct VOBs DSI pointers" with the new option for processing in input folder. I assume the VOBs DSI pointers are then corrected automatically when needed so that the difference is that you just can't uncheck the option anymore?

How does the program work when the new option with processing in input folder is checked? Are the files to be processed (not marked "Skip") copied to the backup folder, then processed in the input folder ending with a "Get VTS sectors" so that the output works right away. Or should the VTS sectors in the output be corrected using IfoEdit or PgcEdit?

jsoto
13th December 2004, 14:23
Originally posted by CoNS
Nice! :)
I can see that you replaced the option "Correct VOBs DSI pointers" with the new option for processing in input folder. I assume the VOBs DSI pointers are then corrected automatically when needed so that the difference is that you just can't uncheck the option anymore?

Yes. You still can uncheck it using the Load Project feature, but I believe it has no sense to be unchecked.

Originally posted by CoNS
How does the program work when the new option with processing in input folder is checked? Are the files to be processed (not marked "Skip") copied to the backup folder, then processed in the input folder ending with a "Get VTS sectors" so that the output works right away. Or should the VTS sectors in the output be corrected using IfoEdit or PgcEdit?
I need to update the help, sorry. This is how it works:
A) Create a VobBlanker_backup folder under Input folder
B) Use the created folder as output folder
C) Process "normally" the files (The skipped VTSs are not processed)
D) Move the processed (new) files up and the originals down to the subfolder (To do this I use an intermediate name, called file.new)
E) Get VTS sectors in the Input folder

So, the output, with sectors corrected, will be in the input folder.

I've noticed the sectors adjustments can fail if you are not processing the menus or the titles (unchecking one of the appropiate boxes). I have to fix this.

jsoto

CoNS
13th December 2004, 18:05
Originally posted by jsoto
I've noticed the sectors adjustments can fail if you are not processing the menus or the titles (unchecking one of the appropiate boxes). I have to fix this.Sounds like a serious bug. Looking forward to the bugfix.

Otherwise, the new function with processing in input folder sounds really great. It'll come in handy when only a few changes are made. What happens if the option is checked and the whole disc is processed (no material marked as "skip")? Will you then get a complete working backup of the disc (the original disc) in the backup folder?

jsoto
13th December 2004, 19:15
Originally posted by CoNS
Sounds like a serious bug. Looking forward to the bugfix.Not difficult to workaround... Simply load the final DVD in IFOEdit/PGCEdit and do "Get VTS sectors". It will take very few timeOriginally posted by CoNS
Otherwise, the new function with processing in input folder sounds really great. It'll come in handy when only a few changes are made. Yes, this is the reason for it.
Originally posted by CoNS
What happens if the option is checked and the whole disc is processed (no material marked as "skip")? Will you then get a complete working backup of the disc (the original disc) in the backup folder? Yes. (I hope)
jsoto.

CoNS
13th December 2004, 19:57
Are you going to implement a "roll back" feature, like in PgcEdit (restore the files in the backup folder)?

jsoto
14th December 2004, 01:41
No sure...
It was my original idea, but, currently I'm not sure it is a good idea. I have to be able to recover from a different VobBlanker instance, let's say, you find something wrong during the test of the DVD and you have closed VobBlanker, so you open a new one. In this case I need to know which files have to be recovered, may be there are more files (manually added, i.e.) than the ones created by VobBlanker.
And, recovering manually is very easy, so I think I'm not going to do anything in this point.

jsoto

jeanl
14th December 2004, 18:55
Guys

I've got an idea I'd like to toss up in the air, see where it falls.
Do you think it would be a good idea to ask jsoto to implement a function in Vobblanker to do a "movie-only backup with menus"?

It could work like this:
- The user selects the title to keep (presumably the movie!).
- Vobblanker blanks everything else including PGCs in VTSMs and VMGM if there are no buttons. I'm guessing vobblanker would keep everything in the titleset of the movie title, just to be sure (in case the movie would be multi-PGC in the same titleset).

I know there are cases where this wouldn't work (for example, movies that span 2 titlesets - but I've yet to see that).
I'm asking because I've noticed a lot of people who would like to use DVD Shrink's re-author mode, but don't like the fact that the menus are not there anymore. This would be a one-click solution for that problem (and it could be made really fast: if you're blanking entire titlesets, vobblanker is really fast).

What do you guys think?
Jeanl

CoNS
14th December 2004, 19:11
@jsoto: You're right, it's not a big problem to restore the files manually. But it would be nice and convenient to have a restore function like in PgcEdit. PgcEdit must have the same potential problems as you describe with modified files etc.?

When copying back the files manually from the VobBlanker_backup folder, do I have to perform a Get VTS Sectors in IfoEdit/PgcEdit?

I did some testing of the new "Process in Input Folder" option today, but it didn't work for me. My disc has two VTS, and I tried to blank the whole second VTS, which contains one title (TTN 5), whereas the first VTS contains TTN 1-4. When processing the disc with VobBlanker I had marked the first VTS with "Skip", but I didn't uncheck the "Process Titles" or "Process Menus" options. The program ended with "Error moving files". :confused:

A whole other thing: I have another disc with VTS 1 containing the main movie (4 gb) in VTST 1. I want to do some blanking in the menu of this VTS. As I'm not processing the VTST, only the VTSM, I'd like to be able to skip the VTST and only process the menu in order to save the time of processing the 4 gb. Can this be done? In the main Window of VobBlanker, if I select the VTS in question and hit "skip" and then mark a PGC for blanking in the menu of this VTS, it's not processed (due to the "skip" mark). Maybe a view of the VTST and VTSM in the same list (like in PgcEdit), where a VTSM can be marked for blanking without reference to the VTST, would be better?

2COOL
14th December 2004, 19:31
Originally posted by jeanl
I'm guessing vobblanker would keep everything in the titleset of the movie title, just to be sure (in case the movie would be multi-PGC in the same titleset). Keep in mind that menus not only reside in VMG and VTSs but they can also be BOVs.

jeanl
14th December 2004, 19:34
Originally posted by 2COOL
Keep in mind that menus not only reside in VMG and VTSs but they can also be BOVs.
yes, you're right, but I don't think it would be worth checking for that in general because that's pretty rare (but I agree, I've seen it!). Checking for the presence of buttons in large VOB files can be extremely time-consuming (we did a few tests with r0lZ) so I'm not sure it's worth the effort in general.
The one-click solution wouldn't work for BOV, but I think that would be OK...
Jeanl

sweetness
14th December 2004, 20:42
Hi jsoto, more requests.

Can you make it so that in the TitleSet window you can select more that one VTS by using Shift+click or Ctrl+click. It just makes it easier to blank out allot of title sets. You would only have to right click once to blank.

Just thought of another one. When you blank out the whole VTS maybe you can change the color of the font. It just makes it easier to see which ones I blanked instead of highlight each VTS and looking at the PGCs area to see the action.

I’m working with a DVD that has 20 VTS that’s way.

Thanks :)

jsoto
14th December 2004, 22:38
@jeanl
(and it could be made really fast: if you're blanking entire titlesets, vobblanker is really fast).Keep in mind many, many times the main movie is with a short PGC (intro) in the same VTS.

May be I can add an option in the menu to blank everything but main movie (assuming it is the longest PGC)

@CoNS PgcEdit must have the same potential problems as you describe with modified files etc.? It is not the same case, PGCEdit backups "all" IFOs.

When copying back the files manually from the VobBlanker_backup folder, do I have to perform a Get VTS Sectors in IfoEdit/PgcEdit? I believe not. But it is always a good practice. Think that even with a just ripped DVD in FILE mode you need to do it.

"Error moving files". It worked for me, but I didn't do many tests... I'll look into it. In any case in the log window you should be able to see which is the file in problem (may be you have a original file read only?, I didn't test this case)

As I'm not processing the VTST, only the VTSM, I'd like to be able to skip the VTST and only process the menu Select Process your VTS and skip the others and uncheck process titles box.
Currently (but I'm not going to change this, eh!) the "Process titles" and "Process Menus" apply to all the VTSs to be processed.

@sweetness
Can you make it so that in the TitleSet window you can select more that one VTS by using Shift+click or Ctrl+click. It just makes it easier to blank out allot of title sets. You would only have to right click once to blank. I was wondering when someone is going to ask for this. Yes, it's in my TODO.

Just thought of another one. When you blank out the whole VTS maybe you can change the color of the font. It just makes it easier to see which ones I blanked instead of highlight each VTS and looking at the PGCs area to see the action. Well, may be. What I can do is add a new VTS action (Process, Skip and Blank, where Blank means process blanking all)

jsoto

CoNS
14th December 2004, 23:01
Originally posted by jsoto
It worked for me, but I didn't do many tests... I'll look into it. In any case in the log window you should be able to see which is the file in problem (may be you have a original file read only?, I didn't test this case)I just checked... Nope, the original files aren't read only.

M7S
14th December 2004, 23:42
This is maybe a stupid question but is there anyway to compile vobblanker in linux? What has to be done to be able to do this? Or would it request a total rewrite of the program?

Regards,
M7S

jeanl
15th December 2004, 00:43
Originally posted by M7S
This is maybe a stupid question but is there anyway to compile vobblanker in linux? What has to be done to be able to do this? Or would it request a total rewrite of the program?
Regards,
M7S
From what I've seen of jsoto's code, it would not be easy to port that to linux, as a lot of the code is merged with windows specific calls (using MFC)... I'm guessing it might take someone a month to do that (working full time on it)...
Jeanl

M7S
15th December 2004, 06:27
I was afraid of that. There are no program in Linux that do something similar to what vobblanker do either, right?

CoNS
15th December 2004, 08:14
There's a version of PgcEdit (http://forum.doom9.org/showthread.php?s=&threadid=85329) for Linux. You can get it here (http://home.tiscali.be/debie.roland/pgcedit/index.html).

With PgcEdit you can blank out whole titlesets only (i.e. replacing the original vob with a 10 KB vob file with one blank frame). It doesn't allow you to blank on PGC or cell level. However, if you're not after saving space on your disc and just want to skip the playback of a PGC or a cell, you can do this with PgcEdit, too, so that the original size of the vob is kept.

Like VobBlanker, PgcEdit has full preview features.

jeanl
15th December 2004, 08:43
Originally posted by CoNS
There's a version of PgcEdit (http://forum.doom9.org/showthread.php?s=&threadid=85329) for Linux. You can get it here (http://home.tiscali.be/debie.roland/pgcedit/index.html).


Like VobBlanker, PgcEdit has full preview features.
not in unix though... :(
And like with vobblanker, adding unix preview would be some work (because the original DVD2AVI code used in the preview is heavily windowsized)...
Jeanl

candsh
15th December 2004, 10:26
I am a complete novice in the use of this program and the only thing I really know is that it works! I use it to remove extras and previews before processing with DVD Rebuilder and have never had a failure with any of the backups I have made. One thing I am curious about is, would it be possible when "blanking" a feature that is keyed to the main menu that the button could be automatically removed or deactivated on the menu without having to go into another program to remove it. I have gotten so used to ripping in ISO mode and mounting with Daemon tools, which seems to work just fine with VOB Blanker, but is it better to do this in file mode? Rebuilder has never rejected the folder created and accepts the folder just the way it is regardless of what I have named it and breezes right through it. GREAT PROGRAM........

CoNS
15th December 2004, 14:53
jsoto, did you have time to do some more testing of the new option with processing in input folder?

Do you get the same error as I described?

jsoto
15th December 2004, 15:14
I didn't have time to do many tests, but you should have something like this at the end of your log:

VIDEO_TS: Opening IFO
VIDEO_TS: Processing VOB (Menus)
VIDEO_TS: Keeping Menu LU 01, PGC 02
VIDEO_TS: Keeping Menu LU 01, PGC 06
VIDEO_TS: Processing IFO (Menu)
Looping into Menu PGCs and cells
Building VTSM_C_ADT table
Filling VTSM_VOBU_ADMAP table
Moving File: VTS_02_0.IFO
Moving File: VTS_02_0.BUP
Moving File: VTS_02_0.VOB
Moving File: VTS_02_1.VOB
Moving File: VTS_03_0.IFO
Moving File: VTS_03_0.BUP
Moving File: VTS_03_0.VOB
Moving File: VTS_03_1.VOB
Moving File: VTS_04_0.IFO
Moving File: VTS_04_0.BUP
Moving File: VTS_04_0.VOB
Moving File: VTS_04_1.VOB
Moving File: VIDEO_TS.VOB
VIDEO_TS: Processing IFO (Ending and writting)
Moving File: VIDEO_TS.IFO
Moving File: VIDEO_TS.BUP

PostCommands changed into Precommands in 4 PGCs of a total of 9

Finished. No Errors, 0 Warnings


Could you post this part? Is VobBlanker able to move any file?

jsoto

M7S
15th December 2004, 15:19
Originally posted by CoNS
There's a version of PgcEdit (http://forum.doom9.org/showthread.php?s=&threadid=85329) for Linux. You can get it here (http://home.tiscali.be/debie.roland/pgcedit/index.html).

With PgcEdit you can blank out whole titlesets only (i.e. replacing the original vob with a 10 KB vob file with one blank frame). It doesn't allow you to blank on PGC or cell level. However, if you're not after saving space on your disc and just want to skip the playback of a PGC or a cell, you can do this with PgcEdit, too, so that the original size of the vob is kept.

Like VobBlanker, PgcEdit has full preview features.

Yes, I know about PgcEdit. It's blanking at pgc level I'm after, for space saving. Is it doable in linux somehow?

sweetness
15th December 2004, 17:15
hi M7S,
you might have to do it the old fashion way by using 2COOL's Cheat Sheets & Guides List (http://forum.doom9.org/showthread.php?s=&threadid=43142).

CoNS
15th December 2004, 17:55
@ jsoto: I tried one more time with the same result: "Error moving files", even though all the files seem to be copied/moved as they should. Here's the log:
VTS 02: Opening IFO
VTS 02: Processing VOB (Menus)
VTS 02: Keeping Menu LU 01, PGC 01
VTS 02: Processing IFO (Menu)
Looping into Menu PGCs and cells
Building VTSM_C_ADT table
Filling VTSM_VOBU_ADMAP table
VTS 02: Processing VOB (Titles)
VTS 02: Blanking PGC 01
VTS 02: Processing IFO (Titles)
Looping into Title PGCs and cells
Changing Post into precommands: VTS 2, PGC 1
Found a Conditional Break. Changed into Goto command
Building VTS_C_ADT table
Processing TMPATI table
Filling VTS_VOBU_ADMAP table
VTS 02: Processing IFO (Ending and writting)

VIDEO_TS: Opening IFO
VIDEO_TS: Processing VOB (Menus)
VIDEO_TS: Processing IFO (Menu)
Looping into Menu PGCs and cells
VTSM_C_ADT table did not exist
VTSM_VOBU_ADMAP table did not exist
Moving File: VTS_02_0.IFO
Moving File: VTS_02_0.BUP
Moving File: VTS_02_0.VOB
Moving File: VTS_02_1.VOB
Moving File: VIDEO_TS.VOB

jsoto
15th December 2004, 18:02
Nope, the last files should be VIDEO_TS.IFO and BUP, just after VIDEO_TS.VOB


Moving File: VIDEO_TS.VOB
VIDEO_TS: Processing IFO (Ending and writting)
Moving File: VIDEO_TS.IFO
Moving File: VIDEO_TS.BUP

Seems we found it: you are skipping VIDEO_TS.VOB files, aren't you?.

jsoto

2COOL
15th December 2004, 19:07
Originally posted by sweetness
the old fashion way:p

CoNS
15th December 2004, 19:23
Originally posted by jsoto
Nope, the last files should be VIDEO_TS.IFO and BUP, just after VIDEO_TS.VOBOf course, you're right.

Originally posted by jsoto
Seems we found it: you are skipping VIDEO_TS.VOB files, aren't you?.No, it's marked as "process". But now I think I've found it: I don't have a VIDEO_TS.VOB file in this discset!!! The program tries to move a file that doesn't exist... ;)

M7S
15th December 2004, 19:23
Originally posted by sweetness
hi M7S,
you might have to do it the old fashion way by using 2COOL's Cheat Sheets & Guides List (http://forum.doom9.org/showthread.php?s=&threadid=43142).
Hi. I can't see how 2COOL's guides can help me. The guides uses either IFOEdit or PGCEdit, at least those I've read. As Cons said, PGCEdit can't blank on PGC or cell level and IFOEdit is afaik only for Windows (and probably won't allow me to blank out vobs on PGC or cell level either).

It's possible that I missed the guide I should have read, if so, please point it out to me.

Regards,
M7S

jsoto
15th December 2004, 22:10
@CoNS
Well, seems I've to fix two cases (skipping VIDEO_TS and when VIDEO_TS.VOB does not exist). May be this weekend...

In the meantime, be careful when processing in the input folder.

BTW, probably, adding a VIDEO_TS.VOB of 0 bytes the program works.

jsoto