Freeze track no longer works since 3.2.0 update

[LDG]

The Pro tools Freeze track feature no longer works on an SD3 song track since i updated to 3.2.0

This was working beautifully, without the need to drag the song tracks midi to the Pro tools track, but now it is doing what happens in EZbass, which i put a post up of that problem a while back.

To be clear, the track does freeze, but it does not play any sound from SD3 song track, (which it was capable of last version), unless you copy the songtracks midi to the Protools track.

Can we please get this feature back, and add it to Ezbass?

 

Thanks

Operating system: macOS Mojave (10.14)

Topic

[Brad]

Do you have MIDI within Pro Tools or in the SD3 grid editor? I have MIDI on a PRO Tools track and froze the track and have wave forms which play back.

Also running Mojave on this image.

Sorry, I use Pro tools very little these days and answered my own question. Doesn’t work if you don’t have content on the PT track.

Superior Drummer 3 version: 3.1.7
Operating system: macOS Mojave (10.14)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• This post was modified 5 years ago by Brad.

[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)

[Brad]

Right now PT complains that there’s no content on the track so I couldn’t get it to freeze at all. I will try placing something on the track but not for the whole length of the session and see if I get the same result.

Superior Drummer 3 version: 3.1.7
Operating system: macOS Mojave (10.14)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[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.

[Brad]

I went back and created a track in SD3, goes to bar 33. I snipped 3 bars off and put them onto the PT timeline for the same track .

It did freeze the track and create audio to the bar 33, which is in SD3.

As well it did set the time selection out point to the end of the 3 bar snippet, so at first it wouldn’t play past there, but I simply moved that to the time selection in point and then it played the whole thing.

The caveat is, as you pointed out, the 3 bars I put on the is audible as well, thus doubling what is on the SD3 track.

I have posted some graphics so you know I ain’t blown’ smoke…. As I don’t use PT much anymore, I didn’t try it before the last update. When there’s nothing on the PT timeline, you get an error message from PT indicating that.

Operating system: macOS Mojave (10.14)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• The post has been modified 2 times, last modified 5 years ago by Brad.

[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.

[John]

Hi guys, which exact Pro Tools version are you on?

BR,
John

John Rammelt - Toontrack
Technical Advisor

[Brad]

John wrote:

Hi guys, which exact Pro Tools version are you on?

BR,
John

Hey John, I am running PT 2020.9.1 (the update after the release that reduced track count)

Also using the latest SD3 available to me. Running on a non-Catalina host. (Mojave)

If you try to freeze a track with MIDI only in SD3, Pro Tools pops up with a warning message;

“Could not complete the freeze comment because there is no content on the timeline”

Since I hadn’t tried this prior to the last Pro Tools update or the last GA SD3 release, I don’t have first had experience on whether it worked. The OP may be able to provide that.

My work around is to place a snippet of MIDI on the Pro Tools timeline, which seems to trigger Pro Tools to freeze the track with all the MIDI on the SD3 track.

Operating system: macOS Mojave (10.14)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• The post has been modified 2 times, last modified 5 years ago by Brad.

[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]

@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.

[Brad]

Glad you found a workaround that works for you!

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Author]

Replies