Apologies for being frustrating.
I do understand the chain MIDI - just wasn’t really getting how the Active MIDI is impacting the patches. Was thinking of it almost like an OMNI.
I have program change somewhat working with my interface now but AUX is still a problem.
This has been useful to try and troubleshoot. I have a patch with SEQ2 in A1 and Analogmono in A2.
I press my AUX button which is currently a MOMENTARY sending 0 or 127 on #69.
First time press after loading the patch I get a stack overflow.
If I hold the AUX I can see Journalctl getting the notes.
When I let go it plays the first 2 notes and then stops.
Any ideas what i’m doing wrong?
EDIT: Since this post i’ve managed to get AUX working with Overloop and Rhythmicon so I wonder if it is something not translating from the Organelle specifically for Seq2?
long hold of aux (2 seconds?) - arms recording , but will start recording when you play first note
press aux will then stop it
short press = play
(stack overflow error is a red herring)
seems to work for me, but I admit its harder to know what ‘mode’ you are in without a screen
(organelle, tells you its armed etc)
aux can be used differently in different modules/patches (remember many modules were derived from c&g patches) , but often a long hold is some kind of ‘clear’
this is already in beta 2!
just edit mec.json , which lives in /usr/local/mec
and add exactly as above.
particularly take care of where the commas are at the end of the line , you don’t have one at the the end of the list of items in JSON.
i.e. there won’t be a comma on the listen port line, and it will need one, and the menu timeout does not have one.
btw, this is a multiple of something rather than an absolute time, so just increase it to something that feels good for your (probably doubling is a good starting point - 350 is its current setting)
as stated above,
as you get familiar with the menus, you will likely find you want to reduce it again, as you’ll know where things are.
also as stated above, and what i do in the videos so you can see, the other option is to just keep the selection moving (easy when using the keyboard on PD client), as the timeout is respective to any activity… so just pressing up/down, will keep the menu up
Success has emboldened me. I’m currently going through WyrdAl’s collection of Orac 1.0 modules to see what works and what doesn’t. Avoiding patches that might require a strong visual feedback component (like Seq3) I’ve had no problems so far but i’m wondering if there is anything in particular I should look out for?
So far from what I’ve tried the following seem to work OK.
Synths: Additive, Apollo, GlassFM, Modalsynth, Polyfolder, Slatra, Spacekittens, Stringmachine, Tapesynth, Titan
FX: Buffershuffler, Constant Gardener, Dust, LFO Delay, Spectral Warper, Warpdelay
Also Mark I got the following error from Wavescanner, don’t know if it is important.
Don’t use Orac 1.0 modules unchanged , they will duplicate the KontrolModule which is likely to cause issues.
(and no, the argument it seems to work is not valid, because there may be edge cases you do not see immediately)
It’s not difficult to migrate them to 2.0, and it’s a good opportunity for the module developer to review and test them.
( you could create a fork and do yourself if you want , and offer the dev a pull request)
Soundfiler errors in log are normal, as long as it’s functional it’s ok
I like the idea of a controller so as not to depend on the osc client but it seems that you are doing a concept like organelle. I see Orac as something different in a way more like a modular synthesizer. I do not have much idea about phyton, and I had planned to do a controller with arduino one for Orac but I do not have much time. The idea is to make a small controller, which can assign many parameters, easy to build by someone inexperienced and inexpensive. I hope to have it in a month and share it.
Well then nobody do what I did!
I’ll just have to reinstall if there are problems - at least now I know how everything works.
I just figured out that I can record stuff in with Norisampler to different slots and then use them all together in Sampler24. That’s a neat trick and explains why the Kit / Slot requirement.
@Makrotulpa for me norisampler doesn’t save correctly the samples in the kit/slot, they are all truncated to 8864 bytes… yours saves them with the right size?
I did notice something weird that I didn’t have time to track down.
Kit 1, Slot1 - sounded fine in the Norisampler but when played from Sampler and Sampler24 was only a tiny loop.
But i’m feel like the other Slots saved fine - I would have to double-check but yeah it could be a bug.
Have you found Overloop samples OK?
On my list to check for tomorrow is… what happens if I have a Norisampler on one chain and Sampler on another? Can I jump from chain 1 sampling input to chain 2 playing back input and how instantaneously?
hi, well, what I’ve done so far is nothing more than a transposition of the pd patch @thetechnobear made as a controller. I’m working also on an integration with novation circuit, if anybody is interested. cheers
How is it going to work? Each chain receives a separate MIDI chan from the Circuit plus controllers or something deeper? Was thinking of getting a Circuit again now they’ve added some things I was missing.
EDIT: If you could get it to switch presets, select modules with each chain, auto-populate macro controllers, and perform aux functions it could make a decent headless controller.
Dear Mark,
So thankful about what you did for orac. Thanks !
Just a quick question ! Do you think a the first version should work ? Or is it a different communication protocol than with Push 2 ?
Thanks
cheers