ISO image with DVD Rebuilder... [Archive]

DD51

24th May 2005, 19:31

First of all jdobbs Thank you for implementing the ISO image builder. Much appreciated!

Now for my problem...I just tried my first backup to do in an ISO format.

DVD-RB 0.93.1 Pro
I have the two files needed (mkisofs.exe and cywin1.dll)
As a matter of fact i did exactly what is stated here:

If you are doing a manual install,
the two files needed (mkisofs.exe and cywin1.dll)
are included in the rebuilder zip file. After
the files exist, the next time you run DVD-RB
the "Output to ISO Image File" option in the
"Mode" menu will be enabled. You can also select
a VOLUME NAME and FILE NAME for the ISO image or
choose to automatically delete the files after
writing (to save space). These options are
selected using the "Select ISO Output Options"
selection -- also under the MODE menu.

Here's what it says:
- Updated IFO: VTS_01_0.IFO
Correcting VTS Sectors...
- Building ISO Image...
- ISO Image successfully created.<---- I can't find it!
[14:22:23] Phase III, REBUILD completed in 15 minutes.

Done.
[14:22:23] PREPARE/ENCODE/REBUILD completed in 81 min.

I cannot find the ISO image anywhere.
It only did an audio and video ts folder
What did I do wrong?[/COLOR]

Fiebre

24th May 2005, 19:50

Same thing happened to me actually. I had it output the iso to the desktop but there was nothing there. Log said that it was created succesfully. :confused:

berndy2001

24th May 2005, 20:58

the output should be in the working folder?

another (small) problem: i just tried to make an "iso output", but i hadn't enough space on my harddisk.
the progressbar stopped in the middle, rebuilder said "done".

is it possible, to show the logfile of mkisofs, like imgtoolclassic does?

pilar

24th May 2005, 21:50

Small question here - is 32k padding used when mkisofs is running? (option -pad is on by default). If yes, is it considered when correcting VTS sectors by DVD-RB?

LIGHTNING UK!

24th May 2005, 22:21

lol, I was just thinking the exact same thing pilar!

Also, from what I've seen within ImgTool Classic, mkisofs doesn't provide any method for padding the filesystem out so that a double layer image can have a proper layer break on a cell boundary.

jdobbs

25th May 2005, 12:54

Originally posted by pilar
Small question here - is 32k padding used when mkisofs is running? (option -pad is on by default). If yes, is it considered when correcting VTS sectors by DVD-RB? No, I haven't changed the default. Should I? Here is the command line used:

mkisofs -dvd-video -V SELECTED_LABEL -o OUTPUT_PATH INPUT_PATH

It worked fine on my testing... but I'm no expert on MKISOFS, so if you have suggestions, I'm listening.

Originally posted by LIGHTNING UK!
Also, from what I've seen within ImgTool Classic, mkisofs doesn't provide any method for padding the filesystem out so that a double layer image can have a proper layer break on a cell boundary.While it's possible, I don't think there are many people using DVD-RB today for dual-layer burning. If I were backing up a dual layer source to a dual layer output I could just use DVD Decrypter alone.

jdobbs

25th May 2005, 13:19

@DD51

Could you try redoing the rebuild and watch to see if it is actually executing? It should take somewhere on the order of 5 minutes to write the ISO image. I need to see what's happening here.

jdobbs

25th May 2005, 13:24

Originally posted by pilar
Small question here - is 32k padding used when mkisofs is running? (option -pad is on by default). If yes, is it considered when correcting VTS sectors by DVD-RB? I just read the MAN for the -pad command -- and I don't understand the impact on correcting VTS sectors (at least on a single layer disc)? It pads at the end of the disc, and the IFOs are all relative to the beginning.

pilar

25th May 2005, 14:15

Originally posted by jdobbs
I just read the MAN for the -pad command -- and I don't understand the impact on correcting VTS sectors (at least on a single layer disc)? It pads at the end of the disc, and the IFOs are all relative to the beginning.

