Another adventure in DVD burning! I wonder whether it will actually work this time without major hassle!
I’m looking at old pages I wrote myself for guidance: First, I took a look at 2004-10-30 Software:
Capture the video, merge scenes that are just one scene, and cut some extra stuff.
Done. I read the two tapes from the camera onto a 60G partition using Kino.
When exporting, I go to Export → MPEG and give it a name, choose file format 8 (DVD), and select the “Scene Split” checkbox (every scene in kino should be a chapter on DVD). Exporting will take quite some time.
Indeed it does. More than 3½h for about 1h of material.
[Time passes...]
It turns out that the stupid software tried to write all the files into my home directory. Soon enough, the home partition was full, and instead of aborting, it kept on transcoding the video for close to four hours. The symptom was that two thirds of all the files had 0 size.
I now picked a different filename and directory, and restarted the process. Isn’t this fun. I also had to change group and write permission for the directory.
[Time passes...]
While I’m waiting, I try to start VLC from the command line:
VLC media player 0.7.2 Bond
Uhm...
[Time passes...]
Open every mpeg file with Totem and save a screenshot as jpg file. Convert them all to 4x3 aspect ratio using the following:
for f in 0*.jpg 1*.jpg; do convert -resize '150x100!' $f title$f; done
Note the exclamation mark to force the new aspect ratio, and note the size which is about right for a menu. Create two aditional menus, one for the stuff before break, one for the stuff after break, drag the jpeg images onto it, drag the mpeg into the bottom section after the menus, create appropriate text buttons, label them, give them the right jump command, then click on all the tracks and make sure that the post-command is to jump to the next track.
#Software
(Please contact me if you want to remove your comment.)
⁂
FWIW, you can stop glibc sending SIGABRTs for detected corruption with an environment variable – _MALLOC_CHECK or similar, if I recall.
– cjb 2006-03-19 05:18 UTC
---
Hm – but what does memory corruption mean? Does it mean a bug in the software or a fault in my RAM? I’m not sure I want to ignore this signal since I don’t know what it means...
– Alex Schroeder 2006-03-19 16:31 UTC
---
Oh, it means a bug in the software. It can often be the kind of bug that causes subtle corruption that doesn’t cause a crash or data loss (but should still be fixed). The SIGABRT feature is new to modern glibc.
– cjb 2006-03-23 05:56 UTC