1

[LDG]

@pat,

Pat, Rather than an all out assassination how about giving some constructive feedback or putting in a feature request.   That’s the most rude post I’ve seen.

[LDG]

@Olof

Hey there, I’m pretty certain after working on a new song that this bug has something to do with the chords track.  I tried to extend the chords to bar boundaries, filling in the gaps, and it moves midi around,  so Im pretty sure they are related.  On the demo i sent you I tested deleting the chords track  and i could then copy and paste the midi fine, no errors.  I hope that info helps to eradicate this bug.

Are you able to give me a status update as to this fix?

Thanks

[LDG]

I want to bump this as this is a major bug and there’s no response.

Im in a new song now and the same problem is happening. i try to extend a chord to a bar boundary and it changes the midi.  please review post above.

 

thanks

[LDG]

I found a workaround fix for this bug , and posted it in the sd3 forum.

cheers

[LDG]

@Brad, @John

I found a painless fix!

all you need to do is create a clip group (rather than a midi file) on the or Sd3/Ezbass track in Pro tools the length of your song.

Then Freeze works for the song duration.

This helps tremendously since ezbass also gets bypassed when recording in low latency mode, which i believe is a bug too .(sd3 doesn’t bypass, nor any other plugins I use) and with both of these methods not working i cant record from my i/o interface with the ezdrums or ezbass playing.

Im thrilled about this until the bugs can just be fixed.  I hope it works for u.

cheers

 

I’m on PT 2020.5.0 ultimate.

[LDG]

Pro tools has real time midi adjustments on instrument tracks, maybe try to lower the velocity on the track and see what happens (if using pro tools). Another idea is that isn’t there a way in ezbass to set a maximum velocity in the playback settings like SD3?  if so try set that below the rattle velocity and i wonder if that will cap it .  The higher velocities do trigger string rattle, but thats expected when you hit a string hard, and i’m glad its there if thats desired. I imagine those are samples though, so i doubt a preference will fix it, but velocity does.

Operating system: macOS Mojave (10.14)

[LDG]

Joachim Smith wrote:

Where? Washboard, spoons and other cool deep South percussion!

I’d love a washboard too. +1

[LDG]

@John

I’m 1 PT update behind Brad, 2020.5.  I will update soon and see if theres any difference, and I’ll test Brads workaround too.  thanks

Operating system: macOS Mojave (10.14)

[LDG]

Scott wrote:

Follow the link in the Forum Announcement section

@scott, it would be great if these links or just the details were in the Product manager app also.

Thanks

[LDG]

@Brad, thats very interesting, its certainly showing it’s not typical behavior. I will try that work around soon, but i still hope it gets fixed next update.

[LDG]

Simon Clarke wrote:

Excellent. It would be nice if you could lock song sections when you’re done with them.

Reply To: Midi Changes on song track Bug! version: 1.0.5
Operating system: macOS Catalina (10.15)

I agree, this would be a great feature.

[LDG]

is there a “whats new” description for updates?

Thanks

[LDG]

@Brad, it will most likely make the clip you put on the track audible, but nothing where the SD3 plugins song track is playing with the host.  Basically if it’s not on the Protools track it will no longer be included in the freeze. It didn’t do that before, really hoping it can go back the old way along with Ezbass.

[LDG]

Since the update the midi has to be on the PT track to Freeze. Before the update you could freeze it with the midi in the song track.  Which was great as you could freeze/unfreeze and tweak it fast.

I can’t recall if you needed at least one clip of midi on the Protools track downstream to perform a freeze. I can’t test that one since its now updated,  but in any case it did use to work.  Ezbass has this same issue.

thanks

Operating system: macOS Mojave (10.14)

[LDG]

This problem is now also happening in SD3 since the latest update

[Author]

Replies