PT12.4 Track Freeze Random Naming?

[Jon_Atkinson]

Hey all,

A very minor query, but for me on 12.4 all is working very nicely thus far, however when I freeze a track, the file in the edit window is consistently being named after a different track in the session.

I was also getting a similar problem in 12.3.1 when I commit a track: the newly created track would be named after a different track in the session.... Actually this is more annoying than the freeze behaviour I'm seeing, as both the file and the track title are incorrect.

Any thoughts as to what I may be doing wrong here? I'm not seeing loads of others raising this as an issue, so I'm assuming it's just me..!

Thanks

[amagras]

They are going to need more information on your system before giving some help, there's a thread named "help us help you" that explains best than I do.

[Jon_Atkinson]

Thanks.

System info is in my signature, but I'm aware that the signature isn't always shown (especially if you're on mobile..)

It's:

Mac Westmere 6 core 3.3Ghz, 24GB RAM, OS 10.10.5, Protools 12.4, Apogee Quartet
AJA I/O Express

[Jon_Atkinson]

Ok, so I'm wondering if this might be a product of hosting my VI's in VEPro (which I've previously done 100% of the time)

Today I'm working on a much smaller setup than my usual template, so I decided to try hosting everything natively in PT and using Freeze, instead of having everything (by which I mean an 18GB template) loaded in VEPro.
Track naming seems to be behaving exactly as you'd expect.

Any other VEPro users seeing track name weirdness?

[Stig Eliassen]

I use VEP, but haven't seen any issues with naming. PT gives me the correct name + the suffix cm. Not tried 12.4 yet.

[Jon_Atkinson]

Originally Posted by Stig Eliassen

I use VEP, but haven't seen any issues with naming. PT gives me the correct name + the suffix cm. Not tried 12.4 yet.

Thanks Stig.

I've not used the commit a great deal, but I was consistently getting the same issue (in PT12.3.1) where any committed track was being named 'Violins 2', which although not a deal breaker, it's certainly a pain (especially if you try and commit more than one track at a time!)

As I say, I'm on a smaller session today (in PT12.4) with everything hosted internally in PT and it's all behaving as expected.

If I get some free time I'll have another look at the previous sessions which were causing issues and see if I can pin it down.

[Stig Eliassen]

Originally Posted by Jon_Atkinson

Thanks Stig.

I've not used the commit a great deal, but I was consistently getting the same issue (in PT12.3.1) where any committed track was being named 'Violins 2', which although not a deal breaker, it's certainly a pain (especially if you try and commit more than one track at a time!)

As I say, I'm on a smaller session today (in PT12.4) with everything hosted internally in PT and it's all behaving as expected.

If I get some free time I'll have another look at the previous sessions which were causing issues and see if I can pin it down.

That is a pain, yes.

Out of curiousity; do you have track and edit selection linked? I usually have that feature on.

[Jon_Atkinson]

Originally Posted by Stig Eliassen

Out of curiousity; do you have track and edit selection linked? I usually have that feature on.

No, I don't have that on, but I'll give that a try and see if it has an effect.

I have looked to see if I've had a different track highlighted than the one I was trying to commit, but I don't think it's the culprit... As I say, I was getting every track renamed as 'Violins 2' irrespective of what was selected or highlighted. The Violins 2 track wasn't even the first track in the session...!