Processor overheating on Macbbok Pro with Photo Raw 2018 and 2018.5
I’m using a MacBook Pro (mid 2015) with 16 GB RAM. When using Photo Raw 2018 or 2018.5 the processor starts overheating. Fan is going like crazy. What’s the deal?
-
Official comment
Tim,
Please note, our app is doing a lot of background calculation to generate the on screen preview while you are editing images in our app. It is completely normal for the program to utilize both your CPU and GPU while you are running the program. To increase speed and performance, we recommend closing all unnecessary applications on your machine prior to editing your photos. This will ensure that all available resources on you machine are available during your post processing.
Also, I would like to provide you with some more information on what our app is doing under the hood. We have made a change in this update in how often the program scans/refreshes the program window on your screen. In the 2018.5 update, the program is acting more like a video game by continuously updating the on screen preview. It is completely normal for the program to utilize between 10-30% (depending on your machine) of your CPU even while sitting idle. Furthermore, it is also normal to see a spike in CPU usage (you may notice the fan running) when you open an image into Develop/Effects or viewing an image in Detail view in Browse. Your CPU usage will spike to over 100% and then drop back down to the normal range (this of course varies depending on your machine’s hardware).
Again, the program is doing a lot of background calculation and relying on both your CPU and GPU to generate the on screen preview depending on what you are doing to this image. Also, it is normal for the fan to turn on while you are processing an image. All computers will enable the fan when needed and have safeguards in place if the temperature of your machine reaches high levels. Noticing the fan on your computer while you are processing your images in our program does not mean that there is a problem or that the fan (or heat) is causing damage to your machine’s hardware. Normal CPU/GPU operating temperature values will vary slightly depending on your machine’s hardware. For example, machines that have a dedicated GPU will run cooler than machines with integrated graphics due to the fact that these machine’s GPU are on a separate chip from the CPU. If your machine is equipped with integrated graphics, the CPU and GPU are on the same chip, therefore will run slightly hotter when assigned complex tasks like photo and video editing.
-
Hi Tim - I've had the same issues with an iMac late 2015 , intel i5, 24gb of RAM. I've been in touch with support and sent log files over last few days. I was told there is a new build which should help overcome this fan problem - I've not had chance to test it out yet since I was sent the EXE rather than the DMG version. I hope you are able to get this new build and see if it fixes your fan/processor issues too. Cheers, Pete
1 -
Hi again tim. Ive now tested the mac version - build 2018.5.2 (12.5.2.5709). The problem with overuse of resources and fan noise is still there for me. its mainly a problem within develop and effects. Looks like I wont be buying photo raw 2018 after this trial is over, sadly.
1 -
I have had the "fan problem" too. I have the current release of On1 installed on an iMac27 Retina and a MacBook Pro 15. On1 will spin up the fans on both systems. I bought some monitoring software and the heat issue (for me at least) is not the CPU load - it is the GPU load. On my iMac27 On1 drives the GPU to 75%; on my MBP it drives the GPU to 100% - hence the fans. Everything still works, and the fans are just an annoyance (the system should throttle processing to avoid damage). However, notwithstanding the comment from On1 - I don't think this should be happening. Apple is strongly recommending that software uses the "Metal" interface to the GPU, and I suspect that would improve this situation a lot. I have checked other image processing software and none uses the GPU as heavily as On1. There is great potential here, but I don't think it is implemented correctly yet.
David
2 -
Thanks for your input David. What monitoring software did you get ? I've looked at a few different ones but reviews seem divided. Pete
0 -
Same problem here, MacBook Pro retina late 2013. I also tried the new build they sent me, but unfortunately it didn't solve the issue. CPU/GPU runs very hot.. monitoring with istat software, I can see temperature jumping at 100°Celsius in a matter of seconds and fan spinning at full reps..
Hopefully we can help the developing team to fix this issue.0 -
Having the same problem here. Fun is going mental after seconds of opening the app. Macbook Pro mid 2015.
Any advice?
William
1 -
I got iStat Menus. Lots of info, but if you check the CPU it also shows the GPU utilization (memory and processor). I think there is an evaluation version so you can test it if you are curious about what is going on. I think using the GPU for these applications is a great idea, but it has to be implemented correctly. For example, Capturer One 11 uses the GPU and doesn't cause this problem. I have another nice app called RawPower that uses the GPU without any problem. The RawPower developer - who used to be responsible for the Apple Aperture raw processing - is developing a new version that will use the Metal interface. I am on the beta list for that but it hasn't been released yet. For Mac users, RawPower is worth checking out - it is very inexpensive (available on the App store) and quite powerful. It works with Photos and as a stand-alone application.
David
1 -
True, every other software I tried (RawPower, Pictorial,skylum, affinity, lightroom) works great, without overheating my MacBook.. the problem is that every software lacks something I would love to be there ( chromatic aberration correction, local adjustment, Luts support, and so on). Photo raw 2018 has everything you need in a single app (maybe the demosaicing is not the best out there, but it works just fine if you are not pixel peeper).
The only problem is that I cannot work with this on1 app on my MacBook, and this is a BIG problem.
I think they can still work on it to make it usable.. metal implementation is a good idea, but it will not work on old machines with an old version of osx. OpenGL are still fine for graphic acceleration on this kind of software.. I have no idea how on1 software use graphic acceleration, they surely know better than me how to max out performance in their apps..
Still hoping for an update, cause I like the idea behind this software.0 -
Any luck with the new build??
0 -
I have seen no improvement on either my MBP or my iMac27 after installing the latest update. It still really spins up the fans with “nothing” happening.
1 -
Same here, no improvement. The one and only version without any problems and by the way, the fastest - was 18.1
I deleted allupdate versions an I am now still on version 18.1 - I think this is a big problem for the fututre of this really good program.
0 -
Had similar problems with a 13” dual core i7, 16gb ram, 512gb ssd running high Sierra - my road warrior.. The fans ran like crazy and the system consumed 300+% of resources just in browse with non catalogued files. Worked with On1 and they couldn’t resolve it other than doing a complete reinsallation of the OS. That helped somewhat but the background idle utilization of CPU was around 60%, the fans continued to run and the system performed terribly. Eventually I gave up.
PR runs fine with my 15” 2017 with 16gb, 512gb ssd, and 560 GPU. It’s basline utilization is less than 2%, files open quickly, and brushes work smoothly. Bottom line PR is a resource hog and one needs to come to the table with big time hardware.
0 -
So, it seems like it runs smooth on new hardware?
I don't think your 13 and 15 MacBooks are like night and day performance wise..
Seems more related to an hardware compatibility issue.. (how old is your 13"?)0 -
I can understand, and tolerate, high CPU/GPU utilization when the software is _doing something_. But, just as for the other posters, just sitting or browsing cataloged directories causes high CPU and GPU utilization. It seems very strange to me, and On1 must be able to replicate this - but they don't have a fix. This is what I don't understand: once everything has been cataloged, what is the software doing? No one has come up with an explanation.
Interestingly, I have a similar MBP15 which still has the problem. Mine is the late 2016 model (running the Mojave beta). I do know that cataloging runs much faster on the MBP with the 1TB SSD compared to the iMac27 working on images on an external USB3 drive. Cataloging uses a lot of I/O and benefits from a fast drive. But what does a GPU have to do with any of this?
David
0 -
@David
I completely agree with you. And what I don´t understand: what happens since version 18.1 where everything was working flawless (catalogs, folders, processing, keywords etc.)? I really think that on1 is packing too much tools in their program. Sorry for my inconvenience, but I need this pogram for professional use. I need a RAW CONVERTER not a designtool! For this I use PS or meanwhile Affinity. And for the converting for raw files (I use a Nikon of the 800 serie) the raw engine works really good. But under this conditions I cannot use it longer - sorry on1.
Greets, Reinhard
0 -
Adam said that PR runs smoothly with a 560 GPU.. it's a Radeon discrete graphic card, not an integrated GPU as iris/iris Pro.. is your MacBook/iMac running on integrated or discrete GPU?
(Hopefully giving them some information could help them finding the problem..)0 -
It's discrete - Radeon Pro 460 with 4GB of video RAM. This was the high-end model for the late 2016 production.
David
0 -
Macbook Pro late 2015 running high sierra. I sent the logfiles to on1 almost in July. And again - Version 18.1 was running perfect without any issues!
Greets Reinhard
0 -
Yes, my 13” 2015 has an integrated IRIS gpu with around 1Gb of memory whereas the 2017, 15” has a discrete 560 gpu with 4Gb of DDR5 RAM. I don’t think cataloging is dependent of gpu but it does suck up resources. My understanding is that the newer versions of PR, are employing continual re-drawing of the image. This is what consumes the gpu and older machines may not be up to the task. Even with complex masks on 36+ MP images, my 2017 never breaks a sweat. I can’t say how it would perform on a 2018 13”.
0 -
Again, the new 2018.5 uses dynamic image refresh and as a consequence it uses much more gpu power. Older machines can't handle the requirements.
0 -
@Erhard
I agree with you.. there is no need for high refresh rate, or not in browse mode at least.. the image refresh should happen when something is changed (moving sliders in develop mode).
Would be nice to have an option to select the refresh rate.. I can understand that older machines are slower, and rendering can't be as snappy as on a new 2500$ laptop, but it's better to have worse performance than cooking the GPU and drastically increase battery drain..0 -
Same here. My MBP15 is a high end machine. On1 is the only image editing application that has this problem.
0 -
Same problem for me on Late 2013 MBP with Iris Pro. GPU has 70% load even when idle. CPU is not used much though. In general I can read how fast On1 is now but from my experience it is one of the slowest editing tools. Some optimisation for Macs on integrated GPUs would be appreciated. I would rather make use of i7 CPU than boil weak GPU with no effect. When some masks and layers are putted it becomes almost unusable. Is On1 Support aware of the problem and working on solution?
1 -
No, Erhard, your machine is not old but it is underpowered to run PR. I had a 13" 2015 MBP and it choked on the new version. 2018.1 ran fine but it struggled with 2018.5; this version uses dynamic image redrawing which requires powerful CPU/GPU. The 13" is inadequate as are earlier 15" with lower end gpu's. The 2015's for whatever reason run especially poorly with extremely high fan/temperatures. On1 knows about this but I don't think they know why. In my book there are a couple options; switch to LR/PS, Affinity, or the myriad of other choices or upgrade your hardware to run PR.
Recently, I sold my 15' 2017 and bought a 15" 2018 with a 6 core cpu. The discrete gpu is essentially the same as last years, but the faster DDR4 memory, SSD, and 6 cores makes even more difference.
0 -
Erhard,
Stop, what? Providing truthful observations about PR? You are correct that other programs are not as resource intensive but this is the direction that On1 has pursued. Perhaps you should complain directly to them?
0 -
I should add that my photos are kept on an external ssd tied in via usb c. Some individual folders have nearly a thousand photos and thumbnail rendering is near instantaneous. On my 2015 13” it took tens of seconds to generate thumbnails, several seconds to open individual photos in Develop/Effects and it choked on masking. Using the same ssd via usb 3 on the 13” was nearly impossible and if I really wanted to edit successfully, I had to first transfer the photos to the internal ssd. Anytime I was editing on the 13” fans ran on maximum and if the computer was on battery power it would drain to <1% after simple edits of a couple photos. These are the facts.
1 -
I searched the On1 Technical Support FAQs for system requirements. There is nothing specifically for 2018.5 but the specs for "2017/2018" recommended hardware is a core I5, 16GB of RAM and OpenGL 4.2 compatible video card with 1GB video RAM and 1920 x 1080 resolution. That is pretty low end nowadays and bothy macs exceed these requirements by a wide margin. If they have increased the recommendations for 2018.5 they should say so. If they now require a "high-end" machine to run the software they just lost a lot of business and have pissed off a bunch of current customers. I have in fact submitted a support request and they even contacted me to ask if the latest update has helped (it didn't and I told them so).
On my systems I can browse and process images, but the fans spin up and it is annoying. Seems to me they need to fix this or they will loose customers. If they want to continue to use the GPU heavily (and I think this could be a good idea) they need to make it work efficiently - Apple now is recommending moving from OpenGL to Metal, and that might help. The downside to this is that Metal only really works well on recent systems (and by recent, I mean models from the last two years) - so that puts us back to the situation of having to buy new hardware. I plan to get a new iMac27 when the new models are released this fall, but how many photographers want (or can) afford a $3K machine?
David
1 -
David, at some level you will need to take a leap of faith. Who do you believe? The folks marketing and trying to sell you something or the end users who are making real world observations? While you implore On1 to "fix this" they are either working on it, unwilling, or unable to troubleshoot it.
From a larger perspective, On1 migrated from a modular system to an all in one integrated platform. They built more and more features into the program and rewrote the code to improve efficiencies in the 2018 releases. There are several apparent issues; either the code requires cutting edge hardware to implement or the coders are out of their element (some will advance LR, Affinity, and other programs as evidence). Either way, one has to make their own decisions about the direction of the software.
0 -
Well,I bought a year of ON1 Plus. At the end of that time I can decide to stay or leave. I was attracted to ON1 primarily because I liked the way they let you use the file structure to “catalog” your files. I don’t have heavy requirements for image editing - most of the time I am happy with the jpegs out of my current cameras (Sony A7RM3 and RX100M5). I have been going back to shots from 10+ years ago with Canon Digital Rebels in often difficult lighting situations. For this I am drawn to software that lets me batch process images (DxO, Perfectly Clear, etc.) so I am not stuck with ON1. One very promising product is RawPower which is adding batch processing and a file manager to the next version.
Anyway, I understand that software is hard and I want to give them a chance to make this work. Judging from the comments I am seeing, and the fact that both my systems have the same problems I know this is a serious problem. I hope they get it fixed. If not, there are obvious alternatives. And, I’m not buying a new iMac27 just to make this software work. (I doubt if it would help now anyway.)
David
0
Please sign in to leave a comment.
Comments
61 comments