Language Selection

English French German Italian Portuguese Spanish

K3b 1.0 Released

Filed under
Software

I am proud to announce the release of K3b 1.0. After years and years of development, all the sweat (actually in the summer it can get sticky in front of the screen), all the tears (ok, admittedly, not that many), and all the countless hours I spent on a single application finally we have what I think is worth the big 1. K3b has come a long way since the early days in 1998 when it started as a dummy project for me to learn C++ and QT development.

Media-centric user interface

Unlike most other CD and DVD applications K3b's user interface does not deal with devices but with media. Thus, in K3b you choose a medium to burn to or to read from instead of the device. This allows K3b to adjust and optimize the user interface, the presented settings, to the context, ie. the selected media. For example when copying a data CD K3b will not bother you with settings like paranoia mode which are specific to audiohttp://www.tuxmachines.org/node/add/story CD extraction. In addition the framework allows for nice features such as an automatic project size adaption to an inserted empty medium.

Always be informed about your media

K3b provides detailed media information: the folder tree view part of K3b's own file browser displays each available device and a short summary of the inserted medium. Move the mouse over the entry to get a fancy tooltip displaying more detailed information. If you need the full blown media info use the context menu to display the media info which shows the full table of contents and even CD-Text entries.

More Here.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more