[ddots-l] Re: Sibelius: New Ownership

  • From: "John Henry" <henryjdh@xxxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Mon, 29 Jan 2007 22:04:17 -0000

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

Other related posts: