Prodyssey MIDI problem

Discuss the Creamware ASB and Klangbox hardware boxes

Moderators: valis, garyb

Post Reply
eric
Posts: 157
Joined: Mon Feb 25, 2008 8:40 pm
Location: Peterborough UK
Contact:

Prodyssey MIDI problem

Post by eric »

Just bought a Prodyssey.

All was going fine until today when I connected it into the rig.
I inadvertently sent a bunch of program change messages to it. The whole patch range from 0-127 was sent in less than a second. Shouldn't be a problem. BUT. Now it wont respond to MIDI on the MIDI in socket. I have reloaded the software and checked my MIDI cable. ALL my midi cable are high quality and checked out with the MIDITest5 cable tester. I have checked that MIDI signals are arriving with a hardware MIDI analyser (Studiomaster MA36).
The MIDI out is working fine but the MIDI through isn't. This makes me suspect the MIDI in opto-coupler as MIDI in is usually hardware connected to MIDI through. It works fine with the Prodyssey software keyboard, which tends to confirm what I suspect. Any other suggestions welcome but it looks like I'll be cracking the seals. :(

Eric.
Your mouse has moved. Windows must be restarted for these settings to take effect.

Eric Northwood - Data Recovery Specialist
http://www.datarecoveryaus.com.au
slammah2012
Posts: 191
Joined: Sat Jun 02, 2007 9:48 am
Contact:

Re: Prodyssey MIDI problem

Post by slammah2012 »

Reloaded the Software???

is this a Hardware or Editor problem....?

Make sure your "local on" is on...turn up the VCA Gain...you should hear sound...midi or no midi...
Then make sure you are on the right midi channel....
...
Midi CCs wont kill the unit....lol
Time has No Master.
*NOW* is the Password.
Just *ASK* and *INVITE* every-
thing you are after..........
eric
Posts: 157
Joined: Mon Feb 25, 2008 8:40 pm
Location: Peterborough UK
Contact:

Re: Prodyssey MIDI problem

Post by eric »

Thanks Slammah.


It's the ASB.
The sending of CC's was coincidental.
A large amount of MIDI data could cause the optocoupler to fail though. :)
Anyway, it turns out it was a broken DIN socket.

All working fine now.

Eric.

Thread closed.
Your mouse has moved. Windows must be restarted for these settings to take effect.

Eric Northwood - Data Recovery Specialist
http://www.datarecoveryaus.com.au
Post Reply