CTM Solutions

Hi all:

Looking for an interim system, while awaiting Apple silicon compatibility.  Thinking of either Mac Pro 6,1 or Intel Mac mini.  Curious what folks are running, and what you would recommend.

Will be running latest AVID MC, Resolve, PS/AE and Logic Pro X.  Most of my AVID work is offline DnXHD resolution.  Hoping to get a machine that runs AVID like butter.  My current 5,1 8-core is struggling on Mojave.

Thanks in advance.

JIM. 

Hi!
I´ve just bought a MacBook Pro 16". 2,6 GHz 6-core Intel Core i7

I want to work with two external displays and I´m looking for the right docking station for this purpose. It´s a jungle out there and my apple-reseller already gave me a docking station that didn´t work. And I´ve lost 4 days of work. So I´m very greatful for any good suggestions. 

Cheers

Erik

In Media Composer 2021 if I set to the export setting of MOV or MP4 and I have a mixed format 720 59.94 timeline in my 720 59.94p project. 

If I set the Export Setting's Frame Rate to 59.94p then the export plays fine, audio and video in sync.

If I set it to 30p or 29.97p or anything, then I hear extra audio in the outputted clip, its like its using a audio clip that's in the sequence's middle but also rolling out and playing some of that handle, but visually in the timeline that audio clip is not where it is playing in the MP4 MOV export.

For example, say I had a OH YEAH! baseball shout at the midle of a 30sec spot.

Then if I export that 720 59.94p spot with MP4 or MOV export set to 30p I hear that OH YEAH HE'S GREAT  (he's great being the handle) playing at the back end of the spot, not even where the OH YEAH that is in the timeline shows in the timeline.

Any ideas?  When I dfdn't use the AVID export MOV setting and more the QUICKTIME MOVIE to export a .MOV I could be in any framerate project and have that Quicktime Movie export dialog set to take CURRENT for framerate, that way no matter what project I was in the "viewable" quicktime I exported came out at that frame rate and all audio fine.

Any ideas guys? Maybe a bug in 2021?

What's the best practice for transcoding archival footage with various frame rates for a 23.976 project when working in MC 2018.12.11?

In the past, I did the frame rate conversion prior to transcoding (ex. in After Effects). Does this cause issues when the project gets turned over to color?

Ex. The original footage is 30 FPS.

I do the frame rate conversion to 23.976 in After Effects before transcoding, then transcode in Avid to DNxHD 36 at 23.976.

The editor makes a cut into the clip at 00:00:00:12.

When the project gets to color, will the timing for this cut remain the same (at what would be 00:00:00:15 in the 30 FPS archival footage)?

This may be a dumb question; it's just something I've never been sure about.

What's the best practice for transcoding 4K (1.9:1) footage for a 16:9 project, if the final delivery is UHD (16:9)? I keep running into jobs where there's a mix of 4K and UHD footage.

If I transcode the 4K footage letterboxed, then Frame Flex / Center Crop, I'm thinking it would allow the editor to change the framing if they wanted to use the left or right side of the 4K footage?

When the project gets turned over to color, will this Frame Flexed 4K footage be treated as if it was blown up (to 107% size or whatever)?

I'm an Assistant Editor with a perpetual license for MC 8.9.2. I've been offered a few days on a job where the editor will be using a newer version of Media Composer (not sure which version, definitely 2018 or higher). Would I be able to do Assistant Editor work using 8.9.2 and still be compatible with the version the editor is using?

At some point, I'll switch over to subscription; but, since I haven't had any jobs up to this point where I had to use my own Avid license (I've always used work computers), I'm reluctant to give up my perpetual license until I get work that requires me to use my own Avid license.

I was adding buttons to my timeline with the Command Palette and accidentally overwrote the audio meter. I didn't realize it was gone until a few hours later when I started playing clips in the timeline and couldn't see the audio levels. Is it gone for good? I can't seem to find a way to bring it back without starting over with a new user profile. 

Hi,

I need to send someone a sequence which has captions created in the title tool (2020.10, OSX 10.14.6), they are using MC on Catalina so no title tool support.  What will happen when they open the sequence?  Should I duplicate it and remove the titles?

Thanks

Hi,

I've got a footage that's shot ProRes 4444 4k which I'm running inside an HD project - linking at the moment rather than transcoding.

I'm finding that when I hit play the picture skips and stubles for a few seconds before settling down and playing OK.  I'm playing it from an SSD so drive speed can't be the problem.  In the dim and distant past (I used it on newscutter) I remember there was a console command that cached the video for a number of seconds from where the playhead was parked ready for instant playback, does this still exist, and if so what is it?

Alternatively any other suggestions are welcome!

Thanks

iMac 5K 2019, 8 core 3.6Ghz, 40GB ram, 10.14.6.  MC 2020.10

Is there a Maximum Bin Limit to what a project can hold?  The project is big but definitely not the biggest I've seen.

A new editor started and he wants to keep all his bins within the same project.  This makes the project extremely sticky.  It seems less so on Window's machines with 2018 versions of software.  But once it is on a mojave mac running 2020.8 it becomes unusable. 

The video and timeline react perfectly once the clip /sequence is loaded but it is the navigation of the project itself that suffers.  Opening or closing bins, opening or closing project, even scrolling up and down to view the bins, only scrolling, is so unresponsive.  Saving to attic takes an age too.  The problems happens when the project is local on an SSD but is exasperated once the project is ran from a NEXIS shared workspace.  

I have tried various 2019, 2020, 2021 versions all that the same issue.  I have upgraded the NEXIS to the latest version and the client.  Rebuilt the OS of the MAC.  Removed the SearchData folder from the project.  Deleted the MC state files.   Deleted the computers reference to the project (that would hold waveform cache etc) but nothing seems to change.  When using windows PC running 2018 the GUI becomes "normal" but that creates assertion errors, which may be fixed by rebuilding databases but that is not the job spec so is not a solution in this case.

Has anyone experience anything similar and what did you try to help/resolve the situation?

Any help or advise is greatly appreciated.  Cheers

Rory