Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

ADOBE PREMIERE 6 --- I HAVE NO WORDS ....

Good news for win7 people. I got CS6 to recognize the GTX 690 for the Mercury Playback Engine (cuda). So other cards that aren't listed may work too.

This motherboard is not working properly with the card and nVidia drivers keep crashing, but I'll try another motherboard later and see what happens.

edit: with one 690 card it's rock solid. Hope to try double 690's in the next few days with a different motherboard.


cs6690.jpg
 
Last edited:
Here is some interesting reading on the topic of Cuda/Mercury Playback in Premiere 5.5 / 6.0 with Nvidia cards. My hunch is that you might find something useful.

http://www.studio1productions.com/Articles/PremiereCS5-2.htm

____________________________________
Scarlet X # 1859 “Bettie Page”
“… preparing to ‘whip’ the competition …”

Zeiss Lenses:

CY 21/2.8
ZF 28/2.0
CY 35-70/3.4
CY 50/1.4
ZF100/2.0

Nikon Lenses:
G 14-24/2.8
G 24-70/2.8
D 80-200/2.8

Tokina Lenses:

11-16/2.8
 
Doubtful - more likely, the update overwrote any modifications you might have made to the card support text files.
 
I have an issue with the sound on my macbook 17 with the new importer. Can't read more than 6 sec on the timeline without loosing the sound. I am sad because RC3 and RG3 are so great... But if i want to still use Premiere, I have to downgrade the importer.


Olivier
 
i'm late to the party, but HOLY F*CK! really cool it plays 5K quite flawless on my 2008 macro, i can access all the metadata in PP, really cool! FCP7 really missed out here...really wish FCP 7 would have this. But props for adobe, really good work!
 
I will have no words when I order my new Mac Pro tomorrow. With my macbook pro 2011 i'm in hell with R3D.
 
Are you sure? They are not much of an update…
 
I was talking about MacPros (as you wrote), not Mac Book Pros …

The new MBPs are a good step forward, but I wonder about the CUDA power of the card – finally Nvidia again.
 
Trying to dig through this thread but if anyone can point out to me how to enable my rocket card in premier pro cs6. I am on a retina, with sonnet TB and rocket set up, i see the card in source settings but not seeing perfamnce increase i expected in the playback or render. Is there a switch i forgot to throw? I am also cutting real time 5k on a downscaled 1080 timeline. Cheers and thanks in advance.
 
I'm on CS5.5, has anybody noticed that enabling mercury playback engine works great (I have a gtx 580) for playback, but when you try to render or export you can sometimes get an 'error compiling movie'. Mine seems to happen on a certain clip every time I export.

Now I've looked online and Adobe suggest many reasons for this, including corrupted clips. However if disabled GPU acceleration, everything exports fine. If I re-enable mercury hardware acceleration I get the error again when I render. Also a company which I freelance for as exactly the same problem with their system. They have to disable GPU acceleration to perform a full export/render on most complicated timelines.

Is this a known issue, Adobe don't seem to say anything about this being the cause for the error. Is anyone else experiencing it?
 
C.H.Haskell said:
Trying to dig through this thread but if anyone can point out to me how to enable my rocket card in premier pro cs6. I am on a retina, with sonnet TB and rocket set up, i see the card in source settings but not seeing perfamnce increase i expected in the playback or render. Is there a switch i forgot to throw? I am also cutting real time 5k on a downscaled 1080 timeline. Cheers and thanks in advance.
Click to expand...

The rocket integration within CS6 hasn't been great or smooth for me either. I actually get smoother playback with GPU acceleration than with the RR. Even render times are about the same both with and without e rocket. Wes, from adobe, has been extremely helpful in trying to pinpoint what's going on, but suffice to say that RCX puts the rocket to best use and I only use the rocket for transcoding when and if needed. Provided that you have the little checkbox ticked under the source settings, that's really all you have to do.
 
Hi Karl,

