Something new: the Trinity V3 ProX I have plays no C or F# from its own keyboard in any octave. It plays all the other pitches fine. The behavior is consistent through various Combi and Program sounds.
If I play the Trinity from another keyboard via MIDI, all the pitches sound fine, the Cs and F#s included. Did the key tracking IC just go bonkers, or could this be some sort of weird user scale setting? (I never messed with those.) Do I reset the synth?
Wacky: Trinity ProX plays no C or F# from its own keyboard
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
Rosen Sound
- Approved Merchant
- Posts: 1056
- Joined: Wed Jan 06, 2010 8:32 am
- Location: Los Angeles, California
- Contact:
Your trinity is dirty under those keys! clean it!
<a href="http://www.rosensound.com"><img src="https://dl.dropboxusercontent.com/u/365 ... r.jpg"></a>
Current gear: Korg Kronos 61, Oberheim OB-8, Alesis Vortex
Past Gear: Triton Extreme w/moss & ram, Korg Radias, Kurzweil Micropiano, Triton classic, & Karma
Come visit my Burbank California repair shop/recording studio! Rosensound.com
And my band: Sirion.us.com
Current gear: Korg Kronos 61, Oberheim OB-8, Alesis Vortex
Past Gear: Triton Extreme w/moss & ram, Korg Radias, Kurzweil Micropiano, Triton classic, & Karma
Come visit my Burbank California repair shop/recording studio! Rosensound.com
And my band: Sirion.us.com
Wrong, robbinhood.
If the keys exhibit a failure mode in a consistent pattern across keys, it is usually a problem with the ribbon cable or more rarely a failed component on the diode matrix.
First try reseating the ribbon cable from the motherboard/scanner board to the keyboard.
If the keys exhibit a failure mode in a consistent pattern across keys, it is usually a problem with the ribbon cable or more rarely a failed component on the diode matrix.
First try reseating the ribbon cable from the motherboard/scanner board to the keyboard.
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
-
Rosen Sound
- Approved Merchant
- Posts: 1056
- Joined: Wed Jan 06, 2010 8:32 am
- Location: Los Angeles, California
- Contact:
derp, i thought he wrote ONLY on one octave not all of em!
yes, Xtrade is correct!
yes, Xtrade is correct!
<a href="http://www.rosensound.com"><img src="https://dl.dropboxusercontent.com/u/365 ... r.jpg"></a>
Current gear: Korg Kronos 61, Oberheim OB-8, Alesis Vortex
Past Gear: Triton Extreme w/moss & ram, Korg Radias, Kurzweil Micropiano, Triton classic, & Karma
Come visit my Burbank California repair shop/recording studio! Rosensound.com
And my band: Sirion.us.com
Current gear: Korg Kronos 61, Oberheim OB-8, Alesis Vortex
Past Gear: Triton Extreme w/moss & ram, Korg Radias, Kurzweil Micropiano, Triton classic, & Karma
Come visit my Burbank California repair shop/recording studio! Rosensound.com
And my band: Sirion.us.com
Progress update
Original poster, reporting back after quite a bit of experimenting:
1.) The Enter - 0 reset dance did reset the sounds, but the weird keyboard behavior remained
2.) The Enter - 5 Test mode went through the internal test (MIDI, System ROM, RAM, IIC I/F, LCF I/F, FDC I/F, TG I/F, DF I/F, DSP I/F, PCM Rom, Battery, Solo Board) with all of these testing OK.
3.) Next I jumped to External Test Item 6: Keyboard & Aftertouch
Step 1, Keyboard. I got the following thing onscreen:
Next-->C8 Vel 061 ERROR
as I played the whole keyboard downward from the top, only the Velocity value changed, depending how hard I hit the keys. However nothing changed when I played a C or F# in any octave. The Next-->C8 value remained at "C8" throughout.
Step 2, Aftertouch
As I played through the keyboard holding keys down, the Max, Center and Min screen readouts changed smoothly depending on my key pressure. On all 88 keys.
A blurb about this Trinity's previous history. I bought it used for a song because it was acting unpredictable. Then, if my memory serves me right, I updated the OS - and from then on, it worked fine! (Could a voltage blip garble a part of the EPRom, so that even if technically the chip tests as functional, some of its 1's and 0's are wack?)
Anyhow, given all the above test results, I wonder what's the verdict. Should I try first another OS install, or is it time for a ribbon / diode matrix combover?
1.) The Enter - 0 reset dance did reset the sounds, but the weird keyboard behavior remained
2.) The Enter - 5 Test mode went through the internal test (MIDI, System ROM, RAM, IIC I/F, LCF I/F, FDC I/F, TG I/F, DF I/F, DSP I/F, PCM Rom, Battery, Solo Board) with all of these testing OK.
3.) Next I jumped to External Test Item 6: Keyboard & Aftertouch
Step 1, Keyboard. I got the following thing onscreen:
Next-->C8 Vel 061 ERROR
as I played the whole keyboard downward from the top, only the Velocity value changed, depending how hard I hit the keys. However nothing changed when I played a C or F# in any octave. The Next-->C8 value remained at "C8" throughout.
Step 2, Aftertouch
As I played through the keyboard holding keys down, the Max, Center and Min screen readouts changed smoothly depending on my key pressure. On all 88 keys.
A blurb about this Trinity's previous history. I bought it used for a song because it was acting unpredictable. Then, if my memory serves me right, I updated the OS - and from then on, it worked fine! (Could a voltage blip garble a part of the EPRom, so that even if technically the chip tests as functional, some of its 1's and 0's are wack?)
Anyhow, given all the above test results, I wonder what's the verdict. Should I try first another OS install, or is it time for a ribbon / diode matrix combover?
Re: Progress update
This, I think. The bad news is that the keyscan 'select' lines are shared with the fron panel button scan lines, so a short or a faulty diode around the front panel buttons might also cause the problem you're experiencing.mrdelurk wrote:...is it time for a ribbon / diode matrix combover?
First I would disconnect the keybed make/break contact harness (CN11A on KLM1820 board) and see the test message. If it remains the same, then the problem is likely to be be on the main (KLM1820) board, before the ribbon cable, obviously. In this case you might want to disconnect one by one the front panel harnesses (CN12A - keybed scan, CN14A, CN15A, CN16A, CN17A - front panel switches).
)
Well, I'll be darned. Waiting on Synthjoe's answer, I replugged CN11, located the other CN sockets on the board, and gently pushed their connectors in (hearing an occasional crackle here and there) just in case if they got loose.
Then I closed the case, powered the Trinity back up to see where we are - and now all 88 keys work again!
Good old Trinity... it still recognizes the hand that gave it a shiny new FD. It even sounds sweeter than before, though it might be just my imagination.
Then I closed the case, powered the Trinity back up to see where we are - and now all 88 keys work again!
Good old Trinity... it still recognizes the hand that gave it a shiny new FD. It even sounds sweeter than before, though it might be just my imagination.
Yup, that's the way it works with old beauties. Job done, I'd say...mrdelurk wrote:Well, I'll be darned. Waiting on Synthjoe's answer, I replugged CN11, located the other CN sockets on the board, and gently pushed their connectors in (hearing an occasional crackle here and there) just in case if they got loose.
Then I closed the case, powered the Trinity back up to see where we are - and now all 88 keys work again!
Good old Trinity... it still recognizes the hand that gave it a shiny new FD. It even sounds sweeter than before, though it might be just my imagination.
