| 1 |
Andrey Moshbear <andrey.vul@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Mon, Jan 30, 2012 at 18:13, Joerg Schilling |
| 4 |
> <Joerg.Schilling@××××××××××××××××.de> wrote: |
| 5 |
> > |
| 6 |
> > Then you need to get the layerbreak value from your authoring software and you |
| 7 |
> > need to tell your authoring software to introduce padding. As mentioned before, |
| 8 |
> > mkisofs hnors the paddung that is announced in the IFO file and it cannot |
| 9 |
> > introduce padding that is not mentioned in the IFO file. |
| 10 |
> |
| 11 |
> I thought mkisofs _was_ an authoring software for data isos. |
| 12 |
|
| 13 |
This is correct, but it does not wholly apply to your case: |
| 14 |
|
| 15 |
Video media needs higher level video authoring software that defines the |
| 16 |
padding. Mkisofs just makes the filesystem structure and honors padding from |
| 17 |
video authoring software. |
| 18 |
|
| 19 |
> Experimental results have shown that mkisofs uses alpha-sort instead |
| 20 |
> of inode, directory-order, ctime, or mtime sort. |
| 21 |
> Is this required as per ISO 9660? |
| 22 |
|
| 23 |
yes |
| 24 |
|
| 25 |
> Also, is there a way to enable a debug mode so that mkisofs states |
| 26 |
> Dir X: File Y: LBA Z |
| 27 |
> for each file? |
| 28 |
|
| 29 |
-> man isoinfo |
| 30 |
|
| 31 |
Jörg |
| 32 |
|
| 33 |
-- |
| 34 |
EMail:joerg@××××××××××××××××××××××××.de (home) Jörg Schilling D-13353 Berlin |
| 35 |
js@××××××××××××.de (uni) |
| 36 |
joerg.schilling@××××××××××××××××.de (work) Blog: http://schily.blogspot.com/ |
| 37 |
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily |
Archives