At 9:54 AM -0800 12/31/03, Philip Aker wrote:
On Wednesday, Dec 31, 2003, at 06:25 US/Pacific, David H. Bailey wrote:
But the complaint about Finale's explode function not copying
unison sections to all exploded parts...
While I do agree with folks who think that a part-savvy Explode
should be b
At 02:41 PM 12/31/2003, Philip Aker wrote:
>"appears as two-note chords" (surely you mean dyads)
Yes, thanks. English not so good today.
>is
>precisely the point. Just because I enter in two or more layers,
>doesn't necessarily mean that it ends up looking like a typical two
>layer staff. I may c
On Wednesday, Dec 31, 2003, at 10:36 US/Pacific, Aaron Sherber wrote:
At 12:54 PM 12/31/2003, Philip Aker wrote:
>That is, two instruments on a staff = entering in two layers.
Oh, that's not necessarily true at all. Two instruments on a staff
often appears in a score as notes in two layers,
At 12:54 PM 12/31/2003, Philip Aker wrote:
>That is, two instruments on a staff = entering in two layers.
Oh, that's not necessarily true at all. Two instruments on a staff often
appears in a score as notes in two layers, but it just as often appears as
two-note chords. Or you can enter them
On Wednesday, Dec 31, 2003, at 09:40 US/Pacific, Robert Patterson wrote:
Expose (which I don't have) sounds incredibly useful for OSX, but the
OS9 Finder needs it less than the OSX Finder does. (The OS9 Finder
compensates in two interdependent ways: one is that when you click on
a window, all w
Yes, I can certainly understand the screen rotation problem.
On 31.12.2003 18:40 Uhr, Robert Patterson wrote
> The thing is, I'm still more productive in OS9. U.I. doodads are uninteresting
> to me in themselves, so I'm happier in OS9 when doing real work. Expose (which
> I don't have) sounds inc
On 31.12.2003 17:50 Uhr, Robert Patterson wrote
> I think some of the postings on this thread show a greatly exaggerated idea of
> how much time Makemusic have spent on the plugin interface. The notion that
> they are packing lots of functionality into the plugin interface at the
> expense of prog
On Wednesday, Dec 31, 2003, at 06:25 US/Pacific, David H. Bailey wrote:
But the complaint about Finale's explode function not copying unison
sections to all exploded parts...
While I do agree with folks who think that a part-savvy Explode should
be built-in, and agree with RGP's comment that it
The primary reason is screen rotation. Although there is an OSX solution out there, I
don't have the necessary hardware for it. If a more general OSX screen rotation
solution emerges, I'll probably switch. My OSX environment is getting more usable as I
configure it to my tastes and learn more ab
At 3:52 PM + 12/31/03, Robert Patterson wrote:
The real problem with Explode is that it re-quantizes. This
essentially renders it useless.
I may be wrong with the dates, but I think the re-quantization
problem with Explode goes back to version 1 of Finale. Everyone is
right that this fix sho
On 31.12.2003 17:16 Uhr, Robert Patterson wrote
> I am as frustrated as anyone over the Fin04 delay. Heck, I'm *more* frustrated
> because I use Finale in OS9 so won't be able to use the new features till
> who-knows-when.
Will you continue to use Finale in OS 9 when the X version is out? What ar
I think some of the postings on this thread show a greatly exaggerated idea of how
much time Makemusic have spent on the plugin interface. The notion that they are
packing lots of functionality into the plugin interface at the expense of program
function is laughable. The plugin interface is ess
I don't think we can read very much into the lack of posts from Coda staff on this
list. I believe Randy Stokes quit monitoring the list years ago. And I can attest that
Allen has been very busy lately: probably too busy to post. (Heck, the holidays always
suppress list activity--as one might ex
On 31.12.2003 15:08 Uhr, David H. Bailey wrote
> There isn't really a point other than that MakeMusic is screwing up and
> forcing us to pay extra money to get the product to work as it should.
>
> Yes, we need to buy these plugins.
>
> But we shouldn't have to. And the fact that core functiona
I don't think the issue of duplicating a unison line is a "bug". How is the program
supposed to know whether you want to duplicate it? Sometimes you do, sometimes you
don't. Coda could add an option, I suppose, but the TGTools Smart Dist. plugin is way
better.
The real problem with Explode is t
But the complaint about Finale's explode function not copying unison
sections to all exploded parts (or at least the ability to turn that
possibility on/off) is more like needing to use a plug-in to accurately
copy a section of a picture in Photoshop. Exploding those unisons along
with the sep
There isn't really a point other than that MakeMusic is screwing up and
forcing us to pay extra money to get the product to work as it should.
Yes, we need to buy these plugins.
But we shouldn't have to. And the fact that core functionality is being
off-loaded from the basic program code into
Aaron is completely right here. All professional programs allow plug-ins.
I´d like to add that all video editors like Adobe Premiere, Final Cut or
Avid come with a limited set in terms of effects and transitions. You have
to invest more to get those fancy things that you see in the Superball.
I i
David, what would you say about Photoshop, which has gobs of plugins from
all kind of sources? That it was piss-poor programming on Adobe's part? Are
you kidding me?
Could it possibly be said that to provide for plug-ins is an innovative and
provisionary thing, even enabling entreprenurialism on
19 matches
Mail list logo
