Joe Procopio
Forum Replies Created
-
so i’m thinking it is indeed a kona thing…i brought up the project and listened back through the digibeta and got the same result…but listening and monitoring the FCP, was correct.
Broadway Video, NYC
AVID/FCP editor/engineer -
thanks for the replies. it looks like there was something going on with the Mac…i had to rebuild it…we moved the project to another system and everything was there….phew…but thanks for the autosave option…
Broadway Video, NYC
AVID/FCP editor/engineer -
kiss your mother with that mouth?
Broadway Video, NYC
AVID/FCP editor/engineer -
maybe you get things thrown back in your face because you think you know everything…apparently you don’t. I’m sure you have done the same to others…I’m glad I won’t hear back from you since you don’t offer any knowledge…just act like you are better than others with your pompous attitude.
You don’t know other people’s level of knowledge just by reading a post, so to assume they don’t know what they are talking about is arrogant…
this is ridiculous…as with everything else, I found the answer without outside help…
Broadway Video, NYC
AVID/FCP editor/engineer -
look up AJA Kona setups…they list Mac Pros and 2008 Mac Pros…better yet, look at this link…
https://www.aja.com/html/support_kona_rec_sys.htmwhat system are you working on? I guess you never ran into this issue, but it is real…in my real world…just because you have never heard of something, doesn’t mean it is a real thing…
Broadway Video, NYC
AVID/FCP editor/engineer -
well…it was indeed due to a difference between the 2 Macs….8 core pre 2008 Mac Pro vs 2008 Mac Pro….capture cards are Kona 3s…the 08 Mac Pro has fixed bus speeds, the pre 08 Mac Pros have adjustable speeds via the Expansion Slot Utility that lives in the System/Library/Core Services folder…these were set correctly way back when they were first installed…on the pre Mac 08 systems…but since then both have been to the reseller for work, and something set them back to their defaults which made the Kona run at 1x instead of 4x
oh and trust me… there is nothing absurd about blaming the build dates of macs….especially since in this case, the only difference wast the build date….same processors, same capture cards, same ram…only the new one is running leopard and the expansion slots are fixed…they change things from system to system, and you have to be on top of things (you can’t install Tiger on a 2008 Mac Pro)….if you’re not working on the new 8 core systems, you don’t know what I mean…and now our new systems are the new intels…thankfully they are only running CS4 for our design team…I figured you guys were all up on the latest from the Apple company…
and if i had more time, and didn’t have a client breathing down my neck, maybe i could have offered yup a little more info, but that wasn’t the case…and I solved it the next morning…first thing…so no need to come back here and ask more questions…
maye I should also state that we are a professional house that doesn’t capture via firewire…ever…and we don’t capture to internal drives…ever, and ….well you get the idea!
Have a great week..I know I will!
Broadway Video, NYC
AVID/FCP editor/engineer -
thanks…i’ll check those out…but since there is no filter showing up that would cuase this…we’re working around it by lowering opacity for now
Broadway Video, NYC
AVID/FCP editor/engineer -
have you installed the latest updates? try going up to 6.0.5 if you haven’t…there was a lost renders issue in v6
Broadway Video, NYC
AVID/FCP editor/engineer -
so, that is exactly what it looks like is happening…but there is no effect on the clip….unfortunately, we can’t start removing things because we have lots of other filters applied on many clips….I think we’ll work around it this time, and worry about outputting it…then we’ll investigate some more…thanks for your ideas though…if you have any more, please feel free to throw them out there.
Broadway Video, NYC
AVID/FCP editor/engineer -
that’s what i’m looking for…i’ll check!
Broadway Video, NYC
AVID/FCP editor/engineer