GPU Acceleration in Chromium causes heavy system load

I experience a heavy system load (especially if I'm watching videos or listening to music on soundcloud) if I use the hardware acceleration feature in Chromium.
I use the standard linux kernel(not the lts one) and the drivers from the nvidia-package. I got a Nvidia GeForce GT 525M GPU.
If I deactivate the hardware acceleration feature in chromium, it doesn't need so much system resources, but maybe there are more factors which cause the heavy system load.
I'd like to be able to activate the feature, because otherwise I can't scroll through webpages smoothly.
The same thing happens if I use the google-chrome package from the AUR.
Has somebody experienced the same problem and/or has ideas how to solve it?

Isn't HW acceleration disabled by default on Linux? AFAIR it always had a lot of problems.
Last edited by dwe11er (2014-10-22 13:32:17)

Similar Messages

  • Mercury Playback Engine GPU acceleration isnot available on this system

    When using Adobe Premiere Pro CS5 with a new system I brought 5 days a ago  I get the message MPE not available on this system.
    OS Win 7 Pro 64bit
    Inte i7 quadcore 2600k 3.4GHz 1155 CPU
    Intel DH67BL mATX mobo
    2x750GB Sata HD RAID 0
    16GB DDR3 1333 MHz
    Gigabtye Geforce GTX 570 OC 1280GB PCIe
    750 watts PSU
    According to the specs on Adobe website this system should work with Adobe Premiere Pro CS5 MPE.
    Is there something I'm missing?
    Have anyone else had this problem before?
    I'm thinking maybe the card is defective.

    The GTX 570 is not on the list of cards that Premiere Pro CS5 will use for CUDA processing.
    That card is on the list of cards that Premiere Pro CS5.5 will use for CUDA processing.
    See this page for a list of cards added for CS5.5.

  • Premiere CC 2014: Message on loading project from older version: This project was last used with Mercury Playback Engine GPU acceleration (CUDA)...

    After installing Adobe CC 2014 I have each time a message when loading an old Adobe pro project. Message:This project was last used with Mercury Playback Engine GPU acceleration (CUDA), which is either not available or not certified on this system. Mercury Playback software will be used. I have very recent HP Zbook 15 with a NVIDIA Quadro K2100M. At webinar today it was explained how to solve this, but sound was not understandable at my machine at that moment. Help? What need I to do.

    Problem is solved since yesterday via Adobe helpdesk. It appeared that the newest driver for the NVIDIA were note present. So after downloading the new drivers it work. But I think Adobe should mention those issues when they launch new versions of Adobe CC like in June.

  • GPU Acceleration causes random frame in encode?

    New Mac Pro (6 core, d500 cards, 32GB RAM, OSX10.9.4). Adobe Media Encoder CC 2014.0.1. Tested on two separate machines of the same configuration.
    I have a just over 2 hour long 1080p ProRes file that I was encoding to MPEG2 for DVD. During QC of the disc, a random frame from another part of the movie was found in a spot about 39 minutes into the encode. The issue was in the encoded MPEG2 stream.
    The client also wanted a lower resolution h264 proof of the video, and that was encoded on the same machine at a separate time. That had the same random frame at the exact same spot.
    I encoded the preview h264 in just a few minute segment of the video around the glitch on the second Mac Pro. It showed up again. I used the same setting but turned off GPU Acceleration, and the frame is gone.
    Does anyone have any ideas as to what is going on here? Obviously there is a problem with GPU acceleration on the new Mac Pro's with Media Encoder, but what could be specifically causing it and what could be done to fix this? With all of the issues in Premiere and After Effects, some of which are being caused by software updates, and the issues with the one Mac Pro needing to be replaced due to bad video cards, I feel like there is just a ton of problems that didn't exist on our outdated Mac Pro with Final Cut Pro 7.
    Please let me know of any ideas to make me not doubt every encode I do on these machines with GPU Acceleration turned on. Thanks.
    -Phil

    Does anyone have any additional ideas on this? I heard from the CreativeCow forums that this has been a known bug with GPU Acceleration on the new Mac Pros. Is this the case? Has anyone else had this issue looked at by Adobe?

  • How to view what session is causing heavy load

    Hi,
    currently I was tasked to view what is wrong with the production server, there's some processing that is causing heavy usage.
    May I know how should I go about investigating this?
    thanks
    more precisely which machine, which sid, what query is causing heavy load on the db server?
    thanks

    Hi,
    Better generate and statspack/AWR and analyse the report to find queries which are causing heavy load for the time period in which database consuming high CPU. You can use top command from OS level to check the process are consuming heavy load.
    HTH
    regards
    Jafar

  • Does LR2 use GPU acceleration?  Other system requirements?

    Does LR2 use GPU acceleration as Photoshop CS4 does?
    Do you think this machine will run LR2 for some time to come:
    Dell Studio with Intel Q9400 quad core; 8GB RAM; 750GB hard disk.
    Currently using integrated graphics, but there is a PCI x16 slot available.

    >Does LR2 use GPU acceleration as Photoshop CS4 does?
    No
    >Do you think this machine will run LR2 for some time to come:
    Yes that's more than beefy enough. To use that 8 gigs, make sure you run 64-bit windows vista on it.

  • AME takes a long time to start encoding when using GPU Acceleration (OpenCL)

    Have had this issue for a while not (current update as well as at least the previous one).
    I switched to using GPU Hardware Acceleration over Software Only rendering. The speed for the actual encoding on my Mac is much faster that software only rendering. However, more often than not, the encoding process seems to stick at 0% waiting to start for a long time, say anywhere from 1 minute to several minutes. Then it will eventually start.
    Can't seem to find what is causing this. Doesn't seem related to any particular project, codec, output format or anything else I can see. I'd like to keep using GPU Acceleration but it's pointless if it takes 5 times as long to even start as rendering by software-only would. It doesn't even pass any elapsed time while it's hanging or waiting. Says at 0 until it starts. Like I said, once it starts, it's a much faster render than what the software would take. Any suggestions? Thanks.
    using an iMac, 3.4Ghz, 24GB RAM, AMD Radeon HD 6970M 2048 MB

    Actually, I just discovered it doesn't seem to have anything to do with OpenCL. I just put the rendering back to software only and it is doing the same thing. hangs for a long time before it starts to run. Activity monitor shows it running 85-95% CPU, 17 threads and about 615 MB of memory. Activity Monitor doesn't say its not responding, it just seems kind of idle. It took almost 7 minutes for it to start rendering.
    1- Running version 7.2.2.29 of Media Encoder,
    version 7.2.2 (33) of Premiere.
    2- Yes, a premiere project of HD 1080 source shot with Canon 60D, output to H.264 YouTube 720, fps 23.976
    not sure what you are referring to by native rendering. The rendering setting i tried now is Mercury Playback Engine Software Only if that is what you are referring to. But OpenCL gives me the same issue now.
    3- H.264 YouTube 720, 23,976 - seems to happen on multiple output types
    4- In Premiere, I have my project timeline window selected. Command-M, selected the output location I wanted and what output codec, selected submit to Queue. Media Encoder comes up, the project loads and I select the run icon. It preps and shows the encoding process setup in the "Encoding" window, then just sits there with no "Elapsed" time occurring until almost 5-6 minutes later, then it kicks in.

  • 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.

  • Error compiling movie: unknown error & Mercury Playback GPU acceleration

    Hardware
    2014 Mac Pro, 12GB RAM, 3.7 GHz Quad-Core Intel Xenon ES Processor, duel AMD FirePro D300 2048 MB graphics cards
    Software
    Mavericks (10.9.4)
    Premiere Pro CC2014 (8.0.1)
    I'm attempting to render out a moderately complex sequence. Raw footage was dslr h.264 MOV files. 30fps 1920x1080 from canon. It has some clips that are pulled from multi-cam sequences and a few that have warp stabilizer applied. 4 total audio tracks with some linked comps from audition. Whole thing is about 14 minutes. It should be noted that I render out similar sequences regularly without issue. However on this occasion whenever I tried to render out using media encoder ( for web h.264 MOV 720 30fps) I was getting an error at the same clip every time. Error Compiling Movie: Unknown Error. So I checked out the clip. It was one of the ones with warp stabilize. I turned that off and sent it out again. Render got further this time but hit a different clip with warp stabilize (after getting through like 2 other clips with warp stabilize enabled) and gave me the same error. I tried getting rid of cache files, saving to a local drive instead of a network drive, uninstalling and re-installing premiere even. (which btw if you check remove preferences then reinstall it def still has preferences so that's a total load.) Anyway I was doing some forum surfing and found several people going all the way back to PP 5.5 saying that the only solution they found was to turn off the Mercury Playback GPU acceleration. Tried that and it's currently rendering just fine but taking roughly 4X longer than with acceleration. The GPU acceleration is a big deal for me since our company relies on putting out a lot of volume quickly. Has anyone else experienced this problem and is it something you were able to fix without turning off GPU acceleration. Grateful for your input.

    sorry I actually wrote that wrong. I am using the H.264 setting 720 30fps to create a web friendly .mp4. Alternately though I decided to watch and see if it was the same clip failing every time. It is. I went into the project and did a match frame for the offending clip. Dragged the a new version of the same content onto the timeline and copied the warp stabilize effect onto the new version. Well this time the encode got past the clip with the issue, however the next clip it hit with warp stabilize caused another error compiling movie: unknown error. I guess at this point my options are to turn off the GPU acceleration and wait for a render that takes more than 3x as long to render with software only, or to go through the whole timeline and replace the clips with warp stabilize (there are a bunch, the shooter wasn't having a great day on glidecam). Not a great solution on either end. Please let me know if I should file this as a bug report. Though it seems people have been having the same issues since version CS5.5

  • Mercury Playback GPU acceleration in CS5.5 not available, Mercury Playback Software only available

    Getting a warning screen each time I open an existing project in PP CS5.5 that says GPU acceleration is not available on my system...when it has always in the past. Editing on a HP Z400 with the NVidia Quadro 2000. I can't figure out how to get GPU acceleration going again. The software only option makes for a painfully slow and clunky edit. Any ideas are gladly welcomed. Hot and heavy deadlines looming...you all know the drill. The warning window I get reads "This project was last used with Mercury Playback Engine GPU Acceleration, which is not available on this system. Mercury Playback Engine Software Only will be used." And there is only an "okay" button to close the window. Also when I try to start a new project GPU Acceleration option is not accessible...defaults to the software setting and it's grayed out.

    Hi Joe,
    Have you updated your video drivers lately? Any OS updates?
    Thanks,
    Kevin

  • 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

  • Any recommendations for a new Graphics card for Prem Pro 2014 (Windows) that offers Mercury Playback Engine GPU acceleration?

    Hi.
    I am led to believe I could benefit from GPU acceleration when editing as my PC is a little under spec. I do have a card but when I switch to GPU acceleration it does work but every time I stop moving / playing / scrubbing on the timeline the preview screen goes black.
    I am not sure which might be the best card to obtain for my reqs. I dont think I put the biggest of demands on the software but it does still struggle. Most of my editing is 3 - 10 min long interviews. 2 camera multi-cam editing. I invariably have need to edit RGB curves, three way colour corrector, transitions and sometimes Neat noise reduction. Any of those leaves my PC struggling. All the usual titles, music & voice-overs etc but nothing too heavy going like making films or inserting lots of video lines.
    I also do an occasional bit of work in After effects too.
    PC spec is:
    Intel Xeon CPU 1.86GHz (2 processors)
    12GB RAM which I am going to upgrade to 16GB
    64 bit op system
    Windows 7
    Radeon HD 5450 graphics card.
    Any guidance would be much appreciated

    Thanks for insight. I am not technical but I suspect your right about the base technology of my PC. The processors and RAM (even if I upgrade) are probably too limited. I was not so sure about the relationship between the main processor and the graphic card. I rather hoped that the card would get round the limitations of the CPU's.
    I maybe need to invest some time looking in to improving the spec of my PC. Any thoughts on a suitable spec from anyone would be helpful bearing in mind my relatively narrow editing needs.
    Even so I will look at the GTX 660 and see what it might offer. The only reason I thought the 5450 might offer GPU acceleration was because the option was available to select in the preferences in PremPro. Figured it wouldn't be an option otherwise. Certainly doesnt seem to work correctly or offer any advantage so gone back to software only.
    This is not going to be a quick or inexpensive resolution by the looks of it :-)
    Thanks again for input.

  • GTX 470 lack of GPU acceleration

    Windows 7 64-bit, 8GB RAM, MSI-branded GTX470, NOT gaming, using with Adobe CS5 applications. CS5 applications are updated to loatest patches.
    I've read a few other posts but I still have some questions:
    1) If the hardware monitor provided with my GTX 470 is correct, and during effects rendering in Premiere and in transcoding in Encore with AME, GPU % used is about 1%, is that expected?
    2) I posted a question on the NVIDIA forum regarding my inability to add Premiere Pro CS5 and Encore CS5 to the list of GPU-accelerated applications using the NVIDIA Control Panel. The *CS4* applications are listed but Control Panel does not allow me to add CS5. I uninstalled CS4 some time ago, before I added the GTX 470.
    3) Today when I attempted to load a Premeiere Pro project, I get a message saying that Mercury GPU acceleration "is not available on this system" and "software only" mode will be used. What changed? Any way to recover?
    So basically two sets of questions:
    a) Shouldn't transcoding use GPU acceleration? Shouldn't rendering in Premiere Pro use it? What else should I expect to NOT use GPU acceleration, aside from video effects, which are pretty clearly marked.
    b) Is there a trick to configuring either CS5 or GTX470 to allow GPU acceleration to be used?

    Some effects are hardware accelerated, these are CUDA effects, because they use the CUDA engine on the video card. Others are not.
    The GPU usage during transcoding is dependant on the source material and the export format. For instance if you start with HD (1920 x 1080) material and transcode to 720x576 SD PAL, the scaling is done by the video card (CUDA enabled). If there is no scaling during the transcode, then there is no assistance from the video card.
    The faster the CPU and the memory, the more work can be done by the GPU, but if the CPU is slow, the video card is constantly waiting for the CPU. A Phenom II X4 is pretty slow, so the GPU is waiting for the CPU and will show low usage.
    Look at the Background Information page at the PPBM5 Benchmark

  • ATI Cedar PRO [Radeon HD 5450/6350] GPU acceleration disabled

    Hi,
    my graphics card is a
    01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350]
    i've installed xf86-video-ati, ati-dri, mesa and linux-firmware.
    if i have a radeon entry in my mkinitcpio.conf or a entry in my /etc/modules-load.d/modules.conf, i get acceleration not enabled:
    [ 15.348683] radeon 0000:01:00.0: disabling GPU acceleration
    any ideas anyone?
    thanks for your help
    mongohorst

    cat /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect pata scsi sata encrypt filesystems usbinput fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    cat /etc/modules-load.d/modules.conf
    radeon

  • Chromium causes overheating / fan to spin at 100% / X to crash

    Hey all,
    I have a Toshiba Portege R835 laptop and have been running Arch Linux on it for the past year.
    Lately when running Chromium (happened within the latest few versions), the laptop heats up badly.  I've tried measuring CPU and GPU usage, toggling different GPU acceleration features within Chromium, and testing on different types of web pages.  Occasionally X will freeze completely, and I'm unable to even switch to a tty via CTRL+ALT+<num>, forcing me to do a cold reboot - when this occurs the fan will begin to spin at 100% and no obvious errors (Xorg.log, dmesg.log) are available after reboot.
    This mainly occurs when browsing JavaScript-intensive pages (facebook, gmail) or viewing HTML5 videos.  Firefox doesn't have this issue when viewing the same pages.
    powertop/top/intel_gpu_top don't seem to suggest any irregularities in CPU (15% or less average across the cores, which isn't abnormal) or GPU usage; the only real difference that I notice is that wakeups when Chromium is open are increased (average is usually between 400-800 idle, whereas with a browser like Firefox and the same tabs open it is around 200-500 idle).
    Additional information:
    Plugins are only run on a "click to play" basis, so I doubt that flashplugin could be a cause.
    I don't have this issue with other webkit-based browsers (midori).
    DE is GNOME 3, but it's occured with xmonad before as well.
    xf86-video-intel graphics driver, occurs with and without SNA enabled.
    Stock up-to-date kernel, i915 parameters are all their default values, with and without KMS enabled during bootstrap
    Thanks for any assistance!
    Last edited by Whip (2012-08-10 21:53:43)

    beepressure wrote:
    ozar wrote:
    My 9600GT and GTS250 cards do that as well and always have, but my GTX260 doesn't do it.
    It's my understanding from the nVidia forums that this is normal behavior for each of these models.  Not sure about your model, though.
    It's really annoying because when i am done using my computer for the night, I quit X and logout. But I cannot sleep with this fan going 100%. I guess i will have to leave X running all the time.
    Yup, I understand completely.  When I first got the 9600GT, that was the first thing that I didn't like about it.  Then the same happened with the 250GTS. Yes, it really is annoying.
    It seems like I remember reading somewhere that a video bios/firmware uprade might stop that behavior, but not sure.  It might be worth checking out, though.

Maybe you are looking for