![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#31
|
|||
|
|||
![]() Quote:
|
#32
|
||||
|
||||
![]()
Alex H.
I started a case for you - 04960070 and have asked support to jump on it. Did you deactivate the license in your iLok Manager prior to doing the migration? Check your spam and junk folder if you don't get a response soon. Marianna
__________________
Marianna Montague Sr. Dir. CX and Community | Customer Advocate [email protected] cell +1 (813) 493-6800 AOL IM avidmarianna Twitter Avidmarianna We're Avid. Learn more at www.avid.com |
#33
|
|||
|
|||
![]() Quote:
No, I did not deactivate the license before (or after) migration. At this point, though, I've done a complete OS system reset, and reinstalled everything (Pro Tools, FCPX, PhotoShop, etc.) from scratch, seemingly to no avail. |
#34
|
||||
|
||||
![]() Quote:
I know that when using Migration Assistant on a Mac with iLok licenses, you are suppose to ensure you deauthorize the licenses from the old computer and reauthorize them on the new computer using the iLok License Manager. Can you deactivate then reactive on the new Mac and see if that makes a diff.? Marianna
__________________
Marianna Montague Sr. Dir. CX and Community | Customer Advocate [email protected] cell +1 (813) 493-6800 AOL IM avidmarianna Twitter Avidmarianna We're Avid. Learn more at www.avid.com |
#35
|
|||
|
|||
![]() Quote:
My Pro Tools authorization is tied to the iLok, not to the computer, and has been that way since before I moved to the Mac Studio. So, I’m not sure what I’d need to do here. I’m not having iLok issues any more. I can open Pro Tools and run sessions, except… that Pro Tools is refusing to utilize video at all. See my most recent posts in this thread. This is a massive challenge, as 90% of what I do in Pro Tools is audio post for video. |
#36
|
|||
|
|||
![]()
How many displays do you have and how are you driving them?
I don't use Sonoma so I'm unaware if there are issues there. But as you've seen the "Missing codecs" error does not always mean there's a problem with any codec. Sometime that will throw if there are files of multiple codecs in the session. Sometimes it's just a hissy fit that a PT restart will fix. I don't remember a case where the video file will show missing and won't relink. That is curious.
__________________
~Will |
#37
|
|||
|
|||
![]()
Three. Two on Thunderbolt > HDMI cables, one from the HDMI out.
Quote:
I’m hoping that’s the root cause of all of this absurdity, but there’s no way to try anything else unitl I get the iLok replaced. It’ll be a few days before I can jump back in. |
#38
|
|||
|
|||
![]()
Just to update everyone, I think the issue is now resolved.
Also, I firmly believe that an ailing iLok USB was the culprit all along, though it could have been a couple of issues. Because of the steps I took, and in which order, it’s hard to tell if it was one thing, or both things. In short, the iLok USB was not being recognized at all by my Mac Studio. I had deleted the AvidVideoEngine folder on the advice of Avid support, but PT would not launch at all at that point. So, I shut down my Mac Studio. I moved the iLok USB to my MacBook Air and launched iLok License Manager to find that the iLok was immediately recognized. The ilok USB was then returned to the Mac Studio and the computer booted up. I opened iLok License Manager to see that the iLok was recognized. I then launched Pro Tools into a 5.1 session with video, and it opened and ran with zero issues. No codec errors, no PACE authorization issues. So, there you go. Perhaps the iLok wasn’t seated correctly (despite numerous attempts to pull it and re-insert it). Perhaps there was a pin out of place, or some slight corrosion on a contact, that was slapped back into submission when I tried it on my MacBook. And, perhaps, the AvidVideoEngine folder needed to be deleted to reset the video engine after all. Hard to tell. But, I’m back up and running, and a bit exhausted from trying to track down this gremlin. Thanks, all, for the guidance. Last edited by Alex H.; 04-03-2025 at 05:41 PM. |
#39
|
||||
|
||||
![]() Quote:
![]() Marianna
__________________
Marianna Montague Sr. Dir. CX and Community | Customer Advocate [email protected] cell +1 (813) 493-6800 AOL IM avidmarianna Twitter Avidmarianna We're Avid. Learn more at www.avid.com |
#40
|
||||
|
||||
![]()
There's something very bittersweet about discovering the issue in a place FAR away from where it was showing its ugly head. It reminds me of a system-wide problem I had a few months ago where seemingly everything I did brought beachballs. I spent two days checking everything. Only to find that one of my audio interfaces had flipped its lid and needed to be restarted. That's all it was. After that *everything* went back to normal. The fact that it was so unrelated to the issues I was seeing made the quest excruciatingly frustrating and I pulled all my hair out, twice, searching for the culprit.
Glad you found yours. |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Video Engine errors | gerswork | Pro Tools | 3 | 04-30-2024 05:08 AM |
Video Engine errors (again, endless story) | kava | Pro Tools 2020 | 1 | 09-03-2020 09:03 AM |
Is 12.6.1 worse for video engine errors than 12.5.2? | Xcurve | Pro Tools 12 | 0 | 04-23-2018 12:21 PM |
Unexpected errors with Video Engine | JonesH | Post - Surround - Video | 1 | 09-22-2016 06:51 PM |
More Video Engine errors... Fill me in, is there anything else I can do? | weezerboy | Post - Surround - Video | 9 | 03-14-2016 08:55 AM |