![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#31
|
|||
|
|||
![]() Quote:
Meanwhile I'm still getting the error. I think only with DearVR Monitor. I didn't want to call it out but they haven't been able to reproduce or find a solution. An earlier version of the plugin did not cause it.
__________________
~Will |
#32
|
||||
|
||||
![]()
I use DearVR in almost all my sessions, but not Monitor.
|
#33
|
|||
|
|||
![]()
Hi Marianna ... this is Nick Allegro
I started having this same issue recently with all of my sessions and with different plugins. The sessions are not large sessions. There is maybe 1 or 2 midi instruments, and on some sessions, there are none, or they have been bounced to audio tracks and made inactive. This is getting very frustrating especially since I'm Mentoring people and this is happening regularly. I'm still using the same PC I've been using, and haven't changed anything except updates. This just came out of the blue and is really affecting my workflow. I've been using Studio One more and more because of this error. Most of my sessions and mentor calls I use Pro Tools, so this is now costing me money. I really don't have the time for the multiple troubleshooting steps especially when the same plugins have been working without a problem and still work on Studio One with no errors. Any help would be appreciated ... funny, how this always seems to happen right around the time I'm supposed to renew my program? .. Thanks in advance ... you have been a great advocate for the consumer. |
#34
|
||||
|
||||
![]() Quote:
Let me get a case going and see what can be done here... cn you provide a few plug-in examples ( names please ) so I can investigate the? 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
|
|||
|
|||
![]()
Having major issues here as well. For me it always seems to be any izotope plugin. What's funny is that there will be no audio in that area of the track, or even on the track. the plug in is in bypass. some times it will give me the error, other times not.
I simply see no cpu spikes. in fact, the cpu never goes about 10% I have updated all isotope plugs, deleted prefs, changed drives, upped the buffer size, literally everything. Am I missing something?
__________________
We, in post sound, are illusionists, not magicians. |
#36
|
|||
|
|||
![]()
Exact same problem here with Fabfilter plugins (Q3, C2, MB, all up to date) but only when importing the tracks from a pre-existing session that has the problem initially (despite cmd+alt+/ to remove all old automations).
Recreating the track from scratch and moving clips and automation from the "corrupted" track can help a bit but not always. There is no way to trigger the problem intentionally, it can happen dozen of times in an hour, only three times in a day or never at all. With other sessions on the same machine (which have the relatively same layout of inserts, same amount of tracks or more) I never had the problem. Mac Studio M2 Ultra, Ventura 13.6.9, Pro Tools 2024.6 (it happened before with Pro Tools 2023.9 to 2024.3, Monterey 12.x and a M1 Ultra) |
#37
|
|||
|
|||
![]() Quote:
__________________
~Will |
#38
|
|||
|
|||
![]() Quote:
This was happening with different plugins but for sure SoundID from Sonarworks, and Verbsuite from Slate Digital. Thanks for your help |
#39
|
||||
|
||||
![]() Quote:
And this is on sessions with say 4 to 8 audio tracks and maybe 2- 4 VI instrument tracks and a couple Aux tracks I thought I would try putting it on my main Mix bus instead and see if that makes any difference. (don't know why it would but thought I would experiment anyway) I'll report back
__________________
System : Studio - Avid Carbon interface , PT Ultimate 2024.10.2 Mid 2020 (intel) iMac 27" OS Sequoia 15.2 Mobile - 2021 14 " MBP M1 Pro PT Ultimate 2024.10 --Sequoia 15.1 Enjoy the Journey.... Kev... Last edited by K Roche; 12-08-2024 at 07:48 AM. |
#40
|
||||
|
||||
![]() Quote:
I know you haven't been in the studio lately but when you can - would you try this please? I reopened the case and will take it over so Manuel doesn't close it again. :) " Can you test a new blank session with just the "Sound ID" plug-in inserted? If the issue is reproduced, can you send the latest Pro Tools log? Here's how: https://avid.secure.force.com/pkb/articles/en_US/troubleshooting/Exporting-Log-files-from-a-Pro-Tools-System" Anyone else having the issue please do the same and if you have a case send it thru there and if not DM me. 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 |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
"Audio Engine Play Startup Deadline Was Missed"... | Johnjohnjohn | Pro Tools M-Powered (Win) | 2 | 07-07-2009 01:05 PM |
"audio engine plays starup deadline was missed" message in pt 8 | nachonieto | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 7 | 05-31-2009 03:34 AM |
Digi: update on "missed audio engine deadline"? | H-man | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 05-29-2009 12:20 PM |
Digi: update on "missed audio engine startup deadline" | H-man | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 05-05-2009 12:54 PM |
"Audio engine play start deadline was missed." Huh? | mixboy bob | Pro Tools TDM Systems (Mac) | 1 | 01-09-2009 12:56 PM |