Could someone give me some help how I can edit the main json file, that sample based patches work. Or is this bug already fixed…? Thanks in advance, Jables
Do you mean sample based presets saved on previous version of Orhack are not working?
Just wanna say thank you again for your wonderful work Audivit. Had hours of fun with it.
I had a small issue: When recording (with the internal capture module on f3) a classic 4/4 beat in a certain BPM (chaos and swing off) and then exporting the *wav. to my daw with that specific BPM set before importing, the beat matches perfectly on the grid for maybe 10 seconds but then drifts away slowly (i think the actual recording is slower than the set bpm in the daw/transport module). That makes it hard for me the add for example some percussion if i have a long synth/bassline/drumrecording from orhack if you know what i mean. Tried it with Reaper and Live. With orac and capture module this worked flawlessly in past…
What am i doing wrong?
No it’s the same problem that I mentioned in my second last post. I can’t record or use presaved samples in sample based patches, when I start a new project from scratch. You planned to fix this with other stuff in the next update, but I thought I could do an easy fix by myself, if someone explains me how to edit the json file ![]()
All the best!
@arkanisgath That’s weird, I’ll check if I can replicate the issue and let you know!
Is this happening on multitrack recordings or on the single master recording, or both?
@jbls tomorrow I’ll look into it for you, sorry for being late but me not using sampler modules much lately has made me forgot about this issue ![]()
@Lijcke I’ve implemented the “one quick aux press to end recording” into the clip module and also fixed other stuff, and you where right it now works like a charm, much more predictable. I’ll release it soon (probably tomorrow) with some other bug fixes.
@jbls quick fix, try to replace the orac.json file inside the 0rhack folder with this
orac.json.zip (654 Bytes)
And let me know if the issue persists…
It’s multitrack recording. Didn’t try singletrack but i can try that later. Thanks!
Ok I’ve pushed update v0.51b on Patchstorage.
Changelog:
– Clips bug fixes.
– Implemented “instant aux press to end recording” in Clips.
– Added bpm tag at the end of multitrack recording names.
– Deprecated sampler modules (audioflow, polytwig, norisampler) as they don’t seem to work (will look for a solution in next updates or create some alternative modules).
@arkanisgath I’ve tried and I could not replicate your issue, provided that I’ve first disabled “WARP” functionality on the Ableton clips (the tracks from the organelle), set the correct bpm and aligned the audio clip with the Ableton grid.
If you do this steps the recordings are playing in sync with Ableton metronome (even with swing), chaos also works but obviously adds some instability to the tempo.
@jbls I’m sorry but I couldn’t manage to make those modules work for the moment I’ve removed them from Orhack, but I’ll look in some solutions and alternative modules. Samplement and Percussion work fine though.
Ok maybe i’m the problem :D. Thanks for your message. WARP was off, but i’ll try again.
Are you clocking the organelle externally?
No, its just clocked by the internal transport module. The beat was made with overdrum and fissions. I’ll run a few tests later when i’m at home.
Could it be a difference in sample Rate? between Ableton & the Organelle?
Usually DAWs like Ableton are internally converting audio files to fit the project samplerate.
Do this test:
- record a 4/4 kick drum using Overdrum->Fission
- put the recordings in your daw
- set your DAW bpm the same as tagged into the recording names
- disable warping from your daw
- make sure to align the beginning of the beat to the grid
- turn metronome on and listen
Does it stay in sync?
Hey, tried it again with v0.51b and now it worked perfect like in the old orac days :D…
Still i have this strange recording with the exatct same settings, which is out of sync. Anlayzed the Track in Traktor and its extactly 96.96 bpm with the internal transport module set to 97. I also have a different example with the internal module set to 120, wich is actually 119.95 Sorry, I don’t know what witchcraft was going there since its gone i wont worry about it anymore. I’ll report if something similar happens again. Here is the 96.96-recording attached if you want to try for yourself.
Ok now I think I’ve actually got what is causing this, will look into it asap!
Wondering if you can help me with this… I have my Organelle midi synced to Ableton. when I hit play in Ableton the Transport in Orhack starts running but Overdrum does not. I haven’t tested with the other sequencers just yet, but do you know how I might remedy this? Thanks.
Actually just realising it only doesn’t set the sequencer off when I start the Ableton track from the very start.
Had the same problem this morning. Most of the time it works for me (Ableton, Reaper) but sometimes the transport module just starts without starting the sequencer, like Hector described.
hey guys,
quite new to organelle, orac and orhack and I have a few questions regarding the workflow;
-
what is the best way to import orac modules to orhack? usually how I do it is that I upload it through the browser, install it and then move it orhack modules subfolder. is there a better way?
-
is there a way to get non-orac modules to work on orhack, like with orac easter egg option?
-
currently checking out orac modules on patchstorage and am wondering is patchstorage the only place where to get orac modules, and organelle patches or is it only one of the more popular repositories?
-
how do I save a session/preset to orhack? should I be doing the save as function on organelle or is there a way to store your session for future use?
Apologies for quite a few questions, but am looking forward to any feedback!
-
Yes thats the correct way.
-
No you cannot load non-orac modules, even if you can with the ester-egg option I would advise against it as it’s only limited to one module and can (and most likely will) cause a lot of issues and instability.
-
I don’t think it’s the only place, but afaik it’s the best place for organelle patches, while this forum is close second.
-
Load an init preset, then navigate to the preset menu and select “New Preset”, now your new preset has been given a number es. “new-1”. This is your preset and now you can load modules, sequencers etc.
Once you’re done navigate to the preset main menu and select “Save Preset”, every change will be saved on your current preset.