Ned Soltz
Forum Replies Created
-
I found that I needed to enable loading plug ins in PPro. Launch SG and allow it to crash. Then return to FxFactory app and disable loading in PPro. It took about 5 minutes for SG to launch but after a toggle on-off it worked.
Ned Soltz
-
The kext files are located in System->Library->Extensions
The difficulty is finding out which files are the culprits.
In my case, it was several kext files installed by Sonnet drivers from various products I had tested/installed. Simply removing everything Sonnet (and no need to restart after removing kext files), solved the problem. One place to start is to look for kext’s that could reference old software you haven’t used or old drivers/system extensions you might have installed.
Hope this helps!
Ned
-
And the answer is…
Apple engineers found some kext’s that were conflicting with installers.
After removing those kext’s, all software installs normally.
-
Solved!
I ran the MC 7 installer again only checking the Media Composer software installation, unchecking everything else.
Software installed successfully, activated successfully and it runs. So far.
Obviously some kind of weird issue with the start up drive.
Ned
-
Wish it were that simple. Gatekeeper set to allow installation from any source.
-
Resolve Lite is limited to 1920×1080 export.
-
You must put the F55 in CineEI mode. That will activate the AXS-5 recorder.
Ned Soltz
-
This is the same issue I had with a loaner BMCC for my upcoming review. The loaner SSD recorded well until the actual shoot we were doing. It then dropped frames on every single take. The anecdotal reports I was receiving from other users is that this Kingston 120 SSD seems to work for a week or two and then fails.
Switched to a SanDisk 480 SSD that I own and we had no problems.
And yes, ShotPut is the way to transfer files. Version 5 has just been released.
Back to my dropped frames, I haven’t seen the footage but spoke with the editor who says that he was able to use multiple takes and cut around the dropped frames.
Ned Soltz
-
Thanks to another careful look at my camera clips and the suggestion of Oliver, discovered that the original F55 clips all began with a timecode of 00:00:00… meaning, of course, overlapping timecode. Just changed the timecode on my 4K clips, went through the whole process again, and now everything links perfectly.
So this either has to do with how the F55 wrote timecode to the AXS drive, how Resolve interpreted the F55 raw footage or more likely because the Sony 4K recorder was an early pre-release firmware and had a timecode issue. I am leaning toward the latter.
Ned Soltz
-
Got it. Issue of importing the XML was more related to some beta software which was making X act flakey. X is now back to normal as is XML import