'dirty' midi

[iandg]

Hallo, David

The Ketron has trad 5 pin midi sockets, and I'm using a USB-midi cable which I've used happily for a number of years.
If I understand what you're saying, the USB-midi cable could be the problem? I guess the only way to know would be to get another (good one) and try it.

But logically, I think there would still need to be some 'proximate' cause to account for the problem arising with some softwares (2, at the moment, of which the other is always a 'distinct beast' in terms of midi set-up) ) and not with others (3 that I've tried, one being also from the Notation stable) ?

I've held off further input today because I believe Sherry is a 'church person'. I will update more thoroughly some tim tomorrow.

Thanks for your 2p.

Ian G.

[iandg]

Hallo, everyone

More about my problems with NC and Ketron SD2

Yesterday
(a) I simply restarted NC after booting up (the notebook having been 'off' for some 12 hours)
Loaded Notation's own 'Twinkle' file and tried to play – result as before ie something is sent to the SD2, but what comes out is just garbled sound and a lock-up

(Have repeated that today, Monday, with the same result. And then have had both Midi-Illustrator Maestro and Midi-Illustrator Player playing through the SD2 and scrolling happily. I don't like their screen as much as NC – but they are working !) )

(b) Removed Notebook and put my Asus Laptop (which has my original purchase of NC3) into the identical hardware set-up.

NC detected the usb midi in, and played a test scale correctly. But then I loaded Notation's own 'Twinkle' file and tried to play – result as before ie something is sent to the SD2, but what comes out is just garbled sound and a lock-up

Conclusion: suggests there may be nothing wrong or garbled with the NC set-up on the Notebook, since the NC set-up on the Asus is reacting exactly the same way. In which case, no point in re-installing ?

It is possible that I am doing something wrong somewhere in the set-up – but what could that be ?

From first principles: it seems likely either that Notation is not sending some initial code which the SD2 expects, or conversely, that it is sending some code which is not necessary/is actually 'confusing' the SAD2.
Again, I can only speculate on how the parallels that are working, are working ?

(c) Have also experimented with LoopBe virtual midi cable. I have had it recognised as the 'out' of NC and the 'in' of OMB, but I cannot detect that anything is passing from one to the other. Eg if I play Twinkle in NC, it scrolls without sound, but 'record' in OMB does not pick it up.

(d)I haven't previously said anything about Windows versions.
The Notebook runs Win 7 Starter
The Asus runs Win 10, upgraded from an original Win 8 installation.
Are you aware that Windows support for Midi varies significantly for these versions ? What is NC3 principally aimed at ?

(e)The last thing I can think of is that I still have NC 2.6.3 on an old desk-top. I could see whether that will run the SD2 happily. If so, it would do all I need on the Notebook (although I note the help window doesn't record the registration code, and I don't think I've got an installation *.exe for it, either).

Sincerely

Ian G.

[dj]

Hi, Ian:

Nothing to add at the moment, but I've got my thinking cap on about this and am trying to suss it out.

David

[iandg]

Well, mostly.....
For some time I had had a set-up with a cheap midi controller keyboard as a midi-in - which had its own printer-style usb connection, so I had 'parked the out' cable of the usb-midi cable in the 'out' of my clavi (knowing I could turn it off with a click in what I have been calling 'my other software'.)
Late last week, I changed that, to physically replace the cheapie with my Roland A500 - but that wasn't then connected into the computer-centred connections at all - it had an-old style 5 pin cables set direct to my Korg 03R/W. So the 'out' of the usb-midi cable was 'floating', and I re-parked it in the 'other' socket of the SD2.
This morning I was adjusting again, to re-instate the clavi as a midi-in option, and it suddenly occurred to me that this 'parking' could have been the cause of the conflict with the SD2. And indeed, so it has proved - 'Twinkle' plays nicely (well actually, it's a fairly horrible track !) from NC.
So principally my fault.........though the fact remains that several other softwares coped. It's possible to be too 'sensitive', perhaps ?

Anyway, I can listen and scroll through NC again, thank goodness.

Regards

Ian G.

[dj]

Hi, Ian, Sherry:

All's well that ends well, as somebody famous once said.

I think perhaps the other software you were using disabled midi echo as a default, whereas it's on with NC. What you were getting sounds like a midi feedback loop -- every time a note came into the keyboard, it was sent back to NC, which sent it back to the midi keyboard -- and 'round and 'round.

It's always something.

David