QUICKSCRIBE IS CORRUPTED AFTER INSTALLATION TO 10.6

[frankymax]

How weird- Font Finagler worked fine for me on 10.6.1 and DP7. I never had DP6 installed. I upgraded directly from Dp5.13 and 10.4.11 to 10.6, then 10.6.1, then installed DP7- I had the same problem with quickscribe looking like Greek, but the bar numbers and text were okay, just notes and clefs were wrong. I did the DP6 Quickscribe updater at MOTU's website- it made the notes appear on screen but not print- I emailed Tech Support and was told to download Font Finagler and run it- I did and presto, it worked for me. I was also told NOT to show the quickscribe font in any of the font folders but that it should reside in the Package Contents/Resources- it's a file called QuickscribeX- I don't know why you guys aren't getting Font Finagler to work- I think I used a beta version that they had on-line. I'm not on my studio computer but I'll look for it tomorrow and try to post a link.

[frankymax]

Frodo- et al:
here's where you can get the Font Fingler beta (it worked for me!)

http://homepage.mac.com/mdouma46/fontfinagler/

good luck
-Frank

[Frodo]

I fixed the problem by removing DP6.01 and moving it to my other Hard Drive. I left DP6.02
on my application drive and then ran the Motu Font Installer and it now works! Wow...can't believe I fixed it.

How many box tops and proof of purchase seals did that take? I'm still struggling, having already uninstalled 6.01 and 6.00 post 6.02.

Now, I'm uninstalling everything related to DP6 to start from scratch.

MOTU's update itself may be spot on, but they really failed with the installer. I have no shame in saying it and I stand by my statement. This installer (not the update) is a potential failure. YMMV.

I have yet to get back up to speed-- still working on it.

[Shooshie]

Yeah, moving other copies of DP off the hard drive is essential to make this stuff work. It can only find the one copy that you're trying to change.

Essentially, here's what you have to end up with:

1. A copy of QuickScribe Font (TrueType) in the USER font folder. (not the global font folder; in fact, there can only be one copy of the font on your system, if memory serves me correctly) [EDIT: A tech support person has told the original poster that this step is not only unnecessary, but could cause problems. In my case, it would not work originally in 6.02 when I ran the MOTU Font Installer until I placed this font in this folder as described above. I leave it to you to decide whether you need Step 1 or not.]

2. A copy of QuickScribeX Font (TrueType) inside Digital Performer. CONTROL-CLICK the app, pull down the contextual menu to "Show Package Contents," then go to Contents/Resources and drop the QuickScribeX font into the Resources Folder.

Done. (if the moons of all the planets are in alignment with the galaxy's core)

Here's the whole thing, graphically. In the "Get Info" windows you will see the dates on the fonts (they're old, not some late model) and you'll see the path to where each resides.

Inside the DP Package, the QuickScribeX Font Lives in the Resource Folder

Get Info for QuickScribe Font in the User Font Folder (path is on the window)

Get Info for QuickScribeX Font inside DP.App (path is on the window)

For Moral support, here's QuickScribe at work in amplidood's Night Mod version of DP7.01, just a few days old. I just don't want anyone thinking that I'm leading you on a wild goose chase. The font does work, in the end.

Be sure there are no other copies of the QuickScribe or QuickScribeX fonts on your drive. If the problem persists after the above steps, do the Mac Safe-Boot, then reboot normally to reset the computer's font cache.

Shooshie

PS: This whole issue is a failing on both Apple's and MOTU's parts. Apple caused it. MOTU should have written their installer and/or instructions better. They probably did not realize the extent of Apple's goof in Snow Leopard, as regards fonts. It was major, and I'll be surprised if there are no lawsuits slapped on Apple by print and design industries.

[frankymax]

hmmm. I didn't have to get rid of DP5 or DP7.0 when I did the font updater and then Font Finagler for DP 7.01 and it worked for me- I guess I was just lucky. Sorry to hear of your troubles, Frodo. I hope you get it up & running soon.

[Frodo]

Yeah, moving other copies of DP off the hard drive is essential to make this stuff work. It can only find the one copy that you're trying to change.

Essentially, here's what you have to end up with:

1. A copy of QuickScribe Font (TrueType) in the USER font folder. (not the global font folder; in fact, there can only be one copy of the font on your system, if memory serves me correctly)

The QSTTF is nowhere to be found. I'll try to bring over this font from my other machine (if it can be located).

2. A copy of QuickScribeX Font (TrueType) inside Digital Performer. CONTROL-CLICK the app, pull down the contextual menu to "Show Package Contents," then go to Contents/Resources and drop the QuickScribeX font into the Resources Folder.

Yes, QSXF is in this location.

Done. (if the moons of all the planets are in alignment with the galaxy's core)

Here's the whole thing, graphically. In the "Get Info" windows you will see the dates on the fonts (they're old, not some late model) and you'll see the path to where each resides.

Inside the DP Package, the QuickScribeX Font Lives in the Resource Folder

