(probably a stupid) reflexion about bitwig-studio

[krsn]

sorry, i didn't follow the "bws-soap-opera" about linux that's going on out there, and i just pop here with a (maybe already) stupid question, in relation with it's installation on kxstudio (because that's the os i'm using on my main workstation, obviously): is the midi implementation just a teaser for an eventual more glowing future of the bitwig linux development or is it a real bug?

i asked a question (not that one) about the issue i'm having on kvr, and (probably because it was too "nooby" of a question, who knows...) i got no answer. so, i'm trying here, maybe some good soul will understand and help...

ok. i install the daw, configure it as i think it should be (jack-audio-connection kit as audio system, system as input and output device, select my controllers (launchpad mini and umx610) and everything works just great, but this lasts until i restart my computer. then, no midi at all. everything works, except for the midi part (controllers that is).

is that normal?

krsn

[StudioDave]

Greetings,

Your controllers may be autorecognized but they aren't autoactivated. Make sure you've selected one as an input device for your track(s) and that its I/O is configured properly.

If that doesn't fix things I may not understand clearly what's happening there.

And btw, there are no stupid questions/reflexions here (or on KVR either). When you don't know, ask away, it's what we're here for.

Best,

dp

[krsn]

the thing is that everything worked just fine right after the installation. doesn't that mean that i set it up correctly at the beginning?

[krsn]

in fact, it's probably the dependencies that were installed and the jack1 dependencies that were removed that created the problem. seems logical since a reboot was probably required to load the "correct" jack settings implied by the bws install. I didn't do that right away, so I figure bws was running with the native kxstudio jack settings - or something like that - that remained in the background. so...

now what?

[krsn]

solved my problem (sorry to expose all my sorrows in public about that, but hey, if it can help - yes, noobs CAN help noobs... sometimes...): i switched off alsa bridge in cadence (selected "none" under "jack bridges") and everything worked.
accidentally stumbled on the answer while reading about something else...

[StudioDave]

solved my problem (sorry to expose all my sorrows in public about that, but hey, if it can help - yes, noobs CAN help noobs... sometimes...): i switched off alsa bridge in cadence (selected "none" under "jack bridges") and everything worked.
accidentally stumbled on the answer while reading about something else...

Perhaps you could post an account of your experience in the BWS forum at KVRaudio too ? Some of the Linux users there might need to know about this.

Best,

dp

[krsn]

right.
just did.

[StudioDave]

right.
just did.

Thanks !

dp

[Excds]

Maybe a link to your post on kvr?

[krsn]

http://www.kvraudio.com/forum/viewtopic ... 9&t=412667