Well this should be the final update in this thread unless I run into something that radically changes things... I finally got Blu-ray video working! I'm not sure if it was because the source video was 1080 interlaced or telecine encoded but forcing the framerate during conversion fixed the playback problem with my blu-ray player. Because of one of the two above, some players thought the framerate should be 60 (or more specifically, 60000/1001) so adding "--fps 30000/1001" to the x264 conversion fixed things. The only oddity is that I had to add about a 275ms delay to the audio to get it in sync for playing on my computer (vlc or totem) but for the blu-ray playback it was in sync without any delay. For Thomas: I tried adding the dvd_obs=64k option but it burned at 4X anyway... I'm not sure what's going on there, but it works so I'm leaving it alone. I've decided that for BD-R's that it's best to fix your problem if you're getting bad burns, not rely on defect management. To summarize the process: Use x264 through ffmpeg or directly to convert the video to H.264 per the recommendations on www.x264bluray.com. Add the -fps flag if you need it. Unless you have a REALLY fast machine or an eternity to wait, use the slow preset instead of veryslow. Extract the audio, I used ffmpeg to extract the existing AC3 audio. Use tsMuxeR to create the proper blu-ray folder structure and mux'ed stream (unfortunately not FOSS, but free) Use ImgBurn under WINE to create the image for burning, which supports UDF 2.50 for blu-ray (and 2.60, but that's not needed). A couple of side notes: My ASUS BW-12B1ST blu-ray burner has worked great without issue, can't recommend it enough. Using cdrskin which is a frontend to libburn has also worked great. No need for the official cdrtools. Not that there's anything functionally wrong with cdrtools, but it keeps me out of the whole cdrtools vs cdrkit debacle. Thanks, Richard

Hi, I would guess that subtle timing effects are involved. My workstation's USB shows similar symptoms with 16x DVD (not on SATA, or on eSATA and USB of younger test machine). Did you use dvd_obs=64k or stream_recording=on this time ? Its use at write time would show up at read time only if really blocks had to be replaced. Its non-use could show up in form of bad or poorly readable blocks. The lack of formatting is detectable. Theoretically this could make a difference for the player's decision not to play. But i would be very surprised if this is the reason for the failure. Whatever: A cdrskin run with formatting would be triggered by option blank=format_if_needed To make it fast and disable Defect Management, use additionally stream_recording=on My guess is that something is still wrong with the filesystem content or meta data. Maybe one of those lets the player take offense. Does this already wrap the folders in a UDF 2.50 filesystem ? http://forum.doom9.org/showthread.php?t=150511 talks of ISO rather than UDF. http://forum.videohelp.com/threads/284836-Basic-Guide-for-HDV-to-Blu-Ray chooses UDF 2.50 in Nero Linux. So i get the impression that tsMuxeR does not do UDF by itself. Have a nice day :) Thomas

On 08/03/2013 06:12 PM, Tom Horsley wrote: .. and none of what you said is true. You can burn to a BD-R disc and play it back in a set-top box or computer. Obviously you have to burn it in the Blu-ray file format. The folder and file structure is different from a DVD format. The only BD authoring software I know if is Windows-based and commercial.

On the blu-ray video front I'm making headway but still running into problems... Using the information I gleaned from: http://irishjesus.wordpress.com/2010/10/17/blu-ray-movie-authoring-in-linux/ http://www.x264bluray.com/ I've been able to convert my ATSC capture from MPEG2 to H264... Use tsMuxeR (free, but not open source) to mux the video and audio Use ImgBurn under wine to take the muxed output and creating an ISO for burning Use cdrskin to burn the resulting image file. Unfortunately it didn't work in my Panasonic blu-ray player... I don't yet know if it doesn't like burned discs or if I did something wrong. On a side note cdrskin burned at 6X this time, not sure why... Trying to load the folder in VLC I get a couple of error that popup but it otherwise works... I'm assuming blu-ray video does not require defect management, correct? Thanks, Richard

Hi, No need to hurry. I could try myself at the cost of wasted media and the risc that my hardware and system differ too much from yours. Kernel 2.6, burner at USB, ... several reasons why i might be unable to reproduce. So it is better to wait. So simply submitting some video files in some filesystem does not work ? Ouch. That's indeed a defeat for Linux. That will depend on some kind of user feedback. Plain BD burning should really be in reach. Have a nice day :) Thomas

Hi, Richard Shaw wrote: Source code and man page of cdrskin indicate that a burn run on BD-R has a transfer chunk size of 32 KiB if not - option stream_recording=on is given - or option dvd_obs=64k is given - or ./configure option --enable-dvd-obs-64k was given at build time So the lower performance of cdrskin compared to cdrecord might come from an unnecessarily high number of SCSI transactions. I am not aware whether cdrecord uses 64 KiB write transactions with BD-R. But in any case it seems worth a try to let cdrskin write with 64 Kib. So Richard, if i can have a test run with your next regular BD-R burn ... :) BTW: How far did you get with playing back your video ? (Especially on non-computer players.) Yesterday it was announced that Brasero has got a maintainer: http://worldofgnome.org/joshua-lock-is-the-new-maintainer-of-brasero/ I posted a greeting and mentioned this mail thread: https://mail.gnome.org/archives/brasero-list/2013-August/msg00000.html It is the first list message since january. Have a nice day :) Thomas

