Speedgrade very slow on GPU acceleration

My system has an nvidia gtx 590.
I run triple monitors so i need both GPu's (590 is a dual card FYI)
When running speedgrade in GPU acceleration even at 1/4 rez the video is maybe 10-12 fps
on software only it plays back realtime at full rez...
I am assuming this is a multiple GPU issue?
any way to fix this?

I appear to have solved this....will post for those searching in the future...
I was using speedgrade in dual monitor mode
the Desktop interface monitor was on GPU 2 while the secondary output was on GPU 1.......speedgrade didn't like that
when I switched both desktop and secondary to GPU 1...everything worked fine. Can now playback at full rez on gpu acceleration

Similar Messages

Lightroom slower when GPU acceleration is enabled

My graphics card is OpenGL compatible and it is shown in the preferences under performance.
When the GPU setting is turned on my develop module is extremely slow. Turning it off is faster and more like LR 5 performance.
All the hype about GPU acceleration and in reality is slows me down.
I've also noticed then if you have an image open and then open the preferences windows and toggle the GPU setting on and off, the image changes.
When I say changes, I mean the image becomes lighter or darker as if the exposure or whites/blacks is being changed.

I agree with Adamnz. I have a slightly older system but using CC 6 is like going back to the early releases of 5.x when the clone tool was jerking around the screen.
Painting with a brush and the mask showing makes the lag time visible.
Jerky tool movements... like trying to paint with Parkinson's.
Screen blackouts while refreshing images.
Slow screen refreshes between images.
CPU usage slightly higher (60%) with GPU enabled
But since this version created a "New and Improved" catalog I can't (i don't think) go back to 5.x...
BTW, I have been waiting for a call back from support for an hour when the stated call back time was 25 to 30 minutes... Not Good.
Here are my specs in case Adobe is listening....
Lightroom version: CC 2015.0.1 [ 1018573 ]
License: Creative Cloud
Operating system: Windows 8.1 Business Edition
Version: 6.3 [9600]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.3 GHz
Built-in memory: 16366.4 MB
Real memory available to Lightroom: 16366.4 MB
Real memory used by Lightroom: 3261.9 MB (19.9%)
Virtual memory used by Lightroom: 3324.1 MB
Memory cache size: 1469.4 MB
Maximum thread count used by Camera Raw: 4
Camera Raw SIMD optimization: SSE2,AVX
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Graphics Processor Info:
GeForce GTX 560 Ti/PCIe/SSE2
Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 350.12
Renderer: GeForce GTX 560 Ti/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler
Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: D:\Pictures\Lightroom\Lightroom Catalog.lrcat
Settings Folder: C:\Users\Dim\AppData\Roaming\Adobe\Lightroom
Installed Plugins:
1) Behance
2) Canon Tether Plugin
3) DxO Optics Pro 9
4) DxO Optics Pro 9 Importer
5) Facebook
6) Flickr
7) Leica Tether Plugin
8) Nikon Tether Plugin
Config.lua flags: None
Updated Toolkit: Adobe Camera Raw 9.0 for Lightroom 6.0 (build 1014445)
Updated Toolkit: Book Module 6.0 (build 1014445)
Updated Toolkit: Develop Module 6.0 (build 1014445)
Updated Toolkit: Import Module 6.0 (build 1014445)
Updated Toolkit: Library Module 6.0 (build 1014445)
Updated Toolkit: Map Module 6.0 (build 1014445)
Updated Toolkit: Monitor Module 6.0 (build 1014445)
Updated Toolkit: Print Module 6.0 (build 1014445)
Updated Toolkit: Slideshow Module 6.0 (build 1014445)
Updated Toolkit: Web Module 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.AgNetClient 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.AgWFBridge 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.Headlights 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.LibraryToolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.MultiMonitorToolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.archiving_toolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.bridgetalk 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.catalogconverters 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.cef_toolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.coretech_toolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.curculio 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.discburning 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.email 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.export 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.ftpclient 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.help 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.iac 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.imageanalysis 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.layout_module_shared 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.pdf_toolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.sdk 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.sec 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.socket 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.store_provider 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.substrate 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.ui 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.video_toolkit 6.0 (build 1014445)
Updated Toolkit: com.adobe.ag.xml 6.0 (build 1014445)
Updated Toolkit: com.adobe.wichitafoundation 6.0 (build 1014445)
Adapter #1: Vendor : 10de
D

AE CC ram previews very slow - no GPU support? Newbie trying to become not newbie, falling at first hurdle...

