Aaron Sherber writes:
I have a hard time believing that this is a bug that
came up late in the beta cycle. If I had to guess, I'd say it come up
fairly early, but they realized they couldn't fix it and still ship on
time.
OK, I'll going to give you that hard time...
Look at:
William Roberts wrote:
David Bailey wrote:
But they're just as bad at not fixing long-standing bugs that some
users have been complaining about for a long time as well as
introducing new bugs and saying we'll try to fix it in a future
upgrade.
So that rather than the two companies really
At 06:41 AM 08/23/2004, Jari Williamsson wrote:
Compare the examples on that page with what you get in the same
situations in the release version and you'll see that the bug appeared
AFTER the build the marketing people were using.
Those examples show only one tuplet which begins with a rest, and
At 07:58 AM 08/23/2004, Jari Williamsson wrote:
The bug has nothing to do with rests specifically - it has to do with
the angle of the calculated bracket slope, and to the bracket/number
compensation for steep angles.
Entering the last tuplet on the topmost example on MM's web page
triggers the
David Bailey wrote:
So because nobody does it, we shouldn't expect it?
That's not what I'm saying. What I'm saying is that MakeMusic and Sibelius could both
be worse. They could simply not acknowledge complaints made by their customers, just
as huge corporations like Microsoft and Adobe do.
William Roberts wrote:
I pay money for my Finale upgrades because they contain features that
I want, and that will save me time. I don't expect my software to be
bug-free -- I'm far too realistic for that. But provided it's
quicker for me to use Finale than it is to use a pencil and paper,
and
Hi Aaron,
Yes, I see what you mean: the larger the intervals get, the more the number
seems to pull away from the bracket; a black eye for Enhanced
Tuplets. However, if you are doing a piece with mostly linear tuplet
passages, I think things will look fairly reasonable, with less fussing
than
David Bailey wrote:
But they're just as bad at not fixing long-standing bugs
that some users have been complaining about for a long time as well as
introducing new bugs and saying we'll try to fix it in a future upgrade.
So that rather than the two companies really goading each other into
At 01:16 PM 8/22/04 -0500, William Roberts wrote:
Quick reality check
how many software companies have you dealt with
who will actually directly acknowledge a bug to you,
and tell you that they'll try to fix it in a future upgrade?
Top of my head...
Cakewalk (when they hosted a news server;
Noel Stoutenburg wrote:
[snip]
I have experienced something that bears on this matter, namely that
MakeMusic! was wrong again this year on their intended shipping date.
You may remember how last year, the product was announced at the end of
July, anticipating shipping the middle of August, and
dhbailey wrote:
Noel Stoutenburg wrote:
[snip]
I have experienced something that bears on this matter, namely that
MakeMusic! was wrong again this year on their intended shipping date.
You may remember how last year, the product was announced at the end
of July, anticipating shipping the
The new tuplets are way better even without Enhanced Tuplets. The feature shape--> bracket - with the option --> never bracket beamed notes - is a great time saver.
Éric
Le 21 août 2004, à 09:01, Owain Sutton a écrit :
dhbailey wrote:
Noel Stoutenburg wrote:
[snip]>
I have experienced
At 09:01 AM 8/21/2004, Owain Sutton wrote:
I'm one lost sale of 2005 because of this problem. Much of the music I
deal with is 'tuplet-heavy'...the new tuplet function was the sole feature
that would make the upgrade worth the money. Now it appears it wouldn't be.
Am I missing something here?
Éric Dussault wrote:
The new tuplets are way better even without Enhanced Tuplets. The
feature shape-- bracket - with the option -- never bracket beamed
notes - is a great time saver.
But that's already in place at least for triplets -- in Fin2004 (and as
far back as I can recall, although I
sorry but I don't see this option in 2004. Could you develop ?
Éric
Le 21 août 2004, à 09:59, dhbailey a écrit :
But that's already in place at least for triplets -- in Fin2004 (and as far back as I can recall, although I don't think as far back as Fin3.5 when I started with Finale) when I
OK. You probably meant the Auto bracket feature with brackets on. So I just learned something that I wasn't using. A great time saver that I was missing from previous versions.
Thanks David,
Éric
Le 21 août 2004, à 10:06, Éric Dussault a écrit :
sorry but I don't see this option in 2004. Could
At 10:17 AM 8/21/04 -0400, dhbailey wrote:
Éric Dussault wrote:
sorry but I don't see this option in 2004. Could you develop ?
Éric
Le 21 août 2004, à 09:59, dhbailey a écrit :
But that's already in place at least for triplets -- in Fin2004 (and
as far back as I can recall,
At 10:05 AM 08/21/2004, Dan Carno wrote:
Am I missing something here? Enhanced tuplets work OK, unless you edit one
by dragging one of the notes (or changing one into a chord), in which case
you will have to edit the number position.
It's not just a matter of dragging or changing. If you
Dan Carno wrote:
At 09:01 AM 8/21/2004, Owain Sutton wrote:
I'm one lost sale of 2005 because of this problem. Much of the music
I deal with is 'tuplet-heavy'...the new tuplet function was the sole
feature that would make the upgrade worth the money. Now it appears
it wouldn't be.
Am I
Well, auto bracket is indeed the setting that makes this work. I never work with MakeMusic Templates so mine wasn't set up to take advantage of this.
Éric
Le 21 août 2004, à 10:17, dhbailey a écrit :
I have no clue where it is set, because it isn't there in the tuplet options, all I know is
Dan Carno wrote, in part:
Enhanced tuplets work OK, unless you edit one by dragging one of the
notes (or changing one into a chord), in which case you will have to
edit the number position. I would rather do this until a fix comes
along than deal with the mess that pre-Fin 2005 tuplets
Noel Stoutenburg wrote:
As soon as FIN 2k5 is installe, I mean to explore what happens, if after
making the corrections, one selects the tuplet tool, deletes the tuplet,
and then recreates the same tuplet.
I can assure you that any changes you have made will be lost in this
case. It is no
I snipped and rearranged from what David wrote to first answer:\
The tech-support reply that Aaron received, however, indicates that
they knew about the bug. The reply didn't contain any Oh my
goodness, we've never seen that before -- we'll start working on it
right now to fix it in the patch.
Noel Stoutenburg wrote:
[snip]
Further, thinking back on my own experiences, there have meen more times
than I want to admit to when some problem occurred, and looking back, I
cannot come up with a single good reason for not seeing the problem
developing. I'm in no position to do anything but
On 21 Aug 2004, at 12:24 PM, Robert Patterson wrote:
A more important concern I would have is that if you take all the
trouble to manually edit your numeral positions, what happens if they
*do* fix the bug in the maintenance release? I'm guessing you'll have
to then go and remove all you
Hi Aaron,
We may be talking about different things here, but when I enter an eighth
note tuplet, with the first note a rest, and do not edit it, I have a
reasonable centered number (vertically horizontally) relative to the
bracket. Now I have to admit, under magnification, the center tine of
David, most of the time I would be in agreement with the position you
define when you wrote:
As for your comments on the tech-personnel's position in the heirarchy
at MakeMusic, as the ONLY interface for the end user after we give our
credit card number to consummate the sale, it is terrible
Dan Carno wrote, in part:
Enhanced tuplets work OK, unless you edit one by dragging one of the
notes (or changing one into a chord), in which case you will have to
edit the number position. I would rather do this until a fix comes
along than deal with the mess that pre-Fin 2005 tuplets
At 03:00 PM 08/21/2004, Dan Carno wrote:
We may be talking about different things here, but when I enter an eighth
note tuplet, with the first note a rest, and do not edit it, I have a
reasonable centered number (vertically horizontally) relative to the
bracket.
But look at
Hi all,
FWIW, I received the following from WinSupport about the tuplet bug I reported:
For your concern about that tuplet bug, it is something we know about, and
it is being looked at for being fixed in an upcoming maintenance release if
possible.
I could go on for several paragraphs about what
What Robert said. Seriously. Aaron, they told you they know about the
bug, they are actively trying to fix it, and if possible, it will be
dealt with in the first maintenance release. What more do you want?
- Darcy
-
[EMAIL PROTECTED]
Brooklyn, NY
In the past couple of hours, since I wrote:
WRT the latter point, the fundamental issue related to this is one
that Dr. Patterson and I both alluded to: lead time. We don't know
when the bug was discovered. While the response of MakeMusic!
suggests that they knew about it before Aaron's
32 matches
Mail list logo
