Thanks for replying! I’ll try to explain better… I read the associated posts thoroughly before asking anything as I wouldn’t want to waste anyone’s time
I’ve successfully saved a preset with a chain setup using m9:3x3+1. In first position for each set of 3 I have chosen the punchy sequencer so I can program simple drum, bass and keys sequences all running together.
The problem is that after restarting Organelle and checking the preset is saved correctly I noticed that the punchy sequencer in the first position for each chain was not loading and I end up with a blank slot. So I had to add it again everytime I started up the preset. Kind of irritating so I tried to fix it by having a look around here and there…
When I checked the JSON file for preset configuration I immediately noticed that the name of the sequencer was > “moduleType”: “U-punch”, (this example in the first slot “m0”: { ) - so it was saved incorrectly and I believe this is the problem why it does not load because there are no modules with this name - it should be saved as > “moduleType”: “U-punchy”, not > “moduleType”: “U-punch”,
So I was wondering if there is a better way to fix this other than having to edit the JSON preset list?
you need to update U-punchy/module.json, to have the module name as U-punchy
then you need to rebuild the preset, after restarting orac.
the issue is , the name in module.json does not match the directory name, and unfortunately what happens is:
when you save a preset it uses the name in module.json,
but when you load a preset, ir uses that store named to load the module from the directory.
so when they mismatch it doesn’t work.
I didn’t know during testing as its was a simple typo, and one I only appear to have made in one module out of quite a few
really I don’t need to store the name in module.json, but when I was developing orac, at the start I had modules all in one directory, and it was needed , but then when I needed more flexibility I moved to different directories and forgot to remove the attribute in the json file.
i’ll fix this in a future release
I’ve noticed that when switching modules using the encoder button + key shortcut I still get notes going out to the external midi interface (seems to happen regardless of modules loaded).
It actually looks like midiOutGate is being sent a 1 so all keypresses generate midi (weird as it looks like MECKontrol should send midiOutGate a 0 in the source code, and I cant find any pd code that sends to it).
Hi Mark,
Sorry to revive such an old discussion, but I was trying to figure out how to implement a sustain pedal in orac (to hold notes in brds or activate the freeze in clds) and I haven’t been able to sort out how to modify the patches. If it’s not possible, that’s totally understandable, but you seemed to imply here that it is. Thanks so much for everything you do, it’s amazing!!!
Basic implementation of sustain is simply,
when the sustain pedal is down , and you receive a ‘note off’ , you store the note off rather than process it.
Then when sustain pedal is lifted , you send all the note offs.
Iirc, I actually have an all notes off message in orac , so that could be simplified, so that you don’t bother storing note-offs, you simply send an all notes off when pedal is lifted.
Usually this would be done in the synth module, but I suspect you could create a router module that implemented this.
One minor issue is often the pedal is treated equivalent to the aux button - but again this assumption is in the router module so can be changed there.
Thanks for the response Mark! I maybe should have mentioned, I’m able to comprehend only the most basic PD, I get lost easily. Any more specifics about how to edit the router module, or even the synth modules? I’ve tried plugging in the [r fS] object all sorts of places, can’t seem to get any results. Sorry, thanks again!
@thetechnobear Hi Mark! Hope this is the right forum to report this. It seems the Latch Function in Seq3 in ORAC does not work. For example, if you arm the recording and then turn on Latch, recording turns off.
Also, if you record a sequence with Latch off, then turn it on while the sequence is playing, nothing happens.
Both of these happened to me using Seq3 and Analog Synth in ORAC.
I believe I’ve found a bug with the “macro” module. Or more specifically, I think there’s a problem with the C++ code that responds to the modulate message.
Steps to reproduce:
From the a1 slot, load CZZ. (This is just an example, the bug occurs with any module…)
From the m1 slot, load the “macro” module.
Select “mod learn” from the menu, twiddle knob 1, navigate to a1, then twiddle knob 3 “sustain.” (Because this is a 0-100% parameter, it’ll be easier to see the results)
Navigate back to m1, turn the knob to 0.
Navigate back to a1, verify that the sustain value is not 0.
Interestingly, this does not happen for the 100%, only for 0%. To debug further, I printed out all the messages sent to KontrolRack: r rackMsgs → print. The last message sent is:
print: modulate m1 10 0
So the value is definitely being sent, but the controlled param does not get set to zero
I started to comb thru the C++ code but haven’t found anything yet. @thetechnobear I’m happy to keep digging and submit a PR if I find anything, but would definitely appreciate your thoughts!
