KXStudio 12.04.1 released!

[deufrai]

A big thank you for all this !!!

[totalchaos]

Already installed. Me and my Computer never felt better.

[GMaq]

Congratulations and Amazing Work! KDE4 never looked so good!

[autostatic]

Congrats Filipe!

[English Guy]

Downloading now

[Thad E Ginathom]

Congratulations on the release! It makes KXStudio a very much more noticeable entity, and should lead to increased numbers getting its benefits.

I just did one live-boot run from the CD so far, and should give it a partition for a proper look, but just to let you know that, although I fumbled a bit at first, even my Firewire device worked fine for playback from both Audacious (needed configuring for jack: possible to make this a default on the distro?) and Firefox/YouTube.

As a personal side issue, I don't think KDE is for me. I guess that means that any new install that I do should still be based on Ubuntu Studio, rather than KXStudio iso, so as not to install all the KDE stuff I don't need?

By the way, I know you are dealing with theme issues, but part of my quick test showed that, in the Audacious File-open dialogue, I could not even see the alternate light-background entries. I wondered where my files were until I ran the mouse over the window!

[Thad E Ginathom]

Going out for the evening now, will try to get back to that one later.

[Animtim]

Congratulations for this release!

[Thad E Ginathom]

Weird. Might have dreamt the thing with the file open dialogue, or might have seen it somewhere else. Doesn't look like that today.

Here's some stuff that enlarges on "fumbling" mentioned above. On startup (This is a DVD "Try without Installing,") there is no sign of cadence running and the cadence icon doesn't start cadence. I just realised that it is finding and trying to set up a RME Digi96 card which is physically in the box, but not really in use (although it should work). This is the cadence log immediately after a re-boot and before trying anything at all.

Code: Select all

Mon Jan  7 01:01:02 2013: Listening for D-Bus messages
 12 Mon Jan  7 01:01:02 2013: Starting jack server...
 13 Mon Jan  7 01:01:02 2013: JACK server starting in realtime mode with priorit    y 85
 14 Mon Jan  7 01:01:02 2013: Acquired audio card Audio0
 15 Mon Jan  7 01:01:02 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|    0|nomon|swmeter|-|32bit
 16 Mon Jan  7 01:01:02 2013: Using ALSA driver Digi96 running on card 0 - RME D    igi96/8 PST at 0xfb000000, irq 21
 17 Mon Jan  7 01:01:02 2013: configuring for 44100Hz, period = 1024 frames (23.    2 ms), buffer = 2 periods
 18 Mon Jan  7 01:01:02 2013: ALSA: final selected sample format for capture: 32    bit integer little-endian
 19 Mon Jan  7 01:01:02 2013: ALSA: use 8 periods for capture
 20 Mon Jan  7 01:01:02 2013: ALSA: final selected sample format for playback: 3    2bit integer little-endian
 21 Mon Jan  7 01:01:02 2013: ALSA: use 8 periods for playback
 22 Mon Jan  7 01:01:07 2013: ERROR: JackPosixProcessSync::LockedTimedWait error     usec = 5000000 err = Connection timed out
 23 Mon Jan  7 01:01:07 2013: ERROR: Driver is not running
 24 Mon Jan  7 01:01:07 2013: ERROR: Cannot open client name = dbusapi
 25 Mon Jan  7 01:01:07 2013: ERROR: failed to create dbusapi jack client

The problem is in not just being able to click on the cadence icon because, once something goes wrong, cadence is renamed catatonic and won't run at all.

The --reset thingy gets us back on speaking terms with cadence, it runs, gets configured to firewire, gets started, gets the alsa-->jack bridged, and all is well again

Audacious says

Code: Select all

ALSA error
No suitable mixer element found.

snd_mixer_find_selem failed.

But it works anyway.

