public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tim Burgess" <tim.burgess@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: Apollo synthesizer problem
Date: Tue, 1 Oct 2002 13:22:53 +0100	[thread overview]
Message-ID: <000e01c26945$5b512660$0100a8c0@tim02> (raw)
In-Reply-To: <x7y99ihs1v.fsf@speech.braille.uwo.ca>

Hi,

If I remember rightly (and it was a long time ago) the buffering and
indexing on the Apollo/Juno synths got changed in one of the firmware
updates that Dolphin issued.  Might be that you've fell foul of this if
yours is a very old unit that's never had an update.  Can't remember the "@"
command for finding out the firmware revision though - probably worth
checking your manual or calling your dealer.

Hope that helps.

Tim


-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Kirk Reiser
Sent: 01 October 2002 20:34
To: speakup@braille.uwo.ca
Subject: Re: Apolo synthasizer problem


I may have seen a little choppieness with the Apollo but not anywhere
near what you indicate in your example.  There are lots of folks on
the list using the Apollo so maybe we can get some more feedback from
them.  From your example I can't tell anything.

  Kirk

--

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Apolo synthasizer problem Darragh
 ` Buddy Brannan
   ` Toby Fisher
 ` Kirk Reiser
   ` Tim Burgess [this message]
   ` Darragh
     ` Kirk Reiser
       ` Darragh
         ` Buddy Brannan
       ` William F. Acker WB2FLW +1-303-777-8123
         ` Darragh
           ` Geoff Shang
         ` Toby Fisher
           ` Darragh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000e01c26945$5b512660$0100a8c0@tim02' \
    --to=tim.burgess@blazie.co.uk \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).