2018.7 So Far...

[capt kirk]

Installed HS and PT 2018.7 today. Ran session with a few audio tracks , 2 instruments, Stucture and Reaktor, and SoundMiner HD+...and video.....on my MBP 2012. One warning came up about low ram. otherwise it all worked as i expected it.....i guess we'll see when I start using 38 tracks and 6gig of clips...

[capt kirk]

BTW, as a professional with serious deadlines and money on the line, I would NEVER attempt this with my main computer. This was my xtra laptop, no pressure haha

[strangeLoop]

My very old unqualified system that has only 8GB of ram is working very well with 2018.7.

My sessions are only 20 or so tracks with virtual instruments and recorded audio.

CPU at 13%

Memory at 30%

John Clavin

[silverhammernz]

Very strange behaviour since installing 2018.7. I am working on television programs, Have loaded an OMF (project is from Premiere which makes terrible AAF files) then proceeded to edit etc.. All is good for a while then I start getting AAE error 22 & 35. I have never got those before. Soon any part of the timeline that references the OMF becomes corrupt. White noise bursts on some while others simply don't play. I am on High Sierra OS 10.13.3. To fix it I rename old OMF and replace it with a copy I have kept. 2018.7 seems to be corrupting my OMF files, gone back to 2018.4.

[Bokir]

It's been a week since 2018.7, I'm reporting two kind of (probably) glitch:


1. In the middle of the project, after I change some busing, I have a none playing track. Even though it was playing just fine previously. Moving the clip to other track solve the problem temporarily. Restarting the ProTools fixed the issue.



I have so far, three incident on three different project.


2. This seems like an old issue, when I write automation of a plugin (EQ3) on the last clip, when I return to the previous clip, the setting is stuck with the last clip. When I try to fix the earlier clip, the next clip is agin stuck with it. Even though all is inn different write automation cycle. Restarting the ProTools fixed the issue.


This is very rare but I have experienced once since upgrading the PT.



Anybody have the same experience.

[amagras]

^^ Sounds like what happens here when a trashing of preferences/databases is due

[climber]

So far so good. Worked on a couple of old tunes, one with many many tracks, and it worked just fine. fingers crossed...

[noiseboyuk]

Originally Posted by silverhammernz

Very strange behaviour since installing 2018.7. I am working on television programs, Have loaded an OMF (project is from Premiere which makes terrible AAF files) then proceeded to edit etc.. All is good for a while then I start getting AAE error 22 & 35. I have never got those before. Soon any part of the timeline that references the OMF becomes corrupt. White noise bursts on some while others simply don't play. I am on High Sierra OS 10.13.3. To fix it I rename old OMF and replace it with a copy I have kept. 2018.7 seems to be corrupting my OMF files, gone back to 2018.4.

There is something familiar about some of this (I think I was googling an AAE error code 22 with no success), unfortunately I can't remember exactly when I got it and what fixed it so not too much help to you. I'm pretty sure I ended up doing what you did and rolling back - between 2018.3 and 2018.1 possibly. Felt like something in the install got corrupted.

At the moment I'm on 2018.4 which has been the most solid I've had for a long time, but I had to roll back 2018.4 to 2018.3 on my previous rig. I have a theory that not all installs are equal, and sometimes uninstalling absolutely everything first will fix a problem with a particular version. Still, that's all for downtime, if you're mid project I'd definitely advise to stay as you are.

[Farhoof]

Originally Posted by Bokir

(cut)

2. This seems like an old issue, when I write automation of a plugin (EQ3) on the last clip, when I return to the previous clip, the setting is stuck with the last clip. When I try to fix the earlier clip, the next clip is agin stuck with it. Even though all is inn different write automation cycle. Restarting the ProTools fixed the issue.

Deactivating and activating the EQ3 probably solves the issue. Are you using 'preview' to set the eq? This only happens to me when I use preview and has been around for years now (I haven't tested 2018.7 yet). Could be a different issue though...

[thierryd]

Originally Posted by silverhammernz

Soon any part of the timeline that references the OMF becomes corrupt.

I would advise to always convert AAFs and OMFs to session format (WAV) files, with "Force to target" when importing.
I've seen problems with referencing AAFs (OMFs) with all sorts of PT versions over the years (especially when moving the session to another PT computer).

Greetings,

Thierry