![]() (or just confirm you have done these already) here is what I'd do with the partial info I have now:įrom reading some of your posts I'm not going to suspect hardware CPU/Memory etc. That can uncover things that have been missed or misunderstood, or maybe eventually help locate some weird corner case of stuff that is buggy. But often users benefit from iteratively troubleshooting online on DUC with other users, discussing what they are seeing in detail, what tests have been done and what to try next. Getting super frustrated like this and spending a long time trying to debug stuff yourself is not unheard of, including for folks who are fairy savvy with computers. I do suspect it's worth spending a few hours more trying one last go at troubleshooting this system but with help from folks here and Avid support. ![]() I know you are very frustrated and it sounds like you have been doing a lot of reading and trying stuff.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |