New Bug since PPro 2024, Finally on my nerves
- November 8, 2024
- 3 replies
- 642 views
So two bugs to report:
#1 - Versions: Started with v24.1 - ish and v25 (current)
We use a pretty simple folder template:
1. assets
2. Post
3. PreExport
4. Finals
Have been using this structure since Adobe Cs6 and the start of CC. However, before the last update in PPro 2023 when I choose our location to output to (ex. ...\3.PreExport\versions\v1\example v1.mp4) it'll auto move the location to the subfolder 3.PreExport and rename the file name (example v1.mp4) as 3.mp4. It's been quite annoying now for over a year and was never an issue. Happens in Media Encoder, PPro, and AE.
The only two solutions I found were to, when naming the file, actually type out .mp4/.mov/.wav/etc. when I name it OR to move the file to the intended folder afterwards and rename it what we need it to be named. It would be nice to go back to the old way Adobe handled it which was to not consider "." in a file path as the file name. Quite frustrating as we have recurring customers that use the footage/assets we make for their marketing and I'd rather not change ours and their workflow after 10 years. Keep it simple and organized for the client right?
Anyway, I digress.
#2 - Versions: v25 (current)
Actually brand new with the 2025 version:
Not sure if anyone else get's caught in this loop, but I'll open up PPro 2025 and it gets hung up looking for render preview files LONG deleted. Every other version of PPro would spit out a warning saying these were missing do you want to relink basically? Now my project won't open. Luckily, when I hit cancel (opening the project) it progresses to the "relink these missing render files" screen which I hit offline like I always do. But anyone not willing to hit cancel or worried for some reason or new to PPro with this version will be waiting a long time as it searches for something not there (aka it never stops trying to relink, I tried on my day off and it went 12 hours before I decided to hit cancel anyway so it'd be searching even longer).
No solution developed yet for this one.
Honestly, I'm very lucky. This is the first time I've actually expiereced any sort of bug in Adobe. I did not expierence the footage deletion of PPro 2014 or get many crashes in the last 11-12 years of PPro/AE. So I feel very blessed and awkward mentioning these measily bugs, but they do interfere with the expierence and workflow we have maintained and improved for so long. Please advise, fix this, or offer alternatives when possible.
If necessary, here is the hardware I use:
CPU: Threadripper 2950x | 16c/32t
MB: MSI Creation X399
RAM: 128GB 2667x Corsair (4x16GB)
GPU: EVGA SC Black 1080TI 11GB
Storage:
OS - m.2 SSD
Media Cache / Project Files - Sata SSD
HDD - 2 6TB WD Blacks + a 10TB WD Gold (not really used anymore for the NAS we have but still in the system from when built)
PSupply - EVGA 850W 80+ Gold
OS: Windows 10
System is plugged into a 1Kw UPS with wired 10GB connection.
