
Moxtelling
Participant
Moxtelling
Participant
Activity
‎Mar 04, 2025
05:26 PM
2 Upvotes
I'm looking into Resolve, if the tool's better it makes sense to use it, and I do like their business model over Adobe's. But as a user of After Effects, PrPro, Illustrator, Photoshop, Lightroom and Audition it's hard (not impossible) to replace all those apps and I do enjoy using them (mostly). Getting back to the focus of this thread, a few little tweaks like this can make a big difference. If only extra attention was given to workflow issues / ideas like this, that have been raised and upvoted for years, but not addressed properly (please take note Adobe staff)!
... View more
‎Feb 19, 2025
02:33 AM
1 Upvote
@Moxtelling try manually resetting your Photoshop preferences https://helpx.adobe.com/ie/photoshop/using/preferences.html#Manually Remember to back up your settings before doing the preference reset https://helpx.adobe.com/ie/photoshop/using/preset-migration.html
... View more
‎Nov 07, 2024
10:23 AM
1 Upvote
I just seen your post here so here is the solotion... open this url. there is folder called "CEP" if it's changed to something like "CEP.old" than changed it back to "CEP" that's it. C:\Program Files (x86)\Common Files\Adobe\
... View more
‎Jan 28, 2024
07:00 AM
Export Error Error compiling movie. Accelerated Renderer Error Unable to produce frame. Writing with exporter: QuickTime Writing to file: G:\Business\Business Projects\Projects\Video Productions\My Channel\Benofi\Channel Videos\Accident VIDEO\Proxies\PXL_20231219_113645894_Proxy.mov Around timecode: 00:00:00:14 Rendering at offset: 0.000 seconds Component: QuickTime of type Exporter Selector: 17 Error code: -1609629695
... View more
‎Sep 17, 2023
01:04 PM
Thank you, I've been monitoring my system load. Premiere gets laggy when I have several graphics on my timeline. I thought throwing it 128Gb of RAM would solve the problem, lol. I will continue to do this before I make any decision on changing hardware. Cheers! thanks for your time.
... View more
‎May 17, 2023
04:02 AM
3 Upvotes
Seems I have solved this issue by pressing ALT key during startup and then select Reset app preferences, Clear media Cache files, Reset plugin loading Cache and hit continue. After that it played back much better. Even at full resolution and with LUT. Furthermore I moved my data-files to another and faster disk, which made playback even a bit more smoother. Hope this solved the issue completely and might help somone else.
... View more
‎May 16, 2023
02:26 AM
same also extremely laggy on macbook m1 max... version 22 works
... View more
‎Apr 20, 2018
06:35 AM
Hi Dan - Per my message above - I'm on Mac. I used free software (dowloaded from Apple app store) called "Free AVCHD to MOV" and it worked like a charm. Converted all my files to MOV in a new folder and retained the file names. I just had to relink about 20 clips, which took 3 minutes, and all is good again.
... View more
‎Feb 01, 2018
05:43 AM
I looked over the posts regarding gaming and editing in the same PC, and now I know why I had agreed with the "keep games off" mantra: It's not so much about the software issues, but it's about the hardware balance issues. You see, games and editing software have fundamentally different hardware requirements to begin with. Games make heavy use of the GPU but relatively little use of the CPU. Editing software, on the other hand, make heavy use of the CPU but only heavily use the GPU in certain rendering tasks. This is exactly why a balanced hardware configuration is very important in an editing PC. Many gaming PCs, on the other hand, have a hardware balance that's severely lopsided towards the GPU but cheap out on the CPU. And too much GPU relative to the CPU can, and does, create problems when running editing software. I hope this clears up things, Randall
... View more
‎Jan 22, 2017
12:13 AM
Hi, I keep having the same issue. It's happened in one project that was created in CC2015. Im currently adding new footage in and that brand new clip caused the render to fail. I isolated it just to be sure. I also had the same error on a brand new project created in CC2017. It seems to be an intermittant fault. It's even crashed on sections without any lumetri effects even present. I have tried everything including a clean install of windows. PC Specs i7-3930K 3.2 GHz 24 Gb RAM Win 10 pro GTX 690
... View more
‎Feb 02, 2015
01:34 PM
‌sorry - I did not read the test/review to the end. I did only read the part with the disk being faster in Some points. I will certainly study this further and try to find the best solution. Thankd for the advice 🙂
... View more
‎Jul 19, 2010
02:04 PM
Too bad this thread has gotten so snotty, as it started out to be a helpful review. Anyhow, I'm locking it for the time being.
... View more
‎Dec 08, 2010
07:14 AM
I'm experiencing the same error myself, and in my case it appears to cause issues with my system restoring from sleep afterwards. (I've seen several reports online of similar issues with FormDesigner and other programs, where the system will report an unexpected shutdown shortly after the error occurs, and there are no other frequent / untoward errors reported in Admistrative events, nor others adjacent to the timing of the crashes. Hence I believe this is probably not a coincidence.) My error log: Log Name: Application Source: SideBySide Date: 12/8/2010 3:37:10 AM Event ID: 80 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Michael-Desktop Description: Activation context generation failed for "C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd.manifest. I've filed a bug report, as suggested here. (Even if it wasn't a related issue, this bug should be fixed by Adobe, as spurious errors make it harder to track down the real cause of problems. In this case, I don't think the error's unrelated though, as explained above.)
... View more