Cadence refuses to work with my Fiio E10K

[SiG]

http://postimg.org/image/gg93dhsyp/
try it, you can set real time priority to about 50.

http://i.imgur.com/pPNBmWZ.png

I'm just about ready to flip a table..

[artek]

Do it as described in the image, try to set real time priority to 50 or even 89.

[SiG]

I've done that since taking that screenshot.

I think the larger problem is that Cadence seems to have issues remembering the JACK configuration. Look at the screenshot, and compare the two logs in it, and you'll see that JACK starts with different parameters than it's supposed to.

In the first log:

Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'device' to value "hw:Audio,0"
Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'capture' to value "none"
Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'playback' to value "none"
Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'period' to value "1024"
Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'nperiods' to value "2"

Which then becomes:

Fri Aug 21 20:01:51 2015: creating alsa driver ... hw:Audio,0|hw:Audio,0|1024|2|48000|0|0|nomon|swmeter|-|32bit

The second audio device must be a capture or playback device, but I didn't set any.

In the second log:

Fri Aug 21 20:02:54 2015: setting parameter 'drivers':'alsa':'device' to value "hw:Audio,0"
Fri Aug 21 20:02:54 2015: setting parameter 'drivers':'alsa':'capture' to value "none"
Fri Aug 21 20:02:54 2015: setting parameter 'drivers':'alsa':'playback' to value "none"
Fri Aug 21 20:02:54 2015: setting parameter 'drivers':'alsa':'period' to value "1024"
Fri Aug 21 20:02:54 2015: setting parameter 'drivers':'alsa':'nperiods' to value "2"

Which somehow ends up as:

Fri Aug 21 20:02:54 2015: creating alsa driver ... hw:Audio,0|hw:Audio,1|128|4|48000|0|0|nomon|swmeter|-|32bit

Again, there's a capture/playback device which I didn't set. Also, the buffer size is completely wrong.

Also note that the first instance of JACK failed to start, while the second one didn't. Why?

[artek]

set everything as on the picture
http://postimg.org/image/gg93dhsyp/
try to set priority to 50 or 89, somehow you are able resist it
from the first log:

Code: Select all

Fri Aug 21 20:01:50 2015: setting parameter 'drivers':'alsa':'nperiods' to value "2"

you have set the periods to 2 and priority to 10

[SiG]

I've done that since taking that screenshot.

Also, the purpose of the screenshot was to illustrate that Cadence is not remembering the JACK configuration correctly.

[SiG]

when you do force-restart you might lose some previous settings that were not saved on time.
use start and stop if you can, leave force restart for serious issues only.

It doesn't just happen after a Force Restart. Even when starting Cadence normally, there's always a playback or capture device in use that I didn't specify, just like in the logs I've posted previously.

Sorry for replying so late.