Bryan Roberts
Forum Replies Created
-
Thanks guys,
Yes, I have the latest CUDA drivers via Nvidia Driver Manager.
Alex – I’ll try disabling those things but I know in my timeline, I already have thumbnails and waveforms off as my own personal preference anyways.
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Thanks David,
I have run the speed test and it’s certainly not the drives. The primary cameras on this episode are an Arri Amira with ProRes 422 media at 1080p and then untranscoded 5D footage, GoPro footage at 1080 (god help us if esata GRAID drives can’t cut 1080p ProRes 422 and 5D / GoPro footage) and then occasionally there’s some helicopter shots with R3D 5K files (surprisingly those don’t choke up if only held for less than 4 seconds or so). What throws me is that it’s not just stuttering and dropping frames while playing, it’s the way it’s doing it. The freeze frame for 2-3 frames at the end of cuts. If it’s a longer shot like for a standup bit, there’s no stutter at all. It’s just going between shots which again, on a fast paced show like this, becomes very hard to watch. The other big indicator that something else is going on is the color correction delay. I’ve never had such a delay when adjusting sliders. It takes several seconds to just update what I’m tweaking with sliders on a longer sequence. When in a shorter sequence (say less than 3 minutes) the delay is almost gone. Something on my machine doesn’t seem to be utilized properly, maybe?
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Hi Joe,
I have it set to:
Quicktime
Apple ProRes 422
1920×1080
Only checkbox is Composite in Linear Color (I have a GTX 780 6GB edition).
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Sorry yes… I’m getting 205ish MB/s write and 215ish MB/s read. I’ve been dealing with all forms of ProRes since ProRes came out and have used much slower drives than these in FCP with no issue.
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Thanks everyone for your responses. Sorry for the delay, I got sucked back into last minute edits on a spot (even though it was “locked”).
My Drive speeds are definitely solid. I’m getting read / write speeds around 200mb/s on the standard esata Graids I’m using. I WAS using a much faster esata 4 drive Graid raid tower that I figured I’d try to nail down as the culprit. So I copied over all my media to a smaller “normal” esata graid and then restarted to see if that might help. Sure enough, exact same issues so that wasn’t the problem.
Thanks for the sequence setting – ironically I actually used that same link to setup my sequences before starting this project as I figured there should be a way to setup a native timeline for ProRes material so that’s not the issue.
Walter – can you clarify simple media structure? I generally keep with the organization that a DIT does on set which is typically Date > Camera Name > Card Name > Media Files
Unfortunately no I don’t have 7.2.2 installed. After my initial spot cutting on CC 2014 went so smoothly, I uninstalled 7.2.2. If I have the time next week to try it out on the older project I will but time is not looking good next week 🙂
So with all that, I’m not sure how to attack this for next time. It is very disheartening to be on edge every time I hit my spacebar to playback a sequence for clients in the bay with me. Eeeesh.
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Thanks guys.
Chris – when you say it shouldn’t be going below -22, do you mean lower like -25 or lower meaning like -18?
This is what mine looks like right now for this 1 minute spot. I saw the peak light turn red for one quick blip but only that one very quick moment. How does this look – would this be broadcast legal and at the same time, I certainly don’t want it to be a lot lower than the broadcast…
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Thank you so much for your response – then perhaps it’s a CPU upgrade I should be eying since the real benefit to getting a 2013 Mac Pro is TB2 which I don’t really foresee myself needing over an eSata or USB3 raid which would cut it 99.9% of the time. I could upgrade to a 12 core 3.06Ghz setup in my tower for around $1,750 installed with a geekbench score of 28,000. Should that be enough grunt to playback R3D 4K at full res with my gtx 780? Or perhaps at that pricepoint, it’d make more sense to look around for a used RedRocket ~$2k
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
I read that as well, I think in the NAB announcement – could be awesome but also gives me pause to having just purchased a GTX 780. Hopefully they don’t exclude that card but with how powerful the 780 is, I doubt they would.
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
UPDATE – when I drop MB Mojo onto the R3D clip in a 4k R3D timeline, the timeline goes from yellow to red but it still plays back without dropping frames and scrubs perfectly so I don’t THINK I’m running at the very limit of my tower but I must be close. However while I can change mojo settings in real time on say native 5D footage, when I change parameters of Mojo on the R3D clip while it’s playing back in real time, it does video stutter just for a second to make the change. Finally though, MB Looks is choppy on native R3D 4k files unless I drop down to 1/8 res. Interesting. Still for anything other than a concert w/ multiple streams of video, this seems to be plenty powerful for a native R3D 4k project…
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com -
Hi Shane – click 64bit Multicore since Mavericks is 64 bit and the Mac Pro is a multicore system (and programs like Premiere use multicores). My 2009 2.93 is the 8th fastest mac available per this list – 17k is the score and fares better than the 4 core trashcan. What am I missing here?
I downloaded a 4K R3D test file to see how my system would handle it playing off my internal 3 year old SSD. It will not scrub or play back smoothly at full res or 1/2 but at 1/4, it responds like a ProRes 1080 file, all scrubbing is as responsive as it could possibly be and playback is perfect. The bar above the clip in the timeline is always yellow.
So now the big question is – considering there’s a yellow bar, does that mean that my system (2.93 octo, 32gb ram, GTX780) can handle the processor side that’s required of 4K native R3D files but my current drive speed is the bottleneck to getting full res playback? Since 1080 is exactly 1/4 of 4k and I have three 1080 monitors, will I even see any degradation of quality if I’m always playing back 4K at 1/4 res in Premiere on 1080 monitors?
Thanks all…
EDITOR
Features : Television : Commercial
http://www.BryanRobertsEditor.com
