[quote user="Pat Horridge"]Create a new partition[/quote]Or you can create a new folder and name it. Then make this new folder into a virtual network drive. see here Inside this new virtual drive folder create an OMFI MediaFiles folder. Move half of your OMF media into this folder. You will probable need to open the console in MC and type

Possible workarounds I would try. (FWIW I have not used either method in recent versions of MC.) Make a video mixdown of the cut and edit this onto a top empty video layer. 1: Use Add edits to split the video track above the mixdown to the desired cut points and create the CC's on this track. When satisfied duplicate this timeline, delete the mixdown

A test I did yesterday for getting an audio only AAF from PT's 2019.12 to MC 2019.12 with media including file names for a question in the Pro Tools forum. I have not used OMF for years but from my reading of your post this method using AAF seemed to match all of your requirements. I used a computer with both MC and PT's on it and without shared

FWIW and I am not on a Mac. I have had MC 2019.11 co-installed with PT's 2019.10 for a month with no issues on Windows 10. Since this morning I have been running MC 2019.11 with PT's 2019.12 also without issues. This system is a standalone, no shared storage.

Thanks Marianna. Yes I am running now without issues so all is good. Sorry but you know I am far to cynical to fully embrace a "bad Luck timing" encounter for an all the same symptoms and same cure problem that occured a few days before the first reports of any Reboot fail issues appearing here. I had fixed the Mac OS reboot problem over the

[quote user="Dom Q. Silverio"]Uninstall Google chrome. [/quote]Only problem with that here was the Mac (10.10.5) has never had Google Chrome installed or even downloaded to it. FWIW here even after reinstalling the OS MC reported the software was unlicensed. The Mac would not see any dongle on any USB port. (It would see every other USB devices

Interesting Randall. For me having had all of the symptoms described in the Hollywood studios hit by thread here on a Mac Book that has never had Google Chrome installed so I am not convinced. (OS is 10.10.5 and MC version 8.3.1 released long before the current Mac Dongle install issues surfaced) My final symptoms from the OS issues (iLock and Kernel

You could try selecting KEEP with the mixdown. Then create a timeline with Source clip and edit in the part Mixdown above it. Step a couple of frames forward from the end of the mixdown and set an in point on the source clip and an out point at the end of the clip. Then try another Mixdown with Use Marks selected. Could identify corruption in the clip

[quote user="Telegram!"]is there a sense that Avid Pan & Zooms, even when rendered, contribute to the kind of performance hits you are talking about?[/quote]Hi Matt, Pan and Zooms renders create Avid media at your projects media resolution so they should be easy playbacks from the timeline.[quote user="Telegram!"]does it make

Rather than render everything I mixdown each part as completed and edit the mixdown back onto a empty top layer video track. Takes the same time as rendering all the parts in the finished section(s) When ever you need to play backs monitor the mixdown layer. (Same principal works for audio mixdowns) I use a dedicated mixdown bin so I can delete some