Get Info for QuickScribe Font in the User Font Folder (path is on the window)

Get Info for QuickScribeX Font inside DP.App (path is on the window)

For Moral support, here's QuickScribe at work in amplidood's Night Mod version of DP7.01, just a few days old. I just don't want anyone thinking that I'm leading you on a wild goose chase. The font does work, in the end.

Be sure there are no other copies of the QuickScribe or QuickScribeX fonts on your drive. If the problem persists after the above steps, do the Mac Safe-Boot, then reboot normally to reset the computer's font cache.

Shooshie

Did the safe boot a couple of times-- no dice. This is so strange!

PS: This whole issue is a failing on both Apple's and MOTU's parts. Apple caused it. MOTU should have written their installer and/or instructions better. They probably did not realize the extent of Apple's goof in Snow Leopard, as regards fonts. It was major, and I'll be surprised if there are no lawsuits slapped on Apple by print and design industries.

I have to agree with this. That the 6.02 Font Updater didn't do the trick is just as troubling as the fact that it had to be done at all. That the Font Updater proclaims a successful install and it still doesn't work renders it an unfair assessment.

It seems to be another one of those simple processes that works for some but not for others. I actually don't mind doing things manually if necessary (if I have the time), but when the manual fixes do not work it's a real bummer.

I've got a couple more tricks up my sleeve, though.

[frankymax]

Again, I don't mean to be a PITA, but the MOTU person I worked this out with said you must not have quickscribe font anywhere but in the Resources folder of the app. Also, I definitely got Font Finagler to fix this on SNOW LEOPARD by using the beta version at the website I posted above. Please try Font Finagler one more time Frodo.

[Frodo]

Didn't need FontFinagler. I got to to work, finally.

I encountered a couple of quirks, though.

1. There is no QuickScribe TTF on any of my system drives. I checked my three system drives on my MacPro tower and no TTF exists on any of them-- BUT the fonts in QuckScribe all work fine without it.

2. We've installed apps in the root directory as well as in the User directory. Apparently, the Font Update will only work if DP is in the root applications directory--- at least that was the key for me. I'm just not sure where others have the DP app installed, or whether those who have had trouble with the Font Updater for 6.02 likewise do not have DP located in Macintosh HD> Applications. I suppose one could just move DP to that location, run the Font Updater, then move it back-- OR-- one could make an alias of the DP app icon and move the alias elsewhere. Of course, the Dock works well for this, but sometimes it's nice to have an alias of the app itself somewhere in the user directory-- imho.

3. This is inexplicable, but when repairing permissions I get the old SUID warning I once saw in Leopard's early days:

Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.

A lot has been written about this, but ARDAgent is apparently part of Remote Access. Some have suggested removing it. I use Remote Desktop and never had this warning with 10.5.8 on my LAPTOP, only on my MacPro. I don't recall which version of 10.5 fixed this problem on my MacPro, but the warning is now routine on the laptop with each run of permissions repair. Grrr.

And-- repairing permissions and emptying the Trash in 10.6.2 are SLLLOOOOOOWWWWWW!!

In any case, the font issue has been resolved.

[AllanKane]

Just have DP 6.02 on your system hard drive. Drag 6.01 to another drive and then install the Motu Font Fixer and it will work.

[Frodo]

Just have DP 6.02 on your system hard drive. Drag 6.01 to another drive and then install the Motu Font Fixer and it will work.

That was but one of the things I had to do. There other things which can prevent it from working, though.

[Shooshie]

Just have DP 6.02 on your system hard drive. Drag 6.01 to another drive and then install the Motu Font Fixer and it will work.

That was but one of the things I had to do. There other things which can prevent it from working, though.

See? That's what's been such a bear about solving this stupid problem. EVERYTHING seems to have multiple states of work/fail conditions and outcomes.

Like the QuickScribe font in my user folder. When I used the MOTU Font Fixer, it did not work until I put that font there. If the font was in the global font folder, it failed. If there was NO QS font in the system, it failed. But when I put it in my user folder, it worked. And I'm talking "in addition to" the QSX font in the app package's Resources folder. I'll remove QS from my fonts folder and see if that causes any problems now. I doubt that it will be a problem. But then... on second thought, maybe I'll leave well-enough alone. Not to be superstitious, but the fact is that there is still more that we don't know about this simple, silly problem.

Shooshie

PS: Yes, DP has to be in the Applications folder. In OSX I quickly gave up trying to have my applications like OS9, anywhere I wanted them. They all go in the Applications Folder, and I use aliases or the Dock to access them easily from where I want. Frankly, I like this way a lot better now.

[James Steele]

Since upgrading to 10.6, my quickscribe has been corrupted with very strange Greek letters
and fonts. I upgraded from the Motu site. Can anyone suggest a fix here?

Please check your CAPS key. It appears to be stuck.

[Frodo]

See? That's what's been such a bear about solving this stupid problem. EVERYTHING seems to have multiple states of work/fail conditions and outcomes.

