Welcome to our community

Be a part of something great, join today!

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 :)

CS6 6.02 update is crazy buggy???

Mike Smith said:
Wes Howell,

Have PM'd you about a non-Red issue related to the 6.0.2 update.
Click to expand...
Having said that, a project consisting of .r3d files has a red timeline in 6.0.2 while it has a yellow one in 6.0.1 in Windows 7 x64. I have not noticed any appreciable difference in performance between the two, but obviously there is a difference that also affects Red files.
 
Mike, did you happen to have your CUDA .txt file hacked so you could use CUDA with a non-supported card? If so, that's why you see the RED bar. Thank for the info in your PM, I am following up on it.

Best,
Wes

Mike Smith said:
Having said that, a project consisting of .r3d files has a red timeline in 6.0.2 while it has a yellow one in 6.0.1 in Windows 7 x64. I have not noticed any appreciable difference in performance between the two, but obviously there is a difference that also affects Red files.
Click to expand...
 
Hi Wes,

Yes, I have done the "hack". But please note that 6.0.1 did not display a red bar - with exactly the same Red project. So Adobe would have had to have changed Premiere in 6.0.2 to not give a yellow bar if a non-listed card is installed. I hope Adobe is not going to get all "police-like" about this. I totally understand Adobe not wanting to have to test every NVidia CUDA GPU out there and approve it. But I think it was totally reasonable for Adobe to allow us to use a non-tested CUDA card if we're willing to live with the hack and no official support. I'm currently using a GTX 260 and it works great. Granted, it probably can't handle as many accelerated effects as a Quadro 4000 or whatever, but it does quite well considering its cost. I intend to upgrade, but would hate to be forced to because of an update to CS6. I want to upgrade in a planned way.

Having said all that, and to be fair, other than the red bar in the timeline, I see no obvious differences yet with Red footage although I'm just getting started with the update. Just the HDV stuff I PM'd you about which did not concern the GPU but was broken in software only acceleration also.
 
F*ck. ppro 6.0.2 started doing weird things. Imported the newest cuda driver, reinstalled the red importers, but now my project stalls with a white screen after a couple of things done. When I hit play I only get audio, nothing else but a white screen. I save the project in order not to lose what I had done, after that I have to force stop ppro.
 
Hey Mike,

I don't think I was clear, but I meant to say that the update probably overwrote your cuda hack - hence the red bar.
You could definitely re-edit the text tile - (or just delete the file altogether)
Best,
Wes
 
Wes Howell said:
Hey Mike,

I don't think I was clear, but I meant to say that the update probably overwrote your cuda hack - hence the red bar.
You could definitely re-edit the text tile - (or just delete the file altogether)
Best,
Wes
Click to expand...

Wes, deleting the text file allows all CUDA cards to work?
 
I can't believe I hadn't seen this thread until now. I Just did the update on a Retina MacBook Pro and I'm having crashes and a lot of lagging problems. If I import a prores 444 animation on top of my RED footage my timeline preview window either freezes or goes completely black. If I switch the codec PPro gets so bogged down that it takes about 1min to move the playhead in the sequence. This is terrible. I'm anxiously awaiting the .03 release...
 
Wes Howell said:
Hey Mike,

I don't think I was clear, but I meant to say that the update probably overwrote your cuda hack - hence the red bar.
You could definitely re-edit the text tile - (or just delete the file altogether)
Best,
Wes
Click to expand...
Hi Wes,

Ah good. I'm glad Adobe are not going the "police" route. ;-) (I could see no reason why you would since I've bought both Adobe and NVidia products.)

Actually I did redo the text file so it's rather puzzling that I still had a red bar. I can recheck at some point to make sure I'm not losing it, but I ended up reverting to 6.0.1 for now and reinstalling the Epic plug-in and re-editing the text file. So I'm happy for now. I'll have another go with 6.0.2 when your tech guys have had time to looking into my HDV/Cineform problems mentioned in my PM (since that part wasn't Red-related).

I also would like to know - are you saying that merely deleting the text file allows all cards? Not that modifying it is a big deal of course. Just curious.

Thanks Wes.
 
Win7/64 GTX480, Cuda 5.0 enabled

Premiere CS6.0.1:
Removed cuda_supported.txt and GPU is enabled.
Removed GTX480 from the file and put it back; GPU disabled.
Removed the file again and GPU is enabled.

After Effects:
Removed raytracer_supported_cards.txt; Cuda disabled
Replaced it with GTX480; Cuda enabled.
 
Cory, you aren't running 6.02?
 
T'anks. Look forward to your comparison between .01 and .02 in the other thread.
 
I am running Cs 6.01 on Mac pro with hacked Nvidia 470
Can I update to 6.02 without loosing ability to use Cuda?
or its better to stay with 6.01?

Thanks
 
Wes, I plan on running a preview version of Windows 8 as a test of the OS. Will CS6 Premiere and/or After Effects work on that OS yet? Also, Will CS6 work on a Windows Home Server OS? If so, will it work as well as on a regular Windows OS?
 
I'm getting 10sec beachballs every time I interact with an Epic file in After Effect CS6. I just tried turning off Rocket usage in the Interpret Footage->More Info dialog. Now I can't see the shots at all - even if I turn the option back on. Rebooting doesn't fix the issue either.

About to try rolling back to 6.0 (from 6.02). I'm running a MacPro 5,1 10.8.1 with a Quadro 4000 and a single RedRocket card. CUDA version 5.0.37. Rocket card is on latest driver and firmware.

Shots are mostly 5K 2:1. This same workflow worked a charm in CS5.5. Would love to get it running smoothly in CS6.

*EDIT* Just finished rollback to AE 11.0 and reinstall of Labs plugin. Issue still remains - cannot see imported Epic shots either in Project window or timeline.
 
Elsie N said:
Wes, I plan on running a preview version of Windows 8 as a test of the OS. Will CS6 Premiere and/or After Effects work on that OS yet? Also, Will CS6 work on a Windows Home Server OS? If so, will it work as well as on a regular Windows OS?
Click to expand...

I strongly suggest you wait a while before switching to Win 7. Whats your rush? Win 7 works fine with all current apps and drivers I am running.

If you insist on living on the bleeding edge of technology, don't be surprised when you have to deal with the consequences. :nono:
 
Happy with my results today. I am using 6.0.2 on the rMBP 10.8.2 and it appears to be working since I updated the new rocket update. The only way I figured how to get fast exports with this set up is to match clip settings and export setting to match seq settings. On a 2 min clip its taking 4 min to export (5K) so half real time export. Although it defaults my export to 1920x1080 when I select the "match seq settings" option even though my source is a 5k seq...I would like to be able to export 5k if I can. I am getting real time playback at 1/2 resolution. These half results are to be expected as the thunderbolt is the bottleneck here. This was a 5k 2:1 video. Will post more more as I Am really trying to hammer down this workflow.
 
You must log in or register to reply here.
Back
Top