PT 2024.3 | Released

[mickeymassacre]

Originally Posted by TimNielsen

This is absolutely pathetic behavior from Avid, but not sure why anyone would expect any less. Zero communication, in an instant broke the entire working paradigm for a ton of us who use either V-Control or Mulligan. Sad and just WRONG. Avid, you could EASILY just FIX the damn driver right?

This stinks! I can't bring a Econ Controller, a network switch, cables, a network to TB3 adapter, etc on the road, nor will it fit in my backpack.

I own Artist Mixes, and they are great. But what they are NOT is convenient for travel. Mulligan was the main reason I switched back to Pro Tools after years in StudioOne and LPX. I can't mix with a mouse. Unfortunately, I also can't always mix in my studio.

[huzzam]

Originally Posted by marianna

HI Devon

I created a case for you as well so we can get on this issue first thing Monday. Case # is 04769525

Thanks for chiming in as the more cases the quicker fixed.

Marianna

In that case, feel free to add my name as another one missing the m-audio protocol, and thus losing access to mulligan, which is integral to my workflow. (Been using it since it was in beta testing…)

At this point I’m rolling back to 23.12 and i guess i won’t be renewing my perpetual in May when it expires.

[OBaldwin]

I'm having an issue where Pro Tools consistently crashes when creating Atmos beds/objects or adjusting my Atmos bed/object structure. This happens on both my Mac Studio (M2 Ultra) and MacBook Pro (M1 Pro) both running Ventura 13.5.1.

This crash is also consistent regardless of the playback engine I'm using (typically MTRX Studio), and whether I'm using the internal/external renderer.

Is anyone else seeing this? Rolling back for now!

[audiogamble]

Originally Posted by OBaldwin

I'm having an issue where Pro Tools consistently crashes when creating Atmos beds/objects or adjusting my Atmos bed/object structure. This happens on both my Mac Studio (M2 Ultra) and MacBook Pro (M1 Pro) both running Ventura 13.5.1.

This crash is also consistent regardless of the playback engine I'm using (typically MTRX Studio), and whether I'm using the internal/external renderer.

Is anyone else seeing this? Rolling back for now!

i wonder if this is related to the io window problem i reported


Sent from my iPhone using Tapatalk

[pbthias]

Originally Posted by mickeymassacre

This stinks! I can't bring a Econ Controller, a network switch, cables, a network to TB3 adapter, etc on the road, nor will it fit in my backpack.

I own Artist Mixes, and they are great. But what they are NOT is convenient for travel. Mulligan was the main reason I switched back to Pro Tools after years in StudioOne and LPX. I can't mix with a mouse. Unfortunately, I also can't always mix in my studio.

Besides working on TDM/Native/HDX Systems all the time I also do a lot of studio support for all kind of studio and producers.

I believe it's a big oversight @avid to ignore the major change in the workfield in the last 5-8 years. So many producers have completly switched over to work from a laptop and are traveling to all kinda places all the time.

Mulligan filled a gap that no Avid controller is offering so far: quick plugin control and transportability.

I can understand if they don't want to support 3rd party hardware, but then at least give us a small eucon plugin controller.

Maybe a half size Avid Dock.

Like only an ipad + the 8 knobs (and maybe hardware buttons for "select" so you can easily switch to EQ Q).
Something you can throw into a laptop bag and easily set it up....

[JingleDjango]

I started an album mix project using this latest release. It's been great so far! I even dared to use the built-in Melodyne and no weird errors or missing edits, knock on wood. The pop-out window is a blessing. EUCON is solid. And I'm totally loving the colour-coded IO. I didn't think I'd have any use for that at all but I took a few minutes to colour my mix template and it makes it that much easier to know at a glance whether any new tracks have been routed to the appropriate busses. Good stuff.

[subwoof]

I’m in the same situation not having access to my M-audio keyboard anymore with 2024.3. All of my sound design is done using this keyboard. I will have to roll back to 2023.12 as well in order to keep working. This might be my last paid upgrade for ULTIMATE PERPETUAL, and I’ve been using PT since version 4.


Sent from my iPhone using Tapatalk

[pherzfeld]

Originally Posted by moshuajusic

Cool. Thanks! In other good news, I just quit PT and it didn't tell me it was forced to quit. Old nagging bug seems fixed.

Are you by chance using Avid Control on an iPad? I have an iPad that lives on the custom hot keys page, and for the last couple of weeks if I hit the side button to lock the iPad screen before quitting Pro Tools I can quit Pro Tools without forcing quit. Until now Ive had to force quit Pro Tools about 98% of the time since upgrading to Monterey. I noticed that on the rare occasion that I didn't have to force quit Pro Tools the behavior of the Avid Control iPad screen was a little different when quitting Pro Tools and it made me curious.

[gthm]

Smooth sailing here.

I have removed so many questionable plugins since the switch to Apple Silicon began and now my plugin folder is nice and fresh with every single one updated and current.

I think Pete Gates's PT Prefs 2 should also come with Pro Tools. Essential tool for quick and easy reference.

Finally, listen to Darryl and check your plugins. Again and again. Fixes many, many issues.

[Fishbone]

Originally Posted by Becharax

It is more sleek I agree but I have graphical issues ... when I move clips between tracks the clip gets distorted graphically while moving it ...

Yep... unfortunately I can confirm that bug in PT 2024.3/Sonoma.

Every time I try to move a clip with transparency it begins to flicker like crazy, which makes that feature practically useless. It's really annoying.