Jeremy Newmark
Forum Replies Created
-
Just to throw in another view, we’ve got an 8TB Dulce ProDQ and it’s been solid since day 1. We’re running it in Raid 3 and we get read and write speeds close to 600MB/sec. In Raid 0 it’s well over 600MB/sec. The thing screams, what surprised me most when we first got it, is how small it is. Compared to our old Huge 320RX, it’s physically about half the size, but twice the size in capacity and speed. I think this thread just shows that there are so many good solutions out there today and if you go with any of the solutions mentioned, you really can’t go wrong. Just my 2 cents.
best regards,
jeremy -
We’ve been able to get very limited playback on clips with the CF plug-in, but RT extreme has to significantly drop the frame rate and resolution, so it is not usable by any means. Keep in mind that this is on an Octo Mac with 8 gigs of ram and a very fast Raid (8TB Dulce ProDQ). We’ve only tested it with 1080 23.976 ProResHQ material, it may be feasible with DV or even DVCPro, but as Walter said, this is not a real-time plug, even with the stand-alone application you will have to render out your final product.
best regards,
jeremy -
[Tyler Dixon] “One thing I forgot to mention is that when I’m going into the deck, if the image is still, as in not playing, it will match that of my display. But when I start to play it, the image on the deck becomes green and fuzzy.”
If it’s updating the image and displaying it properly on the deck monitor when playback is stopped and then goes fuzzy and green when you try to playback, then it sounds like your FCP playback settings are not the same as your Kona 3 settings. Make sure that your output playback settings in FCP exactly match your Kona 3.
best regards,
jeremy -
[number1ftg] “Did you ever find a solution to this problem? I’m having the exact same issue and it’s driving me crazy..”
Nope, for now I’ve just been exporting directly out of motion and importing back into FCP.
best regards,
jeremy -
Keep in mind that if you are ingesting and editing with the Avid’s, you can only ingest the content in SD from the downconverted signal coming out of the JH-3. So it will be an SD workflow, not an HD workflow that you would then downconvert at the end. To ingest HD into an AVID from HDCAM tape you need at least an Media Composer Adrenaline with the DNxcel HD board, which will let you work with the compressed DNxHD codec. Or you need an Avid Symphony Nitris or DS system to ingest the HD in uncompressed.
On the other side if you are using Premier Pro for ingesting and editing, then you simply need the appropriate AJA or Blackmagic card and fast enough storage to work with HD.
best regards,
jeremy -
I’ve been having the same issue with Motion 3 as well.
best regards,
jeremy
-
[Noah Kadner] “And where is the ProRes coming into the equation?”
The media is digitized from HDCAM to ProRes HQ in FCP. Certain shots are then sent to Motion from FCP. However I’ve tried simply importing ProRes HQ media directly into Motion and sending to FCP, but the same thing still happens. I don’t think it’s on the Motion end, because if you export the project directly out of Motion it’s fine, it’s only when it is rendered in FCP that it doesn’t work.
jeremy
-
[Noah Kadner] “What resolution and frame rate?”
1080psf 23.98
-
[RJ] “I’m wondering which eSATA cards support port-multipliers i=on the MBP?”
Check out this link
https://www.macgurus.com/productpages/sata/LYCeSATA-2EC34.php
It supports port-multipliers and is much cheaper then the sonnet cards. We’ve been using this card in a new MBP for a couple of weeks now with no problems.
However, unless you really need the portability, I would go with the MacPro over the MacBook Pro. Our older quad G5 still outperforms the new fully loaded MacBook Pro. The MBP is a great secondary system and works well on the road, but I would not want to use it as my primary editing system, especially for HD work. Just my 2 cents.
Best Regards,
jeremy
-
Do you have tri-level sync?
best regards,
jeremy