Thank you for your reply @Audivit! I’m getting crackles quite a bit whenever I get to the third modules slot. Checking the CPU on my organelle m is close to 50%. Is this still to do with the card speed? I have the 8GB that was shipped with the organelle.
It depends on which modules you’re using, but I would advise in any case to replace the SD card with a faster one.
1 Like
New Update is out on Patchstorage:
CHANGELOG
0.52b
– Fixed bug in Overflow which was clearing all steps occasionally.
– Improved transport start/stop behaviour to and from external midi gear.
@HectorPlimmer & @arkanisgath please report back if your Ableton transport works with this update. 
2 Likes
Wow, thanks a lot. I’m on vacation right now (of course with organelle and orhack at the pool) but ill report asap when im back.
1 Like
Sounds good!
Enjoy your jam at the pool 
Thanks! Btw what i wanted to ask since a long time - is there any way to copy patterns inside overflow/overdrum? Would be much more easy to create variations without have to enter the notes manually again.
1 Like
Not from the UI at the moment…
It would be possible with some tinkering but since the user interface is full the only viable option to implement that would be to replace the “clear all notes” function (long 3 seconds aux press) with an alternating copy/paste function.
I’ll see what I can do for a future update!
2 Likes
I’ve been dreaming about this function… Would it be possible to use the same UI as children of the sample (or some other C&G patches)? Where you hold the key you want to copy and press the one that you want to place it.
Anyway Orhack is amazing, thanks to you and all the people in the open source community for all the work put in here
1 Like
It’s funny 'cause I personally don’t think it’s a big deal to manually re-enter steps to create variations…
The sequencer being a simple 16 steps & two parameters (and not something complex like elektron) makes it easy enough, it also pushes you to experiment with polyrhythms on separate seq tracks and with variations by setting other seq tracks to repeat once every x bars.
I agree! Also the pattern chains allow you to use the same set of sequences in multiple patterns. That’s the only time I really wanted a copy paste function in the previous version.
1 Like
Yeah yeah probably you are both right but i’m lazy as fuck 
and sometimes i got complex melodies in overflow with tons of notes in 5 or more sequences and if i try to evolve this it would be so easy to just copy it to another pattern and erase/add notes there. But i know its just complaining on a high comfort level. Maybe i have to change the way i build my melodies…
Maybe it could be helpful to see the names/numbers of the notes (like in pink mode or in overdrum in the left corner) for copying because i’m not the brightest star at detecting which note is playing right now. Is there a way to mute seqeunces in overflow like in overdrum i didn’t discover yet? Sorry for all the complaining, but I love this patch toooo much and its so awesome to have the possibilty to speak to the creator(s) directly… 
1 Like
Now start/stop behaviour with external clock from my daws (Reaper, Live) works flawlessly. 
1 Like
Hello again @Audivit ! I’m really enjoying diving into orhack. Earlier I asked you about audio in issues I thought I was experiencing. It turns out that part of it was that I was using a balanced signal into the stereo input, which of course cancels itself out if L/R are mixed together… 
I have encountered a new issue, however. I cannot get unlearn to work properly! Following the instructions in an earlier post here, what seems to be happening to me is that the parameter I try to unlearn seems to get signal from the next LFO, or maybe some other random LFO source. If I go through the very long process of unlearning everything, I can sometimes get it to work.
Maybe I did something weird and put the preset into an unexpected, buggy state?
When in “unlearn mode” (to enter this mode press and hold Aux on the modulation source page you want to unlearn, es. LFO 1) all the modulation sources should stop momentarily, and the selected modulation source should send 0 to the destination.
The LED on the selected modulation source should blink and on other modulation source should be fixed red color, you should see on top of the screen the following text “<<<< LFO 1 >>>>”.
Provided that you followed the steps, it could very well be a bug I wasn’t aware of, please let me know!
2 Likes
I’ll try to make a video of my process soon, thank you!
OK I think I found out what my problem was.
I wasn’t aware that one selected an LFO to learn by quickly pressing Aux on its page (the LED becomes purple and the top of the screen reads, e.g. >>>> LFO 1 <<<<).
This makes me wonder, then, what is the behavior when one does not have an LFO selected, and a Mod Learn is attempted?
1 Like
Thats the standard Orac behaviour,
Modulation learning in Orac was added as a bonus, it has never been fully implemented.
This is the reason why I had to come up with this system.
In Orac you had to manually disable any other modulation source beside the one you wanted to learn, and then reactivate all one by one manually, to unlearn you had to do the same plus making sure that the one mod-source you wanted to unlearn was sending out 0, which wasn’t the case most of the time.
So it was very tedious and frustrating because it was very easy to mess up.
In Orhack this process is automated, you just focus on a mod-source and every other mod-source is automatically disabled, and when unlearning the “0 state” is forced trough the modulation source to ensure a successful unlearn.
1 Like
Oh wow! That’s great to know, thank you for explaining that. My “hack” has been to just reload the module with problematic mod mappings if I really screw it up. It’s often faster than unlearning everything, the details of which eluded me anyway.
