Notes dropping at loop start?

Kinda annoying when working on a section & notes at loop start drop out. I don’t know what’s causing this, bug or something else? BM3 v3.0.13 iPad2 Pro iOS 13.2.

Comments

  • edited November 7

    I've had this happen sometimes on loops in versions prior to the update. It may not be a new issue. The only thing I can suggest is maybe zooming way in and putting that first beat a tiny bit after the beginning of the clip.

    I'll see if I can find some time to get a simple project going where the problem is reproducible. If so then I'll post it here.

  • edited November 8

    It’s not new, it’s a long standing bug, and during testing we believe we have determined this only happens with samples that use an AHDSR amp envelope, as the AHD envelope doesn’t have this problem. Still not fixed yet.

  • I see, thank you.

  • edited November 8

    The thread (link below) was/is about a similar, but opposite bug, (only a slither of the sound was played, on loop), (they may all be related.)

    (Although the above vid sounds like the loop (or sample) is not looped perfectly). Maybe that’s what is meant, (not droped notes).

    Don’t know if the below bug been fixed, not making tests with BM3 as I used to.
    .

    2 years ago...
    https://intua.net/forums/index.php?p=/discussion/5766/jumping-around-on-the-timeline-cuts-audio-layer-trigger-issue#latest

    ———-

    I may start rereleasing some old threads..
    Not sure how developer(s) todo lists are handled (all differently I suppose). But we/I shouldn’t need to revitalise threads.
    We have no idea what is being looked into, and sometimes what is supposed to be fixed. Especially when the update log in the store says something like “Bug fixes”... lol - Although, respectfully Intua are quite detailed in their update logs. (so there is good!) ✌🏼
    ..
    King
    .

  • Nah it’s not the looping on the sample, none of those samples are set to loop. It does this even on one bar single note patterns. Throws me off. Don’t remember this being a problem before I updated.

  • edited November 8

    "Throws me off"
    Yep! that's the thing right there..


    If you haven't done so already, one thing I always advise (for many music 'or other' apps, & to anyone) is to start a new session/project, and test it there, (the amount of times a new session has saved me pulling my hair out).
    If it works fine, then one could debug the session where the bug is.

    Start by *deleting track by track (listening in between) until your left with the bugged one (_if,_ you have to delete so many)
    Then, remove stuff like AU's etc, then set parameter to defaults etc, etc, etc.)
    Even Ableton link 'switched on' can throw things off in some situations, believe it or not, (and not just timing)

    • The above advice is for 'ALL' who come across bugs - not just this case.

    So many time its just a button or switch etc. (which also could be a bug)

    (*If one is nervous about deleting tracks, save a 2nd version of your project first) - it only saves data, (not doubling up the samples) in _most_ apps anyway.

    ..
    King
    .

  • edited November 8

    Looks like the latest update has awakened me from my BM3 - 'reports' - slumber.
    Now that we are 'hopefully' able to influence change/progression again.
    @vincent Cheers!
    ..
    King
    .

  • Yep, same issue. Pretty big one to go unpatched for so long.

  • edited November 8

    ADSR engine has a slight issue and it has been well documented by the beta team.

    For now, To prevent retrigger issues with loop brace or tapping the timeline (green play button) these are your options:

    1. Nudge your first note if triggering downbeat of a pattern. Works fine at smallest grid setting (free) i believe. You just nudge it one block. Am I right @ronji ? I forget.

    2. Use AHD engine

    3. Bypass ADSR/AHD engine entirely in modulations tab in sampler view.

    Hope this helps all!

Sign In or Register to comment.