tacotuesday
Participant
Topics Started: 1
Replies Created: 3
Has Thanked: 0
Been Thanked: 0
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?
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.