Hello. I'm currently trialling After Effects CC though Adobe Cloud. But I've hit a snag immediately.
I have an HD video edit in Premiere Pro which I want to dynamically import into AE to work on some bits.... I have imported the project file into AE, it seems to open just fine but the playback is intensely slow!
I have an uncertified GPU - a Nvidia Geforce gtx 460 - too old? I was expecting it to help out a bit, I'm not doing anything too badass, just colour correcting a bit of HD footage.
My processor is an i5 3.4ghz 4 core.
Perhaps I'm missing something fundamental here!? Please tell me what I'm completely failing to grasp
Thank you for your time,
Tony

Yup -- you're misssing a very basic item: AE doesn't work like Premiere Pro. It's not anything like PP, and it doesn't behave like it.
One way is the method you need to play video. Space bars just don't work. You need to do a RAM Preview -- hit the zero key on the numeric keypad, let AE render the frames it can, and then it plays them back as fast as it can.

GPU acceleration is grayed out in Premiere and AE, but not in Media Encoder. However, rendering is slow in all 3 programs.

It worked fine in CS6.
Now, everytime I open a project (Pr or Ae) I get the message: This project was last used with GPU Accelerated rendering. This happens with all projects, even with those that I created in Pr/Ae CC, with GPU Accelerated rendering already disabled.
In Media Encoder, the GPU Acceleration is not grayed out, but still if I render a premiere sequence or an ae comp via ME, its very very slow. (takes 5 hours for a video that took 20 mins in CS6)
Any thoughts?
Thanks, Daniel

I think I found the problem. On the website you linked, it says:
The following notebooks are not compatible with this tool:
Notebooks equipped with switchable graphics
Toshiba® notebooks
Sony® VAIO® notebooks
Panasonic® notebooks
And I have a Sony VAIO.
When searching for drivers, I only found sites like these: AMD Radeon HD 7650M drivers
Are these legit?

Adding GPU Accelerated Cuda Effects is suddenly very laggy?

