4/2/2023 0 Comments Gfxcardstatus 2015 mac![]() I'm saying that it's not unreasonable for a manufacturer to make some tradeoffs like that when there are workarounds that work fairly well. But that would add to the cost of the laptop for every user, even the ones that don't care about having really high-quality audio on their laptop. OF COURSE having better speakers (equivalent in sound quality to the bluetooth workaround) in your laptop would be better if you care a lot about audio quality. What I'm trying to say is that if really good audio quality is important to you, then having a couple of sets of bluetooth speakers in your house strategically placed in the places where you'd regularly watch movies or consume other high-quality audio is a reasonable workaround for a lot of people. I'm not suggesting in any way that carrying around a speaker everywhere is a good idea (it's not). I'm trying to say that carrying around a bluetooth speaker IS impractical (and the initial criticism of it a type of strawman argument because it's obviously impractical). I think you've misread/misunderstood my comment. Lighter is OK, but not at a huge battery life cost compared to the 2015. Then the amount of dog and cat hair (that magically gets everywhere) that's been removed from our keyboards over the years. Dust sensitive? LOL I think back to when the kids were little and throwing rusks, or putting toast in the VCR the moment we blinked. The newer thinner keyboard was both horrible and horribly unreliable. Perhaps I have the wrong sort of fingers again. The touchbar was constantly activating when I typed on the top row of physical keys. Perhaps I have the wrong sort of fingers. ![]() Larger trackpad was so large I would constantly get false activations when typing. The rest seems to come with a cost far worse than the benefit (for me anyway). They always seem to break or get lost at the moment you're sitting with the important client. I still need to use USB sticks and SD pretty frequently and have always hated bags of adaptors. My next Macbook will probably be a Thinkpad way things are going. Hopefully others seeing the same behavior will file support cases so P1 has more data to go on.I updated from 2012 to 2016, hated and sold it after a couple of keyboard fails, and bought a 2015. I'd hoped 12.1.2 would fix it, but it didn't. ![]() I reported the problem to Phase One a little over a month ago (I'm a very late Mojave adapter) and after trying everything Support suggested, was told that the case was forwarded to Engineering. The only downside is that since gfxCardStatus apparently isn't supported anymore, there's no telling how long it will continue working (my guess is as long as Apple remains on Intel processors) I've read that disabling Automatic Graphics Switching (Energy Saver pref pane), makes the MBP use only the Discrete GPU, but I've never tried this method. Just remember to quit that app after you're done with C1 or you'll remain on the GPU.ģ. For example, Photoshop, Aperture, Pixelmator. Before launching C1, launch another app that calls the GPU. Driving the display automatically forces the MBP to use the discrete GPU.Ģ. Two other ways I know of to activate the GPU:ġ. A friend's running it on a 2015 MBP with Mojave and says it's fine (he's the one who got me onto it). I'm running gfxCardStatus on both a 2012 and a 2019 MBP, both with discrete + embedded GPUs, both running 10.14.6. Wondering if I should try it on my iMac, I'm suspicious that Capture One does not use the graphics card as the load on the GPU is never very hgh, and doesn't increase when Capture One runs. The documentation for gfxCardStatus says it requires a 2008-2012, 15-17" dual-GPU MacBook Pro Does it run on other HW as well? It sure would be nice if at least the GPU problem got solved in v12, as well as fixing whatever got broken with plug-ins (sounds like a C1 issue since apparently plug-ins from several vendors are affected). Is anyone else seeing C1 not invoke the GPU under Mojave? And if so, have you filed support cases? I have a friend running Mojave on a MBP who also finds the GPU issue I did. I'm now forcing the GPU before launching C1 using gfxCardStatus. Like the previous version, C1 12.1.2 isn't invoking the GPU on a 2019 MBP running Mojave, but does on a 2012 MBP running Sierra. I just submitted a Support Case.Īlso submitted a Support Case about GPU support. Same here: While Open With loads, Helicon Focus doesn't.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |