PT2024.6 | Issues, Bugs & Observations Thread

[moogboy100]

Originally Posted by Mountclear

That mainly if you are using the new ara or the new markers. Overall it's not a big deal.

I was not using ARA or new markers. All I did was open some sessions, import audio only via Session Import on matched tracks, save and close.

This is an issue when you're working on dozens and dozens of sessions and collaborating with other PT systems who may not have updated to 2024.6 yet. It forces them to have to dismiss this dialog and re-save the session as a new one or overwrite the existing one every time they open the session that comes from me. A HUGE issue, actually.

[moogboy100]

Here's a screenshot of the Error notice from 2023.9. Clicking More Info, by the way, takes you to a 404 error page too.

[skylar_battles]

I tried to do testing similar to strawb's regarding their issue.

It's hard to say but I may not be having the issue in regards to delay compensation from other tracks somehow on this version.

But on someone else's system the other day on 2024.3 in a session with heavy delay compensation, I was sending out simple whole note MIDI data of chords to a synth and the audio was printing incredibly early!

Here's a dropbox link: https://www.dropbox.com/scl/fi/3yb2h...=ntwentgm&dl=0

Also can anyone clarify that since I already have an Auto-Align 2 license, I'll be set to continue to use Auto-Align with ARA after the demo period ends? You never know…

[thebeatless]

I had some crazy issues today!

I had a frozen instrument track for a snare room sample in a mix session. I had to close the session to do something else, and then when I reopened the session somehow that frozen track played back with a kick sample on the left, and close snare sample on the right!?!?

That same session also had a mono to stereo microshift plugin missing on another track, and the volume was WAY off on that track!

I tried ARA RX and it was working incredibly! I was loving it for removing clicks on a track. I texted a friend about to tell them how awesome it was, and immediately after I sent that text, it completely stopped working. I was no longer able to do any spectral editing in this session, even after closing and opening again.

I'm worried that this may be a new severely buggy version!

[damo76]

It is mentioned that the mouse cursor was fixed so that an event from the SDK wont flicker the cursor. That is fixed but the menu bars still flicker when an event is triggere. Any chance you can add that to the bug fix list because I'm working on an app that polls protools for track attribute changes and this is causing the menu items to flicker like crazy...
Thanks in adavance!

[Steviebhoye]

Midi editor graphical issues. The note names on notes is welcome in the midi editor. I am experiencing the notes diissappearing when scrolling in Classic Mode which is not ideal. Seems OK in dark mode?

https://youtu.be/AM2TS2gnoUM

[faraway]

Anyone here running into twitchy auto scrolling and sync playhead irregularities in RePitch Elements ARA that makes it completely unusable for tuning workflows?

Here is a link to a video capture of what I'm referring to:https://www.dropbox.com/scl/fi/119ob...j6zvv0afe&dl=0

Notice when I highlight a region, play it and then stop it jumps back to a previous chunk for no apparent reason?
Also it doesn't seem to handle regions with crossfades. properly It seems to create an overlap of 2 tuning blobs.

Only solution is to constantly keep toggling screen lock off and on which isn't something I need to do in Melodyne or Auto-Tune graphic mode.

[skylar_battles]

I just wanted to say the new MIDI plugins are pretty silly to be quite honest and just not useful. In Human Lite, only 2 of the 11 knob positions work as it prompts you to get the full version when in any of the other 9 positions. It just seems like a wild thing to spend time and resources on and put a Pro Tools logo on the plugin when there are so many real MIDI issues that are being discussed here constantly to be honest.

[Vadym]

Originally Posted by thebeatless

I had some crazy issues today!

I tried ARA RX and it was working incredibly! I was loving it for removing clicks on a track. I texted a friend about to tell them how awesome it was, and immediately after I sent that text, it completely stopped working. I was no longer able to do any spectral editing in this session, even after closing and opening again.

Can you explain more about what do you mean by "it completely stopped working? I was no longer able to do any spectral editing in this session"?
Is the Spectral Editor plug-in UI blocked to you or what exact problem you faced with? Make a screen record if possible.
Thanks!

[Vadym]

Originally Posted by moogboy100

I was not using ARA or new markers. All I did was open some sessions, import audio only via Session Import on matched tracks, save and close.

This is an issue when you're working on dozens and dozens of sessions and collaborating with other PT systems who may not have updated to 2024.6 yet. It forces them to have to dismiss this dialog and re-save the session as a new one or overwrite the existing one every time they open the session that comes from me. A HUGE issue, actually.

This warning needs to aware user that saving in an older Pro Tools version can drop some unsupported new features for him or the original user with a newer Pro Tools version this session came from.
For example, 2024.6 has absolutely new outside-of-the-session file "per plug-in" and "per-clip" methods of saving ARA data which gives a lot of advantages to saving ARA data. But this is not backward compatible which means if you made some Melodyne-edits over the clip in PT 2023.9 and opened it in PT 2024.6 it will open it without any problems, but when user made ARA-adits in PT 2024.6 and sends this session to PT 2023.9 user, all ARA-edits will be dropped once user open and then reSave this session in that legacy version of Pro Tools.

Unfortunately, it is not possible to simply save this ARA data as is even if the user did not touch ARA tracks in PT 2023.9 ​​due to the specifics of saving ARA data model.

But it should not be a problem if you not using any new features in the session compared the the Pro Tools version it is opened in. All data will be compatible in both ways.