Here is what the developer of a very sophisticated OS X audio program has to say about Tiger:
I’ve been “bleeding” along with it since June 2004, and um, well, I hope a lot of progress is made on it in the next couple of weeks. We haven’t had an update for a while now, and I don’t expect one until after the 29th, so prevent illegitimate distribution of the final GM version. Same thing happened with Panther’s release. I’ll have a new MacFOH version by then which will be ready for Tiger. The current one is Panther-only, but will launch on Tiger with some bugs (ie don’t use menu key-equiv’s or it will crash)… some bugs in Panther were fixed in Tiger, and my old workaround(s) cause a responder-chain loop. This was to enable key-equiv’s in the drawer for the contextual popup menus. Tiger handles that case properly.
I would say, don’t rush just yet. Overall, many applications will seem faster, but the Finder still has many problems, and general user experience will be a bit sluggish. MacFOH ran about 15% faster the last time I benchmarked it, but that was a couple months ago and things may have changed. I have to move development to Tiger soon (still haven’t yet) and then I can use the new tools and work on the Live-Sound Toolkit databases, which will emerge in the next couple months, so hang onto your touring, rider, venue, and equipment notes! A nice side-effect of the Tiger upgrade is that all MacFOH database info will be available throughout the system and in other app’s, thanks to SpotLight metadata importers (which I will create). I won’t know if we’ll have to move entirely to Tiger, or if only certain MacFOH features will require it. Once we go public, that will be our backward-compatible version, so I think that should be v2.0 with Tiger. Hopefully most people will have upgraded during the year.
–
Shaun Wexler
MacFOH http://www.macfoh.com
Thanks for pitching in (and BTW, MacFOH looks like some cool software), but I think you may have missed the reason why I posted this link. The headline is humorously incorrect, and most of the article is indecipherable even though it appears to contain english words.
Well, I don’t usually miss the joke. What am I missing in the headline?
I seldom make fun of the abilities of persons whose native tongue is not English — especially since I speak exactly one language. It is clear to me that N. S. Nath has uncovered some problems with the audio based bits of Tiger.
And, as there seems to be some corroborating evidence that, audio-wise, Tiger is not the Second Coming of Christ (subject to final release and updates, of course), I assumed you were looking for some level of confirmation.
The headline: “Apple to Lunch” instead of “Apple to Launch“.
I’m not trying to make fun of the writer, but I am asking myself some questions. Why is someone so inept at the english language attempting to write a technical story in a language they don’t know? Why didn’t some english speaking editor look this story over and correct or reject it? What exactly is the point of this article? Why does it focus, very vaguely, on the idea that some people who use their Macs for music may have to reset some nebulous shortcuts?
But experts doubt that the Mac OS X 10.4 ‘Tiger’ will potentially throw many Mac users into turmoil especially those working in music.
What does that mean? It makes no sense. First, unnamed experts doubt Mac users will be thrown into turmoil, and the ones using music especially won’t (I guess). And then it goes on to tell us:
Many plug-ins, virtual instruments and programming and audio software packages won’t always instantly be available on the new operating versions.
So will it cause a problem or not? At first, no turmoil expected… then, a summary of something that can go wrong. No details given. How does the author know this? Tiger hasn’t been released yet. Is he violating an NDA? Is he repeating unsubstantiated speculation from someone else? Has he illegally obtained a copy? What is his source for the proclamation that musical Mac users will have to change some barely specified settings to make barely specified software work?
The new applications come with some uncommon names such as ‘Spotlight’ and ‘Dashboard’. Musicians around the world can now only hope that the latest edition will be the same plug ‘n’ play phenomenon.
April 15th, 2005 at 11:18 am
Here is what the developer of a very sophisticated OS X audio program has to say about Tiger:
I’ve been “bleeding” along with it since June 2004, and um, well, I hope a lot of progress is made on it in the next couple of weeks. We haven’t had an update for a while now, and I don’t expect one until after the 29th, so prevent illegitimate distribution of the final GM version. Same thing happened with Panther’s release. I’ll have a new MacFOH version by then which will be ready for Tiger. The current one is Panther-only, but will launch on Tiger with some bugs (ie don’t use menu key-equiv’s or it will crash)… some bugs in Panther were fixed in Tiger, and my old workaround(s) cause a responder-chain loop. This was to enable key-equiv’s in the drawer for the contextual popup menus. Tiger handles that case properly.
I would say, don’t rush just yet. Overall, many applications will seem faster, but the Finder still has many problems, and general user experience will be a bit sluggish. MacFOH ran about 15% faster the last time I benchmarked it, but that was a couple months ago and things may have changed. I have to move development to Tiger soon (still haven’t yet) and then I can use the new tools and work on the Live-Sound Toolkit databases, which will emerge in the next couple months, so hang onto your touring, rider, venue, and equipment notes! A nice side-effect of the Tiger upgrade is that all MacFOH database info will be available throughout the system and in other app’s, thanks to SpotLight metadata importers (which I will create). I won’t know if we’ll have to move entirely to Tiger, or if only certain MacFOH features will require it. Once we go public, that will be our backward-compatible version, so I think that should be v2.0 with Tiger. Hopefully most people will have upgraded during the year.
–
Shaun Wexler
MacFOH
http://www.macfoh.com
April 15th, 2005 at 11:32 am
Thanks for pitching in (and BTW, MacFOH looks like some cool software), but I think you may have missed the reason why I posted this link. The headline is humorously incorrect, and most of the article is indecipherable even though it appears to contain english words.
April 15th, 2005 at 5:15 pm
Well, I don’t usually miss the joke. What am I missing in the headline?
I seldom make fun of the abilities of persons whose native tongue is not English — especially since I speak exactly one language. It is clear to me that N. S. Nath has uncovered some problems with the audio based bits of Tiger.
And, as there seems to be some corroborating evidence that, audio-wise, Tiger is not the Second Coming of Christ (subject to final release and updates, of course), I assumed you were looking for some level of confirmation.
Silly me.
April 18th, 2005 at 1:47 am
The headline: “Apple to Lunch” instead of “Apple to Launch“.
I’m not trying to make fun of the writer, but I am asking myself some questions. Why is someone so inept at the english language attempting to write a technical story in a language they don’t know? Why didn’t some english speaking editor look this story over and correct or reject it? What exactly is the point of this article? Why does it focus, very vaguely, on the idea that some people who use their Macs for music may have to reset some nebulous shortcuts?
What does that mean? It makes no sense. First, unnamed experts doubt Mac users will be thrown into turmoil, and the ones using music especially won’t (I guess). And then it goes on to tell us:
So will it cause a problem or not? At first, no turmoil expected… then, a summary of something that can go wrong. No details given. How does the author know this? Tiger hasn’t been released yet. Is he violating an NDA? Is he repeating unsubstantiated speculation from someone else? Has he illegally obtained a copy? What is his source for the proclamation that musical Mac users will have to change some barely specified settings to make barely specified software work?
Huh?