You should use either -no-pad option and leave DVD-RB as it is, or change something in correcting VTS sectors method. I'm not an expert, but to my understanding -pad option makes sure there is at least 32k space between IFO and BUP files. If the menu VOB file (that is placed phisically between the IFO and BUP files) is bigger than 32k there's no problem, but if not (or there's no menu VOB) you should take it into account when correcting VTS sectors, because there will be blank space (padding) somewhere in the middle of the disc and the following sectors will be shifted by some amount.
Ok, @sneaker_ger in other thread pointed to better explanation (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/Burning%20With%20PgcEdit.htm)

DD51

25th May 2005, 14:39

Originally posted by jdobbs
@DD51

Could you try redoing the rebuild and watch to see if it is actually executing? It should take somewhere on the order of 5 minutes to write the ISO image. I need to see what's happening here.

Thanks for getting back...I tried everything. I uninstalled the program and reinstalled it using rockas installer. (the one that was included in the mail) 0.93.1. It shows in the current bar that it's building the image but it never starts.

Hope this works...here's the attachment

jdobbs

25th May 2005, 14:51

Originally posted by pilar
You should use either -no-pad option and leave DVD-RB as it is, or change something in correcting VTS sectors method. I'm not an expert, but to my understanding -pad option makes sure there is at least 32k space between IFO and BUP files. If the menu VOB file (that is placed phisically between the IFO and BUP files) is bigger than 32k there's no problem, but if not (or there's no menu VOB) you should take it into account when correcting VTS sectors, because there will be blank space (padding) somewhere in the middle of the disc and the following sectors will be shifted by some amount.
Ok, @sneaker_ger in other thread pointed to better explanation (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/Burning%20With%20PgcEdit.htm) I'm sorry but something doesn't jive in that. If what you are saying is correct, the discs I've burned wouldn't work at all. Players are exceptionally sensitive to the sector offsets. Also, I've been told that the -dvd-video option overrides several other options, and even restructures where files are put so it is compliant (like the .BUP file location in relation to the .IFO and .VOB files).

Here is what the documentation says and it doesn't match your description:

-pad
Pad the end of the ISO9660 by 16 sectors (32kB). If the total size then is not a multiple of 16 sectors, the needed number of sectors is added. If the option -B is used, then there is a second padding at the end of the boot partitions.

The padding is needed as many operating systems (e.g. Linux)implement read ahead bugs in their filesystem I/O. These bugs result in read errors on one or more files that are located at the end of a track. They are usually present when the CD is written in Track at Once mode or when the disk is written as mixed mode CD where an audio track follows the data track.

To avoid problems with I/O error on the last file on the filesystem, the -pad option has been made the default.

I can set the padding off -- but before I do I need to know 100% that it's the right thing to do.

jdobbs

25th May 2005, 15:11

I just PM'd coujo to get his take on it...

pilar

25th May 2005, 17:31

Originally posted by jdobbs
I can set the padding off -- but before I do I need to know 100% that it's the right thing to do.

I've just prepared some test iso files to check and I was wrong about the -pad/-nopad options. You and the documentation are right - it has no meaning in the problem I'm talking about.
Moreover, after looking inside the iso files I've found that the gaps between IFO and BUP are created depending on VTS sectors in IFO. Shortly, if I create "normal" IFO, there will be no space between IFO and BUP in ISO. If I change the IFO to create 32K space between those files (with PgcEdit for example), mkisofs creates this gap. -pad/-no-pad option doesn't change anything in that matter.

So you don't need to change anything in DVD-RB, mkisofs will create always correct ISO.
I'm sorry for confusion. I should check all this before...

But consider the option to create 32k space between IFO and BUP (of course only in "output to ISO" mode)

jdobbs

25th May 2005, 19:33

Ok, I appreciate all the investigative work. Thanks.

jdobbs

25th May 2005, 20:23

@DD51

I'd like to try and nail down what the problem is. I think I may have an idea what's wrong. I've gotten a couple of other reports of similar behaviour.

Could you post:

1. The path to the DVD-RB directory
2. The path that was uses for the working directory
3. The path used for the output directory (if different than working)

The could you try to do a manual creation using this command line:

"c:\path_to_mkisofs\mkisofs.exe" -dvd-video -V DVD-VIDEO -o c:\path_to_output\DVD-VIDEO.ISO c:\working_path\DVDFILES

(I'm assuming drive c: -- change to whatever is correct)

jdobbs

25th May 2005, 21:07

Ok I think I found the problem on this... like a dumb-ass I forgot to put quotes around the paths... so if there was a space anywhere in the path it would fail. I've fixed it and will release that and a couple of other things in a bug-fix version (probably v0.93.2).

rayvt

26th May 2005, 06:28

Please also put quotes around the ISO label. Also, it would be nice if RB defaulted the label to be the name of the source DVD directory, since decryptor cleverly makes that to have the label of the original DVD.

So source of "I:\DVD RIPS\THE_SANTA_CLAUSE\VIDEO_TS\" would have a default label of "THE_SANTA_CLAUSE".

Thanks

DD51

26th May 2005, 13:04

Thank you jdobbs:)

JohnG

26th May 2005, 14:07

I woke up this morning with a beautiful backup of the Wizard of Oz for my kids, resting in the ejected tray of my burner. Sweet! One click app with the best quality you can get;) . I had no problems creating an ISO and burning automatically with Decrypter. The backup was also played without a hitch on my SAP. Thanks again jdobbs:D :D
btw, I named the ISO "OZ" so I guess that's as short and simple a title you can get...Ironically, I didn't know that the nomenclature could cause a problem until I read this(after the backup was created).

jdobbs

26th May 2005, 14:23

I love it when a plan comes together. :)