Hi, I wonder why cdrskin could be slower. When all setups are made, then it is only about banging out data chunks of 64 kB. If the 4x speed is quite constant, then it might be about speed settings of the drive. If speed is varying, then it might be about the priority settings which Joerg Schilling emphasizes as reason for the need to be superuser. Do you get a different speed if you add option stream_recording=on to the cdrskin run ? If only BD-R experiments were not so expensive ... or if they had a simulation mode ... I can do 16x DVD-R over SATA on my old AMD 2x3000 system. That's a bit less than 5x BD. Could you catch the message output of both programs in log files on the next occasion when you burn BD-R ? program ... 2>&1 | tee -i /tmp/program_s.log Send them to me in private. Have a nice day :) Thomas

On Tue, Jul 30, 2013 at 2:53 PM, Thomas Schmitt <scdbackup(a)gmx.net&gt; wrote: That showed the problem... For some reason optical media mounting and unmounting have not been reliable for me for several Fedora releases. Sometimes when I put in a disc, it isn't detected, other times when I switch disc, the old disc is not properly unmounted, which was the case here. Currently I have a blank BD-R disc in the drive but mount was still showing the previous disc volume label which is why xorriso was failing... I can't answer that, but when you say "kernel UDF" what exactly do you mean? I'm pretty sure I'm using the kernel UDF modules for reading and writing UDF, I'm just using mkudffs from the udftools package to format the image file. Thanks, Richard

On Tue, 2013-07-30 at 08:52 +0200, Thomas Schmitt wrote: For future reference: The gmane newsgroup interface is one way to read old messages and respond to them, in thread. Messages sent through it, end up back on this list. It works in both directions. If I've recalled the right group correctly: News group: gmane.linux.redhat.fedora.general Information: http://dir.gmane.org/gmane.linux.redhat.fedora.general -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.

On Sat, 3 Aug 2013 19:00:01 -0400 Tom Horsley wrote: Or even writable media (typo :-). Factory made discs are it.

Hi, Richard Shaw wrote: You probably mean something like this: Mounted Media: 41h, BD-R SRM Media ID: CMCMAG/BA5 ... READ FORMAT CAPACITIES: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0): 11826176*2048=24220008448 32h(0): 5796864*2048=11871977472 32h(0): 12088320*2048=24756879360 It is an overview of sizes from which you could choose. 00h and 32h are the Format Codes for the SCSI command FORMAT UNIT. (3000) is the size of the Spare Area in hexadecimal numbers counting clusters of 64 KiB. (Cough.) For some reason my burners report (0) with the format code 32h by which i could choose a particular payload size. I read different prescriptions in MMC-5 specs. Shrug. 12219392*2048=25025314816 tells the number of payload blocks, the block size 2048, and the number of payload bytes. The command dvd+rw-format -ssa=256m /dev/sr0 would choose 256 MiB Spare Area and 24756879360 payload bytes. ("256m" computed from (25025314816 - 24756879360) / 1024 /1024 ) You may issue own size wishes with a granularity of 16 MiB. I am not sure whether very small Spare Area sizes below 256 MiB are supported. xorriso would report by xorriso -outdev /dev/sr0 -list_formats a similar list Format idx 0 : 00h , 11826176s , 23098.0 MiB Format idx 1 : 32h , 11826176s , 23098.0 MiB Format idx 2 : 32h , 5796864s , 11322.0 MiB Format idx 3 : 32h , 12088320s , 23610.0 MiB and allow choosing by xorriso -outdev /dev/sr0 -format by_index_3 or xorriso -outdev /dev/sr0 -format by_size_23610m Other size wishes may be submitted. I cannot tell much about Brasero. My problem as user is that i do not have the Gnome stuff that is needed for recent versions. My problem as backend developer is that i cannot get in contact with Brasero developers who would know about its usage of the backends. I am not aware of tools to produce UDF 2.50. mkisofs/genisoimage create UDF 1.02, afaik. Maybe you get lucky with the Linux kernel capability to mount UDF read-write. It will be at least more modern than 1.02. I.e. create large file (by truncate -s, qemu-img, ...), format by mkudffs, mount -o loop -t udf, then cp into it what you need, umount, burn file to BD-R. DVD video and BD video would be an interesting topic for me to explore (UDF specs are public and free, but sooo awful to read). I roughly know what mkisofs writes into its ISO 9660/UDF hybrid filesystems. I lack of testers resp. test equipment, though. A BD player and a bunch of factory made DVDs and Blu-rays would be a good start. But which player and whose Blu-rays are sufficiently standards compliant to serve as reference ? The risk is to buy some overly tolerant embedded Linux which would play any kind of video file from any kind of filesystem. Have a nice day :) Thomas