[k3b] [Bug 257602] K3B cannot burn Blurays (or AVCHDs)

[King_DuckZ]

https://bugs.kde.org/show_bug.cgi?id=257602

--- Comment #24 from King_DuckZ <king_duckz at gmx.com> ---
> there is still the riddle why ImgBurn on Wine produces mostly failing
> results but sometimes succeeds.
> 
> An the first glimpse this does not look much like a filesystem format
> problem but more likely it is a problem between burner and medium,
> or between ImgBurn, Wine, and Linux if you burn directly from ImgBurn.

The error ImgBurn gives me is something like "invalid address for write". Other
users receiving that error were told it's because of the medium quality,
however I doubt that 5 out of 6 50GB Panasonics are so bad that can't be
written, that's more like a scam than just bad quality. Success rate with
Verbatim is also 1 out of 2 tries, so I don't know what kind of blurays one
would have to buy.

> So independently of the endeavor to produce BD video UDF on Linux,
> King_DuckZ should try to let ImgBurn write to a file image instead
> of the burner directly (if that is what is done currently).
> Then use Linux command line burn programs to burn the medium 
> 
>   growisofs -dvd-compat -Z /dev/sr0=image.udf
> or
>   cdrskin -v dev=/dev/sr0 fs=32m -eject image.udf

I followed your advice, I made a .iso with ImgBurn and burned it with your
cdrskin command, on gentoo, kernel 4.12.12 with libburn-1.4.8-r1. The resulting
bluray is unreadable on PS3 and on my computer, so another wasted disk. cdrskin
output: http://paste.debian.net/1008790/

> and use Linux command "mount" to check whether the video files are 
> readable afterwards. E.g. copy them to hard disk and watch for error 
> messages.

I can mount the iso and navigate it just fine with mount -o loop,ro

> Please report any program messages of failed burn, failed "mount", or
> failed read. With "mount" and "read", the output of command "dmesg"
> will be of interest.
> (Check for private info in there and remove it before posting publicly.)

mount /dev/sr0 /mnt/cdrom/
mount: /mnt/cdrom: wrong fs type, bad option, bad superblock on /dev/sr0,
missing codepage or helper program, or other error.

dmesg[ 6079.900117] EXT4-fs (dm-2): mounted filesystem with ordered data mode.
Opts: (null)
[ 6599.454520] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts:
(null)
[ 6599.644744] UDF-fs: warning (device loop0): udf_load_vrs: No anchor found
[ 6599.644746] UDF-fs: Scanning with blocksize 512 failed
[ 6599.644834] UDF-fs: warning (device loop0): udf_load_vrs: No anchor found
[ 6599.644835] UDF-fs: Scanning with blocksize 1024 failed
[ 6599.644909] UDF-fs: INFO Mounting volume 'SS_LC_S1_D1', timestamp 2018/02/04
12:58 (1000)

-- 
You are receiving this mail because:
You are the assignee for the bug.