All this is for information only (I'll gladly test anything else if you wish) and indicative of what happens when an idiot gets hold of the DVD. This idiot isn't going to run round the net complaining that nothing works in Linux audio without hours of command-line configuration Anyway, the hardest part for me was finding where KDE puts the terminal command which is why I don't want to change desktops.

I suggest that you include a terminal on that first menu "Favourites" tag. The real idiots can ignore it, but for the rest of us, it is most likely to be one of the first things we want, and if we do not know the desktop and its menu structure...

[Thad E Ginathom]

Firewire without another card to confuse things

Is much better. I don't think I can ever expect you to detect a firewire audio device and use it automatically, because I suspect that Ubuntu just not support that. Again, it's a Live-CD session. Here's what happens...

No sign of cadence on startup. Here's the log before trying anything

Code: Select all

Mon Jan  7 16:33:35 2013: ------------------
Mon Jan  7 16:33:35 2013: Controller activated. Version 1.9.9.5 (unknown) built on Sat Dec 22 19:05:55 2012
Mon Jan  7 11:03:39 2013: Loading settings from "/home/kxstudio/.config/jack/conf.xml" using expat_2.0.1 ...
Mon Jan  7 11:03:39 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Mon Jan  7 11:03:39 2013: setting parameter 'engine':'realtime':'(null)' to value "true"
Mon Jan  7 11:03:39 2013: setting parameter 'engine':'realtime-priority':'(null)' to value "85"
Mon Jan  7 11:03:39 2013: setting parameter 'drivers':'alsa':'rate' to value "44100"
Mon Jan  7 11:03:39 2013: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Mon Jan  7 11:03:39 2013: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Mon Jan  7 11:03:39 2013: Listening for D-Bus messages
Mon Jan  7 11:03:39 2013: Starting jack server...
Mon Jan  7 11:03:39 2013: JACK server starting in realtime mode with priority 85
Mon Jan  7 11:03:40 2013: ERROR: control open "hw:0" (No such file or directory)
Mon Jan  7 11:03:40 2013: ERROR: control open "hw:0" (No such file or directory)
Mon Jan  7 11:03:40 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Mon Jan  7 11:03:40 2013: ERROR: control open "hw:0" (No such file or directory)
Mon Jan  7 11:03:40 2013: Using ALSA driver  running on card 0 - 
Mon Jan  7 11:03:40 2013: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Mon Jan  7 11:03:40 2013: ERROR: Cannot initialize driver
Mon Jan  7 11:03:40 2013: ERROR: JackServer::Open failed with -1
Mon Jan  7 11:03:40 2013: ERROR: Failed to open server

However, cadence does run its GUI, allowing the Firewire driver to be configured and the bridge to be started. I ran it from the command line in case of error output, but rebooted just to try the icon. Also fine.

This is probably the best a Firewire-device user can expect from Ubuntu ...and, compared to the murderous experience I had trying to get it to work at all, pre-KXStudio, it's pretty-damned good

[Thad E Ginathom]

Yes, agreed that it is the common-sense default.

What would be good is if Cadence GUI was always available, even when something has failed. Some of us don't mind a $ prompt, but to others it typifies what they think is wrong with linux. It needs to handle the stuff that goes wrong, if not smartly, then at least gracefully.

Keep up the good work. It's all good. Quite possibly better than any another way of interacting with Jack

[adrianfernandezfazio]

Can you implement flattr in your website? It's simplify the donation process. Thanks for your work

[scriptwarlock]

just want to thank you falkTX for sharing your work to us. been using kxstudio for while now... some sreenies of ardour 3 beta5 running on kxstudio 12.04.1 http://tinyurl.com/8sbgmb5

[bmarkham]

I just upgraded from Ubuntu Studio 12.04 to 12.10.

Since I store my data on an external drive, I'm not at all averse to blowing away the current install. Would it work okay on Ubuntu 12.10? Or would I be better off downgrading to 12.04? Would I be better off doing a vanilla Ubuntu 12.04 install from which to install KX Studio?

KXStudio -- especially its Jack and Alsa/Jack midi management sound worth trying!

Thanks!