There can be a huge difference depending on what card you're using for CUDA. ESPECIALLY if you're scaling 4k / 5k content. For example, I have seen less stability using non-approved cards or cards with only 1 GB of VRAM. The Quadro cards have been bulletproof and generally cards with 1.5 GB of VRAM are highly recommended if you're working with large RED files.

Feel free to let me know what cards you've been using.

Wes Howell
Adobe Systems
 
Chris McKechnie said:
The rocket integration within CS6 hasn't been great or smooth for me either. I actually get smoother playback with GPU acceleration than with the RR. Even render times are about the same both with and without e rocket. Wes, from adobe, has been extremely helpful in trying to pinpoint what's going on, but suffice to say that RCX puts the rocket to best use and I only use the rocket for transcoding when and if needed. Provided that you have the little checkbox ticked under the source settings, that's really all you have to do.
Click to expand...

Hi Chris,

It's worth mentioning that the Rocket isn't "Slow in general" In your case, part of the slowdown is related to a 4x lane routed through a PCI-express slot on a laptop. I wish I could have been more helpful in resolving these issues but I've had a heck of a time finding a mac laptop that even still uses PCI-Express slots. (As I am a remote empoyee) I do appreciate your willingness to log bugs and your other contributions.

Many are seeing incredible speed gains when using the Rocket internally or with a thunderbolt enclosure. I regularly export faster than realtime using my workstations (with GPU accelrated, scaling, filters and effects, etc)

C.H.Haskell, Can you try the same export with a native 4k, 5k Timeline? You should see much better speed / render improvements when working at native resolutions? Do you NEED to work in a 1080p timeilne? ie, are you mixing your RED footage with HD content? If not, I'd recommend editing at native resolution.

Keep us posted!

Wes
 
Thanks Wes, I was only using 1080 timeline cause I am delivering 1080 and was told to do so but now that I am rocket enabled I will try the 5k native and let you know. Cheers.
 
Wes Howell said:
Hi Karl,

There can be a huge difference depending on what card you're using for CUDA. ESPECIALLY if you're scaling 4k / 5k content. For example, I have seen less stability using non-approved cards or cards with only 1 GB of VRAM. The Quadro cards have been bulletproof and generally cards with 1.5 GB of VRAM are highly recommended if you're working with large RED files.

Feel free to let me know what cards you've been using.

Wes Howell
Adobe Systems
Click to expand...

Hi Wes

I actually have 2 cards in my system, a GTX 570 1.2GB and a GTX 580 1.5GB. I've tried to get Premiere to recognise the 580 and use that, but it seems to always default to using the 570. Even when I have gone into the cuda settings and told Premiere to use the 580 only, it still seems to use the card which is connected to the displays (570).....Still, It works fine for the most parts except for the rendering error.

The other system I use has a single GTX 580 1.5GB (which reports the same error on export) so I don't think it's a RAM issue.

Any other ideas? As a side note I'm not actually using Red footage with this project - its just a collection of SD mp4 files within a SD project. Is there any way to tell Premiere to use the 580 instead of the 570? I don't want to connect the 580 to my displays as I use it for 3D rendering and want to keep all the RAM free. As i say though, even the other system with a single 580 reports the same error on rendering/export.
 
Hi Karl,

We can definitely figure out what the failure on export is. However, I would need to know all of the specifics of the project.

Some of the info that is needed would be:

How large is the project? What types of source files are you using? What are the sequence settings? What kind of filters are using? Any 3rd party filters? Are you using the latest Nvidia drivers?

Also, could you try to export the first half of the project and then the 2nd in order to determine what part of the project is causing the failure?
Ideally, if you could condense the project to smaller size and then reproduce the failure, this would help us determine what is causing it and would also make it easier for me to get some assets so I could reproduce the issue on my end.

Lastly, did you try this with CS6? Maybe try a trial build?

Best,
Wes
 
You must log in or register to reply here.
Back
Top