Rule of thumb on a Windows system: 1. update Windows patches 2. update nVidia drivers 3. reboot and open PP With luck, everything will work...   If using a BETA release, you may need to revert to an older build until the error is fixed (new builds daily) or wait until the next day and install the latest build. ... View more

Windows 10 enterprise 22H2 7/10/2020 os build 19045.5131 updated today Nvidia GeForce GTX 1080 driver 566.14 updated today Premiere Pro 25.2.0 Beta Build 15     ... View more

fixed in build 9 ... View more

This seems to have something to do with an h.264 file that has flaws. I have a file that I ran through Media Encoder in an attempt to make it work, but PP still generates an error when it hits this file on the timeline during a render.  Windows 10 Enterprise 22H2 OS build 19045.5011 Dell Precision 3620 i7-7700 3.6 ghz, 64 gig RAM, GTX 1080 (8 gig) PP 25.2.0 beta build 6 (and earlier builds)   I can upload the H.264 file if needed) ... View more

yes, it is rather old Delirium 2.5 ... View more

The track target V1 to the left of the lock icon was off but the audio A1 target to the left of the lock icon was on. Turning V1 on and A1 off allowed the sequence to be pasted in.   This is another new "feature" caused by the "Microsoft disease" that infects so many software vendors. I have been using Premiere since version 1 (that is correct, Premiere - not Premiere Pro) and never had this happen. ... View more

The most usual reason for Adobe to stop supporting a product is because the development team went elsewhere and there is no one left to provide support. We must remember that Adobe is an aggregator and usually buys existing startup products rather than develop in house. That is why shifting to an open source model might be the only option for continued support of Muse. If you dive into the Muse output HTML code it quickly becomes apparent that the implementation had some sort of design flaws (as does almost all code) that no one really wanted to fix.   Let's agree that the real issue here is the Creative Cloud APP that needs to be FIXED! ... View more

Muse is still the best graphics design environment for portable websites. Other tools such as Pinegrow demand that you have programming skills and have a steep learning curve. Tools such as Weebly are tied to a particular vertically integrated vendor environment and are not acceptable for portability.   If Adobe does not feel that Muse support is in their best interests then perhaps they could spin it off as an open source project and let go of it entirely. Alternatively - give us a permanent stand alone license so we can use it as is without having to reinstall Creative Cloud every time we want to use Muse.   Otherwise there needs to be a certain level of commitment to continuing its inclusion in the Creative Cloud umbrella. That means fixing the Creative Cloud App!   ... View more

The obvious fix for the Typekit issue is to go into the site and replace all Typekit fonts with standard websafe fonts. Enable "show Typekit as Pink" and look for any text with a pink highlight. Replace fonts and save. Uploading to site and save as HTML will then work.   Try to save up all your changes to existing sites and do them all as a batch. Then you can re-enable CC app and close Muse. ... View more

This only works when the repair process is going on and CC is totally disabled. Going into Task Manager and killing all the CC events does not work. Launching Muse starts up several CC processes which end up killing Muse.   It is a real nuisance to have to do this every time you want to use Muse, but better than not being able to use it at all. ... View more

That actually works - sort of... The problem is that once you restart the CC app, Muse dies. So it it necessary to edit in Muse while the CC is off, save the files and upload to web host or save as HTML for later upload. Does not work if fonts are Typekit as there is no Typekit account active until CC app is started. Adobe has really messed this up! ... View more

Might be working on a Mac, but not in Windows10. ... View more

The Google Search Console Team is sending emails to administrators of sites created with Muse saying that there are new reasons preventing pages on the site from being indexed. "Soft 404" and "Duplicate without user-selected canonical" More reasons to update sites to something more compliant with new standards... ... View more

The beauty of Muse is that it is WYSIWYG and isn't target site specific, unlike the locked-in web site builders proprietary to wix, squarespace, etc. Otherwise it's back to Dreamweaver, Pinegrow and so on where you spend more time coding and a lot less designing. Another option is to get into Wordpress themes, which is another can of worms - before Muse I spent a lot of time flipping through wordpress theme catalogs to find something that might work without a lot of coding. Unfortunately Muse code is really difficult to work with in Dreamweaver and does not seem to export to much of anything - that is Adobe's fault for letting the Muse development team dissolve without any vision for future releases. Reminds me of the days when engineering would build something new and exotic then throw it over the cubicle wall and let marketing try to figure out how to actually sell it. ... View more

Perhaps we need to cast a wider net to understand what might be happening: https://www.theregister.com/2024/02/01/windows_10_users_errors_hardware/? ... View more

You can only find it from the Creative Cloud Desktop, not from a browser.   Additionally, it crashes if you have Microsoft Visual Studio 2022 installed - the design environment used in Muse relies on older versions of the .NET framework that are killed off when VS2022 is installed. ... View more

This seems to be a common problem having to do with bad garbage collection in PP...   As near as I can figure out, the old audio render files are not overwritten by the new files. When this happens you may need to "delete render files" within Premiere, save the project and close, then go to the "Adobe Premiere Pro Audio Previews" folder that stores the actual files and delete the contents.  Once that is done, Open the project back up and re render everything. Your changes should now be rendered and should be exported properly. ... View more

I've suddenly got the same issue. What used to be the switch to/from multicam is now a switch to "comparison". The only way I can reach multicam is using the wrench icon on the right. This is REALLY ANNOYING when trying to edit a 6 camera shoot! I need to constantly switch back & forth between Composite Video view and multicam view. The button editor has actually lost the multicam icon and replaced it with a comparison icon. So much for constant updates that end up killing useful features in the name of "improvements". ... View more

All it took was importing 3 hours worth of 1080i AVCHD video to crash PP2018 on Windows 10 Enterprise 64. The little progress bar comes on and after conforming one or two MTS files in a sequence of 8 or 10 files it crashes (on a 12 core dual processor Xeon + 48gig RAM with 200gig flash drive for Adobe temp files, 240 gig system hard drive and 2 terabyte hard drive for video storage - all with at least 25% free space and defragged). Changed the Preferences to allow all Adobe apps to use less than 50% of memory and make it more memory (rather than performance) efficient and that seemed to help flatline it at the assigned peak for a few minutes, but (monitoring performance in Task Manager) eventually memory use began to creep up to less than 2 gigabytes free. Then it changed by +/- .5 gigabytes over a few minutes and finally crashed the entire computer. Had to do a cold reboot to restore system. This has happened several times. Tried saving frequently during conforming, but same files kept needing to be conformed. I can't even get video in a new project fully loaded to edit anything without multiple crashes!  This is a loser until next version fix. Back to PP 2017 to get work done... ... View more

This lap dissolve answer defeats the speed and functionality of the cross-dissolve effect. It is a clumsy workaround. I've been working on a 6 camera shoot for the past few days. Cross dissolves were working properly until just an hour ago (when I hit the 39 minute mark) suddenly a new cross dissolve fades out the video before the cut - but will not crossfade and bring up the video after the cut as it should - instead the video after the cross dissolve now pops on right after the transition.  The previous cross dissolves continue to work properly. If I copy and paste a working cross dissolve onto a new cut it also works as it should. ... View more