Sara Shier
Forum Replies Created
-
Hmm. I suppose that’s a possibility but I’m almost positive they mean to use the .gif or .jpg as the video file. The reason I think that is because the videos are going to multiple websites and one of the websites requires either a .gif or a .jpg of the movie. They can’t take other file types.
-
Interesting. I learned something new.
Thanks so much! You’ve been most helpful!
-
Well, now I have a question about the .jpg extension. Isn’t that a still image format? That’s the only way I’ve ever seen it.
Do they mean motion jpg perhaps? Or can .jpg be a video format?
Thanks in advance.
-
Thank you!
I’m downloading the trial version of Episode just to get a feel for it. Hopefully the interface is nice and this will solve my issue.
I thought .gif was a little strange too but I just found out that I can provide them a .jpg instead of .gif if I want to.
Thanks again!
-
Hi there…
Yes, I figured out the 5GB thing and am now running 4GB. I spoke to AJA again and it is a problem that some machines are having – not all, but some. The tech support guys told me that both Apple and AJA are aware of it but nobody’s really doing anything yet. They said it’s something to do with filters that Apple puts on the RAM?? So it is a real problem but they did provide a work-around. -
Sara Shier
September 29, 2007 at 2:19 pm in reply to: TC breaks when capturing ProRes HQ 1080i 29.97Hi…
I’m not sure if this could be your problem, but it was mine.I have a MacPro Dual Quad Core with 5 GB of RAM, FCP 6 and an AJA Kona 3 card (software v 4.0) capturing to internal SATA 7200 drives. I was trying to capture Apple Prores 422 HQ (1080i 29.97) from an HDW-D1800 HDCAM deck. I couldn’t capture that format or reqular quality Apple Prores because of dropped frames. If I told FCP to ignore dropped frames, I could capture but not playback. DVCProHD worked fine. My system’s definitely beefy enough to handle ProRes. I tried everything I could think of and the following morning I called AJA for ideas. They told me that there’s a software bug with the Kona 3/driver v 4.0 – supposedly systems with over 2GB of RAM have problems working with Prores because of this dropped-frame issue. So I removed 3GBs of RAM and bingo! They’re apparently working on a fix.
So I’m not sure if this might be related to your problem but you might look into it. I posted this awhile back in the Kona forum and a couple of people said that their systems were over 2GB and they weren’t having problems. This is what AJA told me and it fixed my problem (although 2GB wasn’t enough for the work I was doing with prores HQ in FCP so I had to go back up to 5GB after capture for editing)
Good luck! -
They actually had me physically remove the RAM from the tower. Works great now…my RAM’s all wrapped up sitting in a pelican case which isn’t fabulous but at least ProRes is working! I’m not sure if they’re having the same problem with other devices.
-
Yeah, I wasn’t thrilled about having to remove RAM, but I needed my system to work with Prores. I wonder how long it will take for them to fix the problem.