« JamUp Updates | App News | Echo Pad Updated with even more Effects »

Meteor Multitrack Recorder updated with Audiobus!

Meteor Multitrack Recorder is the latest DAW to add Audiobus support!

Thanks to reader Littlewoodg for the news, who notes it, "runs like butter with the most CPU-intensive audiobus-ready synths."

What's new in 1.4:

This version of Meteor now supports the AudioBus application, allowing you to record live audio directly from other compatible applications.

Allowed transferring of .mov, .m4a and .m4v files to and from DropBox.

You can now import videos from a file as well as the Camera Roll (using the video plugin).

Added a Reset Audio option to the 'Help' menu.

Added support for push notifications.

Fixed a bug which prevented pan controllers to be transmitted to connected MIDI instruments.

Buy Meteor Multitrack Recorder on iTunes: $19.99

Reader Comments 18

Doesn't run like butter on iPad 2. The Audiobus guys really need to allow users to change the buffer size, it's way too low right now. Probably wont happen tho since they actually keep saying on their forum that users are idiots and a settings option window/menu would totally confuse our fragile minds. There are ways around it tho like starting Nlog, which scales the buffer size according to the device. On iPad 2 it sets the buffer to 512 (dubble the Audiobus requirements) . And any subsequent apps can't change that buffer. Makes things run smoother, with hardly any more noticeable input lag. Turn off all the effects in Nlog and it shouldn't steal any CPU according to Rolf (the Nlog dev).

Btw, the implementation is a bit buggy. I get two meteors in Audiobus, meteor and meteor1. And it needs to start meteor 2 times to work.

January 21, 2013  | person_outline ChrisG

Hello Chris,

re: Meteor turning up twice - has been fixed now. Just delete Audiobus and install it anew.

re: You blaming us that we don't listen to users: here's a screenshot of the upcoming version of Audiobus: http://imgur.com/fWLLLWQ

I wish you'd have used a more friendly tone because I'm very sure that I've never insulted you or called you an idiot. Depicting us in such a way is uncalled for.
The workaround you're describing is also very confusing to new users so I'd rather you would't suggest it to them. It also has a few negative side-effects which I don't want to get into here because they are actually pretty hard to explain.



January 21, 2013  | person_outline Sebastian Dittmann

If there's one thing that really turns me off about the iOS music "community", it's how often I run into people who talk shit about developers and display a ridiculously bloated sense of entitlement. They seem to infest every iOS music blog, forum and app reviews.

Michael and Sebastian are both friendly, helpful guys and they know what they're talking about. If this wasn't the case, Audiobus wouldn't be as good as it is.

January 21, 2013  | person_outline K△LT

Your stance on this was no buffer settings screen becouse that would simply be too confusing for a user. We were idiots basically. But hey, glad you changed your mind. Looks good.

January 21, 2013  | person_outline ChrisG

:-) The iOS music developers are awesome in every way, and almost always ridiculously under-appreciated and under-paid. Users need to go spend some time with the alternatives (Google / Intel / Microsoft's answer to tablets and phones in the music app space) to get some perspective.

January 21, 2013  | person_outline rrr00b

These settings ARE confusing, because the way they function. Many developers don't understand them fully because they are simply not documented entirely by Apple - especially in a multi-tasking environment.
We're in a privileged position with Audiobus because the way that our users launch Audiobus first before other audio apps and then launch other apps from within Audiobus means we get a little more control over the whole session.

I once again urge you to not put any words into my mouth that I definitely didn't use.

January 21, 2013  | person_outline Sebastian Dittmann

IPad 2 here also, having a blast with Meteor and Audiobus with not a single problem. I am finally doing everything I've wanted to do. I am so happy about how rock solid it has been, and I've not stopped creating, playing, and recording since the Meteor update. I think I may pass out soon from lack of sleep but I'll be sleeping with a smile on my face, so please don't let one critical customer scare you away.

January 21, 2013  | person_outline ZenLizard

Agreed. The unfortunate reality of most online communities is that there is no one checking IDs at the door, so the childish attitudes are bound to show up. Having followed this project from very early on, I am blown away by the amount of thought, effort, and professionalism that has gone into creating Audiobus and rallying scores of independent developers in support of it. There is a huge investment on many fronts that goes into a project like this with no guarantee of success or acceptance. Dropping $10 at the end of the process does not entitle one to anything but a file download. If you want developers to respect your issues and requests, then treat them with the respect they deserve - THEY earned it.

January 21, 2013  | person_outline iClifDotMe

ChrisG: It isn't just that having a setting is too confusing to the user. I have had to handle a lot of email questions related to latency in my own app - so it's actually an empirically verifiable fact that this translates into support costs. "Why is this glitching" vs "Why am I suddenly getting an unplayable amount of lag". The only answer that fixes both problems is to speed up the app that can't keep up.

Non-sequencer apps that you actually play in real-time will have their usability broken when this switch is turned on (512 is just above the threshold of what's usable for interactive use); essentially having one app break another.

I understand that it's unavoidable on some level though; as some combinations of iPad and apps just won't be able to keep up. 256 is actually still a little too high. For interactive use, you need to get down to about 64 where the buffer sizes aren't perceptibly screwing up the audio rendering. Google on Geert Bevin's post about the necessity of also making jitter go to zero by scheduling all events at the sample-level (slightly higher average latency in return for zero jitter).

January 21, 2013  | person_outline rrr00b

Seb: No you didn't use the word "idiots". Anyway, we seem to be on completely different wavelengths here. I'm talking about what the end-users see and experience on their tablets, PCs, MACs whatever. Not all that "confusing stuff" that goes on behind the curtains.

rrr00b: Si señor I'll google Geert!

January 21, 2013  | person_outline ChrisG

I'm wating for beatmaker 2 update... But when i saw this, it's hard to resist!

January 21, 2013  | person_outline Gatan

A note about latency with Meteor pre- the next Audiobus update (the updaye pictured above addresses latency issues, more thanks due to Michael and Sebastian): the Meteor implementation of Audiobus includes a description of how to use Meteor with Audiobus in the "What's New" section of the user manual. The steps there say to open Meteor first, so it's latency protocols can set the latency #s for apps that are opened afterwards. As is the case with many 4pockets apps, it's a good idea to read the freakin manual. The 4pockets guys - like the Audiobus guys, and in this case in conjunction with the Audiobus guys - have already figured out stuff that easily eludes users. I've found that 99 times in 100, my compaints about app implementation, UI, functionality etc etc are resolved when I educate myself by reading the material provided by the apps developers.

January 21, 2013  | person_outline Littlewoodg

Sorry for the offtopic, Has anyone known what happened with Geosyhth and Samplewith developers!?
They don't respond to emails. I'd like to know, are they planning to implement Audiobuz

January 22, 2013  | person_outline Mishik

@sebastion, that screen looks great. "Sequencing" vs "Playing Live" sound less scary and more purpose driven to me.

January 22, 2013  | person_outline Will

it might be helpful, for both end users and developers, to constantly be mindful of the fact that we're all trying to push the envelope, so to speak. we expect (perhaps somewhat unrealistically at present ) to be able to 'produce' content (music, videos etc.) on devices that were principally designed to 'consume' content (music, videos, books, internet, etc.). it's early days, be patient.

January 22, 2013  | person_outline a1

Mishik: I am the GeoSynth developer. I am on the task, trying to get Audiobus into my stuff, but it will be a while. I understand the importance of implementing Audiobus, but I am not a full-time app developer; progress on random midnights during the week.

But for right now: Geo is primarily a MIDI controller, and the synths that it controls generally already have audiobus (turn the volume all the way down in Geo turn off Geo's internal engine). I generally prefer to use ThumbJam or Arctic.

January 22, 2013  | person_outline rrr00b

I want someone to help me how to import midi section to my I pad 2 and open it with the meteor

April 20, 2013  | person_outline Farid ch

If you have a Dropbox you can do it in there, pop the midi file into the meteor folder and then import them then .... You may have to edit the drum track though

April 21, 2013  | person_outline Bianca

  Post a New Comment

Anonymous comments are closed for old articles. If you'd like to comment please Register.


Do not use HTML in your comments. Tags: [b] Bold Text [/b] [i] Italic Text [/i]
Links will be generated if you include http:// or https:// at the beginning of a URL.

Contact | Privacy Policy | Developer Services | Advertise
discchord.com is a service of Gnubesoft