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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

BeatMaker and Apple Loop Export

espiegel123espiegel123
in General App Discussion

I have been experimenting with exporting BeatMaker 3 sliced samples as Apple Loops. The slice markers are there but it seems that the tempo information is not being exported.

I am wondering if others are exporting as Apple Loops and having a different experience.

I am using the exported loops in BeatHawk.

I am wondering if Beatmaker 2 behaves differently.

Comments

  • wimwim

    Have you tried any in Garageband, to eliminate BeatHawk as the cause?

  • espiegel123espiegel123

    @wim said:
    Have you tried any in Garageband, to eliminate BeatHawk as the cause?

    They also don’t behave as I’d expect in GarageBand. For example, a one measure drum loop doesn’t come in as one measure. My guess is there is missing tempo metadata but I could be mistake or doing something wrong.

    I am wondering if someone with BeatMaker 2 could export a one or two bar drum loop that I could try to see if it behaves differently.

  • rs2000rs2000

    @espiegel123 said:

    @wim said:
    Have you tried any in Garageband, to eliminate BeatHawk as the cause?

    They also don’t behave as I’d expect in GarageBand. For example, a one measure drum loop doesn’t come in as one measure. My guess is there is missing tempo metadata but I could be mistake or doing something wrong.

    I am wondering if someone with BeatMaker 2 could export a one or two bar drum loop that I could try to see if it behaves differently.

    From https://forum.audiob.us/discussion/7483/how-is-beathawk-better-than-beatmaker-2

    @Korakios said:

    @Peter321 said:

    I imported some Acid files which where supposed to work with the automatic tempo adjustment, but so far they seem to work just like normal .WAV files, so not sure what's going on :-(

    The user library does not seem to support folders, so importing 100's of samples of your own does not seem feasible, they want you to buy their packs instead, which are nicely organized.

    I downloaded some free acidized free loops plus I export some wav loops from Reaper with the option to store tempo info. On the acid loop beathawk does not read the slice info but reads on both samples the bpm info and it locks the samples to follow Beathawks tempo...
    ...

    So BH can read it and Reaper can export it.
    Looks like it just has to be the right BPM attribute in the WAV file. There are several, incompatible ways to embed BPM info in WAV files.

  • espiegel123espiegel123

    @rs2000 : Am I missing something in that thread about BeatMaker Apple Loop exporting?

  • rs2000rs2000

    @espiegel123 said:
    @rs2000 : Am I missing something in that thread about BeatMaker Apple Loop exporting?

    Certainly not. I suppose that BM simply doesn't tag the files correctly.
    Dunno if you've seen the Pythonista hack (done by @MrBlaschke and me) but a similar hack might be possible with WAV files from BM2/BM3. There is a Python library available for WAV file handling but I'm not sure which tags it supports.
    You would have to enter the bpm manually (except the info is hidden somewhere else in the file) but at least (I hope) it could be written to the file for use in BeatHawk.

  • espiegel123espiegel123

    Is anyone exporting Apple Loops from BeatMaker 2 or 3 and having them work correctly in either GarageBand or BeatHawk?

    Has anyone exported loops from any other app that are seen as loops in BeatHawk or GarageBand so that they adapt to the tempo correctly? I've seen a few references to files from iMPC Pro 2 being seen as loops in BeatHawk and GarageBand but haven't seen any confirmation.

    If someone has iMPC Pro 2 or BeatMaker 2, could you do a simple test to help me figure out if either of those would work?

  • espiegel123espiegel123

    @espiegel123 said:
    I have been experimenting with exporting BeatMaker 3 sliced samples as Apple Loops. The slice markers are there but it seems that the tempo information is not being exported.

    I am wondering if others are exporting as Apple Loops and having a different experience.

    I am using the exported loops in BeatHawk.

    I am wondering if Beatmaker 2 behaves differently.

    I found the source of my problems. When exporting Apple Loops, BeatMaker 3 sets the tempo metadata to the project's tempo rather than using the tempo that you have entered for the sample. So, if you are doing your slicing/exporting from a project whose tempo is different from the loop's, the tempo doesn't match the loop.

    The workaround is to export from a project whose tempo matches the loops.

  • mistercharliemistercharlie

    @espiegel123 Nice detective work! That’s an annoying feature/bug, but not too bad.

    Now you’ve got me wondering about doing it this other way around: using Apple Loops in BM3.

  • rs2000rs2000

    @espiegel123 said:

    @espiegel123 said:
    I have been experimenting with exporting BeatMaker 3 sliced samples as Apple Loops. The slice markers are there but it seems that the tempo information is not being exported.

    I am wondering if others are exporting as Apple Loops and having a different experience.

    I am using the exported loops in BeatHawk.

    I am wondering if Beatmaker 2 behaves differently.

    I found the source of my problems. When exporting Apple Loops, BeatMaker 3 sets the tempo metadata to the project's tempo rather than using the tempo that you have entered for the sample. So, if you are doing your slicing/exporting from a project whose tempo is different from the loop's, the tempo doesn't match the loop.

    The workaround is to export from a project whose tempo matches the loops.

    Good to know, thanks!

Sign In or Register to comment.