Hello,
I've been delaying this question because the problems I have been having are not easy to grasp, I don't know exactly what is happening.
I have made a pretty straightforward midi controller with a Teensy, with nine encoders and some pushbuttons.
The midi output I get from it is clean, I've checked it with midi monitoring software.
The thing is the encoders and buttons work just fine setting actions like "Device: Set Parameter 1", or "Device: Select Next Parameter Page".
But when I try with the Transport actions, I am not getting a consistent result. For example, on the preset I'm making, assigning a button to "Transport: Toggle clip automation write" this button is ignored when I push it. If I deactivate this controller and create a new one and only create this assignation, it works fine.
Or with "Transport: Play", that never works. I've tried it on a Linux PC and on a Windows PC, with different versions of DrivenByMoss and different versions of Bitwig (4.3 and 4.4), and it doesn't work. I even made a quick PureData patch that sends a midi CC when I pushed a bang button and it worked with other actions, but never with "Transport: Play".
Is there anything I'm overseeing, or does this script do this stuff sometimes?
Any ideas?
Problems with Transport functions on Flexi script
-
- KVRer
- 22 posts since 7 Nov, 2016
-
- KVRer
- Topic Starter
- 22 posts since 7 Nov, 2016
Ok like always, I spend days with a problem, and the moment I decide to ask on the internet I come up with a new idea to try.
I just connected a NanoKontrol1 and made a new Flexi controller, and play button works.
But it works different than the rest of the buttons. The play button activates when the button is released after the press. With the rest of the functions they toggle when the button is pressed.
At least I know why Play is not working on my controller, since I didn't write code for when buttons are released, I'll do that tomorrow.
Still, that doesn't answer why sometimes the "Transport: Toggle clip automation write" works and other times it doesn't.
Oh, and I forgot, another weird behavior I'm getting is that sometimes the button I assigned to this function does other function, like for example select next parameter page.
I'm making sure the CCs are unique for each button, and that I am selecting a new slot for every button / function, and saving the preset all the time.
I just connected a NanoKontrol1 and made a new Flexi controller, and play button works.
But it works different than the rest of the buttons. The play button activates when the button is released after the press. With the rest of the functions they toggle when the button is pressed.
At least I know why Play is not working on my controller, since I didn't write code for when buttons are released, I'll do that tomorrow.
Still, that doesn't answer why sometimes the "Transport: Toggle clip automation write" works and other times it doesn't.
Oh, and I forgot, another weird behavior I'm getting is that sometimes the button I assigned to this function does other function, like for example select next parameter page.
I'm making sure the CCs are unique for each button, and that I am selecting a new slot for every button / function, and saving the preset all the time.
-
- KVRer
- Topic Starter
- 22 posts since 7 Nov, 2016
Hi again,
It seems like after cleaning up my code and making the push buttons send value 127 when pushed and value 0 when released has made everything work just fine
Another problem I was having was that the teensy was freezing when used with bitwig. After setting both "Send value to device" options to OFF on every slot it is not happening anymore. I guess the teensy doesn't love receiving midi messages if it is not told what to do with them.
It seems like after cleaning up my code and making the push buttons send value 127 when pushed and value 0 when released has made everything work just fine
Another problem I was having was that the teensy was freezing when used with bitwig. After setting both "Send value to device" options to OFF on every slot it is not happening anymore. I guess the teensy doesn't love receiving midi messages if it is not told what to do with them.
-
- KVRAF
- 9560 posts since 6 Jan, 2017 from Outer Space
Show us some pictures of your controller… Seems a fun project…
-
- KVRer
- Topic Starter
- 22 posts since 7 Nov, 2016
Sure! Here it is:
https://www.instagram.com/p/ClCRR9eOuUy ... MyMTA2M2Y=
The two buttons on the top left select the track. The big knob changes track volume, or pan if shift (bottom right button) is pressed.
Three buttons to the right of the big knob are arm, solo, mute.
The top right buttons select the macro page of the selected device (middle ones), and the ones to the sides select next/previous device in the selected track.
Buttons also have a secondary function if shift is pressed, like add device to the right, add device to the left, toggle clip automation record, stuff like that.
Oh and the encoders move the macro knobs of the selected Page in the selected device in the selected track.
I'm loving the workflow, I wish I had known about this Flexi script before
Daw controllers are many times sold as devices that let you not have to look at the screen. This is exactly the opposite, I made it with the intention of not having to take my eyes off the screen.
Now I work with my left hand on this controller and the right hand on the mouse, keyboard in the middle and launchpad behind the keyboard, and I'm loving it so far))
https://www.instagram.com/p/ClCRR9eOuUy ... MyMTA2M2Y=
The two buttons on the top left select the track. The big knob changes track volume, or pan if shift (bottom right button) is pressed.
Three buttons to the right of the big knob are arm, solo, mute.
The top right buttons select the macro page of the selected device (middle ones), and the ones to the sides select next/previous device in the selected track.
Buttons also have a secondary function if shift is pressed, like add device to the right, add device to the left, toggle clip automation record, stuff like that.
Oh and the encoders move the macro knobs of the selected Page in the selected device in the selected track.
I'm loving the workflow, I wish I had known about this Flexi script before
Daw controllers are many times sold as devices that let you not have to look at the screen. This is exactly the opposite, I made it with the intention of not having to take my eyes off the screen.
Now I work with my left hand on this controller and the right hand on the mouse, keyboard in the middle and launchpad behind the keyboard, and I'm loving it so far
))