So happy these are helpful!

Do you know if it is possible with a fader/rotary or encoder knob to sent a midi message when turned to the right and a different midi message when turned to the left?

I figured it out, just set the trigger to rise and the other to fall

Glad you liked it!

Glad the tips help!

hahaha, alright, we'll see what I can conjure up!

Nice work! I do have a video of Cubase on the way, but yes this is possible. 1st make sure that Cubase is sending MIDI messages. In TouchOSC are you Faders set to receive messages?

@@TimCorpus Thanks for replying Tim! Yep, it's set to receive, so there must be something else I've missed.

@@Vindsvept Ok, sorry that didn't fix it. Stay tuned, a Cubase video is in the works.

@@TimCorpus Thank you Tim!

So you could check out Felix's BPM_tap template he made (github.com/F-l-i-x/TouchOSC/tree/main/examples/bpm_tap) In order to have it light up, probably the best thing would be to have a script that tells a box behind the button to flash a color at a rate that is equal to your BPM listed in the label.

No, TouchOSC doesn't have image support yet, but people have made images by drawing with small blocks in the template to make it looks like an image

So you're trying to send OSC messages but need them changed into MIDI? Why not just send MIDI messages from TouchOSC and skip the hassle? Also, any sort of translation would always add lag. There may be a way to do that in a Mac, but mostly I see people going the other way around, MIDI to OSC.

@@TimCorpus that's naturally true. I also think it's better to send midi from TouchOSC to MIDI based vst inputs. In my case it's all about the time to spend into building the new templates adding midi messages insted of osc messages. (about 50s parameters...) trying to avoid conflicts and so on...mapping etc etc. Many times I find OSC templates already done but for midi based vst so that's the main reason . I' ll give a little try with "OSC Midi Server Pro - Ocean Swift Synthesis" and I'll see wich method is better. By the way, take it as a suggestion, I think that if Plogue-Bidule is mentioned as TouchOSC compatible application should have a little tutorial to manage with some routing examples with some OSC messages inside it , using some bidule functions or patches... dont you think?

@@daysofradiation ya Hexler can definitely add some more tutorials to their site. The lack of information is actually why I started this series. They have an intake form for suggestions. I'm not affiliated with the company at all, I just make production videos about the software for free on my own time. 🤷

Same thing it seems from plogue-bidule side ,maybe they will implement some user friendly functions as OSC learn combined with actual midi learn to ease some workflows…

No there really isn't anything covered in the manual. The scripting language is Lua and basically I've just picked up things from others on the forums, some research and other coders. Maybe I'll address some of this stuff in a next video.

@@TimCorpus ya that would be great. I'm just starting to convert a large Lemur template to TouchOSC and it's a huge PITA having to learn a new language without the help of a real manual from TouchOSC. So thank you for all your videos, they are a life savor at the moment!

@@tylerwesten6059 ya no problem! This stuff is definitely confusing.

@@TimCorpus if you wouldn't mind pointing me in the direction of where you found some helpful scripting info that would be awesome.

@@devsalter ya check out some of the resources I listed in my new video. There are some new sites with scripts, modules, and templates. If you're looking for Lua support, there are some great KZfaq videos talking about syntax and such.