|
|
08-04-2012, 03:00 PM
I'm on the trial right now and as it stands, I am not convinced this program is as responsive as I like. There seems to be a delay when using the timeline and mouse clicks. The pointer tool (V) seems to be a combo of a pointer/trim tool and it's annoying when trying to grab small clips and move around video layers.
Editing R3d native is awesome, maybe that's causing the lag?
Mac Pro 8 core 2.93, 48 GB ram, GTX 285 card with 1GB Ram.
08-04-2012, 08:09 PM
Core i7 960, GTX 480, 12GB ram, SSD and RAID storage, Win7/64: no lag. Have you the latest nvidia drivers and enabled cuda for PPro/AE? It's not automatic. Have you tried HD or SD footage to demonstrate the interface responsiveness independent of hundred-MB/sec footage?
08-04-2012, 09:31 PM
HP Z820 / 64GB ram / GTX 570 / PRO DQg2 16TB raid array / Win 7-64.Originally Posted by Cory Petkovsek
No lag.
08-04-2012, 11:16 PM
Just R3D's right now and I have the latest graphic drivers and CUDA drivers. If my CPU gives me 1/2 res playback and the GPU does 1/4 res, the no brainier is to stick with the CPU. There are probably tasks the GPU can handle better but just previewing a clip from the bin this is what I know from testing so far.
Supposedly the GPU is supposed to be faster, I'll figure it out in time, thanks for your input. Editing directly off the R3D is the way, the truth, the light... On that alone what other NLE competes with CS6? FCP 7, I'll miss you.
08-05-2012, 01:29 PM
Vegas on Windows used to be superior to Premiere in my opinion. I could edit 4k natively on a pentium 4 w/ 2GB RAM in real time (at 1/4 res). The performance and timeline interface are still superior to any NLE I've seen and is excellent for short form. However with CS6, Premiere's feature set and implementation are finally better than vegas in so many other ways that I feel it is superior in spite of the timeline and performance handicap. I feel working in FCP7 is horrific and clunky compared to either. And FCPX, well....
Edit: Also we seem to be talking about the same thing in two threads now. This thread is about PPro lagging on you, the other about CPU/GPU. PPro CS6 isn't laggy. If you're only using R3Ds to test and you're doing so in too high of a resolution, then yes it will lag. Turn down the R3D resolution until it no longer lags and it should be quite adequate for you. If you want to edit at higher resolution, get a rocket or two.
Peace.
Cory
Last edited by Cory Petkovsek; 08-05-2012 at 01:42 PM.
08-05-2012, 01:37 PM
which version of OSX? just upgraded to 10.7.4 lots faster than 10.6.8
cheers,
Joost
08-05-2012, 06:35 PM
Still rocking 10.6.8 for stability.
08-05-2012, 06:43 PM
Rocket cards can't even do 5kFF in FULL res. I've debated this for a while but it's investing $5k in old tech IMO.
Interestingly enough Vegas timeline interface is superior to PPro. Maybe it's not "lag" but I am sure the reason you like the Vegas interface more is because of fluidity, resulting in you being able to work faster. My goal is to work at the speed of my skill and talent with the software working as an extension of me.
More training needed now, it will be interesting to see if I feel the same way a few months down the line.
From this discussion and from what I've read, I think we agree. The Premier timeline could be better.
ADOBE, are you listening? :) Love the native editing of R3D, keep up the good work.
08-06-2012, 08:19 PM
If you guys have feature requests - especially about things like how clips are selected... or requests about how the selection tool works - please file a feature request.
I do not see many feature requests from RED users very often. (I do monitor the feature requests as an employee of Adobe Systems)
If there are specific slowdowns that I can help you nail down, I would be happy to.
Even on 1 or 2 year old workstations, (with Quadro cards / 8 cores with 16GB or RAM or so) I do not find Premiere's interface laggy. I shoot on my Epic and edit regularly (on a couple laptops as well)
Unfortunately, I have seen more issues with the GTX285 than I'd like. From what I understand, there are different manufacturers of that card and even the amount of VRAM can vary. Some have good luck wit h the card and others have had big problems. The fact that you get better playback with CUDA turned off has me a bit concerned. I wouldn't expect this to be the case - I'd expect it to be the same.
Wes Howell
Adobe Systems
08-06-2012, 10:51 PM
Wes - how is VRAM used by Adobe?
And then there's the issue with shared VRAM on a dual GPU card. Is anything in the works for dealing with that?
Are you considering adding support for multiple GPUs on separate cards or multiple GPUs on the same card?
Ideally, I'd like to be able to add many cards, and have this off-load a lot from the CPU.
If you're attending SIGGRAPH, Eyeon Fusion will be exhibiting at nVidia's booth, and they have taken the approach of supporting multiple GPU cards. You're a larger company, so I'd expect that if they can pull it off, you certainly could if you wanted to.
I realize that GPU debayering is not included in RED's API (like it is in ARRI's) so there's nothing you can do about that, but ... RED may build this into the API at a future date.
| « Previous Thread | Next Thread » |
