David Powell
Forum Replies Created
-
It seems this problem only happens to MC owners with the name “David” I put a thread up with the same problem and no answers. I did the same on the avid forum, no answers there either. I just went back to fcp and am waiting for the next update I guess.
-
I read a thread on red giant where they claimed”send to compressor” would fix the problem. Unfortunately any sequence I send to compressor causes it to hang and crash as soon as I apply a setting. Anyone else have this problem?
I get the corrupt renders from dslr footage which is 8 bit. Does fcp automatically render to ten bit? And where can I change the preference to 8 bit?
-
Wow you gotta be kidding me! My MC is completely unuseable for cutting all non-native material then? How does any mac user put up with this? Funny thing is, the kind of work I’m doing right now was really more suited for fcpx, multi-cam dlsr events with no tc or clap sync. But FCP was corrupting so many files, I decided it wasn’t worth the timesaving I got from the bg encoding. So X was useless for exporting and MC is useless for importing. And my only option is getting a PC computer at this point?
Looks like its time to download the premiere trial. This is beyond dissapointing. Now what about if I used the import instead of AMA-transcode? If I import at dnx 45 how would I upres back to dnx 220? Is that not the way it used to work? I didn’t start cutting on Avid until version 5 which I never encountered this problem with.
-
Exactly. And what bugs me is I spent so much time trying to fix it and could never make it work. So it was just all lost time and money. As I sit here now waiting for my next project to finish transcoding, I quite miss the import and proxy workflow. funny thing is, I couldn’t even use it as a hobby YouTube editor with the problems I had.
I guess I was just part of an unlucky bunch.
-
Its purple now? After 3 projects, I finally gave up on fcp X and went back to Avid because I couldn’t get a clean render. It literally cost me days of time. My fix was to export a master file, import into avid, make markers where the corrupt frames were, re-export clean frames out of fcp x, import to avid, overwrite and export out of Avid. Yeah, all that time I saved on bg rendering and import, I paid 10x over in the end.
This happened with and without 3rd party effects in 10.05 and 10.06 and send to compressor didn’t seem to make a difference.
Btw, this happened on fcpx transitions (notably the blur dissolve) which would make the video downsize 75% and turn black, and also random green flashes, freezes and audio dropouts. My client who was also using X on a brand new MBP had the same problem as did the other editor on X. All on 3 different machines.
-
David Powell
December 3, 2012 at 9:10 am in reply to: Sharing practices for those who do not get corrupt framesWell I’ve uninstalled FCP 7 and still no luck. I’m wondering now if its a computer problem in which case I am not very savvy. I wouldn’t even know where to start at this point. Not having used it since the FCP X install, I went back to avid to try and export out footage and its giving me problems as well. I noticed I could export small clips, but it would get stuck when I went across several clips. Prior to the install I had no problems.
I’m not sure the two are related. I’d have to run more tests in avid to see whats really going on. I’d try from 7 but I uninstalled it. Wish I hadn’t now.
-
David Powell
December 2, 2012 at 2:27 pm in reply to: I think the time of the large tower are coming to an end – and the bloated software suits with it 🙂Didn’t avid add the FCP style mixing feature in the latest update? Manipulation from the keyboard?
-
David Powell
December 2, 2012 at 2:14 pm in reply to: Sharing practices for those who do not get corrupt framesThe first project was in 10.05 which had the problem. This latest one is freshly started in 10.06. I uninstalled and reinstalled and am still getting the same problem. Actually now, I’m not getting the green frames. I’m getting complete freezes in various random spots (something that was also happening before along with the green frame).
I’ve also range exported the problem areas and of course they come out perfect. The problems happen at random spots.
I went to the apple site and it had instructions for having both software on the same system. I didn’t see any warnings against doing so. Also this problem only happens when exporting out of X. As far as QT is concerned, I can export out of 7, Avid and AE with no problem. I need Final Cut Studio for DVDSP to make dvd’s when I’m done.
Will I have to uninstall the whole suite? This is bad news if so, though I have a feeling uninstalling FCP 7 isn’t going to solve this problem for some reason. I thought the issue of 7 and X had to do with startup conflict. Both run fine with no issues.
-
David Powell
December 1, 2012 at 3:45 am in reply to: Sharing practices for those who do not get corrupt framesNever thought about the FCP 7 thing. I indeed do have it installed. Funny thing is I had read on here of several people having it installed on the same system with no problem so I never thought of it. I haven’t reinstalled but I did upgrade it from 10.05 which had the same problem and it didn’t get any better. Also I upgraded the OS before going to 10.06.
I’ve done numerous projects on 7 that never had the problem either while having X installed. If it were a QT problem, shouldn’t I see it coming from my other NLE’s as well?
But I’ll try unistalling 7 and seeing if it makes a difference. Thanks for the tip.
-
David Powell
November 30, 2012 at 1:03 am in reply to: Why The Pro Market Should Take FCP X Seriously – HD Magazine articleWow so I’m not crazy! I’ve lost so many hours this week trying to get an hour long sequence out without corruption. Problem is each time out randomly shows up on a different place with or without filters. If this is common, I don’t see how anyone is delivering projects on time. And this is 10.06 with no compound clips.