Importing Loops: Audio vs Midi

Question

Level 1

0 points

Importing Loops: Audio vs Midi

Hello-

I have searched for an answer for this question but have not found one.

Assumption: There are two types of loops: Midi loops and audio loops. Apple also refers to audio loops as "Real Instrument" loops. Audio loops are basically small recordings of real instruments being played versus a Midi loop which is computer data used to trigger a sound.

I have successfully imported both types of loops into Garageband for iOS. File extension .aif for audio loops and .mid for midi loops.

In Garageband for iOS:

1. Imported Midi loops automatically match the tempo and key of the existing song they are added to.

2. Imported audio loops do not automatically match the tempo and key of the song they are added to.

Question: Some of my best drum loops are audio recordings of real drummers. How do I adjust the tempo of these audio loops in Garageband for iOS? Is it even possible?

Question: When I do import the audio loops, because they do not adjust to the tempo, they do not line up on the bar markers properly and therefore do not "loop" properly. Is there a fix?

Question: Also, when I do import the audio loops, because they do not adjust to the tempo, the built in metronome does not line up on the beat. Is there a fix?

Any help is greatly appreciated.

iPad, iOS 5.1.1, Mac user since 1989.

Posted on Apr 8, 2013 10:14 AM

Reply

Answer 1

Apr 10, 2013 10:47 AM in response to tomjangaard

You are touching the topic of Apple Loops that are easy to use but once you are getting into details, are a little more complex.

Some of your assumptions are right, others are wrong and that is where you get stuck. Let me get you a few facts:

Apple Loops are always audio files (i.e. aiff or caf)
.mid are MIDI files not MIDI Loops
There are two types of Apple Loops: Blue (Audio Loops) and Green (MIDI Loops)
Green Apple Loops (aka MIDI Loops) contain the additional MIDI file and Track information (instruments, effects).

The different terminology that is used makes it very confusing. Here is a screenshot from my GarageBand manual

Here is another screenshot that illustrates what happens when you add Apple Loops to Garageband

If you want to learn more about Apple Loops, I have also free manual on my website ("Apple Loops") that explains all the details about Apple Loops. Go to my website and click on the "free Manuals" link at the bottom of the page.

http://DingDingMusic.com/Manuals

These are the requirements for an Apple Loop

An Apple Loop

has to be properly truncated
has to have transient markers to enable tempo and key matching
has to have additional metadata (search capabilities)

The problem you are describing is the result of issues with any of the points above.

If your Loop doesn't match the tempo (and/or key), then it doesn't have the proper transient markers set.

If your Loop doesn't start at the downbeat or doesn't line up, then it wasn't truncated correctly

About a .mid file. This is not a Loop. MIDI files contain data matched to a tempo grid and not to an absolute tempo that need to be matched. The MIDI data (if recorded correctly) matches automatically your tempo and matches your key if you set that feature in your program. This is the advantage of MIDI files. Audio Loops are created to enable that flexibility for audio file too.

Hope that helps

Edgar Rothermich

http://DingDingMusic.com/Manuals

'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Reply

Answer 2

tomjangaard Author

Level 1

0 points

Apr 12, 2013 12:01 PM in response to EdgarRothermich

Thanks very much Edgar, for the detailed answer. It was very helpful. I looked at your Apple Loops pdf and it was helpful also.

The weird thing is when I use these loops in Garageband for OSX, they work fine. Its when I'm importing them into Garageband for iOS that they don't line up, change tempo, etc.

Is this because Garageband for iOS is less featured?

Reply