Each effect app starts up with the output muted to avoid feedback. After a couple of seconds it checks to see what input and output it’s connected to. When the audio route is using both the built-in mic and the built-in speaker of your iOS device, the app stays muted — otherwise you can get some pretty nasty squealing. In other cases — say you’re using headphones or connecting to another app via Audiobus — it should unmute. But sometimes that check gets it wrong — e.g. when the audio route hasn’t finished setting up — so the app stays muted. If you aren’t getting any sound through, check the app isn’t muted. If it is, just press the mute button to unmute.
You can do that with the built-in mic and speakers too, if you love a bit of howling feedback. And what right-thinking person doesn’t?
Okay, they aren’t asked that frequently, but we’ve answered them anyway, just in case.
Frankly, we don’t know for sure. Some of our beta testers have successfully used the software on an iPad 3. Clearly it will also depend on what other apps you are running at the same time. If you have an Audiobus chain full of heavyweight instruments and FX, one of ours might wind up being the one that tips you over the edge.
Yes! Learnable MIDI CCs are implemented for all effect parameters in versions 1.1 of Muckraker and Frobulator. Nebulizer and subsequent apps will have this functionality from the start, thanks in large part to Audeonic’s spiffy MidiBus library.
Neither Frobulator nor Muckraker has any parameters for which sync makes much sense right now. That’s not the case for some of the other things currently in development, and we aim to include MIDI sync where it’s relevant. Watch this space!
Probably. But at the moment we haven’t quite worked out what that’s going to entail. So it be won’t happening right away.
Doubtful. There probably isn’t anything in the app that couldn’t be made to work with iOS 7, but some things would take a fair bit of work and we have no way of testing them. We appreciate some people are still wedded to iOS 7, but we have to work with the development landscape we find ourselves in. The sad reality is that supporting old systems is all cost and no benefit. Don't forget, we’re doing this for free.
Almost certainly not. The whole codebase is heavily tied to iOS, so porting would basically mean writing new apps from scratch. These just aren’t the sort of apps for which there is enough market to make that worthwhile.
Also, we really hate Windows programming.
The tempo of the different delay layers is fixed. You can disguise that a bit by fiddling with the modulation controls, but ultimately it’s an inescapable limitation of the app.
You might want to look at the Frobulator tech page for some background to this.
If you have a problem that isn’t addressed above, or you want to report a bug or make a feature suggestion, please send us a request. Include as much detail as you can — remember, we can’t help unless we can figure out what’s wrong.