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 3 Resampling out of sync?

Yeah, forever the optimist. I was holding back on this but thought most of the issues were more or less sorted. Felt the need for something more DAW like as I never finish anything.

Hoping this one is user error but I can't figure out how. Basically sync record isn't quite syncy enough. The video shows the issue basically, flamtastic.

I've tried every imaginable permutation. Koala (as example) as IAA, Recording to pad, to audio track, changing latency (there's a clue there because it makes a difference to how far off thing get). Any BM3 vets confirm this is an issue?

Shame because I really like what BM3 has to offer but this is a bit of a deal breaker, I just can't be bothered to be doing battle with timing issues and resampling is a key feature for me here.

Comments

  • BM3 is not without its share of issues that's for sure.

    Have you checked if/how the different buffer sizes affect the 'delay'?
    What is your buffer size set to? (Settings>Audio).

    Are any effects loaded on the track?
    I guess no, but limiters and plug-ins with oversampling/lookahead cause some pretty nice delays due to lack of plug-in delay
    compensation which makes it even more 'interesting'.

    If the 'delay/flange' changes when changing the buffer size in BM3 it's a definitive bug...
    (Cubasis has similar issues as well when playing back a frozen track and the live one)

    I guess other BM3 users will chime in in due time...
    Cheers!

  • @Samu said:
    BM3 is not without its share of issues that's for sure.

    Have you checked if/how the different buffer sizes affect the 'delay'?
    What is your buffer size set to? (Settings>Audio).

    Are any effects loaded on the track?
    I guess no, but limiters and plug-ins with oversampling/lookahead cause some pretty nice delays due to lack of plug-in delay
    compensation which makes it even more 'interesting'.

    If the 'delay/flange' changes when changing the buffer size in BM3 it's a definitive bug...
    (Cubasis has similar issues as well when playing back a frozen track and the live one)

    I guess other BM3 users will chime in in due time...
    Cheers!

    It does seem down to buffer size. I did an experiment resampling the same pattern with incremental buffer sizes, none synced up. Interesting Cubasis has a similar shortcoming.

    Seems half the learning curve is figuring out whether unexpected behaviour is a bug or user error, bit tedious. Almost tempted to request a refund but there's so much potential in this one.

  • @SpartanClownTide said:

    Seems half the learning curve is figuring out whether unexpected behaviour is a bug or user error, bit tedious. Almost tempted to request a refund but there's so much potential in this one.

    There's always the option adjust the start point of the recorded audio so it matches up...
    ...at least it's a constant delay and not a drifting one...

  • It‘s neither bug nor user error, just a missing feature... imho.
    Your sampled section has to make a transition from record buffer to playback buffer after the record stops.
    What you hear is an insertion right at the playhead’s point of time in the stop-moment.
    But of course you want that location to be the original start point of the source (the moment you pressed „start recording“).
    It‘s an easy fix for the developer if the buffer organisation is appropriate.

  • It could be an interesting experiment to do an export of the track in question and import the resulting audio to a new audio-track to see if they are in sync or if the delay is still there.

  • I fact... they might have delayed delay compensation until rendering o:)

  • @Samu said:

    @SpartanClownTide said:

    Seems half the learning curve is figuring out whether unexpected behaviour is a bug or user error, bit tedious. Almost tempted to request a refund but there's so much potential in this one.

    There's always the option adjust the start point of the recorded audio so it matches up...
    ...at least it's a constant delay and not a drifting one...

    There's probably workarounds yeah, still a shame as the big attraction for BM3 was the old "streamlined workflow" chestnut. No distractions or interruptions (or workarounds for shonky implementation). No rabbit holes for geeks lacking self control.

    Talking of which, as a point of interest, did an equivalent test with Drambo. The resampled pattern matched up flawlessly. Perfect, sample for sample. Guess I just have to work on my self discipline. 😁

  • @Telefunky said:
    It‘s neither bug nor user error, just a missing feature... imho.
    Your sampled section has to make a transition from record buffer to playback buffer after the record stops.
    What you hear is an insertion right at the playhead’s point of time in the stop-moment.
    But of course you want that location to be the original start point of the source (the moment you pressed „start recording“).
    It‘s an easy fix for the developer if the buffer organisation is appropriate.

    Ha, nice one, that would explain it. Hopefully it's on a long todo list because honestly this thing is really nicely designed. Oh well, living in hope.

  • @Samu said:
    It could be an interesting experiment to do an export of the track in question and import the resulting audio to a new audio-track to see if they are in sync or if the delay is still there.

    OK in the interests of science. Exported the pattern to audio, imported to a new audio track and yes now they sync properly.

  • @SpartanClownTide said:

    @Samu said:
    It could be an interesting experiment to do an export of the track in question and import the resulting audio to a new audio-track to see if they are in sync or if the delay is still there.

    OK in the interests of science. Exported the pattern to audio, imported to a new audio track and yes now they sync properly.

    Good to know!

    So what we've all 'learned' today is that in order to do a proper 'synced recording' in BM3 it's more reliable to do an export and import until this 'issue' is fixed :)

    A bit on the same topic, I have a similar issue with AUM when using plug-ins that add slight delay (compressors, limiters etc.) when doing a synced recording, the loops are seldom 'spot on' and would need to be 'scrolled' left/right on the time axis.

    Think if it like you've got a loop going, you initiate a synced record and it all sounds good but when you look at the recorded wave the transient that should be at the start of the loop is at the end of the recording!

    So when you stop the sound and start it again the initial transient is missing but when the sound loops it's heard since it's at the end of the recording...

    Oh well, at least there's a work-around for the BM3 issue and for AUM I can always record 3 loops and manually chop the loop in the middle. I have NOT checked how BM3 handles plug-in delay compensation on export or when doing synced recordings...

    Cheers!

  • @Samu said:
    A bit on the same topic, I have a similar issue with AUM when using plug-ins that add slight delay (compressors, limiters etc.) when doing a synced recording, the loops are seldom 'spot on' and would need to be 'scrolled' left/right on the time axis.

    Think if it like you've got a loop going, you initiate a synced record and it all sounds good but when you look at the recorded wave the transient that should be at the start of the loop is at the end of the recording!

    So when you stop the sound and start it again the initial transient is missing but when the sound loops it's heard since it's at the end of the recording...

    That is exactly it, I saw this, the initial few samples are stuck onto the end. Throws everything out. I think it's a common fault. I wrote to the Koala dev because I was experiencing this (or something much like it), though didn't have it pinned down so eloquently.

Sign In or Register to comment.