archaeo

26th May 2005, 17:59

I woke up this morning with a beautiful backup of the Wizard of Oz for my kids, resting in the ejected tray of my burner.

just wondering if you did this in 'auto-shutdown' one click mode?
I haven't had time yet to try it yet, so I thought I'd ask :)

jarthel

27th May 2005, 02:52

Originally posted by jdobbs

mkisofs -dvd-video -V SELECTED_LABEL -o OUTPUT_PATH INPUT_PATH

Can the select label be the working directory name"

so if my working directory is d:\dvds\KILLBILL_VOL2 then SELECTED_LABEL = KILLBILL_VOL2

thanks

JohnG

27th May 2005, 14:10

Originally posted by archaeo
just wondering if you did this in 'auto-shutdown' one click mode?
I haven't had time yet to try it yet, so I thought I'd ask :)

No, I never use the auto-shutdown feature. And I'd like to add that I just completed my second "one-click" backup with great success. "Season2 of the Dave Chappelle Show" (btw, the funniest guy on the planet):p It came out at 4.32 gigs and looks awesome! I really can't thank jdobbs enough for this program.:D :D :D

Rockas

27th May 2005, 15:29

I really can't thank jdobbs enough for this program.
http://www.thestylemachine.com/smileys/ah.gif http://www.thestylemachine.com/smileys/yeah.gif
No... you can't... but you can try... another donation on the way? lol http://www.thestylemachine.com/smileys/uy.gif

int 21h

28th May 2005, 09:18

Originally posted by jarthel
Can the select label be the working directory name"

so if my working directory is d:\dvds\KILLBILL_VOL2 then SELECTED_LABEL = KILLBILL_VOL2

thanks

Or alternatively, can you add the Label option for the ISO somewhere to the main screen and take it out of the menu?

Something like:

[Source Path]
[Working Path]
[Output Path]
[ISO Label]

jdobbs

28th May 2005, 12:31

You'd still have to click on it an bring up a dialog...

rayvt

28th May 2005, 20:19

I can't get it to build the ISO. It doesn't look like it even executes mkisofs. It knows it's there, because when I delete mkisofs.exe, that line is greyed out, and gets un-greyed when I restore it. I replace mkisofs.exe with a dummy program which just writes the arguments to a text file, but that text file never gets created.

Update: Thought it was a %PATH% problem. Maybe not. Now I'm stumped.

The DVD-VIDEO.ISO that rebuilder created is 10,022 KB, and rebuilder reported:
Correcting VTS Sectors...
- Building ISO Image...
- There appears to have been an ISO write error.
- ISO Image WAS NOT successfully written.

I opened it with winrar, and it shows all the files as being there. It looks like maybe mkisofs created the directories & filenames, but didn't actually write the files themselves.

Then I manually executed:
mkisofs -dvd-video -V "Shall We Dance" -o f:\00-dvdrb\dvd-vid.iso f:\00-dvdrb\DVDFILES\

And this one is 4,529,464 KB and took 11 minutes to do.

jdobbs

28th May 2005, 22:59

Are you using v0.93.2? There was a bug in v0.93 related to this that was fixed.

rayvt

29th May 2005, 01:03

Yes, v0.93.2(beta). Just dl'ed it last night. First just unzip'ed the zip, but when that failed the same way, ran the full installer exe. Same results.
I'm doing a new encode now, we'll see how it goes.

rayvt

29th May 2005, 04:41

I think it somehow had to do with %PATH% and/or the fact that I have many many cygwin1.dll's scattered all over my system.

But anyway, I found a build of mkisofs that doesn't need or use cygwin1.dll.
I grabbed it from http://stud3.tuwien.ac.at/~e0227529/mirror/cdrtools-2.01-bootcd.ru-w32.zip

Appears to be the same version; this one shows:
g:\dvd-rb>mkisofs.exe -version
mkisofs 2.01-bootcd.ru (i386-pc-mingw32)

and the one with RB 0.93 shows:
g:\dvd-rb-prev\APPS>mkisofs.exe -version
mkisofs 2.01 (i686-pc-cygwin)

The ISO's built by these two are identical.

rayvt

29th May 2005, 05:39

Sorry for all the posts, but......
While debugging I was watching things with process_explorer, and I noticed a couple of things:
* RB (v 0.93.2) doesn't put quotes around the iso label (-V option to mkisofs). This made mkisofs do really wierd things--like create an iso with directories and filenames but no actual data in the files.

* The current directory is "...\Matrix\" rather than the directory of rebuilder. This seems odd. I was getting dump files from mkisofs, and it put "Mkisofs.exe.stackdump" files in \Matrix\. I didn't see them because I was looking in RB's directory.

