. Yea we could ask the developer, or maybe there's a responsive css override possible. Otherwise I'd stick with 1024x768. I noticed in the ardour template, the sliders were a bit dynamic depending on the resolution.Open Sound Control (OSC) is here
-
- KVRist
- 64 posts since 29 Jan, 2018
Nice . Yea we could ask the developer, or maybe there's a responsive css override possible. Otherwise I'd stick with 1024x768. I noticed in the ardour template, the sliders were a bit dynamic depending on the resolution.
. Yea we could ask the developer, or maybe there's a responsive css override possible. Otherwise I'd stick with 1024x768. I noticed in the ardour template, the sliders were a bit dynamic depending on the resolution.-
- KVRist
- 71 posts since 26 Nov, 2017
I was wondering if I could request some additions to the open sound control commands here?
feature requests
\\\
click volume would be awesome
insert scene from playing
play position that could be moved back and fourth with a single fader or rotary
post record action / delay
device page names
some way to force touch osc to check all the values without moving the clip window or track cursor around as sometimes when switching projects it doesn't refresh the touch osc display until the cursor is moved switching to another project works sometimes but only if there is a project to switch to
///
would it be possible to have /device/param/page/{1-8} ? So we could have a whole page of fader banks of 8 dedicated to each page of a selected device? I dont know if thats something bitwig can do but it might be cool rather then switching?
bugs
isQueued does not seem to work with LED feedback
is selected sometimes gets messed up and skips a couple tracks or gets stuck on
tracks with the same name confuse the isRecording hasContent etc. feedback
track/{1-8}/enter only enters the track the cursor is on not the one specified in the address
/track/selected/mute -- /track/selected/solo -- /track/selected/record don't seem to work
sends are not updating on tablet when new project is loaded or when track bank is moved
what does the indicate function do? Iive tried a few things but I can't seem to get it.
once I have it polished up Ill upload it for who ever wants it.
thanks very much for the support
feature requests
\\\
click volume would be awesome
insert scene from playing
play position that could be moved back and fourth with a single fader or rotary
post record action / delay
device page names
some way to force touch osc to check all the values without moving the clip window or track cursor around as sometimes when switching projects it doesn't refresh the touch osc display until the cursor is moved switching to another project works sometimes but only if there is a project to switch to
///
would it be possible to have /device/param/page/{1-8} ? So we could have a whole page of fader banks of 8 dedicated to each page of a selected device? I dont know if thats something bitwig can do but it might be cool rather then switching?
bugs
isQueued does not seem to work with LED feedback
is selected sometimes gets messed up and skips a couple tracks or gets stuck on
tracks with the same name confuse the isRecording hasContent etc. feedback
track/{1-8}/enter only enters the track the cursor is on not the one specified in the address
/track/selected/mute -- /track/selected/solo -- /track/selected/record don't seem to work
sends are not updating on tablet when new project is loaded or when track bank is moved
what does the indicate function do? Iive tried a few things but I can't seem to get it.
once I have it polished up Ill upload it for who ever wants it.
thanks very much for the support
Last edited by sebastian_blu on Thu Mar 01, 2018 7:14 pm, edited 3 times in total.
-
- KVRist
- 64 posts since 29 Jan, 2018
Here's a little css for open stage control to make it look bitwig ish.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- Topic Starter
- 4889 posts since 13 May, 2004
It turns on the color indication on the related knob or fader in Bitwig to indicate what you are controlling (a little subtile to spot).sebastian_blu wrote:what does the indicate function do? Iive tried a few things but I can't seem to get it.
I will look in the bugs/request as soon as I find some time.
-
- KVRist
- 71 posts since 26 Nov, 2017
cool I've just been adding to the list as I find stuff if that works for you.
here is a copy of the interface in case you can use it to test, the first 5 pages are my focus the the last pages are hold over from chronic engineerings template I am adding to/ may delete.
here is a copy of the interface in case you can use it to test, the first 5 pages are my focus the the last pages are hold over from chronic engineerings template I am adding to/ may delete.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- Topic Starter
- 4889 posts since 13 May, 2004
Yes, that's a current limition in the API. You can only enter the selected track.sebastian_blu wrote: track/{1-8}/enter only enters the track the cursor is on not the one specified in the address
/track/selected was simply not selected, will be in the next update.sebastian_blu wrote: /track/selected/mute -- /track/selected/solo -- /track/selected/record don't seem to work
I checked that these values are sent out correctly, so I guess they are problems with TouchOSC.sebastian_blu wrote: isQueued does not seem to work with LED feedback
is selected sometimes gets messed up and skips a couple tracks or gets stuck on
tracks with the same name confuse the isRecording hasContent etc. feedback
sends are not updating on tablet when new project is loaded or when track bank is moved
-
- KVRAF
- Topic Starter
- 4889 posts since 13 May, 2004
Just released # 5.10!
Requires Bitwig 2.3.
Requires Bitwig 2.3.
- Send
- Added /click/volume
- Added /click/volumeStr
- Added /device/page/selected {1-8}
- Added /device/page/{1-8}/ {name}
- Receive
- Added /click/volume
- Added /scene/create Create a new scene from all playing clips
- Added /position {-2,-1,1,2}
- Added /track/selected/{attribute}
- Added /browser/filter/{1-6}/reset Resets the filter of the column
- Added /device/param/{1-8}/reset
- Added /track/{1-8}/volume/reset
- Added /track/{1-8}/pan/reset
-
- KVRist
- 71 posts since 26 Nov, 2017
thanks for implementing that so quick, i put it into action with some mixed results
all of the receive functions seem to work, but can't test the ones that require feedback on touch OSC because its down
all the sent feedback to touchOSC on the tablet is now not displaying. I triple checked. I put the old extension back in the extension folder to see if the old version still works and receive feedback on tablet is working as it had before.
going back to the old version for some more notes...
sends
---
when I change the send level on bitwig there is no feedback on the send fader on touch osc
I tried all vertical and horizontal faders and none of them update when I move the sends in bitwig. It seems strange because they are the same fader objects that work for pan and volume
----
the master fader only sometimes updates on the touches side when switching projects
----
isQueued
seems odd that leds would light up for hasContent is recording and is selected but not is queued, what should I tell the touchOSC people to look for?
update: i just checked and it doesn't seem to work on the lemur app either, I might switch to lemur though
----
ok thanks again
all of the receive functions seem to work, but can't test the ones that require feedback on touch OSC because its down
all the sent feedback to touchOSC on the tablet is now not displaying. I triple checked. I put the old extension back in the extension folder to see if the old version still works and receive feedback on tablet is working as it had before.
going back to the old version for some more notes...
sends
---
when I change the send level on bitwig there is no feedback on the send fader on touch osc
I tried all vertical and horizontal faders and none of them update when I move the sends in bitwig. It seems strange because they are the same fader objects that work for pan and volume
----
the master fader only sometimes updates on the touches side when switching projects
----
isQueued
seems odd that leds would light up for hasContent is recording and is selected but not is queued, what should I tell the touchOSC people to look for?
update: i just checked and it doesn't seem to work on the lemur app either, I might switch to lemur though
----
ok thanks again
-
- KVRer
- 27 posts since 18 Sep, 2017
OSC doesn't seem to work anymore for me ...
Using PureData it's okay and can see OSC packets flying with Wireshark from the computer to the tablet AND from the tablet to the computer.
When using Bitwig it looks like nothing is transmitted from the computer to the tablet except some /bundle messages between 127.0.0.1 and 127.0.0.1 ...
Tablet to computer works okay and IP address of the tablet within the configuration of the script is correct.
No firewall, no IpTables and tested with two tablets (Android 4.2 and Android 7.1)
It looks like the OSC script never sends anything (bitwig 2.3.1 with up-to-date Moss script)
PEBKAC ?
Using PureData it's okay and can see OSC packets flying with Wireshark from the computer to the tablet AND from the tablet to the computer.
When using Bitwig it looks like nothing is transmitted from the computer to the tablet except some /bundle messages between 127.0.0.1 and 127.0.0.1 ...
Tablet to computer works okay and IP address of the tablet within the configuration of the script is correct.
No firewall, no IpTables and tested with two tablets (Android 4.2 and Android 7.1)
It looks like the OSC script never sends anything (bitwig 2.3.1 with up-to-date Moss script)
PEBKAC ?
-
- KVRist
- 64 posts since 29 Jan, 2018
I was working a bit on an open stage control template today and here it works fine. So with Bitwig 2.3.1 and the latest moss plugin. I had written down some settings if it helps: https://github.com/kdejaeger/open-stage-control-bitwig
-
- KVRAF
- Topic Starter
- 4889 posts since 13 May, 2004
Seems I introduced a bug. The variable is called "value" and not "volume". Will be fixed in the next version.sebastian_blu wrote: sends
---
when I change the send level on bitwig there is no feedback on the send fader on touch osc
That will just given you different bugs. I gave up on both of them.sebastian_blu wrote: update: i just checked and it doesn't seem to work on the lemur app either, I might switch to lemur though
I just started to test with OpenSoundControl and already have a nice mixer going. Also the developer is very responsive!
-
- KVRist
- 71 posts since 26 Nov, 2017
ok yeah the editor seems comprehensive and feature rich doesn't feel clunky like the others. Very exciting. Time to rebuild.
-
- KVRist
- 71 posts since 26 Nov, 2017
cool so if you take out
[
"@{parent.variables.n}"
]
from the osc preArgs section on every element on the mixer it starts working with the bitwig OSC address and you still use @{parent.variables.n} so you don't have to make a bunch copies of the
I have no clue why I was just trying stuff out haha. maybe some kind should could explain what that was doing to break it. or not no matter it works now.
ill post what I get over the next few days. anyone more savy know how to make it so its a full screen app on the tablet? it says its not available and I have to save it to my home screen?
[
"@{parent.variables.n}"
]
from the osc preArgs section on every element on the mixer it starts working with the bitwig OSC address and you still use @{parent.variables.n} so you don't have to make a bunch copies of the
I have no clue why I was just trying stuff out haha. maybe some kind should could explain what that was doing to break it. or not no matter it works now.
ill post what I get over the next few days. anyone more savy know how to make it so its a full screen app on the tablet? it says its not available and I have to save it to my home screen?