I've been using Open Stage Control for a little bit now and I have to agree with everyone else - it's awesome!
By way of a shameless plug for my own content, I have been sharing on YouTube a tutorial series on how to use Open Stage Control and the theme of the tutorial series is creating a Behringer BCF2000 in software.
This is a creative and excellent tutorial on how to approach custom fader graphics.
I had looked into the source code approach, but for the same reasons as you I concluded that wasn't going to be a good long term approach.
On a different note, I noticed in the video that you're not using MCU mode. I went back and forth on using my BCF2000 in MCU mode and user mode, and ended up mostly using MCU mode in the end. If you ever consider going in that direction, it might be helpful to know that jean-emmanuel has a good MCU emulator using OSC also on github.
There are at least to ways to skin the cat. One is to rotate the image, the other uses image strips (e.g. generated by knobman).
I really like mackmusic's idea to use the html property of the widget, will give it a try.
I used a different approach. I put an "invisible" (alpha=0) knob widget on top of an image. The image is rotated in accordance to the knob position. The following code goes into the css property of the image widget:
'insCtrlr_1' is the name of the knob widget. '240' and '125' are range and offset of the rotation angle.
If I find the time I might explain an example for the image strip approach, which makes it possible to use a different image for every knob position. It's similar to a 'thumb cinema'
hey @jean-emmanuel - really cool to hear from you directly. awesome tool you have created! the videos are more popular than i had initially expected. seems there is not too much out there. and i'm so glad you like the content - i did wonder what you might think! it's not very advanced what i am doing (i will cover more difficult stuff soon hopefully) but i wanted to show more what can be done visually but still keep the original source code.
i'm not on this forum very often so apologies to others if i have not replied to you. it' easier to get me through the YT comments if you want to interact directly, or also on discord (links in the videos).
agreed there are 2 main ways to do this. i already had 'filmstrips' of knobs from knobman tool becuase of creating VSTs in JUCE framework. (I should really be using SVGs, but that is another story!!)
someone else on here posted a codepen link to a really cool example using CSS transforms implementing a test ADSR control with waveform but i can't find it right now.
i like both approaches and will probably cover the CSS transform option in a future video part.
if i understood @mackmusic and the video right, you have to deal with source code in the slider/fader js... the post from @drjay inspired me, to check this out, as it seems to get it, without any modifications in source code.
and i created an example from the knob to assign a custom image as fadercap.
the image is bound as a base64-encoded image in the value field.
its css looks like this:
At this point i have a question: what is more efficiant, due to resources?
To embed the image as base64 or as a path to a png file as a (cahed) image in the value section?
Becouse the fader will be cloned x-times in the final json...
Thanks to to all of you for the great inspiration and ideas!
