Version 1.0? 
1 Like
Hey,
So today I started to learn and have fun with the new features of Orhack and I have to say it is an absolute dream!
I used Orac a lot but it took me some time to get used to and once i was fluent with it I still found it to be difficult to get things in sync ect…
My first run on the hack today and it all makes beautiful sense 
Overdrum is essentially my favourite module with fission. It’s the first drum sequencer I’ve ever enjoyed using (I’m a drummer as my first instrument and I’ve always found sequencers quite limiting even when used creatively!).
I know this is common but I am getting some crackle which I know is cpu related but it’s happening a random times even when I’m not running too many modules, fx and modulations. I think it’s about picking less intensive modules I guess?
I’m really looking forward to digging into the sampling options.
Congrats on such a marvellous addition to the community and for making an already great addition, quite stunning.
Best
Aaron
2 Likes
Thanks a lot, I’m glad you’re liking the sequencer, I also find it refreshing as it’s very simple yet very effective. 
For the crackles, that is most likely CPU related.
Orhack is really made to run on overclocked units, the idea of creating a system built on ORAC specifically for the Organelle became feasible to me only after overclocking my unit and experiencing the improved stability under higher cpu loads.
On a stock Organelle M/S you are going struggle a lot with your CPU headroom, so you’ll have to choose your modules wisely.
But I’m glad it is still useable on stock units as I understand some people might be reluctant to overclock, as that also means opening the unit and installing an heatsink, which means voiding your warranty and putting “unobtanium” CM3+ module at risk.
I also imagine in the future once CM3+ modules will became available to mere mortals again it will make sense upgrading to a module with built in flash memory, as right now the sd-card is somewhat of a bottleneck especially with sampler modules…
2 Likes
Hey,
It’s very refreshing and using the lfos to change params in fission is great for creating long and meandering sequences.
Hmmm I’ve never looked at overclocking - I’d definitely be interested if it lifts the headroom on the cpu issues.
One thing I was going to say about the overflow is that it would be great to be able to have the option of using a different octave per sequence. Having the sequence stay within the octave range of the organelle keys could become quite limiting. I can assign an lfo to the transpose param of the actual synth which causes some great randomisation but to get defined patterns spread across octaves would be sweet!
That’s true about the octave, it is a limitation of the user interface as there is no space left to put that feature. But a workaround is in the making! 
2 Likes
I like the sound of a workaround!
Alsoooo @Audivit
Does Orhack work with link? I’m trying to link with my norns and can’t seem to get the transport to recognise the clock link.
@Audivit I’m trying to sync up with cheat codes on norns so have tried link which doesn’t seem to work. Midi however does share clock but the issue is that the clocks aren’t locked. if I start my norns clock in cheat codes I have to start the transport in orhack separately and have to get it bang in time (the aux hit to start the clock) or the parts will be slightly out. Is there a way these clocks can be fully synced so that switching the clock on in transport will be in time with the norns clock?
Sorry for the barrage of questions!
Thanks
2 Likes
I haven’t used Link in a while, but it should work.
Also not being familiar with the norns system unfortunately I can’t help you there.
Midi clock and transport start/stop has been tested with elektron gear, ableton and OP-1, and is working fine in both directions.
Have you engaged the parameters “Midi <<” or “Midi >>” in the second page of the transport module?
If you did and it’s still not working then I think it could be your norns not configured to receive transport start/stop messages.
2 Likes
Hey:)
Thanks for this.
I can’t seem to get it to work - Norns works perfectly with link on my organelle for other patches and with orac but can’t seem to get it going here.
What would you suggest I set my transport parameters to?
It is possible that Link got broken in one of the last updates, I suggest using midi for the time being as that should be working fine.
Remember that for usb midi you have to edit the “patch_loaded.sh” file with your midi configuration.
Otherwise you can use midi via cable with the TRS connectors on the back-panel of the organelle.
1 Like
I’ve checked and yes I’m quite sure the Link functionality is broken in the last update, or maybe I’ve disabled it and forgot to re-enable while i was patching inside the transport module, which is quite possible.
However, the Link external in the organelle is not able to send or receive transport messages, so no start/stop functionality over Link, only bpm clock.
Which is probably the reason why I was only using usb midi so far…
Okay cool! Thanks for the update - good to know I’m not going bonkers.
I’ve got it connected to midi but would be awesome to have link so I could utilise the midi cable for another device!
Link probably won’t work with a preview but it’s just a little orhack jam. Had some time to learn a little more of it and got a short vid.
https://www.instagram.com/reel/CtuMclUg7mP/?igshid=ZWQyN2ExYTkwZQ==
3 Likes
Just started exploring Orhack this week and its mind-blowing!! Amazing work.
Just wondering, how would I get towards something of a overdubbing looper functionality with Orhack? I was trying to use the multi-track recorder on the 3rd master FX but no overdubbing.
Thanks!
1 Like
Sure, actually @T8R made some pretty cool looper modules for Orac, you can find them on his patchstorage profile.
The multitrack recorder isn’t for looping or overdubbing, that’s just for recording sessions to later transfer into a daw or other samplers.
2 Likes
Just wanted to say that Orhack is an absolute blast! I’m having a lot of fun with it, but do have a couple of questions that might help me clarify stuff.
- crackle: like some I’m getting crackle and I know it’s a module selection question. I’m checking CPU and its roughly around 35%. Is this considered in the crackle area or is it way higher but the organelle doesn’t show the exact percentage. I’m using the following;
- Audio in with autopanner
- notegen - > plaits+ → genloss
- notegen → braids+
- notegen → modals
all are going to clouds and ringverb
Are any of these moduls very heavy for the CPU? I’m assuming clouds can be quite a bit.
- LFO question: I’m quite a noob when it comes to modular things but I know what LFO is suppose to be doing, however I don’t quite understand the use of the LFO’s on the F#, G# and A# keys. Am I suppose to connect it to an existing module and have it control a specific parameter?
thank you so much for any clarification
For the crackle issue, genloss and modals are very heavy on the CPU.
PD’s CPU meter is not accurate especially with multicore modules so that 35% is not accurate, however IIRC on stock Organelle M/S the crackle seems to appear in the 70%-75% range (using the htop metering in terminal).
While on an overclocked unit along with the headroom increase I’ve found that you can push the CPU to above 90% and most of the times without crackles.
But yeah that chain you are using it’s an heavy one, I’m not surprised you’re getting crackles on a stock Organelle M.
For the LFO’s they are there for you to map them to parameters like if they where midi controllers.
The process of mapping them to a parameter is a bit convoluted but here it is:
Parameter learn on LFO-1:
- while on LFO-1 page press Aux button once,
(Purple LED flashing and “>>>> LFO-1 <<<<" message on top of the screen indicates that the learn focus is on LFO-1). - navigate to the parameter you want to learn (the destination parameter not the LFO parameter).
- click the main encoder and activate mod learn on the main menu.
- move the desired destination parameter.
- press the main encoder and disable mod learn.
- navigate back to the LFO-1 module page and press aux to disable the learn focus.
Parameter unlearn on LFO-1:
- while on LFO-1 page press and hold Aux button,
(Red LED flashing and “<<<< LFO-1 >>>>" message on top of the screen indicates that the unlearn focus is on LFO-1). - navigate to the parameter you want to unlearn (the destination parameter not the LFO parameter).
- click the main encoder and activate mod learn on the main menu.
- move the desired destination parameter.
- press the main encoder and disable mod learn.
- navigate back to the LFO-1 module page and press/hold aux to disable the unlearn focus.
1 Like
Thank you so much for your clarification and the LFO works perfectly now!
Hey dude,
How are you?
I’m Aaron from over at the lines community as well.
Have you tried syncing Orhack with Norns yet?
How are you finding it?
Best
Aaron
1 Like
At the moment I am unable to push an update with this fix for link.
For anyone interested in Link please open the module.pd file inside the transport module folder and connect the loadbang a shown in the picture (in blue), then save and restart Orhack.
That should fix it.
However if you’re interested in start/stop sync, that is simply not possible over Link with the organelle, for that feature you have to rely on USB-MIDI or standard MIDI.
2 Likes
haven’t tried syncing it to Norns yet, but if you’re using Abletone maybe there’s a way to do it through link. However I think @Audivit might give you a more proper answer