Ableton Live – Playback lag in 3.4.0 in arrangement view, reverted back

Superior Drummer 3 Help
Viewing 9 replies - 1 through 9 (of 9 total)
  • Petter Adsten2
    Moderator

    Hi,

    Sorry for the inconvenience! We have noticed that this issue is occurring when 44.1kHz sample rate is being used. The programmers are investigating.

    Other than downgrading, which you have done, another workaround is to use a different sample rate.

    Petter Adsten - Toontrack
    Support & Betatesting

    2

    Thanked by: Matt Ayres and digitalGreg
    Matt Ayres
    Participant

    Same issue hopeing for a fix soon

    Matt Ayres
    Participant

    Any update on this guys? It’s been nearly a month!

    • This post was modified 5 months ago by Matt Ayres.
    Petter Adsten2
    Moderator

    No ETA yet, but the team is working to fix this and other issues in the next software updates to SD3 and EZD3.

    Petter Adsten - Toontrack
    Support & Betatesting

    Matt Ayres
    Participant

    Any update Petter!? Been another month now… and I’ve still had a broken product longer than ive had a working product! 🙁

    Petter Adsten2
    Moderator

    Been another month now… and I’ve still had a broken product longer than ive had a working product!

    Sorry about that Matt! A fix has been found and it is coming in the next update, but before then that version (which includes other bug fixes and changes too) has to go through QA testing. How long this will take depends on the findings of our testers. The fact that we are in the summer vacation months in Sweden right now is going to affect the timeline as well.

    Please let us know if you need any assistance in applying the workaround and we’ll help!

    Petter Adsten - Toontrack
    Support & Betatesting

    Petter Adsten2
    Moderator
    BEST ANSWER

    Please try the latest update now, it should fix this issue. The same fix should come to EZdrummer 3 very soon.

    Petter Adsten - Toontrack
    Support & Betatesting

    1

    Thanked by: digitalGreg
    tacotuesday
    Participant

    3.4.1 it did not fix the issue. m1 and ableton.

    this is an absolutely unacceptable bug with a usecase common enough to warrant dropping all other dev tasks until it’s patched. this fucking bug has completely stalled my session, i’m losing over a day because of it. where’s your urgency? you had no problem taking hundreds of dollars from me for this software, but when users need a real patch because YOU chose to issue a buggy release without QA (or even worse, with bad QA) to the point of stalling a session, oh gee “it’s the summer months so we’re unable to give a shit.”

    how many users suffered from this bug but didn’t bother to post about it? (while we’re at it, why do you registration-wall viewing the forums? an insanely infuriating choice as a user.)

    i’ve been purchasing your products for over a decade, i don’t understand how a mature codebase and product team can let a bug like this escape, and then persist for so long. i don’t understand how “is the audio synced with the DAW” is not the literal first automated test your builds run. nothing works if nothing syncs. is the company dying? is the lack of sd4 information a hint at this? should i start trying to move away from toontrack?

    Petter Adsten2
    Moderator

    3.4.1 it did not fix the issue. m1 and ableton.

    Sorry for the trouble! We have contacted you by email for troubleshooting. I just now reverted to 3.4.0 and was able to reproduce the bug. After upgrading to 3.4.1 the looping works correctly, so we need to have a look at your setup.

    Petter Adsten - Toontrack
    Support & Betatesting

Viewing 9 replies - 1 through 9 (of 9 total)

No products in the cart.

×