I really love OSCPILOT and would love to be able to use it in the future, too. So please forgive me that i’m writing not just one, but a list of feature requests which are based on daily usage of OSCPILOT for a long time, which i think would be of great value to many OSCPILOT users and put it into another league.
Batch-Transformation of Objects:
I spent countless hours of resizing whole interfaces, because only one object can be resized at a time. “Select several objects & Transform size of all together” would be an awesome function. (including objects which are directly layered above each other)
Automatic numbering for OSC address numbers & MultiTextWidget.
I’m building a huge Cliplauncher, consisting of 24 Tracks and 12 Scenes = 288 Clips!
It’s really helpful already, that inserting the # works for automatic numbering!
So /track/1/clip/#/isPlaying works when put into the (Multi)“BUTTONS” Widget! Yay!
Still, it would be awesome to have some sort of automatic add +1 value duplicate function, which makes /track/1/clip/#/hasContent into /track/2/#/hasContent just by duplicating.
AND: It would be awesome to also have a Multi-TEXTS widget, because : when i want to show Clipnames for all 300 Clips → there’s no text-label-multi-widget for many clips. Alternative would be to let the Multi-Buttons-Widget receive text labels for individual buttons (example name adress is /track/1/clip/#/name)
Please reduce horizontal size restriction:
It’s a pity you can’t further reduce the horizontal size of buttons and especially Faders.
Also, it would be awesome if Faders could be borderless!
LUA Scripting region within widgets to let users create workarounds for non-existent features - would be crazy
Use example: I can’t make use of Colors for Tracks and Clips, because OSC/Pilot can’t use RGB format of colors.(link to topic: FeatureRequest: OSC args for Faders and Textbox - #4 by Nowiamone )
A RGB to hex script could do the job, if hex is the right thing for oscpilot (i dont know much about programming, i just found this working rgb to hex script for touch osc:
function onValueChanged(text)
function rgb_to_hex (s)
– Use string.match to extract the three numbers from the string
local r, g, b = string.match (s, “rgb%((%d+),(%d+),(%d+)%)”)
– Return a new string in HEX format
return (string.format(“%02X%02X%02X”,r,g,b))
end
self.color = rgb_to_hex (self.values.text)
end
Another use case for a script would be Clip Playback Progress. With a tiny tiny script it would be possible to get the Clip Playback Progress, based on the length of the clip and the data passed by /beat/str to calculate %complete since clip started playing. Since i love both OSCPILOT and clip-playbackprogress, thinking about possibly having to switch to other OSC Programs just for this makes me sad
Please increase size of settings window for a quick-fix of this issue: Bugreport: Midi Settings Window too small
EDIT: sorry, i didn’t see you answered in the other thread about looking into this. This is great, Wohoo!
Option to send several OSC commands with one Button, with a few ms delay in between commands (or even manual timeset option) Use example: End recording and auto jump to next Track.
All the best, and thanks for making the 1.10.1 version, it’s really nice.
Updated Repost, first post can be deleted:
I really love OSCPILOT and would love to see it thrive with new possibilities in the future. So please forgive me that i’m writing not just one, but a list of feature requests which are based on daily usage of OSCPILOT for a long time, which i think would be of great value to many OSCPILOT users and put it into another league.
Batch-Transformation of Objects:
I spent countless hours of resizing whole interfaces, because only one object can be resized at a time. “Select several objects & Transform size of all together” would be an awesome function. (including objects which are directly layered above each other) Being able to group several objects would also help a lot.
Automatic numbering for OSC address numbers
I was building a huge Cliplauncher, consisting of 24 Tracks and 12 Scenes = 288 Clips! It’s really helpful already, that inserting the # works for automatic numbering! So /track/1/clip/#/isPlaying works when put into the (Multi)“BUTTONS” Widget! Yay!
Still, it would be awesome to have some sort of automatic add +1 value duplicate function, which makes /track/1/clip/#/hasContent into /track/2/#/hasContent just by duplicating.
It would be awesome to also have a Multi-TEXTS widget, because there’s no text-label-multi-widget for many clips. Alternative would be to let the Multi-Buttons-Widget receive text labels for individual buttons (example name adress is /track/1/clip/#/name)
Text-Wrap and spacing possibilities for the text widget.
Please reduce horizontal size restriction:
It’s a pity you can’t further reduce the horizontal size of buttons and especially Faders.
. Also, it would be awesome if Faders could be borderless!
LUA Scripting region within widgets to let users create workarounds for non-existent features - would be crazy
Use example: You can’t make use of Colors for Tracks and Clips, because OSC/Pilot can’t use RGB format of colors. FeatureRequest: OSC args for Faders and Textbox - #4 by Nowiamone
A RGB to hex script could do the job, if hex is the right thing for oscpilot (Example: i found this working rgb to hex script for touch osc:
function onValueChanged(text)
function rgb_to_hex (s)
– Use string.match to extract the three numbers from the string
local r, g, b = string.match (s, “rgb%((%d+),(%d+),(%d+)%)”)
– Return a new string in HEX format
return (string.format(“%02X%02X%02X”,r,g,b))
end
self.color = rgb_to_hex (self.values.text)
end
Other use cases for a script: making a double tap to confirm Button, creating delayed actions like a button sending out several osc messages with a certain delay time in between, creating Faders which send out osc messages faster the closer you come to their maximum (good for scrolling/zooming purpose etc.), and so on.
Option to send several OSC commands with one Button, with a few ms delay in between commands (or even manual timeset option) Use example: End recording and auto jump to next Track.
Adding a Pager Widget and maybe even a List Widget. It’s possible to simulate the behavior of a pager by copying the whole interface Page to another workspace and just changing a specific area, while adding a workspace switch button. This isn’t efficient for complex, big setups, which have several layers/areas of pagers.
A List Widget would be really awesome in general. A scrollable list which is permanently shown, and a dropdown list, which only opens when pressed.
Option to deactivate the automatic pop-up touch Keyboard
Option to deactivate the automatic pop-up bars at bottom and right- which can impair the workflow of moving widgets when trying to position them in those edges.
All the best, and thanks for making the 1.10.1 version, it’s really nice. OSCPILOT is already an awesome software as it is. It’s only “advanced” use cases where it could improve (and the midi port selection bug being the only real bug i know of I m also aware of the background story of OSCPILOT, which makes it unlikely that such drastic changes will ever come - but just wanted to share those ideas anyway
and would love to be able to use it in the future, too. So please forgive me that i’m writing not just one, but a list of feature requests which are based on daily usage of OSCPILOT for a long time, which i think would be of great value to many OSCPILOT users and put it into another league.
I m also aware of the background story of OSCPILOT, which makes it unlikely that such drastic changes will ever come - but just wanted to share those ideas anyway