LinuxAnswers DiscussionThis forum is to discuss articles posted to LinuxAnswers.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
dvdunauthor cases
Hi,
Just to let you know that I have been trying the dvdunauthor for 2 weeks now (by hand & without spunmmux)
This is a great way to learn xml for dvdauthor, but also an easy way to split a 3h
dvd into 2 dvds with a much smaller requant factor (otherwise you may look at a factor ~1.8).
Dvdrequant would need to address this case of long duration (1 title - 1 soundstrack only) in the long term.
Otherwise sometimes t files occur more than once because of loops in the dvd.
I think I have seen one case of chapters files not being numbered in chronological order.
In some cases I had to add a <subtitle lang="en"> tag (I cannot remember the syntax),
otherwise I could not then keep the sub and run some other tools
(error ??? detected , when a language string is expected)
Some of the t files are sometimes generated up to 2 Go or even 5+ Gb (I wonder if all system can cope
with such long file).
I also saw cases of the main title being split in 0.6 Go bits, well then the files names
are still consecutive, but the search algorithm for a human being is still easy ;-)
Files come in the 1 Go flavour as well.
As I quoted from sbdy else, you can reset the time stamp counter whenever you want
(this may be a problem with dvdauthor 0.6.10, to be checked)
If one does that, there is less calculation of chapter / title duration needed.
So within one <pgc></pgc> you can put all the vobs you want, that is all the titles.
Not very elegant, but I am a newbee... :-)
That is all I can think of for now.
Last edited by Emmanuel_uk; 03-09-2005 at 01:17 AM.
As a total nOOb to DVD's, I was referred to this discussion from my post http://www.linuxquestions.org/questi...hreadid=298374
I have spent several hours going through this & several other references. The script looks good, looks like what I want to do but how do you create the .iso? Right now I'm at the point where I have an AUDIO_TS (empty) and a VIDEO_TS (total 4.4 Gig) and each time I try to make an .iso mkisofs stops at 4.0 Gig:
Latest attempt (cribbed the mkisofs command from your script)
Code:
crashedagain@desktop:~$ mkisofs -dvd-video -udf -V MOVIE -o /mnt/hda7/temp/movie.iso /mnt/hda7/MOVIE
0.22% done, estimate finish Mon Mar 7 19:00:35 2005
0.44% done, estimate finish Mon Mar 7 18:56:48 2005
0.66% done, estimate finish Mon Mar 7 18:58:04 2005
<edited...>
91.21% done, estimate finish Mon Mar 7 19:04:07 2005
91.42% done, estimate finish Mon Mar 7 19:04:07 2005
91.64% done, estimate finish Mon Mar 7 19:04:07 2005
File size limit exceeded
crashedagain@desktop:~$
I have no idea what the input/output error is but I get input/output error with k3b also:
Code:
Writing DVD-R in DAO mode.
Using growisofs 5.21 Copyright....
Starting writing...
Could not write temporary file
Error while creating iso image
:-write failed: input/output error
Fatal error at startup: Input output error
I did successfully burn a disk with
Code:
growisofs -Z /dev/dvd -R -J /mnt/hda7/MOVIE/
but that created a data disk which the dvd could not play. It would seem to indicate that the burner hardware is OK though.
Yes K3B uses growisofs, but I am burning my DVD's with K3B's video DVD preset. That is burning the VIDEO_TS folder in UDF DVD compliant format, not creating an ISO file from it.
Now It looks to me as if you either have a problem with the movie you ripped or your mkisofs install is corrupted.
Originally posted by Steel_J .....but I am burning my DVD's with K3B's video DVD preset. That is burning the VIDEO_TS folder in UDF DVD compliant format, not creating an ISO file from it.
Do you mean using the 'create a new video DVD project' ? That's what I was doing. My files seem to be OK; play OK when tested with 'xine dvd:/mnt/hda7/MOVIE/VIDEO_TS' (menus work etc.)
Another source has hinted that it might be an encryption problem since I started from a commercial video. I copied the files using dvdbackup & resized using dvdshrink instaed of using dvd:rip; maybe this is the problem.
On another subject, way back in this discussion KDE DVD authoring wizard was mentioned. What KDE package is that in?
Another source has hinted that it might be an encryption problem since I started from a commercial video. I copied the files using dvdbackup & resized using dvdshrink instaed of using dvd:rip; maybe this is the problem.
That might just be the reason why. Use this script instead and let us know if it works out.
All this time I had understood you had used my script (I should almost say "our" script now.)
That is why I did not figure out your problem.
Yes I meant "create a new DVD video project". If I read you right it seemed to have worked. Is that it?
As for mkisofs and the failed creation of an iso file, well as I can see you ripped your movie with dvdbackup which decrypts all the files automatically, so it can't be an encryption problem since the minute you can see the DVD file content it automatically means they are not crypted anymore.
Your usage of DVDShrink , a win32 native application, in a linux environnment tells me the outputed files might not be too standard anymore and mkisofs doesn't like that.
I am having a hard time figuring out your code for ripping the audio tracks:
Here is the track selection code:
Code:
echo " "
echo -n "Enter the audio ID (AID) codes of the tracks you wish to rip, separated by spaces (e.g. 128 129 etc...) >"
read -a TRACK_AID
NUM_AUD_TRACKS=${#TRACK_AID[@]}
CUR_TRACK=0
while [[ "$CUR_TRACK" -lt "$NUM_AUD_TRACKS" ]]; do
AUD_FILE[$CUR_TRACK]=$( echo "lang$CUR_TRACK.ac3" )
done
Now, you recently explained to me that you did not know about my AID concept and since you don't have a working DVD-RW setup it would be hard for you to see the problem.
Here is what is happening:
1) An AID number identify a particular track. They consist mostly of 3 digit numbers. e.g 128 is most often the 5.1 Dolby english language audio track.
So when we enter our track choice in the script, if we choose 2 tracks for example, it would look like this
Quote:
> 128 129
I don't know if your code can use that properly as input. I think it was made to accept single digit number like 0 and 1. Here lies the problem, every completed rip I did with this new code as ended up with only one audio track that is always called the same:
Quote:
lang0.ac3
It never changes. It seems to me it should comme out with the AID number in it's name like so:
Quote:
lang128.ac3
but it doesn't.
Also, if you choose 2 tracks, it rewrites ittself over because it has the same name. So you end up with one track file only in the work folder for the multiplexing.
2) I think it is directly related but the audio size is not computed in the requantization factor and the final.mpg file comes out being 4.3 gig + the audio, so closer to 4.7 gig which is too big.
In final I figure it all as to do with the "array" portion of the code.
Could you revise that code. Your variable names are many and confusing to me. I will continue too look for the bug but some help would be appreciated.
echo " "
echo -n "Enter the audio ID (AID) codes of the tracks you wish to rip, separated by spaces (e.g. 128 129 etc...) >"
read -a TRACK_AID
NUM_AUD_TRACKS=${#TRACK_AID[@]}
CUR_TRACK=0
while [[ "$CUR_TRACK" -lt "$NUM_AUD_TRACKS" ]]; do
echo ${TRACK_AID[$CUR_TRACK]}
let "CUR_TRACK = $CUR_TRACK + 1"
AUD_FILE[$CUR_TRACK]=$( echo "lang$CUR_TRACK.ac3" )
done
It is your code except for one line that I added:
Code:
let "CUR_TRACK = $CUR_TRACK + 1"
I wrote a litle test script to test it:
Code:
#! /bin/bash
mplayer -nojoystick -nortc -nolirc -dvd-device /dev/dvd dvd://1 -vo null -ao null -frames 0 -v | grep aid
echo " "
echo -n "Enter the audio ID (AID) codes of the tracks you wish to rip, separated by spaces (e.g. 128 129 etc...) >"
read -a TRACK_AID
NUM_AUD_TRACKS=${#TRACK_AID[@]}
CUR_TRACK=0
while [[ "$CUR_TRACK" -lt "$NUM_AUD_TRACKS" ]]; do
echo ${TRACK_AID[$CUR_TRACK]}
let "CUR_TRACK = $CUR_TRACK + 1"
AUD_FILE[$CUR_TRACK]=$( echo "lang$CUR_TRACK.ac3" )
echo $AUD_FILE[$CUR_TRACK]
done
That's just what I was going to suggest. You could also use ((CUR_TRACK++)) like you used elsewhere in the script. But CUR_TRACK does need to increment.
Here's a revised version that should work (I will test it soon):
Code:
NUM_AUD_TRACKS=${#TRACK_AID[@]}
CUR_TRACK=0
while [[ "$CUR_TRACK" -lt "$NUM_AUD_TRACKS" ]]; do
AUD_FILE[$CUR_TRACK]=$( echo "lang${TRACK_AID[$CUR_TRACK]}.ac3" )
(( CUR_TRACK++ ))
done
This should also cause the tracks to be named lang128.ac3, lang129.ac3 etc. instead of lang0, lang1...
Enter the audio ID (AID) codes of the tracks you wish to rip, separated by spaces (e.g. 128 129 etc...) >128 129 130
lang128.ac3
lang129.ac3
lang130.ac3
What we need is to get a way to assign those to a fixed variable for the rest of the script. Anyway it's my theory. Otherwise, on the next loop it justs starts all over again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.