nautilus scripting - shh-cd-record.ksh

schneidz · 12-15-2006, 04:31 PM

hi, i wish this used a gdialog progress bar instead of an infobox:

Code:

#!/bin/bash

# shh-cd-record-v0.1.ksh
# uses cdrecord to create cd. 
#  if the first file is a wav it will create an audio cd
#  else it'll make an iso then make a data cd using that iso. 
# depends: cdrecord, mkisofs, gdialog
# this software can be distributed or modified as needed - season to
taste.
# schneidz
# 12.05.2006
 
pwd=`echo $NAUTILUS_SCRIPT_CURRENT_URI | sed 's/file\:\/\///'`
cd $pwd
 
if [ `file -bi $1 | awk '{print $2}'` = audio/x-wav ]
then
 gdialog --infobox "making audio cd" 200 200
 sudo cdrecord dev=0,1,0 -v -dao -useinfo -text $@ speed=6 -eject 
 gdialog --infobox "audio cd complete" 200 200
else
 gdialog --infobox "making iso file" 200 200
 mkisofs -r -o shh-cd.iso $@ 
 gdialog --infobox "iso file complete\n starting cdrecord..." 200 200
 sudo cdrecord dev=0,1,0 -v shh-cd.iso speed=6 -eject 
 gdialog --infobox "data cd complete" 200 200
 rm shh-cd.iso
fi

unSpawn · 12-15-2006, 05:00 PM

Please post your thread once and in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread should be closed because it is a duplicate of http://www.linuxquestions.org/questi...d.php?t=510861.

schneidz · 12-15-2006, 05:03 PM

sorry, the three i posted today are similar but they are for 3 differnt scripts.

maybe i should've put them in the same post ?

indienick · 12-15-2006, 05:14 PM

I don't see the problem with this script...?

schneidz · 12-15-2006, 05:35 PM

sorry, i didnt describe these posts very well.

the script does run fine but my wishlist includes having use a 'gdialog --guage' instead of an infobox so that it is possible to see how much it has done at any given time.

does anyone know the proper way to re-direct the output of cdrecord to create and update the 'gdialog --guage'?

thanks,

unSpawn · 12-15-2006, 09:53 PM

does anyone know the proper way to re-direct the output of cdrecord to create and update the 'gdialog --guage'?
The "problem" with --gauge is you need to find a way to return a percentage, as in:

Code:

run() { i=0; while [ $i -le 100 ]; do i=$[${i}+10]; echo $i; [ $i -eq 100 ] && pkill -KILL -f $procname \
|| sleep 1s; done | doexec /usr/bin/gdialog $procname --backtitle "ripping-cd bak" --title "ripping-\
cd" --gauge "dvd-rip $currentfile" 8 60 0; }
]$ procname=`/bin/date +%s`; run

but it is not useful in situations where you can not measure a duration.

Maybe you can extract from info like "Track 01: 2 of 619 MB written", something like

Code:

max=700; output 2>/dev/null| grep ^Track | while read string; do 
array=(${string}); fill=${array[2]}; max=${array[4]}; 
prc=`echo "scale=2;${fill}/${max}*100"|bc -l`; echo ${prc//.*/}
done

I think, YMMV(VM).

maybe i should've put them in the same post ?
IMHO you should have.

indienick · 12-15-2006, 10:00 PM

What you could do is, instead of using the "gdialog --gauge", just raise the cdrecord verbosity by two ("cdrecord -vv ..."), and let that be the gauge, then use the "gdialog" to mark that the burning process is complete.

It's not pretty, but it's the easiest way to get a gauge onscreen.

J.W. · 12-15-2006, 11:22 PM

Please post your question in only one forum

schneidz · 12-19-2006, 02:00 PM

the problem with cdrecord (and also with transcade i think) is that it sends its output to file discriptor 2.
is that standard even if it isn't reporting any errors.
either way i haven't had any luck grep-ing out any useful information like current track or estimated file size. (either because it doesn't flush each line or because it delineates lines with an ascii-13 - cr, rather than an ascii-10 - nl)

does anyone have any experience re-directing the output of these two programs ?

thanks,