Hello Adobe Experts,
I am appealing for some help with an issue that has bugged me for a little while. The best way to explain it is to show you the problem in a short 4 minute video which I will post below for those who have the time to take a look. Failing that my description is beneath the video.
Essentially, I upgraded to Premiere Pro CS6 from CS5.5 and discovered GPU acceleration. Wow! I subsequently was due to upgrade my iMac and bring in the specs to make the most of this technology, especially within colour correcting and grading. The new machine we got is a 2012 Mac Pro 12 core (2 x 6 cores 2.4Ghz) with 32 GB Ram and a Nvidia Quadro 4000 for Mac (2GB). It also has an SSD drive as the OS boot and applications drive so hoping that things would be super quick.
For a time they were, I can remember adding the Fast Color Corrector effect to a video clip and dragging the wheel around and everything would move in realtime, the program monitor was updating as I moved the mouse within the colur wheel. It was smooth and silky which I just loved as it meant that colour correction/grading would be now very easy to accurately dial in a look quickly and then move to the next clip. Plus no need to render afterwards either, hooray!
Then recently, and I am not sure what has caused this, it stopped working as well?!? I still don't have to render the clip after adding the effect or making a change to the parameters, however the process of making the change has become slow, unresponsive, laggy, delayed, laboured or any other similar adjectives. Now when I drag the mouse in the colour wheel the update happens in delayed steps and it is certainly anything from smooth and silky anymore. The problem with this is that it is very hard to accurately and quickly move the parameters around and make those fine adjustments which in turn slows down the process greatly.
I am really keen to know the following:
Does anyone else with a similar system have these issues?
Is this just how it is? (Trouble is I remember it being much faster and more responsive. Also I watched Maxim Jago at a workshop and he didn't seem to struggle with these issues when showing off GPU acceleration and adjusting effect parameters, even during playback)
Is it a hardware issue? Does my GPU need to be faster or is it not being correctly allocated to Premiere Pro?
Is it a software issue? Is it something that has come about in more recent versions of Premiere Pro?
How can I go about resolving this issue?
So far I have tried a fair few things like resetting preferences, ensuring the GPU acceleration in the 'Memory' preferences tab is turned on, clearing media caches, removing and reinstalling Premiere Pro et cetera.
If any experts from the community can help or indeed anyone from Adobe can help me resolve this issue, or at least feed back thoughts and comments, then I would be so grateful.
Best wishes,
Alex

Hi Maxim and JFPhoton,
I'll try and come back to all those points:
To JFPhoton-
which version of PPro are you using......CCloud, or CS 6 ? - CC Latest version
is your RAID setup configured in RAID 0......what were test results for speed ? Three internal HDD 3TBs striped together for maximum throughput. Speed results =
To Maxim Jago-
Yes I have reset the preferences. I have also unisntalled Premiere and then reinstalled it. Also completely reinstalled my OS just in case.
Playback is running at full res and has been since I got the machine - never had an issue from the start and then all of a sudden..... meh!
I have three internal HDDs (3TB) striped together in raid for maximum throughput which are pretty quick (speedtest above). I did try to check this though by putting source content onto my boot drive which is an SSD and then trying to see if issue exists in this case which it does. I also tried transcoding to other codecs than h.264 and the problem is still present.
Yes there is a fair bit of software running in menu bar. Used to have iStats running which I have removed now and problem still persists. Others I wouldn't think should be taxking the GPU. Although I will try quitting out of everything none essential.
Definitely up to date on most recent version of PPro
The Quadro 4000 was superb once I first got it. As mentioned above, I could perorm all the edits to the mentioned effects with ease at full res whilst plyaing back and everything working fine! I just wonder however if the card may have developed a fault or need cleaning out of dust or something? (quite a lot of dust present when I last opened the side door). Is there a way to check this?
Same problem persists across different projects and codecs.
As I just mentioned to Maxim, I wonder if my GPU has developed a fault? The reason I say this is because sometimes my monitor doesn't come on correctly (just shows a black screen) and I have to turn on and off again. Also, sometimes within Premiere I have an issue where I resize a window and I get 'ghosting' of that window as I drag. Did also previously have an issue changing between colour correction workspace and editing workspace. The workspace simply wouldn;t change and everything was completely unresponsive. I just wondered if anyone knew a way to check the GPU without taking it out of the machine or indeed if this might be the cause of my problems?
Thank you so much for taking the time to respond. I really really appreciate it.
Best wishes

SpeedGrade render not using GPU, slow render speeds

atHi!
I'm grading a fan-made feature-length film situated in this really obscure place called Middle Earth, and I'm currently rendering the final output.
Rendering speed has been really slow all along, so I decided to check upon GPU usage with a nVidiaInspector. It shows that GPU usage is between 0-5%. I'm able to get GPU usage to spike by switching to Monitor view (and scrubbing in timeline) instead of Output view in SpeedGrade. I understand that SpeedGrade is supposed to be GPU-accelerated throughout (not counting frame decompression made by codecs?), and now it seems that my CPU is doing all the lifting. CPU usage is around 100% all the time.
Render speed varies between 0.7 FPS and 6 FPS, which is far less than I expected, as I got reasonably fluid real-time previews all along the timeline when grading. Most typical clips have two primaries, two secondaries and a vingette mask primary on top. Total render time for 1 h 50 min timeline is expected around 12 to 18 hours.
My source material is 25 FPS 1080p CineForm AVI.
My output format is CineForm in Quicktime container (as AVI output with CineForm coded is not supported at present time) with automatic color calibration on, no audio, alpha discarded. Framing options are not in use (Full image (no proxy), 1:1 pixel aspect ratio, same size as proxy), and rendering is happeing at Online Quality.
My machine's specs are:
- Intel i5 2400S quad-core
- 16 GB of DDR3 RAM
- nVidia MSI GeForce GTX 470 with 1280 MB memory
- Windows 7, 64-bit
- SpeedGrade 6.0.4x25
- GeForce 310.70 drivers
Any input is appreciated.

Maybe due to cineform quicktime? Try other codecs to see what render speed you get.
Regards,
Mark.
PS I am geetin slow renders to cineform quicktime files from other app's (Premiere, Media encoder...)

Multiple crashes fixed by turning off hardware and Flash acceleration; very slow now. Takes five seconds to exit and still listed as a running process

A workaround was suggested by a member of the community to turn off both hardware and Flash acceleration. It worked fine (no crashes since), but runs very slowly. In particular, takes five seconds to exit and is often still listed as a running process. Very slow in connecting to Web pages, and very slow loading them because of the graphics. Very slow in loading video. I expected slower responses, but this is REALLY slow. I'm running 64-bit Windows 7 and an Nvidia GE Force 7800 graphics card with all the drivers updated and the plugins for Firefox mostly set on "ask to activate". Should I expect this much reduction in performance when the workaround I mentioned was put into place? If so, it's half a loaf at best. The only thing questionable is that I have two Youtube downloaders that I am trying, but I made the assumption that these were only applied when you downloaded something from Youtube.

In case you are using "Clear history when Firefox closes": do not clear the Cookies
If you clear cookies then Firefox will also try to remove cookies created by plugins and that requires to start plugin-container processes that can slow down closing Firefox.
Instead let the cookies expire when Firefox is closed to make them session cookies.
*Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: Keep until: "I close Firefox"

Very slow (almost none) 3D Acceleration with current Nvidia driver

Hi,
I'm having a problem on my Vostro 1400 with Nvidia M8400GS graphics card. The thing is that I don't have 3D acceleration to run compiz or 3D games (Urban Terror). Well, I can run GLXgears and start up Urban Terror, but the performance in UT is very slow (unplayable) even in the main menu - the sound is laggin etc). Even if I run Xcompmgr, the performance is very bad. I have had this issue almost a year now under Arch and I haven't found any solution to this problem.
Currently I'm running Nvidia driver from the extra repo version 169.12-4.
I also have enabled nvidia-xconfig --composite option to my xorg.conf file.
Here is my xorg.conf file:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Thu Feb 14 18:20:37 PST 2008
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "record"
Load "extmod"
Load "xtrap"
Load "glx"
Load "freetype"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "ee"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
Option "Emulate3Buttons" "true"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "GeForce 8400M GS"
Option "NoLogo"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
If you have any idea or comment about my problem, please let me know.
Cheers,
Verner

@ OP
You might wanna try tuning your xorg setup a bit as is described on the wiki http://wiki.archlinux.org/index.php/Beg … Fxorg.conf , and just under the section on xorg there is a bit of more info on the nvidia or ati specific stuff.
Is there a reason you are not specifying the default depth portion?
eg:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Or the modes portion?
eg:
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
There's also more detailed info on the wiki about xorg http://wiki.archlinux.org/index.php/Xorg and nividia http://wiki.archlinux.org/index.php/NVIDIA
Although, some of those nvidia specific options can lower your fps, I tried some of them and then removed them as they killed my opengl performance in 3d games, only "Option" I added and kept was the NoLogo one.
Hope something there helps, always has for me
wiki wiki wiki wiki wiki wiki wiki wiki wiki wiki mushroom mushroom
Last edited by RabidWolf (2008-06-20 21:23:38)

Can SpeedGrade use GPU Acceleration in New Mac Pro?

Good afternoon, I would like to know if Adobe SpeedGrade is able to take advantage of GPU acceleration AMD FirePro D500 installed in the brand new Mac Pro. Thanks in advance for your reply.
Message was edited by: Kevin Monahan
Reason: More searchable title

Supported GPU technologies (Mac):
- AMD/nVidia OpenCL for direct link in MacOS 10.8.5 and higher
- OpenGL for SG native
Supported GPU technologies (Win):
- AMD OpenCL, nVidia Cuda for direct link in Win7,Win8, Win8.1
- OpenGL for SG native
Note: Although SG not utilises two GPU's, it should run fine on your new Mac Pro and use OpenCL for acceleration

Preview slower with hardware GPU acceleration enabled than software only?

