[ddots-l] Re: Sibelius: New Ownership

  • From: "Dave Carlson" <dgcarlson@xxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Wed, 31 Jan 2007 17:02:58 -0800

K,

Got it. I'm more assured now, as long as Digi Design or Avid 
does not decide to pull out the rug.

Dave

----- Original Message ----- 
From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: January 30, 2007 9:35 AM
Subject: [ddots-l] Re: Sibelius: New Ownership


Dave,
I only used the word "presume" to cover by behind because I
haven't spoken to David on this specific point for the 
express purpose
of issuing this statement.  I was there.  He did ask.  His 
purpose in
asking was, as he put it at the time, to make sure he was in 
town during
the beta cycle.  He needed to do his best to coordinate that 
cycle with
his various gigs or whatever.
Digi Design is the maker of Pro Tools, among other products. 
I
believe they also own M-Audio.  Sibelius Speaking is David's 
personal
baby, as is Cake Talking.  That's just so we're clear on who 
owns what.

Remember that Dancing Dots is only a reseller.  They are not 
a
developer.  Bill McCann finds products he can sell.  He 
doesn't create
them.  I am absolutely sure that there will be a Sibelius 5 
and there
will be a Sibelius Speaking for it.  I am not authorized to 
speak
officially on behalf of anyone.  However, these are the 
facts and I
don't think anyone can make anything clearer than that.
Kevin

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx 
[mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Dave Carlson
Sent: Tuesday, January 30, 2007 7:35 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Sibelius: New Ownership


Hello Kevin,

I'm not sure I understand whether you are speaking
officially on behalf of Digi Design or Dancing Dots. I know
that you attended the show with David Pinto and therefore
were "on-the-spot" when these discussions were held. However
you use the word "presume" in your most recent message and
that tells me that we need to hear from either DigiDesign or
Dancing Dots to get the official word.

Also I'm not sure I understand this statement from your
message dated January 28, 2007 2:06 PM:

"Incidentally, Dave, Digi Design now owns Sibelius."

IS this correct? Who is DigiDesign? They own Sibelius, or
they own Sib Speaking?

Not trying to pin anyone down, but just getting the record
absolutely straight.

...would anyone from Dancing Dots like to chime, in Bill?

Dave Carlson

----- Original Message ----- 
From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: January 29, 2007 2:16 PM
Subject: [ddots-l] Re: Sibelius: New Ownership


David and I attended a meeting at the recently concluded
NAMM show
hosted by Sibelius.  At the meeting, David spoke to the
Sibelius
developers to make sure that he was included in the Beta
cycle for
Sibelius 5.  I presume that this is for the express purpose
of
developing Sibelius Speaking for Sibelius 5.
David's declining to develop Sibelius Speaking for Sibelius
4
was the direct result of timing issues with the various
development
cycles of the products for which he scripts.  It was never
intended to
signal his unwillingness or inability to support future
versions of
Sibelius through his Sibelius Speaking product.  I have
every confidence
that as soon as the Sibelius 5 Beta cycle begins, David will
commence
development of Sibelius Speaking for Sibelius 5.
As I've explained, our current situations allows us to
create
both scores and parts in Sibelius 3 which Sibelius 4 users
can import.
Those Sibelius 4 users can, in turn, export their work back
to a
Sibelius 3 format file which we can work with.  While this
is
inconvenient, it provided David a breathing space in which
he could
catch up with Sonar 5 and now Sonar 6.  During that time, no
further
work was going on with Sibelius.  Additionally, because of
the solution
I have explained, David felt sure that his user base was
still being
served adequately, a view which I share.
I hope this explains the state of development and the
prospects
for the future to everyone's satisfaction.
Kevin


-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of John Henry
Sent: Monday, January 29, 2007 2:04 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Sibelius: New Ownership


Woops, designated last note as last word, but this message
from Kevin is
so important that I'm breaking silence once more.

First, no one would wish work to be undertaken on a
programme which will
soon be out-of-date.
  Given that premise, do we assume from your note, Kevin,
that you are
speaking on David P's behalf so that:  A. Sib5 will be open
to the
addition of accessibility software like SS and; B., David
will
definitely be willing to resume his excellent work in
developing SS for
Sib5 regardless of any new Sonars?

If so, and I fervently hope it is, then splendid!  If not,
then I would
join others in suggesting that Dancing Dots explore the
possibilities of
alternative developers for such an important programme not,
of course,
that anyone else would be able to make the outstanding
progress shown by
David.

Thank you,

Cheers,

JDH


-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin L. Gibbs
Sent: 28 January 2007 22:06
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Sibelius: New Ownership


For the record, and trust me on this, there is a Sibelius 5
coming. Fear
not.  David Pinto will be in the loop on the beta cycle
which has not
begun yet.  There's no point in scripting Sibelius 4 because
5 is
coming. Tehre will be a Sibelius Speaking 5.  We can work
with 3 and
those who have 4 can export to 3 when necessary.  It's a
pain but better
than nothing.
Incidentally, Dave, Digi Design now owns Sibelius.  So
Sibelius
will be around for the long haul.
Kevin

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Dave Carlson
Sent: Sunday, January 28, 2007 1:15 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Sibelius: New Ownership


            Listening to all the concerns over scripting the
next
generation of Sib Speaking, I think we should all be
focusing some of
our concern and entreaties to the company who now owns the
rights to
Sibelius. For all we know, the next version coming out may
be totally
different or even non-existent.

Something that Dancing Dots would need to consider (and I'm
sure already
have) would be to negotiate a contract with the
new company (wish I remembered their name)   so that any
last accessible version of Sibelius could be distributed to
customers
with any new version of Sib Speaking, to ensure our
continued access to
the latest or final release.

We may already be at the end of the road, and only just a
matter of the
new owners telling us to go look somewhere else?.

As to older versions of Sib Speaking and any upgrades
Jeanine , that is
something that Dancing Dots should be able to remedy, given
that you
made the original purchase.

Dave

----- Original Message -----
From: <JMMReno@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: January 28, 2007 10:24 AM
Subject: [ddots-l] Sibelius4


I am writing to express my disappointment and dismay that 
Sibelius
Speaking will not be upgraded for use with Sibelius 4. While 
the
solution suggested by others on this list, namely switching 
back to
Sibelius 3, may be feasible, it is unacceptable in my view. 
For one
thing, I have never upgraded to Sibelius 3 and I no longer 
have access
to Sibelius Speaking 1.3 and Sibelius 2, having mistakenly 
deleted the
setup program for SS 1.3 from my old computer, not 
anticipating the need
to transfer it to a new computer.
Although I
appreciate the hard work and creativity of David
Pinto and others
in developing Sibelius Speaking, I have often thought that
the ultimate
solution would be to develop an application that would
evaluate mainstream software
to determine its accessibility for visually impaired users, 
then
automatically make the necessary adaptations. In the 
meantime, one
possible solution might be for one developer to devote work 
to writing
JAWS scripts for one application and its upgrades. For 
example, one
person can be responsible only for Sibelius Speaking and 
another could
be responsible for Cake Talking. Or perhaps the development 
of all JAWS
scripts could be a collaboration of several programmers. In 
either case,
I strongly feel that visually impaired computer users 
deserve the same
timely access to mainstream software as sighted users, and I 
urge Mr.
McCann, Mr. Pinto and others concerned with the development 
of Dancing
Dots products to carefully and seriously consider the 
suggestions that I
and others have made in order to prevent this sort of 
situation from
arising again.

Jeanine Mooers

** To leave the list, click on the immediately-following
link:-
**
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following
link:-
**
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

** To leave the list, click on the immediately-following
link:-
**
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following
link:-
**
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

** To leave the list, click on the immediately-following 
link:-
** 
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on 
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following 
link:-
** 
[mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on 
the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to 
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: