In order to display the available fonts faster in the font dropdown menu, these fonts are cached as an XML file when you open a Text node's properties panel. I cleaned up some old fonts, deleted several others, deleted ones I don't need, used FontNuke to delete font caches, rebooted, and now FileBot works.The FreeType library used by the Text node supports a large number of fonts, including TrueType, OpenType, and PostScript fonts. I checked those specific error fonts and they didn't look weird or have any permission errors. The fonts errors on Console were a few, but not all my fonts, they were about 30-40, and randomly selected it seems. I did some reading and apparently Sandbox on macOS has limits to how many fonts can be activated at once(?) or how many fonts can be activated or loaded up within one app(?), one or the other is what I understood. I also noticed FileBot took some time to start up.Īt work, I put the fonts folder (that's in Dropbox) in a compressed file, and deleted the folder and emptied the trash, and FileBot worked on my work computer! I came back home, did the same, and it worked too! Not only that, but when it was sorted, FileBot would start up much faster, like almost instantly as opposed to ten or more seconds. Don't have RightFont installed on my new laptop though. My work computer, home computer, and laptop have Dropbox installed and have all my files synced up. I thought this might be a fonts issue, only thing I did since I purchased FileBot was that I installed RightFont and put all my fonts in Dropbox, they're all activated, at about 3,000~ fonts. That's why I never noticed them before, I always launched Console after FileBot was up and running. Those line items only appear when FileBot is starting up, not afterwards. When I installed FileBot on my work computer, I noticed this in Console. Run FileBot and drop in Movies folder, Match and Rename and see if that works Go to Movies folder and create empty file "Avatar.avi"Ĥ. I don't understand how it could possibly not work on a pristine factory reset system.Ģ. Maybe your account name? Maybe your physical location? Maybe the CIA is hacking you? Maybe a cosmic ray flipped a bit? I honestly have no idea. so no clue what might be different for you. So you're saying you've tried it on the a factory reset 100% pristine with no extra software installed latest version of macOS and it doesn't work? That would mean that it fundamentally doesn't work, for anybody, yet it seems to work for mostly everyone else. But if somehow folders get created by FileBot doing something, then it's probably somehow indirectly related, somewhere deep inside macOS, some strange bug. It's most certainly a sandbox-related issue, but that's on the macOS side, that I can't do much about.įileBot couldn't possibly create folders in /Volume since the sandbox would deny permission to do that as well. Here's a short video of me replicating this with the errors in Console. Here's what I think, when I try unlocking a folder, I get these messages in the Console, I'm pretty sure it's being blocked by the Sandbox. I used the same video file along with another one too, put them on Desktop and the error still appears. I just installed FileBot on a new MacBook I got last week (clean install), barely touched. Strange indeed, but I think what's more strange is how the same error can be replicated locally without any network shares involved. When the unlock dialog pops up, and I drag the folders required inside the "Media" share, it's only then when those folders are created, they're not created before that point. A Factory Reset would probably solve the problem.Īs for the screenshot, those folders did not exist before pressing "Rename" on FileBot. Note that FileBot works for me and everyone else, so there must be something that's different on your system. No change in the code of FileBot could possibly magically solve this issue on your machine, since FileBot is working correctly, yet denied access by the operating system.ĭo you have a second Mac (preferably clean install) you could try FileBot on to see if it works there? Problem is that there's absolutely nothing I can do about it. It could be anything, maybe a strange internal issue of macOS. My guess would be that your system is screwed up in some strange way. My next step would be trying this on a second clean computer, to see if it works, so you can narrow down the issue to either your machine, or the NAS. Why are there folders Media-1 to Media-4? Can you open them with Finder? Did you create them? If macOS shows "Access Denied" on a folder icon on a mount folder, then I don't think that it's related to FileBot, since FileBot is not running and has not created or touched these folders. This looks strange to me, having 5 folders for the same share. This screenshot shows macOS mount folders, so they haven't been created by FileBot, but by macOS when you mounted the network share:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |