Hi
Same issure here on Avid MC 2018.11 and OS X 10.14.1 on MacbookPro (Retina Mid 2015).I have no NTFS drives attached nor Paragon Driver installed as quoted in Knowledge Base article mentioned in this thread.Tried reinstall, restarts and also removed AMA Plugins without any success.
Really looking forward for a solution.
Best,gorbi
Since updating to Mojave I've had regular issues with opening MC 2018.10 and no change with 2018.11.
In my case, I had an older version of the Paragon software installed and removed it from the system, no change.
Here's my current workaround:
-Disconnect external editing HDD (G-Tech Thunderbolt 2 RAID)-Start Media Composer. Loads to select/create new project screen-Reconnect external HDD-Browse to the current project folder and load-When asked, choose Mount All Volumes to access media on the newly connected HDD-Project opens for editing
Thank you for this tip. It seems to help. I'm in the same boat as others. Let's hope this fix holds for now!
Just to update my situation I was able to fix my problem by removing all the AMA plugins installed on my computer and re-installing the newest versions of ones that I use (panasonic, canon, and sony). I think I must have had some AMA plugin conflict. No more error for me.
Dear Avid. None of the tips from this thread helped ;(
I don't have any external drives, no I/O devices, no Paragon, no NTFS partitions.
MC 2018.12 and Mojave 14.2 on iMac 27 2017
I hope I have found a kind of temporary solution. But at first I had to find a method to recall the problem ;)
So the perfect method to recalll Error:AvCFTypeRefPtr(:) Invalid Input Reference is to restart a mac from another partition (which I prepared exclusively for this test) and start freshly installed MC there. Then just quit, restart to the old system and we have our old problem again.
To solve it I use Onyx https://www.titanium-software.fr/en/onyx.html
On the Maintenance tab select only 'Applications' and in options only 'Application cache' then hit 'Run Task" and after system restart MC starts as it should.
For now it works. Can anybody confirm this solution?
I don't have time to try this method with more options like Paragon, and connected external drives - maybe Avid guys can?
And BTW, I discovered that if two different systems with MC exist in one comp, you don't have to deactivate and reactivate each time when switching from one system to another. Just activated one, then another and both works.
I thought the problem had gone, until I updayed to 2018.12, error came back
Tried a boot with all my external drives removed, it was still there
So I uninstalled Paragon NTFS and "seems" to be working now!
Not sure what I do when I get an NTFS drive to use!...
My office just got a brand new iMac Pro (2017) but it was installed with OS Mojave 10.14.2 on it. I installed 2018.12 but the playback is very slow and staggered even for 1080p videos. At a certain point when playing back a timeline, the playback will stop and freeze. The other macs in the office are on High Sierra 10.13.6 connected to a ISIS storage system with Nexis Client Manager and we have no problems. We have tried to downgrade the iMac Pro to High Sierra but that has not worked. Any suggestions?
We are seeing the same error on 2018.11 on OS 10.13.6 on a mc trashcan. The Paragon software is not installed.
Any thoughts on that from the 'bridge' @AVID?
I have this issue as well. I'm on:
OS 10.14.2
MC 2018.11
Aja T-Tap for my IO
no NFTS or paragon installed
working off SSD external drives
like other complaints mentioned, the error comes up during MC boot, after which I can no longer get in. or while working in a project, after which I can usually get around it.
anyone know of what the most stable version of MC is for Mojave that might not have this issue?
I just found out a solution which is working for me.
It seems that the error always occurs, when Time Machine starts on my computer. Or if Time Machine is running, the error occurs immediatley after starting MC. I use Time Machine on a QNAP NAS drive which will be mounted when Time Machine starts. It seems that MC has problemes with such drives ore network shares. I didn't test it with a local attached Time Machine harddisk.
Can anyone conform that this issue is linked with Time Machine Backup?
To avoid the error, I can just turn of Time Machine and start it manually when Avid MC is not running.
I am running OS X 10.14.2 with Avid MC 2018.12.
ok - i think i can 2nd what you just said here.
I also am running Time Machine on an NAS (Synology), and this morming when TM was running, I couldn't get past the error upon booting up MC.
So I shut down, restarted, and set TM to not operate during the day hours while I'm working. And so far, I haven't gotten that error message yet.
Thanks for the tip; hopefully this solution will hold. It'd also be nice if we didn't have to dance around Avid in such a way. Maybe they'll address this in 2019.01? Is that wishful thinking?
Indeed, Time Machine does seem to be the problem causing these "invalid input" "exception" errors with starting MC. If you are a Apple Time Capsule user or store your Time Machine backups on a network device then you know the pain of this error more than most other Mac users. It just seems that MC is rather promiscuous and looks to all drives everywhere, even disk images that are mounted.
Some useful workarounds:
1. Turn off Time Machine (you may have to reboot to get any backup images to unmount)
2. Contact Avid Support till they update the application
3. Unmount "Time Machine" Disk images using the Terminal (sudo diskutil umount /Volumes\Time\ Machine\ Backups/)
4. Contact Avid Support till they update the application
5. Keep Time Machine off while using MC
6. Meanwhile, keeping Time Machine off you may lose data as it may be your only backup plan. Thus, contact Avid Support till they update the application so that you can get back to backing up your computer.
I supose I could have just said that you have to turn off Time Machine all together, but I wanted to make more of a show of it.
I hope these items help us all.
Just had the issue again (haven't worked on this machine in a while) and disabling Time Machine fixed it. Please avid fix this!
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller