Different GPU / Unterschiedliche GPU

hello
I use AE version CC 2014.2 /13.2.0.49
I have a GTX 980, which is not supported by Adobe CC.
Can I use a second graphics card, which I only render (GPU)?
The idea is: GTX 980 use for monitors.
The second video card (GTX 760) use only for AE rendering?
Is that possible?
GERMAN:
Hallo
Ich nutze AE Version CC 2014.2 /13.2.0.49
Ich besitze eine GTX 980, die nicht von Adobe CC unterstützt wird.
Kann ich eine zweite Grafikkarte einsetzen, mit der ich nur rendere (GPU)?
Die Idee ist: GTX 980 für Monitore nutzen.
Die zweite Grafikkarte (GTX 760) nur für AE rendering nutzen?
Geht das?

Solche Features müßten in die Applikation eingebaut sein und AE hat das einfach nicht. es wird immer die primäre Grafikkarte verwendet.
Mylenium

Similar Messages

Running two different res monitors - GPU requirements?

Colleagues,
I will be building a computer for PS CS4 still-photo work and have asked in an earlier thread about how widely current graphics cards support Photoshop's requirements. The answer was: almost every current PCI-e card will do so. Now I realize that I hope to run two monitors from the card I buy and all my research cannot come up (so far) with an answer.
I have a good 21" Viewsonic 2030b monitor for graphics professionals (OK, it's an LCD so I know it has limitations...) that runs native at 1600x1200. I also have a Gateway 24" that runs at 1900x1200. I'd like to calibrate the Viewsonic, display images on that, and reserve the Gateway for tool palettes plus other applications, etc. It would be an even bigger bonus if I could run the Gateway alone in portrait, as I do that often even now. Both would have to run from a DVI signal. VGA signal too "soft". So I know that the display card has to have two DVI-out connectors.
This capability would be worth extra cost over that of a low-end card. Perhaps it's no big deal, absolutely assumed - and that is why it's not mentioned in FAQ's, knowledgebases, and the like. Although I am partial to nVidia I would buy an ATI-equipped card to get this capability if that's what was required. I also know that I will probably have to give up one of the slots with a bulky card. I think that will be OK, as there do not seem to be a lot of demands on the slots these days with so much available through on-motherboard chipsets. (My last build was on a conservative Intel board circa late 2003 - no sound - and the on-board LAN chip went soon thereafter to a nearby lightning strike...! No IEEE 1294 at all and not enough USB, etc., etc. )
Thanks everyone, in advance, for comments.
jonathan7007

again, any card should be good enough just make sure that you get a card with either two DVI ports or with one DVI and a HDMI port+DVI converter.

Can I use Magma's EB1 to run an external GPU for GPU-computation?

Hi,
I'd like to run an Nvidia GTX 285 with my MacBook Pro (late 2008) for double-precision GPU-accelerated computation, not for any graphics output. I think the only way would be via ExpressCard. I've found a card from Magma: the board set for their EB1 unit which supplies an external PCIe x16 slot via ExpressCard/34. I would replace the 60W PSU with ~250W to power the 285. I would need the board set and my own enclosure because the retail EB1 can't fit the double-width 285, and can't power it. Magma says the EB1 has been tested with MacBook Pro's, but not explicitly for GPU processing.
The question is whether there's any particular reason to think the 285 wouldn't be found as a PCIe device using this setup? I'd be using CUDA for development, and it's supposed to be able to find multiple GPU's on your system. I know ExpressCard will only give me x1 bandwidth, but that's fine for my needs now.
Thanks for any thoughts!
Michael
Message was edited by: mgstauffer

Sorry, incorrect. There are no drivers for powerline adapters, just like there are no drivers for your router. They are essentially single port switches. Just plug them in and go. However, can they be used between a modem and the router? That I'm not sure of. I would think they may work since they are pass through devices and do not require an IP. Someone else may know.
Message Edited by sabretooth on 01-11-2009 09:50 PM

Disable GPU features / GPU Sniffer through install?

Hello!
New to Adobe and this community, apologizes in advance if placed in the wrong forum.
I am looking to deploy Photoshop CS6 in an enterprise environment. We have a number of clients which meet the requirements of the program, but do not have the video memory to utilize the graphics accelerated features. I've been asked to research disabling the GPU features (or the GPU sniffer) at the install process to avoid the user experience of the pop up. Is there a customization tool or have any users found a work around for this scenario? I have read the sticky here, and also came across a user submitted solution here which I thought might work but is not an option in our environment.
Challenge: GPU Sniffer pops up notice of disabled features when first run with new user on clients that do not meet GPU acceleration specs.
Goal: Avoid/remove pop up, either by customization of installation, of modification of preferences post install from centralized management.
Again, many thanks for taking a look and any feedback you can provide!

Thanks for the answer. I understand completely.
I apologize if I seemed forward for asking. I have perhaps an oversensitivity, as I once was at the mercy of a corporate IT department that was staffed by, shall we say, technically-challenged folks who made - without fail - penny-wise and pound-foolish decisions. I ended up cutting my engineering department off from them completely, and after outfitting my group with Really Great workstations 20 software engineers began putting out the work of 40. It's amazing what an investment in one's employees can net.
Something did actually dawn on me that could possibly be helpful... When I set up test systems here (I use virtual machines for a lot of testing), I have been successful in developing an initial set of Photoshop parameters, then just copying all the files and subfolders in the following folder. Voila, Photoshop comes up with the same setup as the source system.
C:\Users\NoelC\AppData\Roaming\Adobe\Adobe Photoshop CC\Adobe Photoshop CC Settings
Perhaps you could develop Photoshop settings that could then be copied to the target environments before Photoshop is run.
-Noel

Ac unity with nivida 880m gpu/upgrade gpu

Two questions I have the dominator pro with the 880 nvida gpu, will I be able to play ac unity? I dont have any problems with black flag? Also does anyone know where I can purchase the nivida 970/980 gpu?

If your game can handle Watch Dogs, then it should be ok. Refer to my Watch Dogs video for review.
http://www.youtube.com/watch?v=P6SluJMZY8w
My guess.......high?...

Qosmio X70-A - difference between nVidia and Toshiba GPU driver

Is there any difference between the nvidia display driver and the one packed by toshiba?
I've been using the one from toshiba but Geforce Experience is giving me a headache with warnings about a newer driver and toshiba doesn't seem to supply one.

Yes of course there is a difference between the nVidia GPU drivers (or any drivers provided by graphic card manufacturers) and drivers provided by Toshiba.
The GPU drivers from Toshiba driver page are modified and made for mobile usage.
Every notebook model supports different components (CPU, cooling modules, etc) and different design. Therefore the heat dissipation is always different.
The GPU driver provided by Toshiba supports some kind of GPU overheating protection and protects the graphic chip from damage. This means that GPU performance is controlled by the driver and in case the internal temperature would increase to critical level, the GPU performance would be decreased. Also the notebook shuts down automatically if temperature would be too high.

LR6: Mit GPU Beschleunigung falsche Ansicht in der Entwicklung

Hallo zusammen,
ich habe mit LR6 ein Problem im Entwicklungsmodus.
Wenn ich die GPU-Beschleunigung aktiviere verändert sich die Helligkeit und die Farbe des Bildes im Entwicklungsmodus.
Wechlse ich in die Bibliothek ist die Ansicht wieder korrekt.
Das ist bei allen Fotos so. Auch bei importierten JPGs.
Wenn ich im Entwicklungsmodus bin und dann ins Menü gehe und GPU an- und ausschalte, sehe ich im Hintergrung wie sich das Bild jeweils ändert.
Das heisst, dass die Berechnung des Bildes mit CPU und GPU unterschiedlich ist.
Es liegt auch nicht am Katalog. Ich habe das selbe Verhalten mit einem neuen Katalog und einem importierten RAW.
Ich verwende:
LR6 auf SSD
Windows 7 64Bit (aktueller Patchstand)
8GB Ram
Intel i7 2700
Geforce GTX 560 TI 1GB (aktueller Treiber)
Viele Grüße
View the message

Ja. Adobe Community: What is the best video card for my system?

2014 Macbook Pro Nvidia 750m GPU Kernel Panics

Hello everyone,
After a long battle w a Mac Pro and Davinci Resolve, I moved to a 2014 15.4 Macbook Pro Retina i7 2.7ghz with Nvidia 750m and Intel Iris (dual gfx). Any time I do anything strenuous, such as video editing or color correction, the laptop heats up to between 80 and 100c, the case becomes almost too hot to touch and it eventually kernel panics with the following, along always a GPU based panic. I just performed a PRAM reset w Apple Tech support, but that isnt helping the heat \ kernel panic issue. It occurs after mere minutes in Adobe Premiere Pro, Davinci Resolve, or anything else GPU accelerated. I already confirmed that auto switching was enabled, but I also disabled it to try without success.
Any suggestions? This laptop is 14 days old, so I now need to deal w repairs :/ Does this kernel panic indicate a GPU or GPU VRAM issue? I tested my system RAM with Rember and it passed, also passed Apple's basic HW test.
Huge thanks!
Jason
Anonymous UUID:       4C05B7D8-F112-8114-F9AA-367EA992A371
Mon Mar 30 19:43:16 2015
*** Panic Report ***
panic(cpu 4 caller 0xffffff7fa02b8f63): "GPU Panic: [<None>] 5 3 5f 1d 0 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00100c80: CFG 0x0fe910de 0x00100406 0xc0000000, BAR0 0x101000000 0xffffff821b809000 0x0e7290a2, D0, P0/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.8.6/src/AppleM uxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 4), Frame : Return Address
0xffffff820a4bb2d0 : 0xffffff801d92fe41
0xffffff820a4bb350 : 0xffffff7fa02b8f63
0xffffff820a4bb430 : 0xffffff7f9e655dd8
0xffffff820a4bb4f0 : 0xffffff7f9e720266
0xffffff820a4bb530 : 0xffffff7f9e9016d9
0xffffff820a4bb5a0 : 0xffffff7f9e901508
0xffffff820a4bb600 : 0xffffff7f9e89e26e
0xffffff820a4bb6a0 : 0xffffff7f9e89ab7e
0xffffff820a4bb740 : 0xffffff7f9e89a6c8
0xffffff820a4bb7a0 : 0xffffff7f9e76f31c
0xffffff820a4bb830 : 0xffffff7f9e94a826
0xffffff820a4bb8a0 : 0xffffff7f9e94078e
0xffffff820a4bb970 : 0xffffff7f9e940b57
0xffffff820a4bb9e0 : 0xffffff7f9e96ec9b
0xffffff820a4bba60 : 0xffffff7f9e793efa
0xffffff820a4bbbb0 : 0xffffff7f9e793801
0xffffff820a4bbcc0 : 0xffffff7f9e797369
0xffffff820a4bbd10 : 0xffffff7f9e96e8ff
0xffffff820a4bbd80 : 0xffffff7f9e796f91
0xffffff820a4bbe00 : 0xffffff7f9e63e5b2
0xffffff820a4bbec0 : 0xffffff7f9e60bb65
0xffffff820a4bbf00 : 0xffffff801d9624f9
0xffffff820a4bbfb0 : 0xffffff801da14dd7
      Kernel Extensions in backtrace:
         com.apple.driver.AppleMuxControl(3.8.6)[BE610379-FAEA-3E8F-B6AF-F92B70B3C5CD]@0 xffffff7fa02aa000->0xffffff7fa02bdfff
            dependency: com.apple.driver.AppleGraphicsControl(3.8.6)[76B001B1-30F1-3D72-B264-85D77B254C 2F]@0xffffff7fa02a2000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f9ee5a000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff 7f9e124000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[619F6C9F-0461-3BA1-A75F-53BB0F87ACD3]@0 xffffff7f9e24c000
            dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[42706EB3-1447-3931-A668-FBAC58AAAA 7A]@0xffffff7fa02a5000
         com.apple.nvidia.driver.NVDAResman(10.0.2)[EFB702DE-5458-35DF-84DA-E0FFC4DCA500 ]@0xffffff7f9e605000->0xffffff7f9e87afff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff 7f9e124000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[E5A48E71-70F5-3B01-81D3-C2B037BBE80A]@0xff ffff7f9e5ef000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[619F6C9F-0461-3BA1-A75F-53BB0F87ACD3]@0 xffffff7f9e24c000
            dependency: com.apple.AppleGraphicsDeviceControl(3.8.6)[957EB27F-7D07-3C40-91F5-9B54652F06E E]@0xffffff7f9e5ff000
         com.apple.nvidia.driver.NVDAGK100Hal(10.0.2)[DC43029D-568A-3B7C-976B-E922C17F51 43]@0xffffff7f9e886000->0xffffff7f9ea33fff
            dependency: com.apple.nvidia.driver.NVDAResman(10.0.2)[EFB702DE-5458-35DF-84DA-E0FFC4DCA500 ]@0xffffff7f9e605000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff 7f9e124000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
14C1514
Kernel version:
Darwin Kernel Version 14.1.0: Thu Feb 26 19:26:47 PST 2015; root:xnu-2782.10.73~1/RELEASE_X86_64
Kernel UUID: 270413F7-3B44-3602-894F-AC0D392FCF8E
Kernel slide:     0x000000001d600000
Kernel text base: 0xffffff801d800000
__HIB text base: 0xffffff801d700000
System model name: MacBookPro11,3 (Mac-2BD1B31983FE1663)
System uptime in nanoseconds: 141332154094
last loaded kext at 15872328941: com.paragon-software.filesystems.ntfs 313.2.12 (addr 0xffffff7fa0456000, size 327680)
last unloaded kext at 91860910347: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7fa02dc000, size 8192)
loaded kexts:
com.paragon-software.filesystems.ntfs 313.2.12
com.nvidia.CUDA 1.1.0
com.orderedbytes.driver.ControllerMateFamily 4.6.0
at.obdev.nke.LittleSnitch 4240
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.70
com.apple.filesystems.autofs 3.0
com.apple.driver.AGPM 100.15.5
com.apple.driver.ApplePlatformEnabler 2.1.7d1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 4.3.2f6
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleGraphicsDevicePolicy 3.7.7
com.apple.driver.AppleHDA 269.25
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.GeForce 10.0.2
com.apple.driver.AppleIntelHD5000Graphics 10.0.2
com.apple.driver.AppleMCCSControl 1.2.11
com.apple.driver.AppleMuxControl 3.8.6
com.apple.driver.AppleIntelFramebufferAzul 10.0.2
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.AppleCameraInterface 5.29.0
com.apple.driver.AppleSMCLMU 2.0.7d0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.2f6
com.apple.driver.AppleThunderboltIP 2.0.2
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.5.1
com.apple.iokit.SCSITaskUserClient 3.7.3
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 705.4.2
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.7.0
com.apple.driver.AppleAHCIPort 3.1.0
com.apple.driver.AirPort.Brcm4360 910.26.12
com.apple.driver.AppleUSBXHCI 710.4.11
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 269.25
com.apple.kext.OSvKernDSPLib 1.15
com.apple.nvidia.driver.NVDAGK100Hal 10.0.2
com.apple.nvidia.driver.NVDAResman 10.0.2
com.apple.iokit.IOSurface 97.0.1
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleGraphicsControl 3.8.6
com.apple.AppleGraphicsDeviceControl 3.8.6
com.apple.iokit.IOAcceleratorFamily2 156.6.1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.1d38
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.AppleHDAController 269.25
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 269.25
com.apple.iokit.IOAudioFamily 203.3
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.2f6
com.apple.iokit.IOBluetoothFamily 4.3.2f6
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.3
com.apple.iokit.IOUSBMassStorageClass 3.7.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.3
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.driver.CoreStorage 471.10.6
com.apple.driver.AppleThunderboltDPInAdapter 4.0.6
com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6
com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2
com.apple.iokit.IOAHCIFamily 2.7.5
com.apple.driver.AppleThunderboltNHI 3.1.7
com.apple.iokit.IOThunderboltFamily 4.2.1
com.apple.iokit.IO80211Family 710.55
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 710.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 396
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro11,3, BootROM MBP112.0138.B14, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.15.159.13.12)
Bluetooth: Version 4.3.2f6 15235, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: Internal Memory Card Reader
USB Device: My Passport 0844
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Remove CUDA and see whether the panics stop.
To remove CUDA, triple-click anywhere in the first line below on this page to select it:
/Library/Frameworks/CUDA.framework
/Library/LaunchAgents/com.nvidia.CUDASoftwareUpdate.plist
/Library/PreferencePanes/CUDA Preferences.prefPane
/System/Library/Extensions/CUDA.kext
/System/Library/StartupItems/CUDA
/usr/local/cuda
Right-click or control-click the line and select
          Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Continue with the remaining lines. Some of the items may be absent, in which case you'll get a message that the file couldn't be found. After moving all the above items to the Trash, restart the computer and empty the Trash. Don't try to empty the Trash until you have restarted.
If you haven't already done so, back up all data before making any changes.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
          Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Render Mode GPU generate error when we use window.open()

Hi,
   Am using AIR 3 beta2 SDK. I set the rendermode descriptor to gpu(<renderMode>gpu</renderMode>) in the application descriptor file. In the application I created a window component which can be opened as a new window within the main application.
Some lines of code where I load the new window
var window3DInstance:Window3D=new Window3D();
window3DInstance.open(true)
When I run the application and try to open the new window, it generates the following error:
Error #1508: The value specified for argument renderMode is invalid.
When we set the rederMode to Auto or cpu, the error disappears and the new window is opened. But I need to render it in gpu mode.
How we can solve this issue?

01. The way that a Monkey Patch is applied depends upon your build/test environment. You probably use FlashBuilder. I do not use FlashBuilder, I use FlashDevelop, but the approach is the same, either way. The principle is that the mxmlc compiler, when it looks to resolve a reference to spark.components.Window, will find two possible resolutions. Without a Monkey Patch, it would find only one. Without a Monkey Patch, it would find spark.components.Window only in the airglobal.swc file. With the Monkey Patch, it will find spark.components.Window because you will add that path to the sources that your project is using. When the compiler has both a source and a swc entry, it will use the source instead of the swc entry.
In my build/test environment, the two files are found in my SDK directory:
     G:\FlexSDK\21328
The swc is at:
    frameworks\libs\air\airgloabal.swc
The modified source is at:
    frameworks\projects\airspark\src\spark\components\Windows.as
02. Wherever your spark.component.Window.as file is located, you should first rename that to Window.org. Then, you should save the attachment in this email to that location. To make the modified code visible to your compiler, you will add a sourcepath. Using my example, the added source path is G:\FlexSDK\21328\frameworks\projects\airspark\src.
03. If you open my attachment, you can search for the string 'SSS'. You will find it only twice -- the patch is trivial. The first change is to add an additional argument to the constructor for the class. The second change is to use the value of that argument where Window creates the NativeWindow. I have set the default value to NativeWindowRenderMode.AUTO, but I do not know if that will work correctly or not. In my use case, EVERY sub-window is being created by this invocation:
      new Window (new NativeWindowRenderMode.GPU);
04. If you read the ASDoc notes for the NativeWindowRenderMode class you will see some rules concerning the requirement of a RenderMode specified in your code having to agree with the RenderMode that is set in the AIR Application Descriptor. Since my Application Descriptor sets the value of that <RenderMode> parameter to the string 'gpu', I know that my application is obeying the NativeWindowRenderMode class' rules. What I do not know is how you would create an AIR application in which you had some sub-windows configured for GPU usage and other sub-windows configured for non-GPU usage. I suspect that under this new architecture, it is not possible to mix and match. I suspect it is only possible to have one or the other. Since I must have GPU rendering in at least one of my application's sub-windows, I am setting ALL of them that way even though most of the other sub-windows have no Molehill code running inside them.
05. Since Adobe has not published clear documentation concerning these matters, I have no idea whether or not my setting of the default value to NativeWindowRenderMode.AUTO is generally valid. I have not tested that theory. If it breaks other applications, then I will simply revert to the un-modified spark.component.Window when working with the broken application(s), and only use the Monkey Patch when working with the important application that requires rendering of Molehill code in a sub-window.

Intel Graphics HD4600, Windows 8.1 x64, Driver: 3379 - problem with GPU clock

My notebook is Lenovo B5400.
In my notebook I have Core i3 4000m with HD4600.
When i run gpu benchmark gpu clock goes to 1100MHz (it's fine), but if my system is in IDLE, gpu clock is 600MHz (it should be 400MHz).
I tested it with driers 3345 too and problem was the same.
How to fix this?
Log from GPU-Z, i was waiting to my system hibernation (screen is off after 5 minutes): http://wklej.to/Tol36
After I bought the notebook I run Bios Update Utility, may its the problem, but on Lenovo site there is only one version of BIOS (1.02-1.04) - I have this version now!!
How to repair this??
I have balanced power plan turned on, but tried witth power saving too!

halo?
now have Windows 7 x64 with latest Intel gpu drivers from lenovo drivers site and situation is identical.
(I see thinkpad power manager says that gpu is on 150% (400*1,5=600), so it isnt gpu-z problem)

Loss of GPU acceleration after lastest CC update.

I recently upgraded to the CC programs. I still have a project to complete with my previous version of Premiere Pro CS6. After the latest CC update I lost my GPU acceleration and get the following error message.
"Missing Renderer
This project was last used with a Mercury Playback engine GPU acceleration(GPU), which is not available on this system. Mercury playback engine software only will be used"
I'm running two NVIDIA Quadro K5000 video cards and running Windows 7 operating system. Before the upgrade everything was working great. My lastest update is Premiere Pro CS6 6.0.4

Hi Pete,
Thanks for contacting adobe forums,
Here is little confusion, are you getting this error on Premiere Pro CC or Premiere Pro CS6 ?
because the NVIDIA Quadro K5000 is supported on Premiere Pro CC onwards.
http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-premiere-pro.html
Happy Editing,
Sandeep

HELP! Overclock my GPU &CPU

FIRST overclock my GPU;
My GPU is R9100 core default at 250Mhz(MEM At 250Mhz DDR 4ns)
now I overclock my GPU core to 299Mhz(MEM at 276.25Mhz);& running at 3DMark2001SE and through it successful; But when the core rate over 300Mhz and run again in 3DMark2001SE ; I find every time will shutdown at the same place(Drogan fourth sence);and the ATI VPU will work;
Now I use 3DMark2003 Pro TO test my oc card ! I set my GPU core rate to 311Mhz(default at 250MHZ); but this time through it perfectly!!!(run many times!)The picture is very beautiful!!!
OC=(313-250)/250=25.2%(Good)
I don't know it may some bugs in 3DMark2001SE??
About OC my CPU :
many people say that P4 2.4B(Core voltage at 1.5V ,Northwood core) can overclock over 3.0Ghz ! but when I overclock to 2940Mhz ! The system shutdown
and restart ! in this situition! Need I add more core voltage ?
1.55V? 1.582V? 1.6 V? 1.63V ETC..
how I know that the voltage has no do harm to my CPU ? is'it all looking at CPU TEMP?
another my memory' voltage; My memory now working at 2.6V; If I want to Overclock; may I set it to 2.65V?2.70V???
Any export help??
thankyou!!!!!

any more ! I did not where to change the RAM divider? when I set my CPU to 2800Mhz ! The memory will work at about 199Mhz(default 166);
May I set my cpu CORE voltage to about 1.6V?
I use the powerstrip3.49 to overclock my GPU
"do u have sapphire gpu?" what's the meaning of that?

CPU vs GPU

When I am creating my apps for iOS in which situations should I use CPU or GPU?

GPU for graphic intensive apps and games
CPU for general apps with data (little to no animation)

T420 CPU/GPU Temperatures seem excessive...

I was running Prime95 to check my CPU (Core i5-2520M) temperature (using Real Temp) and I noticed it was a bit high, about 95 degrees celsius. I followed up by running FurMark to check how the NVS 4200 GPU was doing. It ended up sustaining at 87 degrees celsius. I did not run the two tests concurrently.
I decided to strip the heatsink off and apply new thermal compound. After the new compound was applied, the CPU temperature under Prime 95 peaked at 84 degrees celsius. Under Furmark, the GPU sustained at 75 degrees celsius. A very significant drop.
I decided to run the two tests concurrently (after new compound had been applied) and ended up with a CPU temperature of 100 degrees celsius and a GPU temperature of 97 degrees celsius. Pretty horrifying stuff. I can't imagine those values being within operating range.
These torture tests are rather extreme so I followed up with some gaming. I played DOTA 2 for about 3 hours and during that period my CPU peaked at 98 degrees celsius with an average temperature of 93 degrees celsius. I did not log the GPU temperature during this session.
I should mention that Turbo Boost is enabled and the fan was set at maximum speed.
Does anybody have any temperature figures for similair configurations? Specifically in situations where the GPU and CPU are both under high load. I'm curious to know if my temperatures are abnormal.

I started to think that it's not an issue with my sample. I went ahead and confirmed these temperatures on two other identically specced T420s (4178). Under extreme conditions the heatsink/fan unit cannot dissipate heat quickly enough causing both chips (CPU and GPU) to reach dangerous temperatures. If you haven't torture tested the GPU and CPU in your T420 concurrently, you might want to give it a shot. It gets alarmingly hot.
(Do this at your own risk, extreme heat can damage your hardware)
Prime 95: http://www.mersenne.org/freesoft/ (CPU Test)
Furmark: http://www.ozone3d.net/benchmarks/fur/ (GPU Test)
Real Temp: http://www.techpowerup.com/realtemp/ (CPU Temperature)
GPU-Z: http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ (GPU Temperature)
Tests were done while plugged in using the default Power Source Optimized profile.
Prime95 test was run using In-place FFTs. Furmark was run at 800x600 with anti-aliasing off. The tests were run for 20 minutes concurrently.

MacPro(Late 2013) AMD FirePro D700がAfter Effects CC(12.2)でGPU認識されない

MacPro(Late 2013最新モデル）にてグラフィックスをMacPro(Late 2013AMD FirePro D700 6144 MB x2積んでいるのですが、
Adobe After Effects CC(12.2)にてレイトレースがGPU認識がされていません。
またCUDAもNVDIAドライバー、バージョン6.0.37（2014.5.1現在最新）をインストールしていますが、
GPU情報をみても、CUDAが認識がされていません。
MacPro(Late 2013最新モデルは、買ったまっさらな状態で、After Effects CCはインストールしました。
ちなみにPremiere CCはGPU認識されています。
下記にAfterEffects CCのGPU情報画面にてコピーしたものを貼付けます。
アドバイスいただけますと幸いです。よろしくお願いします。
高速ドラフト : 使用可能
テクスチャメモリ : 1535.00MB
レイトレース : CPU
(GPU を使用できません - 互換性のないデバイスまたは CUDA ドライバーです)
OpenGL
ベンダー : ATI Technologies Inc.
デバイス : AMD Radeon HD - FirePro D700 OpenGL Engine
バージョン : 2.1 ATI-1.20.11
合計メモリ : 2.00 GB
シェーダーモデル : -
CUDA
ドライバーのバージョン : -
デバイス : -
現在使用可能なメモリ : -
最大使用可能メモリ : -

こんばんは
レイトレース3DのGPU高速処理をしてくれるのは、NVIDIA製の対応GPUが搭載されていて、かつCUDAドライバをインストールされている場合ですね。
After Effects CS6「”After Effectsエラー：レイトレース3D：レイトレーサー用にページングされたマップメモリが不足しています」

Different GPU / Unterschiedliche GPU

Similar Messages

Maybe you are looking for