New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uhm yes hello these modules are amazing, thank you #5
Comments
Hehe ty, feel free to suggest improvements/features. Also if you have OSC templates/presets for whatever software you use with VCV + OSC'elot and want to share |
yeah! that would be fun. I've been using this OpenStageControl template for some time now on Rack 1 with trowasoft's osc modules. here's a demo from the depths of the sea (I also have an expression pedal and two foot buttons to control the Circle module on the left. It's my own module I've been working on for quite some time now, it handles all the sound emergence.) I'm still working on setting it up in Rack v2. |
Pairing OSC with VCV Rack has really uphauled my music workflow to be based around live creation (+ Circle). I was very relieved when I found your modules in the library when I sat down to get v2 working today. Then I started playing around with them and I was like, wow, there is a lot of care put into these. So thanks a lot again 🙏 . |
Hmm how they all have the same fader IDs, are you using one fader to control all of them, or is there a bug there |
There's a bug. It works somehow though. The messages I send are of this format: e.g. 1 e.g. 2 You see I set the preArgs to 0 for everyone, because I noticed it didn't make a difference, as they were differentiated anyways, and I was lazy. Also, when I set the preArg to '1' (as well as '2' & higher), I got a long number like FDR-16497724.. Reading how OpenStageControl works, it says |
Ah I see, ok yes I did code it so that it'll work as long as the address/id combo is distinct. All OSC messages consist of an address and a list of args. OSC'elot expects 2 arguments, if you give more its fine, will be ignored as long as it has a usable ID and value. In OpenStageControl pre-args are just 'hardcoded' args. The other args come from moving the slider like value. Your config is fine :) |
The issue with the long fader ID seems like a bug, are you setting the type of ID to Int and value to Float. Should be type 'if' in OpenStageControl. You can also see a basic OpenStageControl preset in the OSC'elot folder. |
Ok great. Ah yes it seems like it is cast to float by default. Setting the 'if' there fixed it. I did not know of the preset's, that would have helped I'm sure (I'm not sure if you do mention it in the manual, if you do that's good). |
What do you use? |
Yeah I think I've mentioned it, if not I will add it when I update it with the new features, banks etc. I use a hardware controller and OpenStage for testing: |
Ah cool. It's nice you have something tactile. |
You are on spaceship levels my good sir |
Hey I noticed another issue that I have to sometimes open the patch twice in order for OSC'elot to recall ALL the mappings I made. Sometimes it only recalls the first page. It also has trouble turning on the receiver sometimes, and I have to restart for it to work. I'm noticing I have to sometimes open a patch 3-4 times for both the receiver to work and OSC'elot to remember all the mappings. It is quite strange. |
Hmm can you send me the patch? There might also be errors in the log when it doesn't connect. |
https://drive.google.com/file/d/1E3dW6rSTQLxBBJoIGG8uGdtVOE8xtYAp/view?usp=sharing Here you are. Here is what I just did, maybe you can reproduce: Open Rack, OSC'elot is missing many assignments, receiver starts green. Thank you for helping too 🙏 |
I just realized that if I press 'scan for next mapping' the mappings I thought were lost reappear. Though I would like them to all be mapped at the same time and it doesn't seem possible in this scan mode. |
Sorry I was on a couple of weeks break from work/tech.
Hope that clears up any problems/bugs, if you still see something lmk and I'll try to repro/fix |
Thank you! I will. |
No description provided.
The text was updated successfully, but these errors were encountered: