Oh, boy I've been reading the threads asking for AME to render imported CC and .srt language subtitle files-- I don't want it!

I am not yet a veteran CC producer. Like many, I've been drawn into the requirement as editor.

I have fresh downloads from REV in three popular timecoded formats. The minute they land, AME pounces on them. So I figured, OK, let it work.

Three hours later (these are all feature length files), I tried laying what was a .scc file, now a rendered .mov file, into my testbed HD timeline.

I gave it a chance. No dice. Black screen, even when the .mov file is correctly upscaled 300% to fill a 1920 X 1080 frame, Display Settings are enabled and set to the right stream. (REV works from lightweight SD files so it needs upscaling).

So I save all these useless .mov files (I am a packrat) and import new fresh-from-REV CC and language .scc, .mcc, and .srt sidecars.

This time I rudely interrupt and dismiss AME.

I place an unsullied .scc file in the timeline to review it, and voila, looks perfect and allows editing in the Captions pane AS EXPECTED.

Meanwhile, again pesky AME reloads and starts chewing away at my sidecars. Once again, I blow it off in the middle of process.

There's a setting somewhere to disable AME process, right? Where is that?

I don't use AME in any direct manner. I don't ingest through AME. I don't export through AME. Works in the background, Terrific. Keep it there and don't poison my sidecars.

Is there a five hour video tutorial explaining why this happens and why some folks need rendering upon import? Because I can self medicate and absorb it if necessary.

But, because I'm paying 600 a year, maybe NOT??

What the heck?? Help, Adobe.

Same full length .mcc file is attached so team members may inspect REV's work. .mcc format was chosen because it's the only CC format supporting true 24P, the timebase for the feature I'm working on, trying to get reviewed, adjusted sidecars out the door to the distributor.

Thank you.

Best, as always,
Loren