So, I've had Mojave since July. It hasn't been bad. I've liked it so far. I got a batch of updates a few weeks ago and now I get the beach ball/color wheel thingy all the time. Copying an empty file? Beach ball. Open a file? Beach ball. Rename a file? Beach ball.
I couldn't stand it so convinced the owner to buy me more ram. I now have 32GB of DDR4 ram and am still getting the beach balls of doom for seriously anything and everything on my computer. Opening pallets in adobe programs, changing tools in pitstop, opening files (possibly unrelated, but I sometimes have to double click on a file multiple times to get it to open once), dragging a file into XMF, changing file location in finder, doing anything in finder. I don't get it. Restarts do nothing. Onyx does nothing. I have 34 fonts installed so that can't be it. My trash has 50 GB in it, but it's holding files I am not completely sure I want to delete just yet - I set it to delete after 30 days.
I have no idea why this is happening. Disk Utility First Aid says my hard drive is OK.
Do you have the very old free edition of Linotype Font Explorer on it? If so...get rid of it. It causes major issues in Mojave.
If you don't have that try creating a test admin account. Log into it and see if the issue persists. If not there is probably some kind of corrupt file in the user account you are using now. Had the same issue with a freshly formatted SSD with a clean install of Mojave recently. After getting it setup with all necessary apps it was unusable doing the exact same things. Created a new account and everything works fine in the new user account.
If the new account does do the same thing there is probably a corrupt file in the system folders.
I have seen corrupt fonts create havoc as well but it is dangerous to remove any font files from Macintosh HD/Library/Fonts or Macintosh HD/System/Library/Fonts. Be careful in there.
I still use Linotype font explorer. I am still on Sierra but will have to update after the Christmas rush to the latest. I can't update Indesign etc. and I hate converting .idml files. Then I'll be dealing with other issues I'm sure, like updating other programs.
Any advice for a font management program?
Suitcase Fusion 6 plays well with Mojave for us...
Quote from: Joe on December 02, 2019, 08:47:30 PM
Do you have the very old free edition of Linotype Font Explorer on it? If so...get rid of it. It causes major issues in Mojave.
If you don't have that try creating a test admin account. Log into it and see if the issue persists. If not there is probably some kind of corrupt file in the user account you are using now. Had the same issue with a freshly formatted SSD with a clean install of Mojave recently. After getting it setup with all necessary apps it was unusable doing the exact same things. Created a new account and everything works fine in the new user account.
If the new account does do the same thing there is probably a corrupt file in the system folders.
I have seen corrupt fonts create havoc as well but it is dangerous to remove any font files from Macintosh HD/Library/Fonts or Macintosh HD/System/Library/Fonts. Be careful in there.
No Linotype or any other font management software at the moment. I'm using a shortcut to my ~/Library/Fonts folder and just dropping them in there as I need them, then deleting.
I'll try making another user folder and see if that fixes it. Would be very interesting if it is the issue.
New question... I'm setting up a new user account on my machine... Can I log into Pitstop with the same credentials or do I need to log out of the other user and then log into the new one?
Thanks!
Same credentials. You will probably still be logged in when you go to use Pitstop. It should just work without you having to do anything. Same for Adobe CC.
Thanks Joe!
So far the new user account is working much nicer. I wish I could peg down what the culprit was so I could avoid this in the future but sheesh, I don't think I ever will.
Since you have an account that works well now you could always go back to the original account and start deleting things to see if it is something that could be fixed. I would start with preferences. Notably Apple prefs since it seems to happen system wide. I would start with Finder prefs.
Alright. I'll give that a shot.
Thanks Joe!
Things have been working so well so far on the new admin account I haven't switched back.
I've kept pretty much everything default. With that said, it should be safe to turn on right click right? I'm even getting used to Apple's "Natural" scrolling - which is in no way natural.
Edit... Why is secondary click off by default? It didn't bother me not being on, my left hand is right there anyway for shortcuts for copying while dragging and other hotkeys in the adobe apps, but it has me curious.
Right click and unchecking Apple's unnatural natural movement shouldn't affect anything.
Cool. Thanks Joe!
Quote from: AaronH on December 03, 2019, 11:51:12 AM
Quote from: Joe on December 02, 2019, 08:47:30 PM
Do you have the very old free edition of Linotype Font Explorer on it? If so...get rid of it. It causes major issues in Mojave.
If you don't have that try creating a test admin account. Log into it and see if the issue persists. If not there is probably some kind of corrupt file in the user account you are using now. Had the same issue with a freshly formatted SSD with a clean install of Mojave recently. After getting it setup with all necessary apps it was unusable doing the exact same things. Created a new account and everything works fine in the new user account.
If the new account does do the same thing there is probably a corrupt file in the system folders.
I have seen corrupt fonts create havoc as well but it is dangerous to remove any font files from Macintosh HD/Library/Fonts or Macintosh HD/System/Library/Fonts. Be careful in there.
No Linotype or any other font management software at the moment. I'm using a shortcut to my ~/Library/Fonts folder and just dropping them in there as I need them, then deleting.
I'll try making another user folder and see if that fixes it. Would be very interesting if it is the issue.
You really find that this is a good alternative to using a dedicated font management utility?
Quote from: pspdfppdfxhd on December 05, 2019, 04:03:30 PM
You really find that this is a good alternative to using a dedicated font management utility?
That is how I roll too. You can actually create customer folders inside of there and move them in and out as needed. A poor mans font management system.
Quote from: pspdfppdfxhd on December 05, 2019, 04:03:30 PM
You really find that this is a good alternative to using a dedicated font management utility?
It works rather well actually. I haven't gotten as crafty as it as Joe has, but if I'm having problems getting indesign to recognize the fonts that came packaged with it, I'll drop them into my user fonts folder and then it will usually recognize they're there. It doesn't happen that often though.
There is a known Apple issue between processors where the font name is recognized differently. You could have 2 Mac Pros, almost identical in every way, running the same OS, but the processor is different and it will see the font on one and not on the other. For example on one Mac Pro it might look like: Helvetica Bold and on the other: Helvetica Bold (OTF)
I run into something like this all the time with my customer's fonts. They'll supply packaged files with TTF fonts, and InDesign will ask me to find TTF fonts. I usually have to remap them to the ones that are listed in the font list. Makes no sense. They're still TTF fonts.
Just to repeat....
FONTS ARE EVIL!!!!!
TOOLS OF THE DEVIL!
:dev2:
Quote from: AaronH on December 06, 2019, 12:11:59 PM
I run into something like this all the time with my customer's fonts. They'll supply packaged files with TTF fonts, and InDesign will ask me to find TTF fonts. I usually have to remap them to the ones that are listed in the font list. Makes no sense. They're still TTF fonts.
yeah
like that
:banghead:
Quote from: Joe on December 06, 2019, 12:18:00 PM
Just to repeat....
FONTS ARE EVIL!!!!!
TOOLS OF THE DEVIL!
:dev2:
It's been about 10-12 years ago, but I had the biggest problem with Quark. I don't know how I figured it out, but there was a corrupt font on my system (not 100% but I think it was a system font) that kept Quark from launching. Deleted it, and all was well again. Peace and Harmony.
I haven't touched a Quark file in 3-4 years.
Fuck Quark. Fuck fonts.
Quote from: DigiCorn on December 06, 2019, 12:25:36 PM
Quote from: Joe on December 06, 2019, 12:18:00 PM
Just to repeat....
FONTS ARE EVIL!!!!!
TOOLS OF THE DEVIL!
:dev2:
It's been about 10-12 years ago, but I had the biggest problem with Quark. I don't know how I figured it out, but there was a corrupt font on my system (not 100% but I think it was a system font) that kept Quark from launching. Deleted it, and all was well again. Peace and Harmony.
I haven't touched a Quark file in 3-4 years.
Fuck Quark. Fuck fonts.
Agreed.
An older prepress guy I used to work with used to say that when he was going to take over the world (of printing/design), he would make it so computers came packaged with the same fonts, regardless of OS, and that there would be a finite number of them and all font websites and all font design software would cease to exist.
No doubt this would still have hiccups and issues.
Quote from: DigiCorn on December 06, 2019, 12:25:36 PM
Quote from: Joe on December 06, 2019, 12:18:00 PM
Just to repeat....
FONTS ARE EVIL!!!!!
TOOLS OF THE DEVIL!
:dev2:
It's been about 10-12 years ago, but I had the biggest problem with Quark. I don't know how I figured it out, but there was a corrupt font on my system (not 100% but I think it was a system font) that kept Quark from launching. Deleted it, and all was well again. Peace and Harmony.
I haven't touched a Quark file in 3-4 years.
Fuck Quark. Fuck fonts.
I have a co-worker that Quark 8 crashes at launch. I am suspecting a font. But there are like 78 bazillion fonts loaded on that machine. So no more Quark on that machine. THE END!
Quote from: DigiCorn on December 06, 2019, 11:49:29 AM
There is a known Apple issue between processors where the font name is recognized differently. You could have 2 Mac Pros, almost identical in every way, running the same OS, but the processor is different and it will see the font on one and not on the other. For example on one Mac Pro it might look like: Helvetica Bold and on the other: Helvetica Bold (OTF)
Is
that why the fuck that happens?? I had one just the other day, various iterations of Robot used throughout, InDesign claimed they weren't loaded even though they were right there in the Document Fonts Folder so I meticulously remapped all those bastards.
Revised (Packaged) file came in today - no issue whatsoever even though I used the entire
new Packaged Folder supplied.
:facepalm:
Fonts, are how you really know a seasoned Prepress operator. Ask them about fonts, and sit back and listen. If they don't stand on a soap box :cane: for at least 5-10 minutes, they haven't been in the "oven" long enough. Time to throw'em back in for a while. :gom:
#thebadolddays
Quote from: scottrsimons on December 10, 2019, 08:44:02 AM
Fonts, are how you really know a seasoned Prepress operator. Ask them about fonts, and sit back and listen. If they don't stand on a soap box :cane: for at least 5-10 minutes, they haven't been in the "oven" long enough. Time to throw'em back in for a while. :gom:
Hell, I can do 25 minutes on Apple's System Helveticas alone... Don't get me started.... :gom: :gom: :gom:
My favorites now are Lato and pretty much anything else that is an Adobe Typekit font.
:sarcasm:
75% of the time if not more, it'll recognize you need it, download it from the site, then it says its a different format. Usually OTF.
:facepalm:
Alright, its been a month since I changed to a new Admin user on the Mac. I am running minimal apps (Adobe stuff, Pitstop 2020, Microsoft office, XMF and amazon music), regularly run without fonts in the user font folder and am still having issues.
I can't save files, open files, change what app is in focus, sometimes even typing without getting a beachball that lasts anywhere from 5 seconds to a minute or sometimes longer. I'm at a loss for what to do.
The new profile worked great for a short while but it has progressively gotten worse overtime.
went back and reread this...
what mac are you using?
Laptop or iMac?
Its an iMac Retina 5K, 27 Inch, 2017 model with a 4.2 GHz Intel Core i7, 32 GB 2400 MHz DDR4 memory and a Radeon Pro 575 4 GB graphics card.
Quote from: AaronH on January 16, 2020, 03:53:04 PM
Alright, its been a month since I changed to a new Admin user on the Mac. I am running minimal apps (Adobe stuff, Pitstop 2020, Microsoft office, XMF and amazon music), regularly run without fonts in the user font folder and am still having issues.
I can't save files, open files, change what app is in focus, sometimes even typing without getting a beachball that lasts anywhere from 5 seconds to a minute or sometimes longer. I'm at a loss for what to do.
The new profile worked great for a short while but it has progressively gotten worse overtime.
How much RAM is in this Mac and what configuration is it, ie...16 GB RAM might be two 8 GB RAM modules.
I'm just wondering if you might have a bad RAM module. As a test if you have 2 or 4 ram modules try removing one at a time and use it for awhile and see if it gets better. If it does that particular RAM module could be bad.
On the issue of "I can't change what app is in focus," I run into that sometimes with Mojave when selecting an app with the mouse. My fix to use to COMMAND+TAB to go to a different app and then do it agian to switch back to the app that couldn't get the focus before. That usually works.
Desperate measure to is to downgrade back to High Sierra or Sierra and I've been contemplating that for awhile because clearly Mojave sucks hard.
Quote from: AaronH on January 16, 2020, 05:17:53 PM
Its an iMac Retina 5K, 27 Inch, 2017 model with a 4.2 GHz Intel Core i7, 32 GB 2400 MHz DDR4 memory and a Radeon Pro 575 4 GB graphics card.
You have the exact same Mac as mine except I only have 16 GB of RAM and I'll tell you I haven't been happy with it since day one. I upgraded from a 2013 iMac with an older, slower i7 CPU and Fusion drive and this damn thing is slower than my old Mac was. So I added an SSD drive. Still slower than the old iMac with the Fusion drive which makes no sense.
I just ordered a new 2019 iMac for my owner this week and it only has an i5 CPU with a Fusion drive and 8 GB of RAM and it is faster than my damn iMac with the i7 CPU.
I'm seriously contemplating downgrading to High Sierra. Have to stick with High Sierra and above because Adobe 2020 apps won't work on Sierra.
Just trying to figure out now when I have time to do it and make the bootable USB installer.
Quote from: Joe on January 16, 2020, 05:27:38 PM
Quote from: AaronH on January 16, 2020, 05:17:53 PM
Its an iMac Retina 5K, 27 Inch, 2017 model with a 4.2 GHz Intel Core i7, 32 GB 2400 MHz DDR4 memory and a Radeon Pro 575 4 GB graphics card.
You have the exact same Mac as mine except I only have 16 GB of RAM and I'll tell you I haven't been happy with it since day one. I upgraded from a 2013 iMac with an older, slower i7 CPU and Fusion drive and this damn thing is slower than my old Mac was. So I added an SSD drive. Still slower than the old iMac with the Fusion drive which makes no sense.
I just ordered a new 2019 iMac for my owner this week and it only has an i5 CPU with a Fusion drive and 8 GB of RAM and it is faster than my damn iMac with the i7 CPU.
This machine feels kinda like a lemon too. Not sure what to do with that though. My co-worker's Mac is a 2011 and is due for an upgrade but I'm almost considering switching us over to windows with all the issues we have with file server crap and everything here. That probably won't fix anything really though and would probably make more issues.
I was hoping I could get my new file server approved by management but no luck and am still having fonts with Zero KB size issues. Hard to work from your desktop and copy files to the server if your customer has a change later if you get rid of the desktop files later. As a work around I'm copying all fonts to a Font Library folder in my user folder then copying them to ~/Library/Fonts as needed - wish I didn't have to though.
Also having beach balls on a mac mini running Mojave. It's something network related for sure. 2 other machines on Mojave and they are fine. Besides the standard Adobe / Pitstop stuff, the similar stuff I have to AaronH is I'm also running XMF and have a NAS unit. Can't really not use the NAS, but have you noticed if the beach balls occur when running XMF? I never trust java apps. I'm going to run without it for the week and just use one of the other workstations when needed. Might be a driver issue and XMF/java network access on newer Apple machines.
Quote from: seratne on January 20, 2020, 11:35:27 AM
but have you noticed if the beach balls occur when running XMF?
Yeah I was getting beach balls with everything, including XMF.
I went ahead and downgraded the iMac to High Sierra. That was a PITA. High Sierra doesn't install on APFS drives, so you have to Partition it to MacOS Extended (Journaled), which will then wipe the drive and do it correctly. Then I had to try to install High Sierra several times, because the Mac for some reason wanted to boot from the hard drive and not the attached USB stick to finish the install. Let it sit over the weekend and this morning it worked like a charm. Now I have just a couple adobe apps to finish installing and get Pitstop up and running and I'm back to where I was a 4:00 on Friday (But with a stable system hopefully).
Well, I have no idea what is wrong with this iMac. Everything I do causes it to throw beachballs at me. Copying an empty 6kb folder to the network share takes 30 seconds to a minute to do, and that's the fastest thing this machine will do. Opening an indesign file takes ages, then once it's open, it kinda runs fine unless you want to access any of the menu items up top, then nope, beachball for several minutes.
This is on top of a fresh reformat (zeroing out the HDD too) recently. I have no idea what to do.
If it still under warranty I would call Apple support about it. They either need to fix it or replace it.
Good idea. I don't know why I forget about AppleCare sometimes.