Known Participant

P: Video Import Error caused by MediaCore plugins

Forum|Forum|5 years ago
September 24, 2020
18 replies
770 views

When I try to import video files into my catalog it tells me "There is a problem with the video file (12)". There is no issue with my video files. I removed a video that had previously been imported to my catalog with no issue and tried reimporting as a test and it would not import. I received the same message. I created a new catalog to test and same message and video would not import. This is a recent issue as i have been able to import videos with no problems. The issue is occurring on both my Mac Book Pro and my Mac Pro.

Show previous replies

M

michaelk5102444Author

Known Participant

I had an import video error before and that was related to a dynamiclink issue and had to do complete uninstall with the help of adobe support and that fixed the issue. When i had that issue it told me in the import dialog that i had a dynamiclink error. I am noticing that only one of the 2 dynamiclink processes is running in activity monitor link before when i had the dynamiclink error. It is weird that both computers get the same error at the same time.

Here is what my log file says:

ScreenShot20200928at07.14.50a4-a15f9e4f-27d0-4995-9ecf-1121fe80d538-1504436755.png

F

FeedbackCommunityMember

Inspiring

I had the same issue, and after a few hours of investigation I found it was caused by MediaCore plugins crashing dynamiclinkmediaserver. I had the GoPro Reframe and Insta360Importer plugins installed in /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore.

Removing both plugins resolved the problem for me.

Log files I checked in the process:

~/Library/Logs/AdobeIPCBroker.log (indicated that dynamiclinkmediaserver was crashing)
~/Library/Application Support/Adobe/dynamiclinkmediaserver/13.0/Plugin Loading.log (indicated that third-party plugins were being loaded)

Running Lightroom Classic from the terminal also provides some helpful additional output that doesn't seem to be caught by any logging facilities.

M

michaelk5102444Author

Known Participant

On both computers im running

LrC 9.4

macOS 10.15.6

None of the solutions provided have worked.

G