Call for Testing - Cadence pre-Beta

Unofficial support for the KXStudio Linux distribution and applications.
More info at http://kxstudio.linuxaudio.org/

Moderators: MattKingUSA, khz

hellalive
Established Member
Posts: 91
Joined: Mon Nov 29, 2010 7:10 pm

Re: Call for Testing - Cadence pre-Beta

Post by hellalive »

I'm a little late, been buisy the last days. So, I have to say that the problem is still here, here we go with my aplay -l

Code: Select all

federico@federico-desktop:~$ aplay -l
**** Lista di PLAYBACK dispositivi hardware ****
scheda 0: SB [HDA ATI SB], dispositivo 0: VT1818S Analog [VT1818S Analog]
  Sottoperiferiche: 0/1
  Sottoperiferica #0: subdevice #0
scheda 0: SB [HDA ATI SB], dispositivo 1: VT1818S Digital [VT1818S Digital]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
scheda 0: SB [HDA ATI SB], dispositivo 2: VT1818S HP [VT1818S HP]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
scheda 1: Loopback [Loopback], dispositivo 0: Loopback PCM [Loopback PCM]
  Sottoperiferiche: 8/8
  Sottoperiferica #0: subdevice #0
  Sottoperiferica #1: subdevice #1
  Sottoperiferica #2: subdevice #2
  Sottoperiferica #3: subdevice #3
  Sottoperiferica #4: subdevice #4
  Sottoperiferica #5: subdevice #5
  Sottoperiferica #6: subdevice #6
  Sottoperiferica #7: subdevice #7
scheda 1: Loopback [Loopback], dispositivo 1: Loopback PCM [Loopback PCM]
  Sottoperiferiche: 8/8
  Sottoperiferica #0: subdevice #0
  Sottoperiferica #1: subdevice #1
  Sottoperiferica #2: subdevice #2
  Sottoperiferica #3: subdevice #3
  Sottoperiferica #4: subdevice #4
  Sottoperiferica #5: subdevice #5
  Sottoperiferica #6: subdevice #6
  Sottoperiferica #7: subdevice #7
scheda 2: NVidia [HDA NVidia], dispositivo 3: HDMI 0 [HDMI 0]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
scheda 2: NVidia [HDA NVidia], dispositivo 7: HDMI 0 [HDMI 0]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
scheda 2: NVidia [HDA NVidia], dispositivo 8: HDMI 0 [HDMI 0]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
scheda 2: NVidia [HDA NVidia], dispositivo 9: HDMI 0 [HDMI 0]
  Sottoperiferiche: 1/1
  Sottoperiferica #0: subdevice #0
It seems to see quit everything, but I cannot select anything in cadence - I simply wrote manually hw:0 and jack started..

Anyway, there also two other minor bugs that still occur to me in claudia: this and this. Nothing major.
He had a lot of nithing to say, we'll miss him
User avatar
GraysonPeddie
Established Member
Posts: 657
Joined: Sun Feb 12, 2012 11:12 pm
Location: Altha, FL
Been thanked: 6 times
Contact:

Re: Call for Testing - Cadence pre-Beta

Post by GraysonPeddie »

Code: Select all

if language == "English" then ...
else if language == "Spanish (Spain)" then ...
else if language == "Spanish (Mexico)" then ...
else if language == "German" then ...
else if language == "French" then ...
else if language == "Italian" then ...
else if language == "Japanese" then ...
else if language == "Greek" then ...
etc.
end if
--Grayson Peddie

Music Interest: New Age w/ a mix of modern smooth jazz, light techno/trance & downtempo -- something Epcot Future World/Tomorrowland-flavored.
hellalive
Established Member
Posts: 91
Joined: Mon Nov 29, 2010 7:10 pm

Re: Call for Testing - Cadence pre-Beta

Post by hellalive »

Ok it works with

Code: Select all

env LANG=C cadence-jacksettings
eheh. Great job! For everything!
He had a lot of nithing to say, we'll miss him
b4rney
Established Member
Posts: 31
Joined: Sat May 26, 2012 10:32 am

Re: Call for Testing - Cadence pre-Beta

Post by b4rney »

falkTX wrote:It seems to me that the new device-discovery method (calling "aplay -l") doesn't actually report all ALSA devices.
You showed me your previous output of 'aplay -l', but hw:3 is not listed there. How is this possible?
It is no longer attached ... this is my point. If a claudia/ladish session is saved with a device which is then removed, it used to be easy to simply reconfigure jack and the session would instantly continue.

All this week I have not been able to restore the session no matter what I do.
See this video:
http://youtu.be/THU3y_4FhbE
falkTX wrote:You can force cadence-jacksettings to use the old method for querying interfaces (asking jackdbus).
Edit this file:

Code: Select all

/usr/share/cadence/src/jacksettings.py
and almost at the top change:

Code: Select all

if "linux" in platform:
to:

Code: Select all

if False:
This fixed my problem. After this fix loading a saved ladish session with removed hardware devices is easy. First it fails. Then I reconfigure jack and the session springs to life. This is how it used to work.
See this video:
http://youtu.be/tR96AR7k-vo

Hope this helps.
Cheers
Barney
b4rney
Established Member
Posts: 31
Joined: Sat May 26, 2012 10:32 am

Re: Call for Testing - Cadence pre-Beta

Post by b4rney »

Hi falkTX,
Thanks for the quick response.
falkTX wrote:but first, can you confirm me that the hardware/device detection is working now?
both the old method and new one only show hw:Intel (hw:0) devices...
Yes. With the new version my usb device is instantly detected when plugged in. Loopback devices are ignored too.
falkTX wrote:To get around the ladish crash bug, you can edit the studio file manually.
Thanks for the advice. It's a shame this no longer works using the ui as before (second video). I imagine this will affect a lot of users with multiple devices or shared sessions.

Like you said, this isn't directly a bug with Cadence but the new hardware detection has triggered a bug that wasn't obvious before. If I use the new method I am forced to manually edit the ladish studio files for them to work.

Thanks for your help with this. :D
Barney
b4rney
Established Member
Posts: 31
Joined: Sat May 26, 2012 10:32 am

Re: Call for Testing - Cadence pre-Beta

Post by b4rney »

Just found another fix for this without editing files.

I launch my claudia/ladish session .... jack crashes.

I then launch QjackCtl, configure my preferred interface and the session launches instantly.
Hope this helps someone.
Barney
b4rney
Established Member
Posts: 31
Joined: Sat May 26, 2012 10:32 am

Re: Call for Testing - Cadence pre-Beta

Post by b4rney »

falkTX wrote:Anyway, this is why ladish has rooms vs studios. Studios define an entire JACK setup, while rooms are used for "projects inside the studio".
You should create studios for different hardware setups, but use the rooms for projects.
I didn't know this. I've been creating a studio per song. I will do this from now on.

Now I can get back to work!
Many thanks Filipe.
Barney
hellalive
Established Member
Posts: 91
Joined: Mon Nov 29, 2010 7:10 pm

Re: Call for Testing - Cadence pre-Beta

Post by hellalive »

I've been working like this with ladish too, and never understood completly why rooms and projects were actually there. I guess some more documentation about it would be nice. :/
He had a lot of nithing to say, we'll miss him
stanlea
Established Member
Posts: 700
Joined: Wed Apr 25, 2012 9:49 pm
Has thanked: 41 times
Been thanked: 23 times

Re: Call for Testing - Cadence pre-Beta

Post by stanlea »

Ubuntu 12.04.1 64 bits
kernel 3.2.0-23 realtime
xfce

Lauching cadence -> logs produces intense HD activity, freezes the mouse and crash
skavar
Established Member
Posts: 97
Joined: Sat Sep 15, 2012 9:21 am

Re: Call for Testing - Cadence pre-Beta

Post by skavar »

Slight problem: right click cadence icon in system tray, click tools then catia, opens catarina :?
landry
Established Member
Posts: 7
Joined: Mon May 21, 2012 4:28 pm

Re: Call for Testing - Cadence pre-Beta

Post by landry »

Having some issue with starting jack at times.

Running on a Lenovo T61 (dual core, 4GB mem) Have installed Ubuntu Studio 12.04 then upgraded using KXStudio repositories (following docs on the KXStudio web site -> Documention, upgrading from an existing Ubuntu install)

IN the system I have my internal sound card and have plugged in a USB headset (headphones and mic) and a M-Audio Solo firewire soundcard (all plugged in at boot time.)

I seem to be able to start/stop jack and move between the internal and USB sound cards - get some issues with at times getting a message about not being able to stop jack, but it does stop anyway and usually can be restarted - but when I start the firewire sound card, then stop it, that's the last time I can start jack until I reboot the system.

Not at home right now so I can't give the exact details, just wondering what would be the best way to go about gathering the information you would need to troubleshoot the cause? Any suggestions?
wolftune
Established Member
Posts: 1350
Joined: Fri Feb 24, 2012 7:40 pm
Location: Portland, OR
Been thanked: 2 times
Contact:

Re: Call for Testing - Cadence pre-Beta

Post by wolftune »

I just started some testing and had several issues.

First of all, I had a MIDI note hang from playing the VMPK into Calf Organ, and I forget if there's any kill-notes option anywhere. It would be great if Catia and other JACK programs included a button to just send a MIDI kill signal across all MIDI connections.

I had some crashing but sorry I can't be more specific about the causes.

Last thing: I can open the simple mono sampler (the one that works in Rosegarden) in Carla, but it won't open the GUI so there's no way to load a sample.

Best,
Aaron
Aaron Wolf
Music teacher, scholar
http://wolftune.com
landry
Established Member
Posts: 7
Joined: Mon May 21, 2012 4:28 pm

Re: Call for Testing - Cadence pre-Beta

Post by landry »

falkTX wrote:
landry wrote:Having some issue with starting jack at times.

......
I know about this and already reported to nedko, it's a known bug in jackdbus code (still present on the upcoming v1.9.9 version).
jackdbus sometimes crashes when quitting, thus not unlocking the soundcard properly. Cadence detects when such things happens and warns you.
This is not something I can fix myself, we have to wait for a fix/workaround on jack's code directly.
Thanks falkTX .. going to mess around with jack_control and see if there are any workarounds.

BTW: Don't know if you saw this before, but looks like it could be an interesting potential feature to add (assuming it works as shown.) http://rg42.org/blog/jack2dbus
wolftune
Established Member
Posts: 1350
Joined: Fri Feb 24, 2012 7:40 pm
Location: Portland, OR
Been thanked: 2 times
Contact:

Re: Call for Testing - Cadence pre-Beta

Post by wolftune »

falkTX wrote:
wolftune wrote:Last thing: I can open the simple mono sampler (the one that works in Rosegarden) in Carla, but it won't open the GUI so there's no way to load a sample.
The GUI opens fine here, but I can see the note being stuck.

Perhaps carla should be built in debug mode for now?
Maybe. I don't know about that, but here's what happened for me. I can open Carla's editor but the button that is supposed to open the simple mono sampler's custom GUI, I just press it and nothing happens. It looks like it is being pressed, but no GUI window comes up.
Aaron Wolf
Music teacher, scholar
http://wolftune.com
User avatar
DoosC
Established Member
Posts: 268
Joined: Tue Apr 20, 2010 8:28 pm
Location: Saeul, Grand Duchy of Luxembourg
Has thanked: 5 times
Been thanked: 1 time
Contact:

Re: Call for Testing - Cadence pre-Beta

Post by DoosC »

falkTX wrote:I believe all GUIs should work again.
UIs are back for good, no issues with LV2 and VST but I can't get any UI for DSSI plugins (I tried WhySynth, Calf, Hexter, etc) and no errors show up in the terminal... it is like carla thinks it launches the UI but in fact nothing shows up.

Any similar issues guys or is it just me ?
| DoosC |
Post Reply