Here is something interesting.
Today I realised that #Orca can send MIDI CC signals, so really the possibilities are almost limitless, even in conjunction with #SunVox.
I know it's rather silly, but here's a sort of little #synthesizer powered by SunVox, but the whole interface is done in Orca. Of course I don't think it's all that practical, it's more of a concept. But we can automate things this way.
Today I realised that #Orca can send MIDI CC signals, so really the possibilities are almost limitless, even in conjunction with #SunVox.
I know it's rather silly, but here's a sort of little #synthesizer powered by SunVox, but the whole interface is done in Orca. Of course I don't think it's all that practical, it's more of a concept. But we can automate things this way.
Devine Lu Linvega
in reply to vacuumbeef • • •vacuumbeef
in reply to Devine Lu Linvega • • •Devine Lu Linvega
in reply to vacuumbeef • • •vacuumbeef
in reply to Devine Lu Linvega • • •If I remember it right, it was a long time ago, I used to bang something like $bpm:130 in OrcaJS to obviously change the bpm. Looks like orca-c does not has $ at all, and in orca-uxn, although $ exists, there is no such function to change tempo. I'm right?
Devine Lu Linvega
in reply to vacuumbeef • • •It could be made to use its own rune, or maybe there's UX to change BMP that I haven't tried.
The reason $ is called self, was to manage all things related to the runtime itself. I could bring back commands to $ in orca-uxn if you're interested.
vacuumbeef
in reply to Devine Lu Linvega • • •It's not that needed and I too felt something unnatural in it, so I know what you mean.
I thought about it because of this auto-album idea - a lot of febrajam tracks have different speed. I guess I'll have to change bpm manually in right timing, which is not a problem, but for this reason, absolute album automation will not work.
And, unfortunately I won't be able to use the uxn version, with heavy sunvox projects it slows down a bit, so the tempo is unstable,due to my weak processor.
Devine Lu Linvega
in reply to vacuumbeef • • •Devine Lu Linvega
in reply to Devine Lu Linvega • • •vacuumbeef
in reply to Devine Lu Linvega • • •Devine Lu Linvega
in reply to vacuumbeef • • •vacuumbeef
in reply to Devine Lu Linvega • • •1) will be there any maximum value of bpm? (orca-toy has much slower maximum than orca-c, for example)
2) What do you think about reset? To reset the global clock to the first step in any moment.
Devine Lu Linvega
in reply to vacuumbeef • • •In uxn orca, the bpm is a ratio of 1/60th of a second, so the fastest is 60 beats per seconds.
vacuumbeef
in reply to Devine Lu Linvega • • •vacuumbeef
in reply to Devine Lu Linvega • • •Devine Lu Linvega
in reply to vacuumbeef • • •Devine Lu Linvega
in reply to Devine Lu Linvega • • •vacuumbeef
in reply to Devine Lu Linvega • • •vacuumbeef
in reply to Devine Lu Linvega • • •Devine Lu Linvega
in reply to vacuumbeef • • •Kartik Agaram
in reply to Devine Lu Linvega • • •On the other hand the benefits might be lower in a CA with lots of animation like Orca. I think Game of Life wouldn't save much space recording just mutations.
Devine Lu Linvega
in reply to Kartik Agaram • • •You might record a state X, but by the time you undo, the grid has changed a lot and the diff no longer applies.
Kartik Agaram
in reply to Devine Lu Linvega • • •So when you say 2-3 frames, when you undo it would go back to the state when you made the change?
What if you put all changes to the grid on the history, whether they were automatic or not? Then on undo unwind all changes to last manual change.
You'd only have a limited history of n seconds. No edits in n seconds = 0 undo.
vacuumbeef
in reply to Devine Lu Linvega • • •vacuumbeef
in reply to Devine Lu Linvega • • •But if orca is about LIVEcoding, it does't fit into that concept I think, so forget about it.
Kira 🌱
in reply to vacuumbeef • • •Orca question: how are you getting those values in -- comments? -- to feed into the output?
vacuumbeef
Unknown parent • • •