Like the QuickScribe font in my user folder. When I used the MOTU Font Fixer, it did not work until I put that font there. If the font was in the global font folder, it failed. If there was NO QS font in the system, it failed. But when I put it in my user folder, it worked. And I'm talking "in addition to" the QSX font in the app package's Resources folder. I'll remove QS from my fonts folder and see if that causes any problems now. I doubt that it will be a problem. But then... on second thought, maybe I'll leave well-enough alone. Not to be superstitious, but the fact is that there is still more that we don't know about this simple, silly problem.

Shooshie

PS: Yes, DP has to be in the Applications folder. In OSX I quickly gave up trying to have my applications like OS9, anywhere I wanted them. They all go in the Applications Folder, and I use aliases or the Dock to access them easily from where I want. Frankly, I like this way a lot better now.

Dude- there are so many considerations that it makes me dizzy any more. It's one thing to have an app in one place on one's system and it's another thing to have it in another place on another's system; different steps to effect the same solution.

Perhaps if I suffered from the more youthful symptom of ADD I'd understand it all-- you know where they just toss a bunch of garbage into the equation and expect you to understand it all, but I fear that my signs of getting old (and quite reluctantly) are starting to get the best of me.

Well, duh... why WOULDN'T one put all their applications in the Applications Folder?

Because, Apple once said that we could install applications anywhere we wanted. That's why.

My applications folder looks like crap now. I haven't reorganized it into the folders which might separate the less-frequenty accessed OSX apps like Chess, Automater, PhotoBooth, Main Menu, and so on, from apps that actually mean something to me.

Anyway, I'm flying high right now. I got all my versions of DP working slicker-n-snot in 10.4.11, 10.5.8, and 10.6.2.

I can't be *that* old yet-- or.....?

[frankymax]

Like the QuickScribe font in my user folder. When I used the MOTU Font Fixer, it did not work until I put that font there. If the font was in the global font folder, it failed. If there was NO QS font in the system, it failed. But when I put it in my user folder, it worked. And I'm talking "in addition to" the QSX font in the app package's Resources folder. I'll remove QS from my fonts folder and see if that causes any problems now. I doubt that it will be a problem. But then... on second thought, maybe I'll leave well-enough alone. Not to be superstitious, but the fact is that there is still more that we don't know about this simple, silly problem.

I feel like I'm beating a dead horse here and no one cares, but here's the exact email responses I received from MOTU when I had this problem:


My email #1:
"Hi - well I finally got DP 7 and 7.01 installed and overall everything is going fine. I am however, having a big issue with the Quickscribe font. When I open Quickscribe I get non- note fonts- I went and downloaded the DP 6.02 font updater for SL but it gave me an error when installing ( error 11500:2, -14) & said the error prevented the install from completing. I checked thruout my hard drive (User Library, regular Library, System Library) but no Quickscribe font seems to exist. I checked the package contents under DP7.01 and under Resources the QuickscribeX font appears but what can I do to get the font to work? Don't I need a quickscribe font in my users folder? Help, please!!"

Response #1:
Hi Frank,
Is this happening with both 7.0 and 7.01?

Control Click on the DP 7.01 Application and choose Show Package Contents. Then open the Resources folder. Unzip the attached file and drop that font into that folder. Does QS start showing the appropriate symbols now?

The QuickScribe font should never be in any of the User or System Font folders. This can cause conflicts in various versions of DP.

My email #2:
"Hi Jon- Quickscribe looks fine now on screen but when I try to print it give me an error message -9705 and then prints the page with staves, bar numbers , name of instruments, ties, but no notes! Help!!"

Response #2:
"Hi Frank,
Right, I think there's a further font conflict on your system. I would remove the QuickScribe font from the library folder and download an application called Font Finagler. Snow Leopard seems to have introduced a good number of font caching problems and what your describing sounds like one of them. Download Font Finagler and run the Clear Font Cache option. This will force a restart, but should hopefully clear up the issue for you.

Also - is this only happening with older files or new files as well? Would it be possible to get a copy of a file this is occurring with?">

,,,so as you can see from MOTU's responses, they claim the QS font should NEVER be in the Users or Systems font folders. Awright, I've gotta clean up this dead horse mess...I'm outta here...

[Frodo]

It's clear that we could use another update of SL to resolve whatever font issues remain. Someone observed a difference in certain symptoms when SL was installed over 10.5.x as opposed to doing a clean install of SL when apps were installed *after* SL was. Strangely, some who took the former approach had fewer problems with certain apps having been installed in Leopard already-- meaning that things continued to work fine for the most part whereas the otherwise conscientious approach of doing a clean install of everything presented a different combo challenges to sort out.

One of the things I didn't do on my Intel was to port over any projects prior to DP 5.12. Part of the reason why this happened was that I didn't get into VIs seriously until then, so many of my projects in DP4.x were largely OTB. I think what may be at issue on my system is that the older TTF was never cached on the new machine as a result of running older projects.

Dunno. Why things can go right or go wrong on different systems using the same sets of instructions and the same software may be a question we'll never get fully answered.