Log in

View Full Version : VobBlanker 2.0.1.0 released


Pages : 1 [2] 3

ricardo.santos
4th December 2005, 15:34
It would be great to change the background just by importing and BMP/JPEG.
Is it possible to include in the next version ?


That would be a nice addition to VobBlanker.

CirTap
4th December 2005, 16:34
I second that, but never dared to ask for it :-)

jeanl
4th December 2005, 17:13
I triple that! :)
jeanl

r0lZ
5th December 2005, 10:27
This request has already be done several times, but that requires a real MPEG2 encoder. It's not a simple addition.
But I agree, it's probably the main missing feature to add (with angle support.)
Jsoto, maybe you could find an open source encoder somewhere. IMO, it's probably not too difficult to add the encoding of a still image, w/o audio.
What do you think?

blutach
5th December 2005, 10:42
Sorry to be a little fly in the ointment, but how hard is it to make a little DVD from a still image with muxman and replace the cell in VobBlanker? It really is a trivial exercise (5 minutes).

Angles is much more pressing IMHO - but we still do have Derrow's wonderful prog for that.

@jsoto - message for you at the other place.

Regards

CirTap
5th December 2005, 15:06
but that requires a real MPEG2 encoderthat's why I never really asked for this feature, but maybe it'd be possible to have it "grab" an I-frame from an existing M2V file, rathern than a VOB (there's still blutach's argument.)
Everyone here can make a M2V from a (bunch of) stills, but speaking/thinking of that: there are tools that allow to replace a cell with a M2V file available, aren't there?
@blutach: your're right; I just can't recall if VobBlanker would accept a VTS_*.vob as a replacement for a menu? (or was it PgcEdit?) -- guess I need to elaborate that step.

Have fun,
CirTap

jsoto
5th December 2005, 19:11
This request has already be done several times, but that requires a real MPEG2 encoder. It's not a simple addition.
The encoder = MuxMan.
I was trying to find code for an encoder, but finally, I decided to use MuxMan as a "external tool" via CLI. Much more easy. And (may be ) useful in the future for other more complex features.
Sorry to be a little fly in the ointment, but how hard is it to make a little DVD from a still image with muxman and replace the cell in VobBlanker? It really is a trivial exercise (5 minutes).
I bleieve it is not so trivial... You need to preserve the buttons in a menu. I did not play with MuxMan buttons capabilities, do not know if it is easy or not... In any case it will be easier to do not take care about them:
- Export the bmp (using VB or other tool)
- Modify your bmp in a graphic editor.
- Import the bmp with VobBlanker
- Hide the unused buttons with pgcEdit

jsoto

r0lZ
5th December 2005, 19:53
The encoder = MuxMan.
Good idea, indeed. And you are sure you will always have the best encoder!

So, you are working on a way to modify the background of a menu? Great!

FilipeAmadeuO
5th December 2005, 20:17
To create m2v from a JPEG/BMP file i´ve been using dvdauthorgui.
It uses the free codecs: png2yuv and mpeg2enc
They can be found in http://mjpeg.sourceforge.net
I´ve encoded a lot of times and is perfect. But it would be great to use only vobblanker.

The log created from dvdauthorgui when creating and vob is the folowing:

DVDAuthorGUI 1.005 - 8/18/2005
*creating m2v still
convert: Length and filesize do not match (C:\teste.bmp).
INFO: [png2yuv] Parsing & checking input files.
INFO: [png2yuv] Image dimensions are 720x576
INFO: [png2yuv] Movie frame rate is: 25.000000 frames/second
INFO: [png2yuv] Non-interlaced/progressive frames.
INFO: [png2yuv] Frame size: 720 x 576
INFO: [png2yuv] Now generating YUV4MPEG stream.
++ WARN: [mpeg2enc] Unknown stream tag encountered: 'C420jpeg'
INFO: [mpeg2enc] Selecting DVD output profile
INFO: [mpeg2enc] Encoding MPEG-2 video to C:\teste.m2v
INFO: [mpeg2enc] Horizontal size: 720 pel
INFO: [mpeg2enc] Vertical size: 576 pel
INFO: [mpeg2enc] Aspect ratio code: 2 = 4:3 display
INFO: [mpeg2enc] Frame rate code: 3 = 25.0 (PAL/SECAM VIDEO / converted FILM)
INFO: [mpeg2enc] Bitrate: 7500 KBit/s
INFO: [mpeg2enc] Quality factor: 8 (1=best, 31=worst)
INFO: [mpeg2enc] Field order for input: none/progressive
INFO: [mpeg2enc] Sequence unlimited length
INFO: [mpeg2enc] Search radius: 16
INFO: [mpeg2enc] GOP SIZE RANGE 9 TO 15
INFO: [mpeg2enc] Setting colour/gamma parameters to "PAL B/G"
INFO: [mpeg2enc] Progressive format frames = 0
INFO: [mpeg2enc] Buffering 39 frames
INFO: [mpeg2enc] SETTING 3DNOW and EXTENDED MMX for QUANTIZER!
INFO: [mpeg2enc] SETTING EXTENDED MMX for MOTION!
INFO: [mpeg2enc] SETTING MMX for TRANSFORM!
INFO: [mpeg2enc] SETTING EXTENDED MMX for PREDICTION!
INFO: [mpeg2enc] GOP LENGTH = 1
INFO: [mpeg2enc] Frame start 0 I 0 0
INFO: [mpeg2enc] Frame end 0 242.78 242.78 9.1 9.06
INFO: [mpeg2enc] GOP LENGTH = 0
*process complete

jsoto
6th December 2005, 15:58
Hi all,

Here you can find a beta, including the changelog

http://www.vcdhelp.com/~jsoto/temp/VobBlanker_2020b2_exe.zip

Added: Motion2still accepts external I-Frames, from a VOB or bmp. bmps are converted using MuxMan.
Added: Drag and Drop in preview pane (used in motion2still)
Added: Tools menu to select external tools and Temporal folder
Added: html links in Main Menu to homepage and guides
BugFix: Video Attributes (resolution) were not correctly mapped.
BugFix: Replacing reused cells failed
BugFix: Some minor problems in menu final size estimations


To use the external I-Frames, you have to select "File" in the I-Frame selection combobox, or simply drag and drop the file (VOB or bmp) on the preview pane.

[EDIT]: Note bmp2VOB conversions are done just when the bmp is loaded in the preview pane, and stored in the temporary folder. When processing, VobBlanker uses the already created VOB files.

jsoto

jeanl
6th December 2005, 22:05
AWESOME jsoto!
jeanl

jsoto
6th December 2005, 23:20
Thanks jeanl, but lately you are the awesome programmer.... How can you produce so much (and so fine) code?

jsoto

jeanl
6th December 2005, 23:30
jsoto, get out of here! :D
jeanl

blutach
7th December 2005, 01:10
Wow - thanks jsoto. A little suggestion if I may?

I often do the credits as stills (maybe 3 screens of 15 seconds each) by making a BMP and using muxman to make a little DVD and replacing the credits cell. Can your new routine be make to work in a VTST cell?

Regards

CirTap
7th December 2005, 02:23
that's awesome, jsoto! muchias, muchias gracias!
I can't believe you added this feature so quickly :-)

If you keep going you may need to rename VobBlanker to VobBuilder :D
.. gotta go and find a DVD now ...

Have fun,
CirTap

jsoto
7th December 2005, 02:36
Wow - thanks jsoto. A little suggestion if I may?

I often do the credits as stills (maybe 3 screens of 15 seconds each) by making a BMP and using muxman to make a little DVD and replacing the credits cell. Can your new routine be make to work in a VTST cell?

Regards

Try it. It should work. If not, let me know.
Note there is a restriction: Motion2Still in Titles domain always Keep the audio, so you can freeze the credits (or change them with other still) but the music will be there..

EDIT: Err, ATM, only one still per cell....what are you doing to have 3 screens of 15 seconds each?

jsoto

spyhawk
13th December 2005, 18:53
With the b2 version, I dragged the unmodified bmp, captured using BMP button, into the preview pane, and it spits out this error: "Unknown error running MuxMan. Please see log file c:\...\VobBlanker\STILL1_01_000_000\mxp_log.txt". Funny thing is there is no log file, only mxp.mxp. I already have the path to MuxMan configured.

But if it I select (via File in I-Frame selection drop-down list) or dragged the VOB, created by MuxMan, it accepts.

I tried the same procedure for the VTS cell -- same result. Am I missing something while others have it working?

jsoto
13th December 2005, 19:30
Seems a bug...
Could you post your Working path configuration? Are there strange chars (may be spaces) on it?

EDIT: Please also post mxp.mxp (it's a text file)

jsoto

spyhawk
13th December 2005, 19:36
Temp Working Folder
C:\DVD Installed Tools\Ifo_Vob Editing Tools\VobBlanker

Path to MuxMan
C:\DVD Installed Tools\Ifo_Vob Editing Tools\MuxMan\MuxMan.exe

Only spaces.

mxp.mxp:
Section=Content
{
Item=Segment
{
Name=Segment_1
Display Mode=P/S and LB
Resolution=720x480
Force=No
Item=Video Stream
{
Coding Mode=Mpeg-2
Standard=NTSC
CC Field 1=No
CC Field 2=No
Item=Video Play
{
File=D:\TEST\test.bmp
Size=0
Duration=Default
}
}
Item=Scene List
{
Item=Scene
{
Name=Segment_1_scn1
Scene Time=00:00:00:00
Uop=00000000
}
}
}
}

spyhawk
13th December 2005, 20:40
The only difference I see between the mxp.mxp and the project I saved in MuxMan, using the same bmp, is the Size and Display Mode (which I can change).

In mxp.mxp, Size=0
In test.mxp, Size=1036854

Regardless, both will generate the same-size VOB and accepted by VobBlanker. So does Size really play a role? I'm sure it's there for a reason.

jsoto
13th December 2005, 20:53
Only spaces.

Yep, a newbie's bug. I'll fix it.

jsoto

jsoto
17th December 2005, 18:11
Hi all,

Here you can find a new beta, including the changelog
VobBlanker_2100b1 (http://www.vcdhelp.com/~jsoto/temp/VobBlanker_2100b1_exe.zip)

I've changed the minor number of the release (now 2.1) to emphasize a significant change in the internal code, needed to cell-split feature. So, be careful with this beta, may be I've broken something.
I'll appreciate a lot some kid of regression tests (comparing with VB 2.0.2) in the case of bug reports.


Added: Split-Cell ability in Titles domain. Splits a Cell and can add a new Program and a Chapter. Multiple splits (in different cells) are allowed ion the same process session
Added: VID/CID renumbering ability. Selected as default instead of filling the VID/CID sequence with blank cells.
Added: Motion2still accepts external I-Frames, from a VOB or bmp. bmps are converted using MuxMan.
Added: Drag and Drop in preview pane (used in motion2still)
Added: Tools menu to select external tools and Temporal folder
Added: html links in Main Menu to homepage and guides
Improvement: Detection of possible orphan subs in cell split and title cut.
Improvement: Window titles in Menus/Preview and Cell dialogs show the VTS and other useful info.
Improvement: Playing a PGC in the preview automatically changes the Cell at the end of the current one
Improvement: Some improvements opening the preview window to show the previous (if any) selected frame
BugFix: Video Attributes (resolution) were not correctly mapped.
BugFix: Replacing reused cells failed
BugFix: Some minor problems in menu final size estimations


To use the external I-Frames, you have to select "File" in the I-Frame selection combobox, or simply drag and drop the file (VOB or bmp) on the preview pane.
Note bmp2VOB conversions are done just when the bmp is loaded in the preview pane, and stored in the temporary folder. When processing, VobBlanker uses the already created VOB files.


jsoto

jeanl
17th December 2005, 18:27
Yeeehaa! Thanks jsoto. I won't have much time to test :( but I'm really happy about the new cell-split feature!!! and the rest of them!
:)
jeanl

knife
17th December 2005, 19:57
Thanks,

Added: VID/CID renumbering ability. Selected as default instead of filling the VID/CID sequence with blank cells.

If I understand above point right the cells are purely deleted like they are in IFOEDIT when you strip VIDs. Can this like in IFOEDIT end up with strange chapter numbering.

//knife

mad-eddy
17th December 2005, 21:24
I can only follow @jeanl.
Distinguished.
Thanks @jsoto

jinjin_jp
18th December 2005, 00:09
I think very effective for dual-Layer burning by Imgburn, PgcEdit and ImgToolClassic, because sometimes the cell size is too big and there's no Layer.Br point(cell) to be selected.

The result was impossible to split.
Waning message is
"First part: From sector ** to **. Total=0
WARNING: No Navs found!: outputing a blank cell ".

before processing
[Ch 06] [Pg 06] [Cell 08] [V/C Id: 8/ 1] Layer Br.: time: 00:02:05.09 / 30 fps

==>after processing (1)Settings"Renumber VID/CIDs" : check ON
[Ch 06] [Pg 06] [Cell 08] [V/C Id: 8/ 1] Layer Br.: time: 00:00:00.15 / 30 fps
______________[Cell 09] [V/C Id: 8/ 2]________: time: 00:02:05.09 / 30 fps

==>after processing (2)Settings"Renumber VID/CIDs" : check OFF
[Ch 06] [Pg 06] [Cell 08] [V/C Id: 8/ 1] Layer Br.: time: 00:02:05.09 / 30 fps
______________[Cell 09] [V/C Id: 8/ 1]________: time: 00:02:05.09 / 30 fps

I tested 2 DVDs(3 cells), and the result was same.

bigotti5
18th December 2005, 00:22
WARNING: No Navs found!: outputing a blank cell

Got the same warnings first time I used it because I made a mistake

In Cell Split Mode after draging the slider in the "Go to" section you must push the mark button in the "Split point selection" section and the warnings are gone

jinjin_jp
18th December 2005, 01:44
@bigotti5
Thanks very much for your advice.
I made mistake, didn't push the mark button. Now I succeeded, when Settings"Renumber VID/CIDs" check is ON.

But when Settings"Renumber VID/CIDs" check is OFF, there is only the time of second part.
==>after processing (2)Settings"Renumber VID/CIDs" : check OFF
VTS overview
[Ch 06] [Pg 06] [Cell 08] [V/C Id: 8/ 1] Layer Br.: time: 00:01:34.22 / 30 fps
______________[Cell 09] [V/C Id: 8/ 1]________: time: 00:01:34.22 / 30 fps

VTS_C_ADT
8. Cell: VOB ID 8 [0008]
8. Cell: Cell ID 1 [01]
8. Cell: Start sector 8549 [00002165]
8. Cell: End sector 49131 [0000bfeb]
9. Cell: VOB ID 8 [0008]
9. Cell: Cell ID 1 [01]
9. Cell: Start sector 8549 [00002165]
9. Cell: End sector 49131 [0000bfeb]

Log is written like this,
VTS 01: (CB) Splitting Cell VID/CID: 08/01 --> 08/01
___First part: From sector: 8549 to 19138. Total=10589
VTS 01: (CB) Splitting Cell VID/CID: 08/01 --> 08/01
___Second part: From sector: 19138 to 49132. Total=29994

blutach
18th December 2005, 03:13
@knife

AFAIK, Renumber VCIDs does the same thing as FixVTS (www.videohelp.com/~FixVTS) does when it corrects for ARccOS.

Removing the crap cells in ARccOS can leave gaps in the VCIDs which can make some progs throw up. So this fixes them - much like what the old VIDChanger did. It's a good innovation and won't hurt chapter numbering, which is done separately.

Regards

bigotti5
18th December 2005, 03:16
But when Settings"Renumber VID/CIDs" check is OFF,

Doesn't make sense to me to check this off if you wanna split - two cells with the same number is the result

jinjin_jp
18th December 2005, 03:34
Doesn't make sense to me to check this off if you wanna split - two cells with the same number is the result
I tested and thought if added new VID/CIDs like AddChapter,
for example
1/1,2/1(split),3/1
=> 1/1,2/1,2/2,3/1 (when Check off)
=> 1/1,2/1,4/1,3/1 (when Check on)
but I think no need to check-off.
So this function(Split-Cell) is very helpful to dual-Layer burning by Imgburn, PgcEdit and ImgToolClassic.
Thanks.

jsoto
18th December 2005, 05:16
@bigotti5
Thanks very much for your advice.
I made mistake, didn't push the mark button. Now I succeeded, when
I didn't check if the mark=0 , just to allow the insertion of a blank cell... May be I can issue a warning when you close the preview window.

But when Settings"Renumber VID/CIDs" check is OFF, there is only the time of second part.
==>after processing (2)Settings"Renumber VID/CIDs" : check OFF
VTS overview
[Ch 06] [Pg 06] [Cell 08] [V/C Id: 8/ 1] Layer Br.: time: 00:01:34.22 / 30 fps
______________[Cell 09] [V/C Id: 8/ 1]________: time: 00:01:34.22 / 30 fps

Mmm, seems a bug introduced in the final code cleanup. I'll look into it

jsoto

blutach
18th December 2005, 05:29
I just did a little cell split - renumber VID/CID cells to be consequtive was ON.

I split 30/1 and it made 30/1 and 30/2 (with cell flag 8). Is this not OK? Only problem is finding a splitting point where you don't have a broken GOP. In fact, there was a broken GOP, so do we need a cell flag of 10?

EDIT: Have now done it with renumbering OFF and have two cells with same VCID (where have I seen that before jsoto?? :D) - cell flag 10 is the second cell. Although the cell numbering is legal, transcoding progs may choke on it, as we know.

Regards

jsoto
18th December 2005, 12:42
I split 30/1 and it made 30/1 and 30/2 (with cell flag 8). Is this not OK? Only problem is finding a splitting point where you don't have a broken GOP. In fact, there was a broken GOP, so do we need a cell flag of 10?
Well, in this case, VB sets the appropiate GOP flag to mark it as Broken one. I believe this should be enough to don't show pixellations when accesing directly to the cell. And, not sure, but because the cell joint is seamless linked (it is, because it cames from a single cell), I'm assuming a normal playback w/o any problem when playing in a continuous way. SW players do not show any problem (even w/o marking the GOP as broken) but I did not check this assumptions in my settop...
I really think the cell flag should be 8. If not, the player should finish the audio and video playback (audio is usually delayed vs video) before starting the new cell. This has to produce a/v synch problems.

Have now done it with renumbering OFF and have two cells with same VCID (where have I seen that before jsoto?? :D) - cell flag 10 is the second cell. Although the cell numbering is legal, transcoding progs may choke on it, as we know.
Where? don't remember.... :D) .
It's a bug. I'll fix it.

jsoto
18th December 2005, 13:44
Hi all
- Found a bug in de-ILV process which can produce non-working VOBs. Internal VOB pointers not always are fixed in the de-ILV cells.

- To avoid the problem check "Fix always VOB int. pointers" in the main dialog.

I hope this is the cause of all reports of a non working VOB in Polar express...

NOTE: This bug has been introduced in VB 2.0, and it is in all 2.X.X.X versions.

jsoto

jsoto
18th December 2005, 15:25
Hi,

New beta:
VobBlanker_2100b2 (http://www.vcdhelp.com/~jsoto/temp/VobBlanker_2100b2_exe.zip)

Changelog versus beta 1:

Improvement: Unsynchronized packs are now skipped in Keep, cut and split modes. A Warning is issued, but process is not aborted.
BugFix: Fixing VOB pointers when de-ILVing cells not always was done.
BugFix: 2nd part of cell split bad numbered if VCID renumbering was not checked.

jinjin_jp
18th December 2005, 16:04
BugFix: 2nd part of cell split bad numered if VCID renumbering was not checked.
I confirmed to be fixed. Thanks.

blutach
18th December 2005, 21:34
Thanks jsoto!

Regards

dirio49
20th December 2005, 00:57
Question

if you i for example want to cut the last cell that contains the credits?

what I did before is used the cut function, but now i just spit the cell were i want and then use the psl plugin to remove the cell,
after that i run it though fixvts.

the question i have is there anything that can go wrong with this?
because sometimes with cut function it failed to cut the cell.


P.S.
thanks jsoto for the cell splitting function

jsoto
20th December 2005, 01:36
if you i for example want to cut the last cell that contains the credits?
what I did before is used the cut function, but now i just spit the cell were i want and then use the psl plugin to remove the cell,
after that i run it though fixvts. Seem complex, but should work.....

because sometimes with cut function it failed to cut the cell.
Really?, please report the bugs. (FYI split-cell reuse part of the title-cut code)

jsoto

dirio49
20th December 2005, 02:22
Thanks for the fast reply

I haven't tried in some time.

but i remember that what i used to do
i tried to cut between the marks, in the same cell.
and i will fail saying

nav pack out of vob.

something like them hope it helps.


P.S.
I will try to reproduce if i can and post a log.

jsoto
23rd December 2005, 02:02
Hi,

New beta, two critical bugs fixed:
VobBlanker_2100b4 (http://www.vcdhelp.com/~jsoto/temp/VobBlanker_2100b4_exe.zip)

Changelog versus beta 2:

Added: Registry key with the Version
Improvement: Detection of cells in PGCs not listed in C_ADT tables
Improvement: Detection of mismatches between C_ADT and PGC tables.
BugFix: Crash (or unknown results) when adjusting sectors (last step) in a skipped VTS
BugFix: A reused cell in the same PGC (consecutive) was being confussed with a splitted one and produced a corrupted IFO. (i.e., blanked VTSs with pgcEdit) (thanks for the report, dirio49)



jsoto

dirio49
23rd December 2005, 05:17
thanks jsoto ;)

P.S.
I confirm it works

naiden_99
23rd December 2005, 18:57
@jsoto

I'm having problems with the last two betas of VobBlanker.

When I am previewing the cells of a title to see whats in the cell then close the preview window I cannot see the cell list anymore (the lower part of the cell list window). This does not happen with version 2010.

I hope you have time to check this out.

Anyway, it's time for me to thank you for a VERY useful program, and to wish you a merry Christmas in the company of your loved ones.

jsoto
23rd December 2005, 19:16
@jsoto
When I am previewing the cells of a title to see whats in the cell then close the preview window I cannot see the cell list anymore (the lower part of the cell list window). This does not happen with version 2010.
The cell list? Are you able to close the cell list? And, are you able to open it again?
could you post an image to see what are you exactly saying? Not sure if I'm understanding,...

Anyway, it's time for me to thank you for a VERY useful program, and to wish you a merry Christmas in the company of your loved ones. You're welcome

jsoto

naiden_99
23rd December 2005, 19:37
@jsoto

May I PM you? Cause I speak Spanish better than English and it's easier for me to send you the image as attachments than to post it here.

Thanks for your fast response.

jsoto
23rd December 2005, 21:18
May I PM you? Cause I speak Spanish better than English and it's easier for me to send you the image as attachments than to post it here.
OK, PM or email me ( jesus_soto_viso at terra punto es)

naiden_99
23rd December 2005, 23:22
@jsoto

I've sent you an e-mail with an attached pic and the info you wanted

Saludos

naiden_99
24th December 2005, 00:53
@jsoto

I've received your e-mail and posted a reply with the info you asked

Thanks

jsoto
24th December 2005, 01:30
Seems the problem is mfc42.dll version...

jsoto