Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Audiobus 48 KHz is needed
Since most IOS I/ O audio gear is finally 24bit 48kHz capable ( or better) not to mention the growing list of apps shouldn't Audiobus be updated also? I would like to use professionally what I produce on the ipad but I cannot use audiobus for anything because 48 KHz minimum is required.
Comments
I would second that request.
Using a 48 kHz audio interface, AudioBus have a strange number of frames in "Latency Control": 235 frames, i.e. 256 / 48 * 44.1 and every Input shows an error and/or no sound.
Figuring out it was due to the lack of 48 kHz audio support had me loosing some time.
48 kHz audio support, or a least a clear statement about supporting only 44.1 kHz and above, would be appreciated.
Keep on the good work btw. Thanks.
I third it. I have devices that connect to iDevices that are aggregated with others on a Mac and I can't run the whole kaboodle at more than 44.1 whereas other gear in the aggregate I'd like to use to record at 48k. So, I'd like to suggest that AB have the ability to at least support 48k - not that it necessarily be the default though.
Fourthed.
I do all of my tracking at at least 48k and would love to have a shared sample rate between iOS and OS X.
News about this?
We agree! I'm looking into this at the moment. It's something I began working on last year, but there were more pressing things at the time. I'm resuming that work now.
48KHz DAT sounds good.
I 2nd, 3rd, 4th and 56th this :-D
If audiobus goes 48khz will my akai eie red face 44.1k continue to work?
From what I've read. And I've read a lot about this. 48k & 96k are easier on the processor than 44.1 due to the math conversion by the CPU. e.g. it's less processing to get better sound. Not that I can hear the difference though admittedly.
Good question. My guess is yes, although stranger things have happened.
Oh, wait, I don't think 44.1 should be abandoned, just that 48k should be there too! :-)
Pretty much all video (i.e., serious videos and broadcast, not amateur selfies) is 48KHz.
I second^n 48K. For me, I author for HDMI LPCM which is 48K. 48K is a rational number for frame size computations. 44K1 is not. That gives me headaches.
24/96 is what I use on the mac
the upcoming version of ivcs does 96khz with an audio interface
so lets have 48khz now
Looks like I'm now in the 48k boat with the rest of you all after getting a new processor/iOS interface that doesn't support 44.1k.
Wow, that sucks. Really sorry to hear that. Nothing will kill that new gear smile like silence.
I'm all for a standard, accepted bare minimum of 48K, but we still have a handful of rather significant apps that don't even do 24-bit, let alone 48K – as AudioCopy kindly reminded me just a few days ago ...
Things are going to get better. Mike's already testing 48khz Loopy and Audiobus is going to follow. After that other DAWs/hosts are going to join as well if they don't already support it. Patience
max specs for iOS are 24/48 and 5.1
nothing supports this software wise
nothing supports surround mixes yet?
why?
doing a little surround panning with a xy box can't be rocket science
yes 5.1 is exotic, but when to start if not now?
I am pretty sure if you like 4k video you will like 5.1 and 24/48 or 24/96
so we can edit what 3 or 4 streams of 4k video in imovie on iOS, but our sound will be 16/44.1 stereo
hm, wtf apple?
i just looked into my audio midi set up,
the iPad only outputs 44.1khz over the lightning port
this is bad
The newest version of AB doesn't automatically give me the weird unsupported 118 frames rate when I connect my 48k interface. On the previous version, AB wouldn't even let me load apps without errors at 48k, but now I can. So it seems AB supports 48k now? We just need apps to become compatible with 48k?
iPads are still 44.1 I believe. Newer iPhones are 48k. I think most of the time it is better to stay at 44.1, unless you have a newer iPhone, in which case I have no idea what rate you should work at.
I'll accept the thrown tomatoes & "'what the f's", but in this age of streaming, compression algorithms and now the LUFS standard, I think going to 48k from 44.1k is negligible at best. If you're interested in high quality archival 96k+ is the usual go-to...48k isn't.
I'll admit I never bought the advantage of 48k over 44.1k in the DAT days, or when MDM's (Modular Digital Multitracks) like ADAT's & DA-88's had 48k as standard. It was just a pain in the ass when your master was going to be 44.1k/16 bit.
And I had guys bugged eyed saying I was nuts but I remember we did 2 big blind tests at a project studio in the early 2000's with about 6-8 dudes, engineers & musicians. NO ONE, me included, could tell which one was the 48k.
If you can, by all means go for it, use 48k. I also find it funny the one's who do go higher resolution will sometimes be making EDM where they've added saturation plug ins and distorted dub kicks & basslines...
Audiobus is never used here - because of being crippled at 44.1k
I agree with @JRSIV the audible improvement of 48k over 44.1k is close to nothing.
It's a workflow thing in the 1st place (if your library is based mostly on 48k samples or if you're doing video, etc)
96k isn't worth bothering in that context either, unless you do audiophile acoustic recordings or some very high end low loudness electronics.
For any contemporary production it's a waste of effort because the usual 'mastering' introduces tons of artifacts (intentional clipping and high THD rates).
Let alone the use of consumer grade converters and average plugins.
I'm picky about sound, microphones, preamps... and made a lot of comparisons with higher sample rates, but never even had a glimpse of an improvement worth building a workflow upon.
A fellow with a similiar setup does indeed all of his work based on 96k and is convinced about it's advantage, but I fail completely to hear that in his published results.
Tbh I really like a bit of a gritty digital undertone here and there in a mix as an additional sound color. Nothing is as boring as everything beautifully clean processed - which does NOT mean drive or distortion, it's a more subtle aspect of basic sound processing.
I thought the issue was fixed as of Audiobus version 3, can someone double check please?
(I don't use iOS device for music these days)
By the way, the point here is not an idiophil talk but a feature request. People have their reasons, please respect them.
@melomac I still see no setting related to sample rate in Audiobus 3. Just buffer settings. Nothing in the manual about 48k, either.
My guess is it still is just 44.1k, unless it switches itself between 44.1k and 48k without you having any say, which would seem problematic.
there is no question that any sample rate (of common gear) SHOULD be supported.
But several resonses were about a supposed inferiority of the 44.1 khz rate.