What app is everyone using to write dvd's today? xfburn claims burn mode
isn't implemented yet, and k3b insists on reformatting a dvd+rw, but
then does not recognize it to burn the image.  Is there some magic
invocation I'm not doing?

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Gene,

most people are suggesting "brasero", but for me personally "k3b" is my favorite (I am using plasma as desktop).

K3b: Are all binaries installed? Check for "/usr/bin/dvd+rw-format" in k3b below "programs".

I never had issues with dvd formatting, even (and that makes me wonder) dvd-rw are formatted. This was not always so, maybe after many years the lib is capable of this, too.

As far as I know, brasero and k3b relyon the same libs.

Best

Hans

Am Montag, 16. Dezember 2024, 16:25:03 CET schrieb gene heskett:

What app is everyone using to write dvd's today? xfburn claims burn mode isn't implemented yet, and k3b insists on reformatting a dvd+rw, but
then does not recognize it to burn the image. Is there some magic
invocation I'm not doing?

Cheers, Gene Heskett, CET.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Gene Heskett wrote:

What app is everyone using to write dvd's today?

I use my own program xorriso, mostly in scripts as the list of arguments
can become lengthy.
If you describe what you want to do then i could describe what i would do.

xfburn claims burn mode isn't implemented yet,

Sounds like
https://forums.linuxmint.com/viewtopic.php?p=1952263#p1952263

Proposed remedy is to click at the button with the circular arrow beneath
a text field which tells the medium type (in that case "DVD+R").

k3b insists on reformatting a dvd+rw,

In the first few write runs of a DVD+RW life, the drive reports yjay the
medium is partly formatted. A skilled burn program then issues the SCSI
command for background formatting, waits a dozen seconds until a reply
arrives from the drive and then begins to write while formatting goes on.
(Only DVD+RW can be formatted that way.)

but then does not recognize it to burn the image.

