2

[Petter Adsten]

neurozero wrote:

I still don’t understand where those B notes come from.

Good question! I will forward your example to our development team so that they can have a look at the logic behind this.

Petter Adsten - Toontrack
Support & Betatesting

[Petter Adsten]

Hi,

The underlying issue here is that bar 2 has been analyzed as an E minor and not a D. When you have notes that are not included in a chord, any subsequent transpose action will apply to those notes as if that chord is correct and that the notes should be included in that chord.

The solution we would recommend in this particular instance is to cut the chords in half and then use the Correct Chord feature in the chord wheel and make it a D instead of an Em (and C at bar 2,5-3).

Petter Adsten - Toontrack
Support & Betatesting

1

Thanked by: John

[Petter Adsten]

Is EZbass activated in the Studio One View > Plug-in Manager? (activate it by clicking the dot next to EZbass in that list if the dot is greyed out/dark).

Also, please make sure that the .vst3 plug-in is located in C:\Program Files\Common Files\VST3

Petter Adsten - Toontrack
Support & Betatesting

1

Thanked by: Mick Avoidant

[Petter Adsten]

Noah M wrote:

Thanks heaps! It seems the bug may have been missed for a few years since it also doesn’t work for me in version 3.0.6.

Hmm, perhaps. Although it does work for me on another mac that has Sequoia 15.4 installed. So it could be some recent change to macOS that is causing it. But perhaps it can be fixed in our code still. Let’s see what the programmers say!

Petter Adsten - Toontrack
Support & Betatesting

1

Thanked by: Noah M

[Petter Adsten]

BEST ANSWER

I was able to reproduce this now with Logic 11.2.2 and Sequoia 15.6.1, and I’ll report it to the development team for further investigation.

I did find a workaround. Launch Logic Pro in Rosetta mode (right-click the app > Get info > Open using Rosetta).

Petter Adsten - Toontrack
Support & Betatesting

I was able to reproduce this now with Logic 11.2.2 and Sequoia 15.6.1, and I’ll report it to the development team for further investigation.

I did find a workaround. Launch Logic Pro in Rosetta mode (right-click the app > Get info > Open using Rosetta).

Petter Adsten - Toontrack
Support & Betatesting

1

Thanked by: Noah M

[Petter Adsten]

MintberryCrunch wrote:

–> Good to know, thanks.

Sorry, you were right, after some discussion and further investigation it isn’t as easy as I commented before that the resampler just adds 16 samples of latency. Using other sample rates than 44.1kHz will not improve latency.

Wolfgang wrote:

So does this only affect Ableton Live?

Not necessarily, no. We had some reports come in to support indicating that there were issues in other hosts as well. But we weren’t able to reproduce the issues.

Petter Adsten - Toontrack
Support & Betatesting

1

Thanked by: MintberryCrunch

[Petter Adsten]

– Edited to remove incorrect information –

Petter Adsten - Toontrack
Support & Betatesting

• This post was modified 2 months, 3 weeks ago by Petter Adsten.

1

Thanked by: MintberryCrunch

[Petter Adsten]

Thanks for the feedback. Just to make sure, you are suggesting that we should provide a way for users to actively disable the 16 samples latency that was introduced in 3.4.1?

• At sample rate 44.1 kHz, the plug-ins (not in the standalone) now always have and report 16 samples added latency, to prevent potential latency changes during playback. Related to this, in some hosts (for example Ableton Live), looping would in version 3.4.0 cause an audio glitch.

I can make sure that the development team receives the request. Is there anything else you would like to add to this, before I forward your message?

Petter Adsten - Toontrack
Support & Betatesting

[Petter Adsten]

Where did you find that information? We want to correct it if there is inaccurate information somewhere.

Petter Adsten - Toontrack
Support & Betatesting

[Petter Adsten]

tacotuesday wrote:

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

[Author]

Replies