* I generally start RB with a batch file that does:
"start /dg:\dvd-rb /belownormal rebuilder.exe"
Proxexp and taskmanager both show that RB runs at this priority, but mkisofs runs at normal priority.(!) I thought that sub-processes inherit the priority of their parent---but evidently it doesn't work that way. Now I'm wondering if the encoders run at normal priority instead of lowered, as expected.
Anyway, would it be possible to have another option in RB, to run the applications at belownormal priority, in addition to the existing option of running minimized?

Thanks.

jdobbs

29th May 2005, 12:30

That's true... but I thought it was illegal to have spaces in a Volume label? I'll put quotes around the volume label.

I believe it is possible for an application to set its own priority and override what you've set.

In the "MATRIX" directory? That could be because it was the last directory accessed and has become the default.

alfixdvd

29th May 2005, 16:42

@raydt

I think it somehow had to do with %PATH% and/or the fact that I have many many cygwin1.dll's scattered all over my system

The first place where a program looks for a dll is the same directory where the program resides.

curious d

1st June 2005, 17:14

After reading these posts, I'm still not sure if there is a way to have the output iso named differently (ie the folder name) when creating an iso with DVD-RB Pro. I got an image named "DVD_VIDEO" on my first attempt. Thanks.

jdobbs

1st June 2005, 17:48

You can't change the folder, only the name of the file... you select the folder when you choose an output directory.

rayvt

2nd June 2005, 02:28

I thought it was illegal to have spaces in a Volume label? I'll put quotes around the volume label.

That's what I read, too. Theoretically also illegal to have lower case letters. However, I'm seeing plenty of commercial DVD's with mixed case and spaces in the label---at least, in the label that DvdDecrypter sees and uses as the ripped directory name.

My feeling is that whatever you see in commercial DVD's is de-facto legitimate.

jdobbs

2nd June 2005, 02:40

Hmmm... I don't think I've ever seen any lower case letters. Usually its all upper case and underscores are used for spaces.

spyhawk

2nd June 2005, 04:44

I occassionally see mixed case label in commercial DVDs. If the label is long I usually mixed case with underscores using mkisofs. I also tried with spaces as a test and it works on my settop players and on pc, but I wouldn't recommend it for compatibility purposes.

SkVid

2nd June 2005, 09:11

It is a question of what labels you are talking about. There is no problem of having blanks and spaces in the label of the udf part but the iso label must have upper case labels and no blanks. This is the rule.
If you use DVD Decrypter to change the label and you try to enter lower case labels or blanks for the iso label he gives back an compliance error. But you can save it if you want and on my players I had no problems. But normaly I don't do that.

http://forum.doom9.org/attachment.php?attachmentid=4006&stc=1

In that linked picture (sorry I don't know how to insert them directly) you can see how the Decrypter handles this. You can enter two different volume labels, one iso and one udf label. The udf label is more free on what you can enter. You can have blanks, upper and lower case and some symbols like "/".
The udf label is the one that the Decrypter shows as label when you insert a disc. And he uses this label to create the folder name as far as I can see. Maybe we should have the option to enter both labels.

jdobbs

1st July 2005, 03:16

I've just prepared some test iso files to check and I was wrong about the -pad/-nopad options. You and the documentation are right - it has no meaning in the problem I'm talking about.
Moreover, after looking inside the iso files I've found that the gaps between IFO and BUP are created depending on VTS sectors in IFO. Shortly, if I create "normal" IFO, there will be no space between IFO and BUP in ISO. If I change the IFO to create 32K space between those files (with PgcEdit for example), mkisofs creates this gap. -pad/-no-pad option doesn't change anything in that matter.

So you don't need to change anything in DVD-RB, mkisofs will create always correct ISO.
I'm sorry for confusion. I should check all this before...

But consider the option to create 32k space between IFO and BUP (of course only in "output to ISO" mode)
@Pilar

I'm doing some last minute fixups to be sure I'm doing this right... so correct me if I'm wrong... in order to get the 32k minimum spacing between the end of the IFO and the start of the BUP -- all I have to do is set the last sector of IFO (offset 0x1C) in the IFO to create the space and adjust the VMG_TT_SRPT tables, right? MKISOFS takes care of it from there? (I'm pulling from this thread: http://forum.doom9.org/showthread.php?t=88033&page=2&pp=20)

Malphas

1st July 2005, 18:13

Hmmm... I don't think I've ever seen any lower case letters. Usually its all upper case and underscores are used for spaces.
Perhaps as much as a third of my DVDs seem to have lower case or mixed lettering in the volume label, haven't beeing paying attention enough to notice if spaces were used instead of underscores. Also often the volume label is along the lines "Untitled", "DVD_Volume" or "NEW", I tend to just leave the label as it is on the original regardless. I'm in Region 2 if that makes any difference.