Sorry if this had been asked before.
But somehow my preview/playback was slower and choppy once I enable the hardware GPU acceleration(I mean I select the 'mercury playback engine gpu acceleration' under Project-Settings-General')
I followed the following tips to enable my graphic card, (thanks David)
http://www.studio1productions.com/Articles/PremiereCS5.htm
I was working on a clip of approx 3 mins long with majority of the footage(1920 and 720) from a DSLR, some 1920 clips from gopro hd2 and some 1440 clips from a P&S camera(scale to 1920 to match the sequence setting). main effects applied (magic bullet looks).
Before I enabled my graphic card and selected it from the project setting, the preview was ok, nearly smooth all the way except some sections with dynamic links, but once I turn it on, the preview became ridiculously choppy, I couldn't believe my eyes, so I turned it off (select mercury playback engine software only), did playback again, it became much smoother!(or just as smooth as it was when it was under that setting, it's just that comparison gave me a bad impression of my hardware gpu acceleration).
btw: I'm running on a low spec laptop
Core™ i7-2670QM 2.2GHz turbo to 3.1GHZ
8GB DDR3 memory
NVIDIA GeForce 555M 1GB graphics
750G HDD(I partition to 150G system drive and 600G media drive) 5400RPM (I know, it's slow)
currently have about 80G and 400G empty space on two drives respectively.
15.6” HD display (max resolution 1366x768)
I know the machine is not a proper workstation to work with CS6, but the hardware gpu acceleration was slower than the software only gpu acceleration was beyond my understanding, not a minor difference we are talking about, it was much much slower!
Have I done something wrong?
Any tips would be appreciated.

Here's my guess.
MB Looks runs on the GPU at all times, though not in the same way as Adobe's 'accelerated' effects. With CUDA off, the graphics card was free to process the Looks effects at full speed. With CUDA on, PP took some of those resources and Looks processed slower.
Remove Looks and replace it with PP's native accelerated effects and you'll see what all the hoopla is about.

ATI R200 - very slow 3D acceleration

Hello!
I have a problem - 3D acceleration is very slow. I'm using ATI Radeon 9200. glxgears returns about 730 FPS and xbmc runs terribly slow. Arch was upgraded yesterday, KMS is disabled, I don't use Compiz, xorg.conf is deleted.
glxinfo - https://gist.github.com/9f2eeaa98a25cc4d0fe6
dmesg - https://gist.github.com/5011c3baef5b9672fba6
messages.log - https://gist.github.com/b323b3a27e70d4a47d4b
Please, help me.
Last edited by pezzy (2010-03-10 20:55:56)

I have same problem with Radeon 9200 PRO (RV280). Even basic 3D games aren't playable becouse they are too slow (for example teeworlds).
xorg.conf
Section "Module"
Load "glx"
Load "dri"
Load "drm"
EndSection
Section "Device"
Identifier "Radeon 9200" # your alias
Driver "radeon"
Option "AccelMethod" "XAA"
Option "AGPMode" "8"
Option "ColorTiling" "on"
Endsection
Section "DRI"
Group "video"
Mode 0666
EndSection
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 (RV280 5960) 20090101 AGP 8x x86/MMX/SSE2 TCL
OpenGL version string: 1.3 Mesa 7.7
OpenGL extensions:
GL_ARB_draw_buffers, GL_ARB_imaging, GL_ARB_multisample,
GL_ARB_multitexture, GL_ARB_point_parameters, GL_ARB_point_sprite,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_histogram,
GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil,
GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_polygon_offset,
GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp,
GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array,
GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_ATI_fragment_shader, GL_IBM_multimode_draw_arrays,
GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat,
GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent,
GL_NV_packed_depth_stencil, GL_NV_texture_rectangle,
GL_NV_texgen_reflection, GL_OES_read_format, GL_SGI_color_matrix,
GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays
8 GLX Visuals
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
0x21 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x22 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x71 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x72 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x73 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x74 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x75 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x68 32 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 Ncon
8 GLXFBConfigs:
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
0x69 0 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x6a 0 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x6b 0 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x6c 0 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x6d 0 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x6e 0 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x6f 0 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x70 0 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow

IMAC's Top graphics card frustration - Cheap and no support for Adobe Mercury Playpack Engine GPU Acceleration?

If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
Please, if you have a solution for me, let me know. Otherwise I find it pretty frustrating that I purchased a top-end iMAC, fully maxed-out in every way possible, and that the iMac doesn't support Adobe Premiere's Mercury Playback Engine GPU acceleration. Also, an old USB 2.0 Hub and thus the built-in SD card reader is slow. If you have SD cards with 95MB/s Transfer, Read and Write speeds, the iMAC will only transfer at around 30MB/s if you're lucky. Technically 480Mbs which is around 50MB/s but I haven't seen those speeds.
I figured this could at least be circumvented with a Thunderbolt SD card reader or a Thunderbolt to USB 3.0 adapter but of course no such thing exists.
Well, nothing with a reasonable price tag. This all might seem trivial to some but when you're uploading 24 hours of HD video footage from a 128GB SDXC card, the speed makes a big difference.
And come on, no BluRay support? Ridiculous. I get the politics of why but still, just ridiculous. It would be nice to be able to burn a BluRay to watch in my home theater system. There are other methods but BluRay is convenient and great for backing up large Video Files. Unfortunately BluRay looks like it's not going to make it. Maybe cable distribution companies will increase their Internet upload speeds one day and I can just store everything in the cloud and watch full length movies(that I've created) on Vimeo.
Anyways, I went and took a look at the hardware Apple stuffed inside my fancy (3.4 Ghz i7, 16GB 1333 DDR3, 2GB AMD 6970M, 256 GB SSD Internal and 2TB 7200 Internal) machine and it appears to be pretty middle of the range stuff. It's an iMAC, not a Mac Pro so why am I griping? Because my 2009 PC(which I tricked out over the last two years) is faster and does support the Mercury Playback Engine. I spent $2100 total on this PC which includes all my upgrades. I spent around $3300 on the iMAC. I feel ripped off.
Yes, I do love my iMAC on multiple levels but had I known my dated 2009 PC would render video projects faster, I would have gone with a MAC Pro or just a new PC. It seems that Mac is moving completely away from making high-end computers for niche markets(video editing) and focusing on their tiny laptops, IPADS and IPhones for the masses. Obviously smart from a capitalistic perspective(at present at least) but very frustrating for some.
I was actually told to purchase a MAC for video editing. I've been a PC guy for 15 years. I went with the iMAC because I had read many good things about it(probably just Apple propaganda) and also the MAC PRO was to be discontinued. Also the MAC Pro would have been triple the cost for what didn't seem like a whole lot more.
It's one's thing to prepackage a computer with inferior hardware(the iMAC I have is fast for most things and more than enough for 99% of the population) but to not allow us to pop open the computer and make a quit upgrade to the machine is what really makes me feel like I'm using a computer built for Grannies. I mean there is a reason my mother loves iMacs and Iphones. Amazing that I was able to upgrade my memory from 4 to 16GB but I've heard Apple has even done away with that. I get why they do it. Apple Warranty, Apple Care issues, Profit and World Domination: Apple wants a monopoly on everything.
Was great to see Adobe bounce back after the whole Flash/HTML5 thing and knock Final Cut Pro off the face of the Earth for good. People are still buying it b/c of the brand name but Final Cut is done. David Fincher used Adobe's Workflow for everything when he made The Girl with The Dragon Tattoo. Hollywood is making the shift and the world will follow. The Adobe Workflow has finally come together and there is just no way Apple can compete with Adobe Creative Cloud and an Engine that can just swap from Premiere to After Effects to Prelude to SpeedGrade to Photoshop to Story with speed for $29 bucks a month(or $49 for some). Apple better start supporting Adobe's Mercury Engine or they may have a problem. And if you're using Final Cut X, you're severely handicapping yourself. Problem is that people don't want to take the time to learn Adobe's products(steep learning curve for sure) which is where Apple's Granny software, and perhaps computers, comes in to play. Arnold Schwarzenegger once said "Milk is for babies, Real Men Drink Beer". I'm beginning to think that "Mac's are for Grannies, Real Men Use Adobe and PCs".
The major problem with Apple is you're forced to use Apple. Not sure but history has proven that people don't like to be forced into anything. Autocracies don't work. These systems eventually topple, even in the corporate world.
Amazon.com, now that's the company to emulate. What an amazing machine!
I've read that Apple may even discontinue the iMAC after 2013. Who knows?
If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
1) Graphcis Card - AMD Radeon HD 6970M 2048 MB (6990 would have been better or something from NVIDIA.
2) USB 2.0 Hub with only 480 Mb/sec
3) Seagate Baracude SATA I 7200 RPM drive with 3GB/s transfer rate and only a 32 GB Cach. It's ok. I would have expected at least a Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB or the Velociraptor at 10,000RPM.
4)APPLE SSD TS256C Flash Drive. As you can see, it doesn't stack up so well against other SSD Drive.
Just average. http://www.harddrivebenchmark.net/hdd_lookup.phphdd=APPLE+SSD+TS256C

Whining and ranting about how iMacs can't do this or iMacs/orMacs can't do that is not going to get you a lot of help here.
Your "I love my MAC" is typical of the ever ubiquitous PC whiner.
If your video work needs were that computer intensive and critical , you should've done some online research and you should have budgeted for a Mac Pro.
Mac Pros are completely expandable and upgradeable unlike the iMac.
Mac Pros have much more faster and more CPU cores than the iMac line.
iMac line is limited to CPUs with 8 cores. The Mac Pros, I believe, are up to 16 core CPUs, now.
The Mac Pros can have their GPU upgraded and you even add/expand to use specialty audio/video cards.
Mac Pros are the defacto standard for real video work.
iMacs, even the high end model, is not really designed to do really heavy and intensive video work.
iMacs do do video creation and editing. Just not on the level that is needed from a more "Pro" computer.
It seems to me you are asking your iMac to do more than it was originally designed for, in terms of professional video editing.
You get a lot more out of a Mac Pro than an iMac for any real serious video, CGI or animation work.
You just didn't want to spend that much cash on one.
iMacs are not user upgradeable or friendly to user upgrades at all!!!
If you purchased a Mac Pro, you could've had that better, faster HD, better faster SSDs.
That said, I can offer no real help to but because of the nature of your post and the fact you just simply annoyed me, I feel some advice and explanations are in order
First off, you picked Adobe video editing software suite as your video creation software on the Mac. It's no secret to long-time video content creators on the Mac that Adobe products, especially those for video creation and editing are very user unfriendly on the Mac. Even though Macs are supported from Adobe, Adobe for a long time has treated the Mac and Mac users as second class citizens.
Before purchasing and installing Adobe Premiere, did you even check Adobe's site for the preferred system hardware and software requirements? Hmmm?
This is why you should KNOW what software you are going to be running on a computer first then research what computer make and model will run said software.
That's why Apple has its own apps like Aoerture, Logic and Final Cut.
Despite your ignorance in this matter, Final Cut Pro X is alive and doing well, thank you, and using this software on your iMac would kick Adobe Premier in the you know whats.
Final Cut Pro X is a complete video solution for and completely designed around the Mac.
Why are you using USB 2.0 connections for video work when you have a perfectly good FireWire 800 connection.
In case you are not aware, FireWire 800 is called so because it has a max throughput of 800 Mbps.
Your 2011 iMac can take up to 32 GBs of RAM. Not just 16 GBs.
This changed when the 2010 model iMacs came out.
Blu-ray? I believe you can buy external Blu-ray writers that work with Mac using said FW800 connection.
So you cite one movie and one videographer using Adobe Premier for your premise that Final Cut is dead in Hollywood?
Your argument that Apple locks you into everything in their world can be countered by saying Windows and Windows PCs lock you into the Windows world. What's your point?
Apple is not discontinuing their computers platforms any time soon.
All you are regurgitating is rumor. Probably from all of the PC crowd.
iMacs and professional desktop Macs are not going anywhere.
Currently, Apple is the only desktop/laptop computer maker that is still making a profit on their Macs and increasing their market share percentages for the last 5 years during which the PC market has continually slumped/dropped in its market share.

