Yeah it is broken after the koala update. I used to hit play on my digitakt and it would start koalas sequencer. Then I’d hit stop on my digitakt and it would stop koala. I really hope they patch this because I love using both of them together
2 Likes
I knew it wasn’t just me. I was frustrated because I felt I wasted a lot of time to realise it was broken. I was gonna use it as a sort of slimmed down MPC alongside octatrack. I made 4 drum kits and loaded them into a koala project, made a custom launchpad mode, set it all up then turned on external sync and…sync doesn’t work. lol. got it working okay as an AU loaded in Drambo but who needs another layer of abstraction at this point. really hope they get to this soon.
2 Likes
I messaged the developer so hopefully it’ll get fixed
2 Likes
nice. post up if he responds
2 Likes
Anybody here use Koala with anything else?
I’m interested in advanced Koala workflows.
I mostly use Drambo, Aum, and Loopy Pro, and would love to hear any methods anyone has of overcoming Koala’s limitations etc, or of how you integrate it into a larger setup.
just an aside in the meantime, what are the main limitations you experience?
All the usual stuff, like LFOs, proper envelopes etc.
My main rig is very full, 2 Macs, 2 Ipads, Hapax, Deluge, synths etc. I love that you can do anything to any sound.
But then I use Koala standalone and I enjoy the simplicity.
I’d like to eventually incorporate Koala to my main setup in some way!
2 Likes
I use Koala with a Push 3, hooked up via ADAT with a little ADAT USB adapter. I sample out to Koala, chop and slice, improvise, and record back to clips on the Push.
It works really well.
5 Likes
I mainly use it within AUM, loaded it into an effects slot so that I can sample other apps into it.
Sometimes I’ll sequence it with something else - Atom 2 or Polybeat, for example - so that I can use a Mozaic script for round robins etc, but generally I just resample things into Koala and use the internal sequencer.
I send the individual outs to separate audio outputs on my interface and have them split out to channels on my analogue mixer, with a load of controls mapped out to a MIDI control to handle AUv3 effects
3 Likes
Just got a response back from the developer!
Really sorry about that - I’ve found the problem and will update koala very soon (hopefully tomorrow)
6 Likes
Interesting!
Another piece of the fascinating puzzle that is music technology!
Gonna try this, thanks!
Do you sequence the recording of the pads at all?
I’d love to see a demo of that workflow.
After the SP404 integration, I’d really love to see an update to the Koala Stems separation. It’s great to have it, but with the AKAI version is very good from the outset and Serato has been getting better and better through it’s lifecycle.
1 Like
Not usually, I tend to just record single notes and crop them to be single cycle waveforms or keep them as one shots
1 Like
Sorry, can’t help it 
2 Likes
hell yeah thanks for posting that’s great news
1 Like
I never actually asked you to make a video on it.
Sorry, I couldn’t help it.
1 Like
Guys, I need your help!
I installed Koala on my Android tablet (and phone) and when I first plugged the USB from my AR it went all fine. Unfortunately, I can’t get it to work anymore despite having the same settings. I installed Midi Commander on my tablet and it does recognize the AR, but the transport send just won’t happen, not matter if use my phone or tablet.
AR settings: transport send, clock send. output: MIDI+USB. Global config: USB MIDI
Koala setting: MIDI external sync activated
What am I possibly missing out here?
Vincent
If you scroll up a little bit you’ll see we discussed this and the developer is working on an update soon
2 Likes