| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1253.1 | from another MIDIot ... | MIZZOU::SHERMAN | put down the ducky! | Tue Mar 15 1988 12:32 | 10 |
| The only wierdness I've experienced along these lines is the QX's
inability to take a Casio dump. Can't make the QX wait the right
amount of time. My guess is that the FIFO on your interface (assuming
it has one) is too slow (not likely) or too small to handle any
reasonable amount of data, maybe? More likely, the controller is
sending out a weak or noisey signal (which would explain the JXP
working okay). Just guesses from the hip ...
Steve
|
| 1253.2 | ... and play the saxophone! | AKOV68::EATOND | | Tue Mar 15 1988 12:45 | 10 |
| RE < Note 1253.1 by MIZZOU::SHERMAN "put down the ducky!" >
> More likely, the controller is
> sending out a weak or noisey signal (which would explain the JXP
> working okay).
Why would this explain the JX8P working?
Dan
|
| 1253.3 | you saw the Sesame St. special, too? | MIZZOU::SHERMAN | put down the ducky! | Tue Mar 15 1988 14:41 | 7 |
| I was thinking that maybe the output of the RD200 had a little noise
on it (maybe from a bad power supply) and that the QX7 and MSQ didn't
see the noise. As the Sonus is (I'm guessing) powered by the C64,
if the power there is not up to snuff, the Sonus might be sensitive
to the noise.
Steve
|
| 1253.4 | STACK Problem?? | SIGANA::JWILLIAMS | | Tue Mar 15 1988 18:02 | 28 |
| Midi interfaces can cause all sorts of wierd behavior. For example,
when running a CZ230S off of an ST, it was dropping bass notes here
and there. Very annoying. I tried MIDI slow, that didn't appear
to work. I finally tried transposing the duration of the note to
shorten it by one clock tick. SPROING! It worked flawlessly. I have
since purchased an MT-32 and have had no problems of this nature.
I guess the moral of the story is, FULL MIDI compliance is more
than byte patterns, it is how well the synthesizer responds to
sequences. If you have notes on and notes off within a clock tick
of each other, some synthesizers might get confused. My own personal
theory is that many synthesizers store byte data in a stack while
they're working. The note on goes on top of the stack and is executed
before the note off ( which should have been the previous clock
tick ). The OFFICIAL way of doing it is to use a fifo, but cost
cutters find it economical to use the stack instructions found in
a normal micro processor.
I don't know about you, but I quantize almost everything ( I am
a good guitar player, but can't hit keys worth a drat ). This makes
the " STACK " problem surface, especially if you have alot of things
going on at once. I'd really have to dig into to the hardware to
speak any of this with authority, but it's my personal guess.
If you can edit individual events, try shortening some of the
durations.
Good Luck,
John.
|
| 1253.5 | What's in the black box? | ROLLIN::BAILEY | Steph (stef') Bailey | Wed Mar 16 1988 09:48 | 20 |
| Dan,
Do you know, roughly, what is inside the Sonus interface? A
description, to the precision of: hundreds of ICs of all sizes,
or one 40 pin IC and a bunch of discretes (transistors, resistors,
capacitors) would be useful.
It's hard to debug the problem if you (I) don't know who's doing
what in the process.
.4 seemed like a likely candidate for the sequencer problem--I
would call it ``differences in voice assignment algorithm'', rather
than ``MIDI noncompliance''. That would explain why the JX works
and the RD200 does't, but it still doesn't explain why your patch
editor doesn't work.
Noise seems unlikely to me.
Steph
|