Nigel Barker
Forum Replies Created
-
I never did get any help from Red Giant Support & this never worked. In the end I had to insist on a refund. The answer that I got was “Supporting C300 spanned MXF files is on the list for inclusion in a future version, but we don’t have a specific time for when it will be available.”
I see that PluralEyes is now on version 3.5 so maybe that is supposed to support C300 spanned MXF files but as I no longer own a C300 or indeed do video professionally any more I have no idea whether it works or not.
-
It would have been nice if this had been documented then I wouldn’t have spent an hour or two chasing a problem that didn’t actually exist. The update just referred to ‘Bug Fixes’ unless of course this is an unintentional feature aka a bug that got introduced.
-
I logged a support ticket with RedGiant yesterday but had no response. I thought that just for a giggle I would try using PluralEyes 3.1 with a complex sequence involving on long C300 clips & multiple XF105 clips (all from the same camera) plus a load of DSLR clips (4 cameras) 2xGoPro & 2x stereo audio tracks. This time it imported all the clips correctly from Premiere Pro although the video of the MXF clips cannot be viewed. I click Synchronize & it does its thing & shuffles the clips around so that they look to be synched correctly. However when as per the documentation I exit PluralEyes to return to Premiere nothing happens there is no new sequence imported. So I decide to try it once more but this time PluralEyes hangs with s spinning beach ball while ‘Preparing media’ So not inly does it not work but is buggy & unstable.
Has anyone got this software to work correctly with Canon C300 or XFnnn MXF files?
-
Evidently not. The new version released last week (3.1) is claimed to support MXF files but I just tried to synch a Premiere Pro sequence with just an audio track & a C300 video clip & it fails. I tried the workaround necessary in PluralEyes 2 i.e. Render & Replace audio on the MXF clip but that made no difference.