[ddots-l] Re: Strange MIDI problem

Curioser and curioser said Alice (and Tim!).

Glad you sorted it out. 

Best wishes.

Tim Burgess
Raised Bar Ltd
Phone:  +44 (0)1827 719822

Don't forget to vote for change at http://www.raisedbar.net/petition.htm

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Kevin L. Gibbs
Sent: 25 October 2006 17:40
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Strange MIDI problem

Tim,
        The solution was to delete nad recreate my ttsseq.ini file.
Everything works fine now.  
K.

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Tim Burgess
Sent: Wednesday, October 25, 2006 1:38 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Strange MIDI problem


Hi Kevin,

1 - Grab a copy of MIDI-Ox from http://www.midiox.com (it's free for
personal use) and then enable only the MIDI In port that the surface is
connected to within the Options menu.

2 - Move the offending fader and see what comes up on the MIDI-Ox display -
it should tell you what channel and message the fader is transmitting.  

If you get nothing but the other faders give you a result then things look
bad for the fader.

Can you do a hard reset on the Peavey to set everything back to factory
defaults then try again?

Best wishes.

Tim Burgess
Raised Bar Ltd
Phone:  +44 (0)1827 719822

Don't forget to vote for change at http://www.raisedbar.net/petition.htm

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin L. Gibbs
Sent: 25 October 2006 07:37
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Strange MIDI problem

Guys, 
        I have an old Pevey PC1600X which is a box with 16 MIDI faders.
For some reason, when I move fader 1, I get no MIDI data sent to SONAR.
I have enough eye sight to know the following:

1.  when I move fader 1, the appropriate MIDI IN light glows on my MIDI
interface just the way it does when I throw all the other faders.

2.  I get controler events in the event view when I throw all the other
faders. 
3.  I get audible changes where appropriate when I throw all the other
faders except 1. 
4.  I can see the indicator on the Pevey move when I throw fader 1.  I'm not
inclined to think the fader is broken.  

        I used to remember a MIDI matrix in old versions of Cakewalk.
Is it possible that somehow I'm not sending on channel 1?  What makes me
think this is that when I set my MIDI  IN port to port 3, channel 1, I'm not
able to record with any of my faders.  I've closed and reopened Sonar
several times, turned my MIDI interface on and off with no luck.  

Any help? 
Kevin 

** 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: