Frazer Lockhart
Forum Replies Created
-
I’ve been having the same problem. You might already know this, but I just found out that the audio is still there–it’s just at -∞. So, if you want to recover it, you have to actually raise it on the timeline–using audio gain won’t work.
-
It sounds like a codec issue to me. The GoPro mp4 is a pretty demanding codec, so it sounds like your software is getting overwhelmed and your computer isn’t fast enough to keep up. This is further demonstrated by how much switching to 720 helped. I’d try transcoding to Prores 422 (LT) using MPEG Streamclip or something similar, as it doesn’t take up much more space an it’s way easier for any editing software to digest. It’s an extra step, but if you’re crashing that much it will probably save you time and frustration in the long run!
-
Hi Jim,
CS6 is working perfectly now on my machine, and I have almost an identical setup. The only time it sometimes struggles is when it’s working with more complex codecs such as R3D or GoPro mp4, or using multiple layers of complex effects such as warp stabilizer. It rarely crashes, though. A few questions for you: are you using the software disk version or the creative cloud version? Is there anything consistent about your editing (like are you always using the same codec, and if so, what is it)? Did you experience any similar problems with your previous editing software, if you had any?
-
Hey Rui,
I can’t speak to how well it works compared to its optimum performance level, although with GPU acceleration I’m sure the program would be far faster than it is now. Still, CS6 works very well on this machine–I’d say equally as well if not better than FCP7 on the same setup.Cheers,
Frazer -
Scott,
There is a workaround Afraid the only real solution is to wait it out, although there is a workaround in the meantime. For me the error only showed up when I was connected to the internet, so if you disconnect you should be able to run FCP. Annoyingly, you won’t be able to be online and running FCP at the same time, but at least you’ll be able to edit.
Good luck,
Frazer -
So it turns out that after a couple of days the problem righted itself. I didn’t do anything differently. Just a weird FCP bug.
-
Has anyone ever experienced an instance where this message pops up in error? I ask because I’ve checked every other computer using this LAN and none of them are running FCP. I suppose it’s also possible that someone broke into our office, installed FCP 7 on their computer, stole our wifi password, and didn’t take anything else, but that seems less likely to me than a FCP bug. Anyone have any thoughts on what to try before I go for an uninstall?
-
I am on a work LAN, but it is a protected LAN and none of the other computers on it are running FCP. Does the message only appear when someone is using the same SN on my LAN, or when someone else is using it in general?