I have this strange problem with AVID MEDIA COMOPOSER 2024.
When I open it for the first time it makes an error and it doesn't open. Only when I close it via TASK MANAGEMENT and then reopen it does everything work perfectly. I'll pass on the message the CONSOLE gives me. The specifications of my notebook are Windows 11 home, i9, 16gb ram, nvidia RTX 4080


The console message on first startup and AVID doesn't work
Local Disk Cache - PurgeDataToMaintainQuota:

Bytes Purged: 0d

Elapsed Time Milliseconds: 1

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 2048MB is the same as current size 2048MB.

The console message on second startup and AVID works
Local Disk Cache - PurgeDataToMaintainQuota:

Bytes Purged: 0d

Elapsed Time Milliseconds: 1

Distributed Processing - Reset SubmitQuery cache

qm2b is enabled

The default render wait time is 50

PreReads will bias DueTime by 0.000000 seconds.

Reloading plugin: acpl_lut.acf

Media Composer needs Windows Professional or Enterprise. Home isn't qualified/tested. See:

https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/compatibility/en267087

Hi thanks for the reply. So this is the fourth laptop that I have in my hands and that I have configured. On the first three there was WINDOWS 11 HOME and it NEVER caused any problems. But I'll tell you more: I have the same problem on a CERTIFIED WORKSTATION: HP-Z2-TWG5 running AVID 2022.07. So, with all due respect, I don't think it's a WINDOWS 11 HOME problem. Now if you want, I'll upgrade, but I have every right to ask for a refund if it doesn't work! I believe that perhaps first we need to try to understand the problem and then provide the solution. If it were Windows 11 HOME, there's no explanation why AVID works fine on the second boot!
Sorry for my bad English!

Job is right in his response in that if you want anyone to try and reproduce it they cant as no one is using that config. in support.

With that said....  I would iook at the drive first.  I did a earch on Local Disk Cache - Purge Data To Maintain Quota and a lot pertains to the disks.  

How is the system set up with the application locatation and media files?

Marianna

Hi Marianna, Re-Hi Job. All Mediafiles and AMA are in external SSD, so also the Project. I never used internal disk becouse so I can work at home or on office PCs without problems.
I don't understand what do you mean when you write  "I did a (s)earch on Local Disk Cache - Purge Data To Maintain Quota and a lot pertains to the disks."

But now I must give you new info and upgrades to understand the problem.

At the link you will find the sequence plan of what I do: I open Avid which is already focused on the clip and it freezes. On the second boot it works.
https://vimeo.com/927280358?share=copy
Password: Avid


The clip in question is an AMA recognized as APPLE PRORESS HD created by BLACK MAGIC and linked via UME LINK. Same problem with a MP4 linked by UME LINK. Now, if I transcode it or use QUICK TIME Link instead of UME LINK everything works on first startup. I would like to know why? Is it an AMA problem? I also have the same problem on a certified WORKSTATION (HP-Z2-TWG5) but on the timeline the clips are all transcoded. But Why it worked on other notebooks less performing, an MSI Vector (i7 with 64 gb ram and RTX 3080Ti), MSI Stealth (I9, RTX 4060 with 32gb ram) and MSI Creator (i7, RTXa2000, 32gbram)? It is also true that on these three machines the clips were not very fluid but the AVID did not freeze at the first start while on this machine excluding the problem of the first start, these clips are managed very well without any problem! Could it be affected by the fact that the machine on which I am experiencing the problem only has 16 GB of RAM? But then, why does it make the error only on the first start and on the second everything works perfectly? What happens between the first and second boot that I'm missing? Sorry for my bad English and thanks for your time spending to read me!

IT WAS RAM:
I increased the RAM and solved the problem