[Craig Seeman]

Generally speaking, even the M1 chip will handle 4K. If you’re dealing with camera specific raw codecs or harder to decode codecs the M1Pro and especially M1Max will handle much more complex codecs with layers and composites.

Some people are speculating a 27″ iMac Pro with appropriately powerful CPU (24″ is just M1″) as early as March but others say later in the year. If you can wait until March I’d wait.

[Craig Seeman]

Not are what your contract says but it doesn’t sound like it matched the discussion you had. If you get numbers from the client, you write them in. If they change them, the have to fill out a change order. Also a contract should have clear dates decisions need to be made by the client.

If the contract doesn’t reflect the discussion, deadlines, work time involves than perhaps you need help writing your contracts.

[Craig Seeman]

Sounds like you did your best under the circumstances.

[Craig Seeman]

Is the 55MB file a Zoom recording?

Are you re-editing that file?

Ugh. Zoom has a highly compressed recording format with a very difficult GOP structure that generally is a problem for NLEs. Zoom has a NLE compatible mode that one is supposed to use if the file is to be edited later.

The file will be very small but difficult to edit. You should convert to Apple ProRes. Baring their extreme encoder settings, it will be difficult for you to compress that small with that quality. BTW you can see the actual GOP structure and frame by frame bit rate in Telestream Switch Pro. Ideally you’d want multipass, High Profile, CABAC entropy but it would be difficult to match their very sparse keyframes.

[Craig Seeman]

When you say “original clip” please explain. What codec? You mention the “original clip” being 55MB H.264. Using that clip would be a problem.

You would need the source for their compression, ideally ProResHQ or some equivalent at the source frame size.

Have you examined the compressed clip in something like Media Info to see what their compression settings were?

Some encoders are better than others. Do you know what encoder they used?

[Craig Seeman]

It requires Big Sur 11.5.1 or higher.

So Catalina be gone if you’re andFCP user.

[Craig Seeman]

For FCP users (and other non-Adobe users). My guess is raising subscription prices for non-Adobe users, focus on Adobe integration over others, and possibly dropping support of non-Adobe products at some future point.

[Craig Seeman]

Previous versions of Vidchecker aren’t online. You’ll have to contact support.

Of course they’ll try to get you to pay to update and continue support but they might get you a link to the older version in the meantime.

http://www.telestream.net/telestream-support/vidchecker/contact-support.htm

[Craig Seeman]

and if one were on Mac

User/Library/Application Support/Episode/Assistant.plist

User/Library/Application Support/Episode/Assistant.xml

User/Library/Application Support/Episode/IOServer.plist

User/Library/Application Support/Episode/IOServer.xml

User/Library/Application Support/Episode/Node.plist

User/Library/Application Support/Episode/Node.xml

User/Library/Preferences/net.telestream.episode7.plist

User/Library/Saved Application State/net.telestream.episode7.savedState

User/Library/Caches/net.telestream.episode7

[Craig Seeman]

All the potential problem files that one might delete to get Episode working again.

C:\ProgramData\Telestream\Episode 7\IOServer.xml
C:\ProgramData\Telestream\Episode 7\Node.xml
C:\ProgramData\Telestream\Episode 7\Assistant.xml

and

C:\Users\Administrator\AppData\Roaming\Telestream\Episode 7
C:\Users\Administrator\AppData\Local\Telestream
C:\ProgramData\Telestream\Episode 7
C:\Windows\Temp\Episode

C:\Windows\Temp\EpisodeCache