Do you have any exact messages which i could search in Debian's K3B
sources ?
( https://sources.debian.org/src/k3b/24.05.2-1/ )
Maybe i can find out what's its woes in terms of drive and medium.

Is there some magic invocation I'm not doing?

So you want to burn an image file to DVD+RW.

I'd do in a shell terminal with appropriate content in variables "drive"
and "image":

drive=/dev/sr0

image=...path.to.the.image.file...

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image"

If something goes wrong, there should be error messages which i'd ask you
to copy+paste into a mail to this list or to my mail address if you deem
them unsuitable for public exposure.


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Hans wrote:

As far as I know, brasero and k3b relyon the same libs.

Brasero depends on
https://packages.debian.org/sid/libbrasero-media3-1
which does ISO 9660 production by libisofs and burning by libburn.
Xfburn uses the same libraries for the same purposes.
It recommends
https://packages.debian.org/sid/brasero-cdrkit
for the tasks of audio burning with CD-TEXT (libburn could do that, too)
and UDF filesystem production for video DVD. This package depends on genisoimage for UDF and growisofs for video DVD burning.

K3B uses genisoimage for ISO 9660, cdrdao, wodim, or cdrskin for CD,
and growisofs for DVD.
https://packages.debian.org/unstable/k3b


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12/16/24 11:09, Thomas Schmitt wrote:

Hi,

Gene Heskett wrote:

What app is everyone using to write dvd's today?

I use my own program xorriso, mostly in scripts as the list of arguments
can become lengthy.
If you describe what you want to do then i could describe what i would do.

xfburn claims burn mode isn't implemented yet,

Sounds like
https://forums.linuxmint.com/viewtopic.php?p=1952263#p1952263

Proposed remedy is to click at the button with the circular arrow beneath
a text field which tells the medium type (in that case "DVD+R").

interesting & thank you, it refused to write a staples brand dvd+rw, it
went thru the motions of formating the disk several times, then didn't recognize the disk even if ejected and reinserted, but is working just
as expected on a virgin Sony brand dvd+rw. Didn't have to do anything
special other than select the drive. There's two in this machine, a sata
half height, and a skinny usb portable on a too short cable.  So now I
have a copy on two different media. memtest86-64-v7.4 went thru one loop
of my 32Gigs in under 40 minutes w/o any fuss. But after a reboot, the
lag we've been looking for is back. Took me 5+ minutes to navigate my
pictures dir to send a friend a couple gimp smunched snaps of my work, searching with gimp, I had to wait out the lag for every directory level shotwell makes. Boring. Re install #31 coming up when I've finished the
current 3d printer rebuild. But now that I know how to boot from usb
I'll put the net-install on a key.  Thank you, all.

k3b insists on reformatting a dvd+rw,

In the first few write runs of a DVD+RW life, the drive reports yjay the medium is partly formatted. A skilled burn program then issues the SCSI command for background formatting, waits a dozen seconds until a reply arrives from the drive and then begins to write while formatting goes on. (Only DVD+RW can be formatted that way.)

but then does not recognize it to burn the image.

Do you have any exact messages which i could search in Debian's K3B
sources ?
( https://sources.debian.org/src/k3b/24.05.2-1/ )
Maybe i can find out what's its woes in terms of drive and medium.

Is there some magic invocation I'm not doing?

So you want to burn an image file to DVD+RW.

I'd do in a shell terminal with appropriate content in variables "drive"
and "image":

drive=/dev/sr0

image=...path.to.the.image.file...

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image"

If something goes wrong, there should be error messages which i'd ask you
to copy+paste into a mail to this list or to my mail address if you deem
them unsuitable for public exposure.

Have a nice day :)

Thomas

You too Tomas.

.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12/16/24 11:50, Timothy M Butterworth wrote:

On Mon, Dec 16, 2024 at 10:25 AM gene heskett <gheskett@shentel.net>
wrote:

What app is everyone using to write dvd's today? xfburn claims
burn mode
isn't implemented yet, and k3b insists on reformatting a dvd+rw, but
then does not recognize it to burn the image.  Is there some magic
invocation I'm not doing?

I use k3b. It works fine for me with no issues. Formatting/Erasing the
DVD works as well, although it says it is not needed for DVD. Have you
tried with a new DVD to see what that does? Have you tried
reinstalling k3b?

I think the lag is messing with its mind, it draws the initital
retangular window outline only, then has to wait 30 secs on the lag to
time out. that lag is back with a vengeance after a reboot, bothering everything I've done since. So eventually I'll do yet another install.
This thread is ended.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law
respectable.
  - Louis D. Brandeis

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Gene Heskett wrote:

xfburn claims burn mode isn't implemented yet,

I wrote:

Sounds like
https://forums.linuxmint.com/viewtopic.php?p=1952263#p1952263
Proposed remedy is to click at the button with the circular arrow beneath
a text field which tells the medium type (in that case "DVD+R").

Gene Heskett wrote:

interesting & thank you, it refused to write a staples brand dvd+rw, it went thru the motions of formating the disk several times, then didn't recognize the disk even if ejected and reinserted, but is working just as expected on
a virgin Sony brand dvd+rw.

Congrats to the success.

It would be really interesting to see whether xorriso with its diagnostic messages can tell anything enlightening about the problem with the other
DVD+RW media.
Since DVD+RW are re-usable, it would be no waste of media if you try in
a shell terminal with appropriate path texts in "drive" and "image":

drive=/dev/sr0

image=...path.to.the.image.file...

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image" 2>&1 | tee -i /tmp/xorriso.log

The messages will show up in the terminal window and also be copied to
the file /tmp/xorriso.log .
This file would be interesting for me to see. So if you can send it to
me in private i will inspect it for clues and report them to this mailing
list.

If the run fails and stays obscure, then we could even watch the SCSI
command dialog of libburn and the drive by help of an additional option
in the xorriso run. This would become very verbose.

If the run is successful, then the GUI programs are thinking too much
about things which they should better leave to their burn backends.

In 2 different dvd writers in this machine,

If you do not know which one is /dev/sr0 and which is /dev/sr1, then
you may do

xorriso -devices

which will tell vendor and model of the drives, like:

0 -dev '/dev/sr0' rwrw-- : 'HL-DT-ST' 'BDDVDRW GGC-H20L'
1 -dev '/dev/sr1' rwrw-- : 'ASUS ' 'BW-16D1HT'

("HL-DT-ST" = "Hitachi-LG Data Storage" drives are usually labeled "LG".

If this does not give the decisive clue, insert the medium into the
desired drive while having the other drive empty, and do

xorriso -outdev /dev/sr0

xorriso -outdev /dev/sr1

The one with the DVD+RW is supposed to report on stderr:

...
Media current: DVD+RW
...

whereas the empty drive will report:

...
Media current: is not recognizable
...


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12/17/24 04:23, Thomas Schmitt wrote:

Hi,

Gene Heskett wrote:

xfburn claims burn mode isn't implemented yet,

I wrote:

Sounds like
https://forums.linuxmint.com/viewtopic.php?p=1952263#p1952263
Proposed remedy is to click at the button with the circular arrow beneath >>> a text field which tells the medium type (in that case "DVD+R").

Gene Heskett wrote:

interesting & thank you, it refused to write a staples brand dvd+rw, it went >> thru the motions of formating the disk several times, then didn't recognize >> the disk even if ejected and reinserted, but is working just as expected on >> a virgin Sony brand dvd+rw.

Congrats to the success.

It would be really interesting to see whether xorriso with its diagnostic messages can tell anything enlightening about the problem with the other DVD+RW media.
Since DVD+RW are re-usable, it would be no waste of media if you try in
a shell terminal with appropriate path texts in "drive" and "image":

drive=/dev/sr0

image=...path.to.the.image.file...

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image" 2>&1 | tee -i /tmp/xorriso.log

The messages will show up in the terminal window and also be copied to
the file /tmp/xorriso.log .
This file would be interesting for me to see. So if you can send it to
me in private i will inspect it for clues and report them to this mailing list.

If the run fails and stays obscure, then we could even watch the SCSI
command dialog of libburn and the drive by help of an additional option
in the xorriso run. This would become very verbose.

If the run is successful, then the GUI programs are thinking too much
about things which they should better leave to their burn backends.

In 2 different dvd writers in this machine,

If you do not know which one is /dev/sr0 and which is /dev/sr1, then
you may do

xorriso -devices

which will tell vendor and model of the drives, like:

0 -dev '/dev/sr0' rwrw-- : 'HL-DT-ST' 'BDDVDRW GGC-H20L'
1 -dev '/dev/sr1' rwrw-- : 'ASUS ' 'BW-16D1HT'

("HL-DT-ST" = "Hitachi-LG Data Storage" drives are usually labeled "LG".

If this does not give the decisive clue, insert the medium into the
desired drive while having the other drive empty, and do

xorriso -outdev /dev/sr0

xorriso -outdev /dev/sr1

The one with the DVD+RW is supposed to report on stderr:

...
Media current: DVD+RW
...

whereas the empty drive will report:

...
Media current: is not recognizable
...

gene@coyote:~/AppImages$ xorriso -outdev /dev/sr1
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr1'
Media current: DVD+RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free


And on that same staples dvd+rw disk:

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image" 2>&1 | tee -i /tmp/xorriso.log

apparently xorriso, which I had to install, completed normally but did take a long time closing, I'll send the log by PM

Have a nice day :)

Thomas

.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12/17/24 04:23, Thomas Schmitt wrote:

Hi,

Gene Heskett wrote:

xfburn claims burn mode isn't implemented yet,

I wrote:

Sounds like
https://forums.linuxmint.com/viewtopic.php?p=1952263#p1952263
Proposed remedy is to click at the button with the circular arrow beneath >>> a text field which tells the medium type (in that case "DVD+R").

Gene Heskett wrote:

interesting & thank you, it refused to write a staples brand dvd+rw, it went >> thru the motions of formating the disk several times, then didn't recognize >> the disk even if ejected and reinserted, but is working just as expected on >> a virgin Sony brand dvd+rw.

Congrats to the success.

It would be really interesting to see whether xorriso with its diagnostic messages can tell anything enlightening about the problem with the other DVD+RW media.
Since DVD+RW are re-usable, it would be no waste of media if you try in
a shell terminal with appropriate path texts in "drive" and "image":

drive=/dev/sr0

image=...path.to.the.image.file...

xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image" 2>&1 | tee -i /tmp/xorriso.log

however, if the disk is re-inserted and:

gene@coyote:~/AppImages$ xorriso -outdev /dev/sr1
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr1'
Media current: DVD+RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free gene@coyote:~/AppImages$

Something definitely aglay with that disk. See line 190 of the log.

The messages will show up in the terminal window and also be copied to
the file /tmp/xorriso.log .
This file would be interesting for me to see. So if you can send it to
me in private i will inspect it for clues and report them to this mailing list.

If the run fails and stays obscure, then we could even watch the SCSI
command dialog of libburn and the drive by help of an additional option
in the xorriso run. This would become very verbose.

If the run is successful, then the GUI programs are thinking too much
about things which they should better leave to their burn backends.

In 2 different dvd writers in this machine,

If you do not know which one is /dev/sr0 and which is /dev/sr1, then
you may do

xorriso -devices

which will tell vendor and model of the drives, like:

0 -dev '/dev/sr0' rwrw-- : 'HL-DT-ST' 'BDDVDRW GGC-H20L'
1 -dev '/dev/sr1' rwrw-- : 'ASUS ' 'BW-16D1HT'

("HL-DT-ST" = "Hitachi-LG Data Storage" drives are usually labeled "LG".

If this does not give the decisive clue, insert the medium into the
desired drive while having the other drive empty, and do

xorriso -outdev /dev/sr0

xorriso -outdev /dev/sr1

The one with the DVD+RW is supposed to report on stderr:

...
Media current: DVD+RW
...

whereas the empty drive will report:

...
Media current: is not recognizable
...

Have a nice day :)

Thomas

.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Gene heskett wrote:

on that same staples dvd+rw disk:
xorriso -as cdrecord -v dev="$drive" fs=16m -eject "$image" 2>&1 | tee -i /tmp/xorriso.log
apparently xorriso, which I had to install, completed normally but did take
a long time closing, I'll send the log by PM

Summarizing the burn run:
The medium was not yet completely formatted.
The drive became ready for writing after 25 seconds of formatting.
The image was just 6 MB small and written within 7 seconds.
Then it lasted 144 seconds until the drive indicated that it was ready
for more activity.

I did not get this long waiting time on a fully formatted DVD+RW. But a
new one in an ASUS BW-16D1HT drive needed 86 seconds from end of writing
until the background formatting ended and the medium state could be
inquired by xorriso.
When i look at the writeable side of the DVD i see a narrow dull ring surrounded by a broad shiny ring. So most of the DVD is still unformatted
and waits for a burn run with more data.

At the end of the xorriso run, the medium status was "closed".
With overwritable media this assessment of xorriso is an emulation of
the content state. "closed" means that there were non-zero data readable
in block 16 of the medium which do not look like an ISO 9660 filesystem superblock. (xorriso has a strong tendency towards ISO 9660.)

however, if the disk is re-inserted and:
gene@coyote:~/AppImages$ xorriso -outdev /dev/sr1
...
Media current: DVD+RW
Media status : is blank
Something definitely aglay with that disk. See line 190 of the log.

The log states:

Media status : is written , is closed

That's not a good sign. This time there was no non-zero data readable from block 16. This usually means that the read quality of the written medium
is very poor.

The dye of aged DVD+RW can sometimes be revived by exercises.
You could give the disk a few full burns with all zeros:

dd if=/dev/zero bs=2048 count=2295104 | \
xorriso -as cdrecord -v -nopad dev=/dev/sr1 -eject -

The last "-" means to read the image data from standard input into
which dd pours nearly 4483 MiB of data.
Option -nopad prevents adding of padding data which would not fit on the
DVD after dd sent the full capacity of 2295104 blocks.
The run is supposed to last about 15 minutes with 4x DVD+RW or 25 minutes
with 2.4x DVD+RW.

If such a run is successful, then the medium be classified by xorriso
as "blank".
After a successful run with non-zero non-ISO 9660 data it will be
"closed".
After a successful run with an ISO 9660 filesystem image, e.g.
a debian*.iso, it will be "appendable".


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12/17/24 10:35, Thomas Schmitt wrote:

dd if=/dev/zero bs=2048 count=2295104 | \
xorriso -as cdrecord -v -nopad dev=/dev/sr1 -eject -

It's an older disk, 2.4 speed. Before I started the above, there was
a darker area about 3/16 inch wide, the rest was still shiny,
matching your description. After the above was finished, still bad,
outputting this:
Writing to '/dev/sr1' completed successfully.

xorriso : NOTE : Re-assessing -outdev '/dev/sr1'
xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/sr1'
Media current: DVD+RW
Media status : is written , is closed
Media summary: 1 session, 2295104 data blocks, 4483m data,     0 free
So I'll do an up arrow and do it again but first reinsert disk then:
gene@coyote:~/AppImages$ xorriso -outdev /dev/sr1
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

libburn : SORRY : Asynchronous SCSI error on waiting after START
UNIT (+ LOAD): [2 30 00] Drive not ready. Incompatible medium installed.
xorriso : FAILURE : Cannot acquire drive '/dev/sr1'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'

gene@coyote:~/AppImages$ dd if=/dev/zero bs=2048 count=2295104 |  
xorriso -as cdrecord -v -nopad dev=/dev/sr1 -eject -
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

libburn : SORRY : Asynchronous SCSI error on waiting after START
UNIT (+ LOAD): [2 30 00] Drive not ready. Incompatible medium installed.
xorriso : FAILURE : Cannot acquire drive '/dev/sr1'
xorriso : NOTE : Giving up for -eject whole -dev ''
xorriso : FAILURE : -as cdrecord: Job could not be performed properly.
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
Looks like that disk is burnt toast.  And stay away from Staples. Found
more Sony's, be here the 23rd. Still cheaper than usb keys.
Thanks Tomas.  Have a Merry Christmas.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Gene Heskett wrote:

It's an older disk, 2.4 speed.

I know these only from hearsay. My DVD+RW are all 4x.
Oldest from 2006. Some of them are still in regular use here.

dd if=/dev/zero bs=2048 count=2295104 | \
xorriso -as cdrecord -v -nopad dev=/dev/sr1 -eject -
...
Writing to '/dev/sr1' completed successfully.
...
Media status : is written , is closed

Not what should be told after a successful run. :(

So I'll do an up arrow and do it again but first reinsert disk then:
gene@coyote:~/AppImages$ xorriso -outdev /dev/sr1
...
libburn : SORRY : Asynchronous SCSI error on waiting after START
UNIT (+ LOAD): [2 30 00] Drive not ready. Incompatible medium installed.

This error code [2 30 00] comes from the drive, which seems to be really
angry at the medium.

(The first component "2" tells the error class "Drive not ready".
The other two hex numbers are called ASC and ASCQ and tell error reasons.
A large collection of these SCSI ASC/ASCQ error codes for disks, tapes, burners, etc. can be found at
https://www.t10.org/lists/asc-num.htm
In our case the second component "30" leads to
https://www.t10.org/lists/asc-num.htm#ASC_30
where the third component "00" is the vanilla version of reasons why
a medium may be considered unusable:
30h/00h ............. INCOMPATIBLE MEDIUM INSTALLED
)

Looks like that disk is burnt toast. 

The culprit is often not easy to determine when the relationship between
drive and medium is broken up.

Check whether your drive still can handle the other DVD+RW media (Sony ?).
If it appears to stay in bad mood, give it a power cycle (e.g. reboot of
the computer where it is in).


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)