Ann, confirming: You're using x58? ... View more

Yep, we're investigating already... ... View more

When you reference speed changes, you mean linear speed changes applied to the whole track item, or keyframed speed changes?  ... View more

"not a production"  makes sense, if PPro was not able to write a .prodset file.   I propose to leave Productions out of troubleshooting, for now; they have their own project locking behavior, distinct from the failures you're seeing with standalone .prproj files.   We'd like to get a copy of PPro Beta's preferences; one copy from when you cannot save changes, and another (after you've cleared them) from when you can.  Are you launching PPro Beta 'as an Administrator', on that system?  ... View more

Interesting! Sorry for the verging-on-pedantic confirmation request below, but...is the following true? 1. Launch PPro 25.1 official release. Create test.prproj in OS user's home directory (~/).  Save project. Close PPro 25.1. Launch latest PPro 25.2 beta. Open ~/test.prproj. Add a bin or something; make test.prproj 'dirty'. Save ~/test.prproj. Result: Failure? ... View more

[updating status] ... View more

>So it seems Premiere lost all write functionality to projects...   PPro never alters OS-level user permissions, or storage read/write access. The fact that no one else has reported this problem, and that thousands are using the same beta build without issue, makes us hopeful that the problem is specific to your system... Confirming: You see this access failure in independent projects, not just projects within a Production, yes?  Confirming: Same behavior, when attempting to save on local drives, or network drives, yes? Confirming: Same behavior, when attempting to save to your OS User's home directory (to which you're pretty much guaranteed to have write privileges), yes? Are you perhaps logging into that editing system, with a different OS User account (with fewer privileges)? What else might have changed about your system, between the last time you were able to save PPro projects, and now? ... View more

> If i tell PPro to use 10 gb of the 16, but it says that its using 40 gb, its not me that asked it to use 40, its forcing it self to use that 40 gb.   Again, as stated above; PPro's RAM guidelines apply to processes PPro owns. Many things users do in PPro, spawn processes which PPro does not own. That's why we recommended reserving more memory for processes other than PPro, in PPro's memory preferences. >If premiere is using some of the storage data as ram... That's controlled by the OS, not PPro. ... View more

More RAM will never hurt; PPro making use of all your system's resources, is in no way a "bug problem". 🙂 ... View more

>I just want to know how to fix the issue...   You haven't identified any specific issues, other than saying AME doesn't act as though it's installed. Have you tried uninstalling/reinstalling AME?  If you would like our help, please provide specific steps you're following, which reliably generate errors, on your system.   We're glad to hear your rendering and export normally work without issue, every single week. ... View more

'stuck at 70%' must be a different issue.  [send us the XML] ... View more

I helped Avid write the panel, but have no information about the functionality it provides.   What does Avid say, about the issue you've encountered with their panel? Can you reproduce the issue by importing the same media, without involving their panel?    [Mike's pref suggestion is also worth trying]   ... View more

Great details, thanks!  We're tracking this one as DVARC-3775; we'll keep you informed of our progress. ... View more

Not every process is limited by CPU/GPU power. Some are limited by available RAM; some are limited by storage access speed. Also, many processes cannot be GPU-accelerated; the introduction of one non-GPU-acclerated effect on a track item, can force all effects on that track item to not be accelerated.  >Has Adobe done absolutely nothing... If you read PPro's release notes, you will see that we've been actively/vigorously accelerated slower parts of the application, for years. ... View more

Interesting!  Not sure we've gotten there yet in our efforts, but we're tracking this one as DVAPR-4255386; we'll keep you informed of our progress (your email is in the bug). ... View more

That's correct behavior; there's no 'media-like object' behind a bin. ... View more

There is no way to enforce visibility of a plugin. ... View more

> `createBin` works on `projectItem`, I don't have any `projectItem` in empty workfile. Workfile? As PProPanel shows, the root of the project is itself a projectItem: app.project.rootItem.createBin("Some name"); >`project.newSequence` works, but it expects absolute path to preset file itself Right; you can create sequence preset (.sqpreset) files in the New Sequence dialog, and your extension can include or referenct different .sqpreset files, for different purposes. ... View more

We hear you Stan, and... Since you've confirmed the problem isn't specific to PPro, you may get better traction/visibility on that issue by posting in the Creative Cloud forum, rather than here in PremiereTown. 🙂   PS: Profanity nearly always helps...the user, if not the actual technical problem in question. ... View more

Based on what Markie said about this problem ONLY occurring after PPro runs, it seems unlikely that the problem comes from a startup item, which would presumably hold onto the external drive regardless of whether PPro had been run... ... View more

I can provide no meaningful input, from my "one of the teams that builds PPro" perspective; we've reached out to the CC Desktop team. ... View more

The fact that the fans are running minutes after you've quit PPro, strongly suggests that something else is still doing work, and conceivably hanging onto that external drive.    Are you using any panels/extensions, within PPro?  Are you syncing any cloud sharing services (OneDrive, Dropbox, Box), to that external drive?  Interesting test (if you have the time): Reboot the system for luck, and close any apps that automatically launch after reboot.  Open Activity Monitor... Set Window --> Keep CPU Windows on top to "on" (checked) In Activity Monitor, choose CPU view, sort by CPU usage (descending) Launch PPro, do some stuff; see the CPU usage dance around. Close PPro...and keep an eye on the CPU usage. Who's using it? Oh yeah; those Acrobat and content synchronizer processes = NOT PPro. 🙂 ... View more

> I don't think there is anything to create bin programatically...   createBin() works! 🙂 >...struggling even to create empty sequence programatically PProPanel shows how to create an empty sequence, and how to create a new sequence from a sequence preset.  ... View more

Specifically, what adobe process do you think is preventing the ejection of your external hard drive?  Do you see a process name in a warning message, or Activity Monitor / Task Manager? ... View more

The current PPro beta is version 25.2, and the current PPro shipping version is 25.1; any reason you're testing with 25.0? Have you contacted ReVisionFX? [We work with them regularly, and they haven't mentioned any Twixtor issues...] ... View more