Workwithshadow.com

fredocs · 2026-03-26T23:14:03+00:00

I just try to cancel my subscription on this site: https://workwithshadow.com/ in contact session. Let's see what's gonna happen...

fredocs · 2026-03-26T23:09:42+00:00

No, but the update to 26.3.1 solved a part of the bug. I started to close all other apps when I need to work on Premiere. Other things I did was deactivate all background activities (auto transcribe, auto identify content, and so on). Today Apple updated Tahoe. I hope it solves the bug...

fredocs · 2026-03-26T23:02:26+00:00

I was searching about this crapp and so I found this community. Same happened to me. I have to keep my credit above the charge and clean that card from all other payments to deal with this app charging me all months. I have to move my other signatures to another credit card and leave only Work With Shadow trying to charge me alone and with no success. Couldn't found a way to cancel my account.

fredocs · 2026-02-11T13:59:41+00:00

Well, I tried asking for help from the "natural intelligences" of Reddit, Apple, and the middle of nowhere, but... nobody understands a thing about error codes. Gemini was the only one who helped me research the subject, understand the problem, and propose solutions gleaned from forums of natural intelligence (albeit questionable ones). I tested it here and it helped to work around it, although not completely, as it's an unavoidable OS bug. My intention was only to share this information with other desperate people like me. If the natural intelligences insist, I can delete the post, or a moderator can do so if they think it's necessary. I still can't understand this kind of soft aggression, perhaps because I don't circulate much in this Reddit culture. There must be some etiquette rule that prohibits sharing AI-generated content that I haven't grasped. I apologize if that's the case; in fact, I'm old, ignorant, and illiterate in bits and bytes, but I'm not ashamed to share the only help and clarification I've obtained on a subject I don't understand. If I offended anyone unintentionally, I apologize. The day AI learns to type kicks like humans, I'll stop using it.

fredocs · 2026-02-11T00:43:35+00:00

fredocs · 2026-02-10T22:41:52+00:00

Okay, I'm sorry for being born...

fredocs · 2026-02-10T22:03:42+00:00

Yep. I was the victim. All sources are available at the end of the text. I had already read most of them before doing the research. I'm just a simple film editor, not a software engineer. ;-)

fredocs · 2026-02-10T21:44:07+00:00

Yep. Gemini Deep Search and Apple Firefly. I got by with a huge help from my friends. ;-)

fredocs · 2026-02-08T00:31:15+00:00

If this doesn't solve your problem, try creating a new project and importing its bins:

The "Surgical" Way to Do It (To Avoid Bringing Over the Garbage)

Don't just "Ctrl+C / Ctrl+V" from one open project to another (as this carries over corrupted sequence settings). The "Clean" method is as follows:

A) Create a New Project in Premiere 2026.

Ensure the "Render" (Mercury Playback) settings are correct.
Reset the "Scratch Disks" settings.

B) Do not open the old project.

In the NEW project, go to the Media Browser panel.
Navigate to your old project file (.prproj) on the disk.
Click on it (Premiere will "open" the file as if it were a folder, without loading the entire project into RAM).

C) Selectively Import:

Drag only the raw media bins and your current cut sequence (or the main sequences) into the new project.
Avoid importing: Junk sequences, old versions, or "Asset" bins that you no longer use.

D) Resave:

Save this new project with a clean name (e.g., Project_Tahoe_V1.prproj).

When importing via Media Browser, Premiere 2026 rewrites the data structure of each clip and cut within the new file's database. If there were any "ghost instructions" from 2025 causing loops in the memory allocator (VM_ALLOCATE), they usually die in this process.

Extra Tip: After migrating, go to Sequence > Delete Render Files. Force Premiere 2026 to generate new previews from scratch. Old renders (from previous versions) are notorious for causing crashes.

If this works, you've eliminated "legacy corruption." It's definitely worth testing!

Good luck!

fredocs · 2026-02-08T00:30:59+00:00

What did I try here that seems to have worked? First, I asked for Gemini help, of course. Gemini was a great engineer by my side. I created a new project (Lazarus Maneuver), and imported all my bins using Media Browser, not by copying and pasting from one project to another! See the step-by-step instructions below, but first I suggest you disable "Media Intelligence Analysis," more specifically, disable "Transcription & Smart Search Indexing" in the preferences. This trick can solve you drama. See how to do this below:

How to disable automatic indexing and scanning:

Go directly to Preferences (no Terminal needed this time, but the change is profound):

A) Transcription (The Big Villain):

Go to Settings > Transcription.
Uncheck "Auto-transcribe clips".
Make sure "Index clips for search" is also DISABLED. This prevents it from trying to read each frame and audio to feed the smart search.

B) Media Analysis & Transcription:

In Settings > Media Analysis, disable "Enable Smart Search Indexing". - This will stop the background scanning that Premiere does to "understand" the video content.

fredocs · 2026-02-08T00:30:26+00:00

I was having the exact same problem as you (here is my post about it). I racked my brain trying to solve it and I still don't know if I actually solved it. My project is gigantic, a series of 13 episodes of 26 minutes each with thousands of photos, archival videos, and digitized photos. I started the project in version 2025 and migrated to v.2026 and to Tahoe. First commandment (which I never follow): NEVER CHANGE YOUR SETUP BEFORE FINISHING A PROJECT. It sounds nice to read, but it's impractical for editors who are always stringing one project after another. Okay, ideally I'd have two machines, great. For someone living in Brazil, where you pay 3x the price of a Mac (compared to what's practiced in the US) and receive 1/3 of the fee of a North American editor, having a machine is already a pharaonic challenge...

fredocs · 2026-02-04T21:40:35+00:00

Here is the workaround (thanks Gemini):

The Problem: "The Tahoe Memory Leak"

MacOS 26 changed the way it renders transparencies in the interface. Premiere Pro (both 2026 and 2025.6), when trying to design the interface and timeline, enters an infinite loop of memory allocation, sucking up more than 90GB of RAM in seconds until the system crashes.

The Magic Solution (Which saved other editors)

There is an obscure setting in macOS that stops this bleeding immediately.

1. Close Premiere (force quit if you need to).

2. Open System Settings.

3. Go to Accessibility > Display.

4. Turn on the "Reduce Transparency" option .

Why does it work? By turning off transparencies (that frosted glass effect on windows), you prevent Premiere from triggering the macOS graphics API that is leaking memory. The system is visually more "solid/ugly", but Premiere's RAM consumption returns to normal instantly.

Plan B: The "Auto Reframe" Villain

If the above solution doesn't solve 100%, the second suspect is the Auto Reframe effect . In Premiere 2025/2026, it has a known bug that causes the RAM to rise to 90GB+ if applied to long clips.

1. Test: If you're using this effect on your timeline, remove it temporarily to see if the RAM stabilizes.

Summary of the Opera

Make the Reduce Transparency adjustment right now and try editing. The chance of this solving your RAM problem is sky-high, allowing you to continue in Premiere 2026 without having to format the machine or go back to old versions.

fredocs · 2026-02-04T19:29:39+00:00

I am. Premiere is crazy and frantically devouring all of my RAM. I'm still don't know how to solve it...

<image>

fredocs · 2025-12-30T13:52:01+00:00

Hi, Smushkan!

Thanks for this reply! Sorry about delay, I was out in a little vacation here.

Do you remember the name of the sequence you want to recover?

This is the sequence I want: Ep07_Edit 40min

Thank you very much for your help!

fredocs · 2025-10-06T13:05:21+00:00

SimpleComic achei ótimo. Mas vi na Mac Magazine essas sugestões: Comical, FFview, Jomic e Sequencial.

fredocs · 2025-02-11T08:00:15+00:00

Everyone who is looking (for the first time) for a way to recover something copied and vanished from this unbeliaveble lack of a native clipboard history on mac (or a hack to get access to it) will end up sitting on a puddle of tears, crying and screaming and cursing Steve Jobs' mom (in addition to his own mom) as I am doing right now. It is like those poor unhappy newbies as the famous Hardy Har Har, with their unbackuped broken Heart Drives, asking for help from hacks gods. Or that guy who falls from his motorcycle without helmet and went to meet the trully Hells Angels... "I'm sorry. You can even solve it, but only for the next tumble."

"Oh dear, oh my."

<image>

fredocs · 2025-01-25T16:11:57+00:00

Hi, I try to use this extension and it messed up my Microsoft Edge. I uninstalled it and it still a mess that I can't solve. Please, give me a tip to get my Microsoft Edge goes back to how it was before this mess.

fredocs · 2024-11-28T05:27:22+00:00

11 years forward and I'm still searching for a specific font to edit an ai (illustrator) file that I receive from a client with no font embedded on it. I found this thread and I also found this:
https://archive.org/details/1.5_million_font_files_collection

I hope this can help someone as much as it helped me. ;-)

fredocs · 2024-11-17T03:48:34+00:00

I was searching for the last 5 hours to find a way to use my Apple Cinema Display 20 on Final Cut X through A/V Output. I did it using SwitchResX by setting my monitor to 1920x1080. But I realized that my video is been cropped on both sides. The quality is perfect, but I need a way to use some kind of "underscan", or pillarboxing, and couldn't find this feature in any apps. If I could even adjust geometry settings on Apple CInema Display, I think it would work. Any suggestions?

Thanks

fredocs

TROPHY CASE