Package: wodim
Version: 9:1.1.11-3
Severity: important
Tags: upstream

This one is a weird one. Its also reported to Fedora Team.
wodim/growisofs will take anything as input for a data track and burn it.
"Etching a Tape". Reading back this tape WILL FAIL short of the burned media
size.Try it with /dev/urandom for some cheap entertainment....

Try this with an audio file, however and at least wodim complains about
mimatches and bad formats, even if given a wave file.I used the old KCS tape
program for dos to test a theory. We know wodim will burn a normal wave
file.The test was to see if we could hide data inside an audio file(very old
school) and burn the audio file "tape" to disc. In thoery we generate a
compliant mono wave file as output.In reality, I think the headers get screwed
up doing this somehow.The file "recording" is less than 80mins and should fit
onto the disc.K3B thinks otherwise.

Use a 5MB or less source file if you want to try this.

Wodim complains and I cant get anywhere, even after using audacity to set the
wave file parameters to something reasonable.This seems to indicate wodim
doesnt like wave files and also that only audio tracks are scanned for ISO
compliance, when both aidio AND data tracks should be checked. Also, using
audacity should fix any bad header information.

I dunno where the dev issue is either.Jorg is complaining that we arent using
HIS code as cdrecord and the like.For the obvious reasons, we CANT DO
THAT.Whats wrong with MIT or GPLv3?



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wodim depends on:
ii  libc6    2.19-19
ii  libcap2  1:2.24-9

Versions of packages wodim recommends:
ii  genisoimage  9:1.1.11-3

Versions of packages wodim suggests:
pn  cdrkit-doc  <none>

-- no debconf information

Reply via email to