Photoshop CS6 very very slow (Windows 7)

Hi, im desperate as ive run out of options i think. Photoshop CS6 behaves slow, very slow.
Even with no document open, right after launch it reacts with delay on any mouseclick, sometimes it takes
more than 20 seconds before a menu pops open after clicking. Painting paintbrushes are impossible slow.
Basically any action is dragged.
Its impossible to work like this. With all previous versions of PS i never encountered this.
Things i tried :
- turned off gpu acceleration (i read that gpu can cause performance issues, some ppl solved slowness by turning it off)
- updated latest nvidia drivers
- reinstalled photoshop
- tried to inspect photoshop processes with ProcessHacker, even when at 5% cpu it runs extremely slow
specs :
Windows 7
Nvidia GT545
1 terrabyte free scratch disk space (on C:)
8 gb ram
CPU i7 2600

Has it always run slow, or did this start recently?
What anti-virus are you using? Have you tried disabling it to see it that make a difference?
Are you working over a network?

CS4 very slow vs. CS3

I have been doing large layouts in photoshop for years for the film and advertising industry. I have recently started using cs4 and found it to be pretty much unusable when working with large layered files. I have followed several tutorials on increasing and optimizing speed, turning off acceleration, etc. I have checked my graphic card drivers and it is still a dinosaur compared to cs3 on my Nehalem macpro. I have also reproduced the same results on my older Harpertown macpro. Redraw, tweaking curves and drawing with the lasso are all very slow. I have two friends who have the same experience and downgraded back to cs3. I have one friend who claims it works fine on his xp64 system.
Are there any artists who really use this program on mac for serious work? -or have most people abandoned it and gone back to cs3? I have found cs4 to be pretty much unusable.
BTW, can somebody please update the curves tool??? It would be nice to zoom, have independent bezier handles, and also be able to invert curves like many other programs have been able to do for years. It is quite silly that photoshop has one of the most primitive curve tools in the industry.

