DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)
-
- KVRAF
- 12083 posts since 2 Dec, 2004 from North Wales
When I get this message I unplug the USB and plug it back in and it has worked.
X32 Desk, i9 PC, S88MK3, S1, BWS, Live + PUSH 3, Osmose, RedShift 6 Pro3, Tempera, Syntakt, Digitone II, OP1-F, OPXY, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!
-
- KVRAF
- 6533 posts since 9 Dec, 2008 from Berlin
That message is as old as windows itself - and totally misleading.
Most of the time it means, that more than one app is trying to access a midi port.
Not sure how it applies here though.
Cheers,
Tom
Most of the time it means, that more than one app is trying to access a midi port.
Not sure how it applies here though.
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
-
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
This looks all good. Also did test it again and don't see any issue.Gummiball wrote: Fri Jun 12, 2020 4:05 pm Hello.
Sorry for my bad english.
Today my Launchpad Pro MK3 arrives and I want to test the behavior with Bitwig. At the moment I can get it to run.
This are the settings for Launchpad Pro MK3 wich was autodetected:
Are you on the latest Firmware 1.1.1?
-
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
So, you get also mutliple instances of the extension for the controller?Axis08 wrote: Sat Jun 13, 2020 9:26 am I'm using Bitwig 3.2.1 (Windows 10) and have the same problem as deailes and Raketenbauer for my midi controller - Native A61
"Komplete Kontrol A61 Midi : Could not open MIDI Ouptut. There is not enough memory available for this task. Quit one or more applications to increase available memory, and then try again".
Even if I get this message at every Bitwig launch I can play with the controller.
Do you have power connected to the Push 2? That is normally the behaviour if it is only powered via USB.Axis08 wrote: Sat Jun 13, 2020 9:26 am Also I do have a problem with my Push2 and the hardware push buttons only light up if I press one (for example the Browser button is always dark until I press it). Quite hard to use the push2 then.
-
- KVRist
- 85 posts since 10 Jul, 2012
Hi Jürgen,
yesterday I got a brand new Novation 61SL MK3 and I think I found a bug in your script. I created some device pages for some VSTs in this case NI's RC-48 but the plugin doesn't matter. I mapped the parameters I liked to the pages and renamed some of them. But the SL MK3 does shows only show up the original parameter name of the of the plugin, not my renamed! There is also a SL MK2 here and this one shows up the right, renamed parameter name. I hope you understand. I wish I could write in German language, would be quiet easier to explain.
I made a screenshot:
yesterday I got a brand new Novation 61SL MK3 and I think I found a bug in your script. I created some device pages for some VSTs in this case NI's RC-48 but the plugin doesn't matter. I mapped the parameters I liked to the pages and renamed some of them. But the SL MK3 does shows only show up the original parameter name of the of the plugin, not my renamed! There is also a SL MK2 here and this one shows up the right, renamed parameter name. I hope you understand. I wish I could write in German language, would be quiet easier to explain.
I made a screenshot:
- The parameter that I mapped
- The original parameter name of the plugin
- The renamed, mapped parameter
- What shown in the old SL MK2
- What shows up in the SL MK3
You do not have the required permissions to view the files attached to this post.
Last edited by AFranke on Sat Jun 13, 2020 5:56 pm, edited 1 time in total.
-
- KVRist
- 85 posts since 10 Jul, 2012
Some additional Information. After restarting BWS the right parameter Names where shown up. But: the parameter can't be changed from the SL MK3 anymore! Seems to be the same problem I reported some days ago, where I had trouble with mapping some parameters of Arturias SEM V. The funny thing in this case is, that while the original mapping process the parameter could be changed from the SL MK3, but after restarting BWS not at all!AFranke wrote: Sat Jun 13, 2020 5:38 pm Hi Jürgen,
yesterday I got a brand new Novation 61SL MK3 and I think I found a bug in your script. I created some device pages for some VSTs in this case NI's RC-48 but the plugin doesn't matter. I mapped the parameters I liked to the pages and renamed some of them. But the SL MK3 does shows only show up the original parameter name of the of the plugin, not my renamed! There is also a SL MK2 here and this one shows up the right, renamed parameter name.
Last edited by AFranke on Sat Jun 13, 2020 5:57 pm, edited 1 time in total.
-
- KVRist
- 85 posts since 10 Jul, 2012
Next problem with mapping parameters to a device page. Mapped the midi channel selector of a hardware device to a device page. If I move the knob it shows and set up wrong values.
The right Values should be:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16
What the script show in the display:
Ch 1,Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15
What the script sets up in the hardware device:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16
The right Values should be:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16
What the script show in the display:
Ch 1,Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15
What the script sets up in the hardware device:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16
-
- KVRer
- 16 posts since 30 Dec, 2014
That was the problem. Thank you.moss wrote: Sat Jun 13, 2020 5:27 pmThis looks all good. Also did test it again and don't see any issue.Gummiball wrote: Fri Jun 12, 2020 4:05 pm Hello.
Sorry for my bad english.
Today my Launchpad Pro MK3 arrives and I want to test the behavior with Bitwig. At the moment I can get it to run.
This are the settings for Launchpad Pro MK3 wich was autodetected:
Are you on the latest Firmware 1.1.1?
-
- KVRist
- 85 posts since 10 Jul, 2012
Another thing I realized. I'm running the SL MK3 sequencer (slave) in sync to Bitwig (master). I press play in Bitwig an it starts up its sequence together with BWS and runs as expected, but if you switch from track view to device view and vice versa, the hardware sequencer of the SL stops running while BWS goes on. This is a absolute show stopper, isn't it?
Addition: Sometimes it comes to hanging notes while the sequencer stops unexpected. The Seqencer also sometimes stops running if I switch between the green mode where I can select a device and purple mode where I can select the device pages.
Addition: Sometimes it comes to hanging notes while the sequencer stops unexpected. The Seqencer also sometimes stops running if I switch between the green mode where I can select a device and purple mode where I can select the device pages.
-
- KVRer
- 11 posts since 4 Mar, 2018
Thanks ! ! !Do you have power connected to the Push 2? That is normally the behaviour if it is only powered via USB.
Yes I do, so I cleared every duplicate but the message is still there.So, you get also mutliple instances of the extension for the controller?
-
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
I tried with several plugins and parameters but cannot reproduce the issue. I don't have the plugin you use. Anyway, could be a little bug in Bitwig with caching the values. You can try to report it to support.AFranke wrote: Sat Jun 13, 2020 5:38 pm I made a screenshot:
- The parameter that I mapped
- The original parameter name of the plugin
- The renamed, mapped parameter
- What shown in the old SL MK2
- What shows up in the SL MK3
-
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
I am afraid I cannot do anything about it. Don't think that Novation tested this use-case intensively.AFranke wrote: Sat Jun 13, 2020 6:16 pm Another thing I realized. I'm running the SL MK3 sequencer (slave) in sync to Bitwig (master). I press play in Bitwig an it starts up its sequence together with BWS and runs as expected, but if you switch from track view to device view and vice versa, the hardware sequencer of the SL stops running while BWS goes on. This is a absolute show stopper, isn't it?
Addition: Sometimes it comes to hanging notes while the sequencer stops unexpected. The Seqencer also sometimes stops running if I switch between the green mode where I can select a device and purple mode where I can select the device pages.
-
- KVRist
- 43 posts since 12 Jan, 2019 from Zwolle
Hello,
Request to add a different knob/slider behaviour in Flexi: Manual synced fader
The current implementation seems to send every value from a non-motor fader knob without "respecting" the project setting.
Example:
A controller & bitwig slider are linked to the volume value of the selected track:
1. Midi Controller slider is on 25 (setting from a previous project)
2. Bitwig slider is set to 127 (last save state in the loaded project)
3. When I touch the controller slider bitwig set the track directly to 25 and disrupt the volume setting (127) of the track
Request behaviour:
Flexi only sends values if the slider is first set (or passed) to the current set value (in this case 127).
Results:
Controller slider is on 25 / Bitwig slider is set to 127
Moving the controller up or down does not directly send the 25 value to bitwig.
The slider first needs to pass the current set value (127) before changing the slider in bitwig
Why: this prohibits the unwanted drastic change of current (non-motor fader controllers) on your current project. Also, the slider/knobs position is now first "manually synced" with the project before changes are applied. It the same behaviour as a motor-fader (setting the fader to the current value) but then manually executed.
benefit #2: non-motor faders are now useful in the "selected track" parameters. The current behaviour will first duplicate the previous midi knob/slider setting on your current track if you touch or move the midi controller's knob/slider.
Request to add a different knob/slider behaviour in Flexi: Manual synced fader
The current implementation seems to send every value from a non-motor fader knob without "respecting" the project setting.
Example:
A controller & bitwig slider are linked to the volume value of the selected track:
1. Midi Controller slider is on 25 (setting from a previous project)
2. Bitwig slider is set to 127 (last save state in the loaded project)
3. When I touch the controller slider bitwig set the track directly to 25 and disrupt the volume setting (127) of the track
Request behaviour:
Flexi only sends values if the slider is first set (or passed) to the current set value (in this case 127).
Results:
Controller slider is on 25 / Bitwig slider is set to 127
Moving the controller up or down does not directly send the 25 value to bitwig.
The slider first needs to pass the current set value (127) before changing the slider in bitwig
Why: this prohibits the unwanted drastic change of current (non-motor fader controllers) on your current project. Also, the slider/knobs position is now first "manually synced" with the project before changes are applied. It the same behaviour as a motor-fader (setting the fader to the current value) but then manually executed.
benefit #2: non-motor faders are now useful in the "selected track" parameters. The current behaviour will first duplicate the previous midi knob/slider setting on your current track if you touch or move the midi controller's knob/slider.
-
- KVRist
- 85 posts since 10 Jul, 2012
Hmm, that's funny, because in Ableton Live this Problem does not exist. So it seems to me there is a problem with BWS or the script. Is there a way to debug this in any way and get it fixed? The same problem exist on pushing the Opions button btw.moss wrote: Sun Jun 14, 2020 9:25 amI am afraid I cannot do anything about it. Don't think that Novation tested this use-case intensively.AFranke wrote: Sat Jun 13, 2020 6:16 pm Another thing I realized. I'm running the SL MK3 sequencer (slave) in sync to Bitwig (master). I press play in Bitwig an it starts up its sequence together with BWS and runs as expected, but if you switch from track view to device view and vice versa, the hardware sequencer of the SL stops running while BWS goes on. This is a absolute show stopper, isn't it?
Addition: Sometimes it comes to hanging notes while the sequencer stops unexpected. The Seqencer also sometimes stops running if I switch between the green mode where I can select a device and purple mode where I can select the device pages.
-
- KVRAF
- 9544 posts since 6 Jan, 2017 from Outer Space
To make the external sequencer stop needs an information sent via Midi to the SL... Try to monitor the Midi stream to the SL, then you'd know. I doubt this has to do with the script, it might be Bitwig. If you figured what triggers the stop, send a report to support and demand a fix...