Three problems i've encountered so far...
HI, just starting with Drambo, actually the first piece of ipad software which made me seriously consider using tablet instead of 'proper' music gear...anyways, i'm having some issues so i'll just put it here, sorry if it's already reported.
- I have hard time syncing Drambo with other apps inside of AUM. My plan is to use miRack and Drambo together like i'd use eurorack and octatrack together, meaning that i'd generate some cool sequence with turing machine or something similar, drive a synth directly or record that sequence to a sequencer of drambo/octatrack, and then add some drums or whatever directly from octatrack. RIght now i can't even make some simple basic sequences to play perfectly in sync, not even talking about recording stuff. Every time i restart transport in AUM it goes all over the place. Developer of miRack, who i've communicated with, says that Drambo has a weird way of starting/restarting it's clock/transport, like it doesn't wait for the bar, or it doesn't go to the beginning and starts from where it was...sorry, i can't explain better, i only know that sync problem is real, and that it's not likely a problem in miRack(although midi out is a beta function), simple because miRack syncs with other midi sequencers perfectly, it's only the Drambo which gives me hard time.
- Midi input in Drambo. Even if i set Receive midi on some particular track to Never it still gets all the midi data, and if i program a step it just programs a chord often, although there should be no input, unless i misunderstand what Never means....
- HUGE CPU spikes when Drambo GUI is open, which i think are somehow connected to crossfader functionality. It's like goes from 30% to 130% sometimes when i move the crossfader with only a couple of parameters assigned to it...
- Not really problem, haha, but why is there no step components for changing the sequence direction? It is such a basic functionaly in any more or less advanced sequencer...Sorry, this fourth thing doesn't really belong to the list, but i just couldn't help it)
Thanks for the great app, it's a lot of fun!
Comments
It's what I also reported, it seems that the sequencer still gets midi input the track itself not. Guess we should mention it again to @giku ;)
@nnbveh About 3. CPU spikes
Standalone or AUv3?
If AUv3, which host?
What's the audio buffer size you've used?
What iDevice and iOS version?
What parameters are you controlling by the crossfader?
I've just tried in AUM with a few parameters morphed and when crossfading, I don't even see a difference in CPU load.
Does not for me, i can literary set up two track in drambo both sending impulses on the same step, one is controlled by the internal sequencer, and one by the sequencer in miRack and they are out of sync, and every time i restart out of sync differently...
Auv3, inside AUM, buffer was set up to 256, i shall try bigger one i guess, ipad 9,7 with the latest os, parameters were different in different cases but mostly something like filter cut off, maybe resonance, shaper amount...don't really remember, i was just messing around, built-in modules...
ok, i'll try to tonight! and yes, it's synced...
@nnbveh You're right, that's not tight.
oh no, sync wars again!
I’ve been battling sync issues on iOS from the day one. I actually don’t have any major issues with AUM in AU but Drambo is the only sound source other than loopy and Samplr (both IAA) and I always assumed that they’re the ones responsible for any marginal fluctuations (flam).
I’m using link these days and don’t have complaints.
iPad Pro 10.5 13.5
GUI related cpu spikes are common on iOS.