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.

SOLVED THANKS ALL What Newb mistake am I making?

Ok made some beats in iSpark at 120bpm.
Exported them to Audioshare.
Imported them to Auria Pro.
Made new project and set to 120bpm.
Imported each file into an audio track in a row.

Problem the beats of the audio are shorter than the beats of Auria. Can't say I've had this before when taking audio this way from other drum machines.

So what stupid thing am I doing? Lol

Comments

  • edited September 2016

    I've encountered similar issues, but randomly, and with various apps. Not sure if it's a clock sync / quantize sort of thing, but it can certainly happen in this ecosystem. Are you zooming Auria down to the sample level on your waveforms and making certain that transient one of your drum loop is exactly at the front of the region. Sometimes even a seemingly minuscule amount of dead space at the beginning of a region can make things sound not tight. Though it doesn't sound like that is your issue if the regions are too short to match your 120 BPM grid. Do they sound way off when you play the metronome in Auria, or just slightly? If it's negligible, and you are tied to those recordings, you could try quantizing the audio in Auria using the transient detection feature. that usually works pretty well with a bit of fine tuning I've found.


  • This is a pic of where the 2 bar audio is reaching to in Auria.
    I've checked it's exactly at the start of the track. The beats don't correspond with Auria at 120 at all

  • @Fruitbat1919 said:

    This is a pic of where the 2 bar audio is reaching to in Auria.
    I've checked it's exactly at the start of the track. The beats don't correspond with Auria at 120 at all

    Indeed they don't. Was iSpark possibly being controlled via Link and tied to a different BPM than what it was displaying? I am not familiar with iSpark so I'm afraid I can't offer much help there, but I have seen some apps that show a native BPM, different from the BPM being used via a Link setup. Also, any chance iSpark was operating at an off time signature different from the 4/4 you've got setup in Auria?

  • @brice said:

    @Fruitbat1919 said:

    This is a pic of where the 2 bar audio is reaching to in Auria.
    I've checked it's exactly at the start of the track. The beats don't correspond with Auria at 120 at all

    Indeed they don't. Was iSpark possibly being controlled via Link and tied to a different BPM than what it was displaying? I am not familiar with iSpark so I'm afraid I can't offer much help there, but I have seen some apps that show a native BPM, different from the BPM being used via a Link setup. Also, any chance iSpark was operating at an off time signature different from the 4/4 you've got setup in Auria?

    Thanks will do some more checking :)

  • I've tried exporting direct and still the same.
    I've tried importing other 120bpm 2 bars and they are fine.
    Seems the problem is with iSpark showing 120bpm 4/4 but not exporting at the correct timing as the length of the audio is more akin to between 125 and 126bpm

  • maybe they use different sample rates for the base calculation ?
    at least visually it fits the 44.1 to 48k difference...

  • @Telefunky said:
    maybe they use different sample rates for the base calculation ?
    at least visually it fits the 44.1 to 48k difference...

    Auria shows them as 44.1 16 bit files.

  • @Telefunky said:
    maybe they use different sample rates for the base calculation ?
    at least visually it fits the 44.1 to 48k difference...

    that would have been my guess too, had this problem in Cubase recently and it turned out to be different sample rates in the project settings and the imported loop

  • @cabo said:

    @Telefunky said:
    maybe they use different sample rates for the base calculation ?
    at least visually it fits the 44.1 to 48k difference...

    that would have been my guess too, had this problem in Cubase recently and it turned out to be different sample rates in the project settings and the imported loop

    Yep I was thinking that this might be the answer, but Auria is set to 44.1 and works fine with other beats I'm importing to the project. The only one wrong so far is anything from iSpark.

  • Did you use 'snap to beat' in Audioshare?

  • @robosardine said:
    Did you use 'snap to beat' in Audioshare?

    Was going to suggest the same, just as a test for the source file(s). Could also drop it in Loopy with 'Stretch Imported Loops' turned off. Set both/either apps to 120bpm and see if the iSpark loop lines up. If not, Rolf! If so, Rim!

  • if you don't find any preference settings and the beats play in sync on their native system, it might be an internal process.
    Shit happens - I've seen it before with the first version of the Logic Sample Rhodes (EVP88 iirc) which was detuned 1 half tone due to this fact.

  • @robosardine said:
    Did you use 'snap to beat' in Audioshare?

    I've ditched the AudioShare route and now just exporting direct to Auria, so that I know it's nothing to do with AudioShare making issues.

  • @syrupcore said:

    @robosardine said:
    Did you use 'snap to beat' in Audioshare?

    Was going to suggest the same, just as a test for the source file(s). Could also drop it in Loopy with 'Stretch Imported Loops' turned off. Set both/either apps to 120bpm and see if the iSpark loop lines up. If not, Rolf! If so, Rim

    Think it's Rolf lol

  • @Telefunky said:
    if you don't find any preference settings and the beats play in sync on their native system, it might be an internal process.
    Shit happens - I've seen it before with the first version of the Logic Sample Rhodes (EVP88 iirc) which was detuned 1 half tone due to this fact.

    Just recorded in as Audio from iSpark straight into Auria and the Audio is in sync this way. So it's happening with the export process of iSpark.

    Well at least I know it's not me being stupid...well I think not lol

  • I did suffer from something similar with iSpark, I fixed it by disabling link and resetting the bpm and re-saving the song file before exporting.
    I remember always checking the BPM immediately before exporting as it could load up with a different bpm to what I thought should be there.

  • @AndyPlankton said:
    I did suffer from something similar with iSpark, I fixed it by disabling link and resetting the bpm and re-saving the song file before exporting.
    I remember always checking the BPM immediately before exporting as it could load up with a different bpm to what I thought should be there.

    You've cracked it! Changing the tempo and then back to 120 has cured the problem! :D

  • @Fruitbat1919 said:

    @AndyPlankton said:
    I did suffer from something similar with iSpark, I fixed it by disabling link and resetting the bpm and re-saving the song file before exporting.
    I remember always checking the BPM immediately before exporting as it could load up with a different bpm to what I thought should be there.

    You've cracked it! Changing the tempo and then back to 120 has cured the problem! :D

    ;) Sorry I didn't see this earlier, could have saved you some messing around.

Sign In or Register to comment.