FalkTX, thanks once again for your valuable attention and excellent work on KXStudio.
Personally, I used to love dark themes. Used to. I actually complained loudly when blinking lights and switches gave way to nixie-tubes, then to monochrome green/amber on black monitors, then to RGB color, then to black on white. But I learned to live with the progress of technology. Who is to say that I might not still come back around to your preference for dark themes? Aging eyes, I suppose; and maybe a bit of curmudgeonry.
While consuming multiple pots of hot coffee, I've been tweaking my installation of KXStudio (this, over a fresh install of ubuntustudio12.04 amd64), and trying to resolve the two major issues I have so far discovered. These are, (1) getting 'audacity' to see jack and work with it, and (2) trying to have the system use the proprietary nvidia driver for my Nvidia Quadro card.
So far, I have been unable to get the nvidia driver to work. The suggestion provided by user i2productions above did not work for me, though I think it points in the right direction. Anyway, I put that on the back burner for now since the system appears to be usable without it, though I would like easy access to the tweaks the proprietary driver affords. Onward.
I'd finally managed to install a very useful-to-me visual theme/style using the procedure I outlined above. One thing, though: 'cadence' and its associated UIs are still very dark--irritatingly so, for me. I keep my monitor set at low levels of brightness, saturation, gamma, etc., because at my current level of poverty, a new monitor purchase would be impossible. This monitor is an old CRT, but it's 21” and though it's now a bit “fuzzy” I like it mainly because it works and I'm stuck with it.
So, I played around. Last night, I performed and recorded some music, playing guitar through 'guitarix' along with a 'hydrogen' drum part, set up a MIDI keyboard connected to 'zynaddsubfx', microphone, and recorded in 'rosegarden'. Nice. I look forward to doing some real work very soon.
However, the potential lack of 'audacity' is irritating. I have used 'audacity' for years. It's almost second nature to me. I would hate to have to abandon it. So, I decided to try to get 'audacity' to recognize and work with 'jack'.
First step was to gather some initial information.
Log out and in. Jack is running. Start audacity, jack stops. I restarted 'jack' with 'cadence' while 'audacity' was running. It restarted seemingly OK, but 'audacity' still failed to see 'jack'. Tried to play a youtube video, but no sound. Log out and back in. Started 'jack' with 'QjackCtl' to see if that made a difference. No difference. Managed to get 'audacity' running at the same time 'jack' was running (but 'audacity' still failed to recognize 'jack') and record something. Massive xruns. Tried to stop 'jack', couldn't stop 'jack'. Log out and back in, try other stuff, to no avail. I didn't keep very good notes, but then again, this is just preliminary fiddling around to gain some information.
Along the way, I un-installed/removed completely, 'bluez-alsa', a bluetooth item which was reported to cause some problems with 'audacity' and its recognition of 'jack', but that did not make a difference. Onward.
While running 'audacity' from a terminal, I got some more clues (too long to detail for this post), and decided that maybe I should see what the latest stable 'audacity' release had to offer. Well... I decided to compile the latest version (which is 2.0.1) to replace the initially installed version (which was 2.0.0), and see if that made a difference.
I had some initial resistance to doing this because I had seriously wanted this installation to be relatively free of clutter, and devoted solely to music-making. So much for that plan. Onward.
So, checking dependencies, I installed what was necessary. Well, there were a few packages, notably, “nyquist:i386”, and “libavcodec53”, which caused synaptic to desire to uninstall, among other things, the entire KXStudio meta. So, I declined to install these “dependencies” (and ask, maybe therein lies further clue to this 'problem'?)
I compiled 'audacity 2.0.1' with success.
Running it, I experienced the same lack of 'audacity' to recognize 'jack', the same stopping of 'jack' when 'audacity' was run, and no real difference that I could easily detect. :sadness:
Despite this travail, I think I am going to stick with KXStudio. Damn. What are the options other than 'audacity'? I don't want/need another learning curve. I still hope to resurrect 'audacity'. That would make life nearly perfect, except for the nvidia driver issue. Heh
Thanks again, falkTX.