robotpaper wrote:
Nope. I do a ton of maya, c4d and zbrush. I have had no issues with either of my nvidia cards (8800 and GT 120).
If you are saying CS4 doesnt support either of those cards that is rediculous [sic].
Ridiculous is not knowing how to spell ridiculous.
Hey, I'm just trying to help.
I don't see any "GT 120" on the list. The 8800GS and 8800GT are on the list, both with 512MB of VRAM.
I hope you're talking about two different machines. Photoshop does not support more than one card on a given machine, and two different video cards on the same machine spells crashville.
Apple's support for multiple or dual graphics cards seems to be very poor. Many users with two cards report all kinds of trouble.
http://kb2.adobe.com/cps/405/kb405711.html
This is a list of graphics display cards that were tested
by Adobe before release of Photoshop CS4. They are listed by operating
system, and with the amount of video RAM that was on the card during
testing.
Mac OS graphics display cards We tested the below cards on Mac OS 10.5.4 and 10.4.11.
The following cards were tested only on Mac OS 10.5.4: 8800GT, iMac 8800 GS, and 8600M.
MACTEL iMac 8800 GS 512 MB
      MACTEL 8800 GT 512 MB
      MACTEL Radeon x1900 512MB
      MACTEL nVidia Quadrofx 4500 512MB
      MACTEL nVidia 8600M 256MB
      PPC nVidia 7800 256MB
      MACTEL ATI HD 2600 MAC 256MB
      17" MACTEL iMac x1600 128MB
      Macbook Air intel GMA X3100
Q. Why can't Photoshop take advantage of more than one display card?
       A. When you move an image window between two monitors that are each on a separate display card, the GPU attached to the second monitor does not have access to the data necessary to accelerate drawing. The SLI and Crossfire technologies that use more than one GPU to speed up full-screen games will not work with Photoshop, because their use is limited by design to accelerate only full-screen games.
from: http://kb2.adobe.com/cps/404/kb404898.html
Finally:
25. Jun 10, 2009 10:55 PM in response to:                                     captainlang
Re: OpenGL & 3 or more monitors
Paul,
Dual video cards = crashes in all cases.
Matching Dual Video Cards = few occasional crashes.
Non-matching video cards = crashes consistently
I really don't think the GL features factor into it that much. It's the Apple video drivers. The OS simply is not well-designed for multiple video cards in a video-intense application. As I've posted, I run dual 8800 cards and still have about 2 crashes an 8 hour day. Crashes generally occur when doing the most rudimentary things, like dragging a layer between two documents. I simply save more often. The 11.0.1 update helped a bit, but not completely. And CS3 never crashed with dual 7300s installed.
from: http://forums.adobe.com/message/2030437#2030437

PP5.5 very slow on brand new iMac

I have seen a number of threads similar to this, but none have been helpful.
I purchased a brand new 21.5" iMac late last year.
Processor 2.8 GHz Intel Core i7
Memory 12 GB 1333 MHz DDR3
I installed CS5.5, and found it to be pretty slow. So I got some more RAM. I now hav 12GB of RAM. I saw an improvement, but it's still really slow. Premiere is the worst. When I press play, even on low-res video footage, it often takes a couple seconds to start playing.
I clicked Project Settings, and for Renderer, the "Mercury Playback Engine Software Only" option is grayed out.
I looked at some threads... and apparently I have to manually set a graphics card or something like that? I know nothing about that.
I have finally had enough of this. Very frusterating. I was sold in PP5.5's speed, and it has been extremely slow.
Any suggestions? Thanks!

Basically, there is nothing that you can do with that 2011 iMac. Upgrading to CS6 still would not have allowed you to enable GPU acceleration: OpenCL GPU acceleration only works if the GPU has 1GB or more dedicated RAM (and officially, CS6 for MacOS only supports Macbook Pros, not iMacs, with the HD 6750M or HD 6770M and 1GB or more dedicated graphics RAM for OpenCL GPU acceleration on AMD GPUs). Your iMac's GPU has only 512MB of dedicated RAM, as I mentioned. That's too little RAM to even allow the enabling of the GPU acceleration in CS6.
As for the addition of the Thunderbolt external hard drive, that would still gain some improvement in performance, especially since your iMac is bottlenecked by the use of only a single disk (the OS disk for absolutely everything). The iMac's internal hard drive uses a SATA interface like Windows PCs use - and a single SATA connection can only pass data in one direction at a time (this is what I meant by "half-duplex"); a block of transfers in one direction (either read or write) must be completed before any transfers start moving in the opposite direction. And most video editing tasks require simultaneous transfers in both directions on a disk interface (which a single SATA connection cannot perform; this is why we often needed two or more disks).

Speedgrade very slow on GPU acceleration

Similar Messages

Maybe you are looking for