MIDI, Music, Audio

I think setting it up correctly would take many pages.

It is feasible especially if there are users and volunteers….
MIDI capture needs testing and certainly fixing, especially with USB.
Pete’s module seems to be more efficient in capturing, to confirm!
Note I just discovered on Rick’s Blog that there was a version 0.12 of the MIDI module.

It’s a shame that the MIDI import throws away so much information.

Import or capture ?

Anyway I think both could use some improvement…

@Raik
I have the same kind of keyboard as yours, I didn’t realize that it was this kind of keyboard that you were using, a KeystationMini32M.

@Rick
Bonne visite médicale et surtout bonne santé.

Rick’s Blog that there was a version 0.12 of the MIDI module.

;)

Unfortunately the work on adding the virtual “cables” broke one of the promises that the module made (namely, if a device is unplugged and plugged in again, it’ll be given the same ID even if a different device was plugged in in the meantime) so I’m going to have to look at making that work again, because constantly shifting IDs isn’t so useful.

Import or capture ?

Import. Individual note velocities seem to be lost, but more concerning is that it doesn’t seem to reproduce the sustain pedal.

I didn’t realize that it was this kind of keyboard that you were using

Yamaha PSR-E333. A not-crap entry level sort of thing…that I’m terrible at actually playing. :(

Bonne visite médicale et surtout bonne santé

Merci, mais essentiellement: Humain? Oui. Vivant? Presque. Ça suffit, je vous voir en cinq ans.

@Raik
Have you been able to do other tests?
For my part, I started testing again, and actually what works well is MidiMan, Pete Everett version.

I tested this routing and I can use my Roland exploder via the UR22MKII and Midisynth interface.
So 30 instruments + 2 DRUM kits.

With routing you can send the keyboard data directly to Midisynth and at the same time to Rhapsody.
For Rhapsody, just activate the Midi True mode in aynat before opened a new score to choose an instrument, it is the one we will hear.Both sources can be used at the same time!
Rhapsody capture works too:
I am not a pianist and therefore the steptime mode suits me.
Note: the “mini” keyboard does not help too much to play, keys size at least for the mini32

For real -time capture it is better to use the metronome.
But maybe you already knew that?

@ Rick
I test your sequencer.
bq. Import. Individual note velocities seem to be lost, but more concerning is that it doesn’t seem to reproduce the sustain pedal.

Note Velocity, I do not know how to translate it on a score, there is information like Staccato which is interpreted by Rhapsody as well as the nuances(ff/mp/p…)
Hence the interest of the sequencer for MIDI files.

Analysis of a MIDI file and its transcription takes some time (Basic program) and durations and timings are not always correct … (these files can come from a sequencer or a editor.
The LameDemo/Midi file is well loaded by Rhapsody but I do not see the controls Events! to dig.

Many thanks for the answers.

@Raik
Have you been able to do other tests?

Sorry, no. The snow last week and my wifes wishes are stolen my spare time. ;-)

Glad to have another person interested.

My interest is a technical one.
The “musicans” are my children especially my son. He use the midi stuff often and I hope I find a usable setup for him.
He use also a SDP stage piano and a Roland keyboard. Both with Midi in/out, own sound and full size keys.

I will try same things this week and will specify the error messages etc.

My interest is a technical one.

For the MIDI USB capture the pete module is more suitable, because it detects the entries in the buffer, if this is not the case Rhapsody remains waiting!
I found that the capture tests were better.

Thank you for Feedback.

Of course I’m also interested in playing, but like football or programming, I’m pretty talent-free.

I agree. Looks like the pete module works better. No error last time.

Have I something missunderstand? I not get an sound output on PBPro if I press the AKAI keys.
Routing is working. Capture works and I see die pressed keys on the MidiMon keyboard on screen but no sound. MidiSynth is runnig.
The Midiplay keyboard play sound if I activate…
Looks like more investigation needed.

Have you activated in the window opened by the iconbar item menu module midisynth?

If this is the case for midisynth must be in the routing and must have the port 0 as input.
Remember to save configuration if it suits you!…

I agree. Looks like the pete module works better. No error last time.

Could you be more specific? If there’s a problem….

because it detects the entries in the buffer

What, you mean Rhapsody does? What SWI should I be looking at to fix this?

I don’t have a synth (I’m not mathsy enough to do that), but you can route with my module as well – the included program makes it point and click.

What SWI should I be looking at to fix this?

SWI MIDI_RXCOMMAND, I think this order has “trouble filling” detection at the USB buffer.
In the source, the expectation of receipt is in the procedure PROCuk. Crunched Name:-(

MIDIUSBinfo displays my two devices well, keyboard and expander.

MIDIUSBdebug displays an interval RX of 2 centisecond. It may be the difference with the pete module that uses a millisecond timer?
Note, if I manage to “hang” your module, I can capture notes, but it lacks …
Sorry if I explain myself badly ..

FYI it is better used the file! Runimage in the zip rhap4_runimagetest.
https://jeanmichelb.riscos.fr/Musique/Rhapsody4.html

Could you be more specific? If there’s a problem….

The problems I have beside Rhapsody if I capture. With MIDI 0.11 I get errors from time to time with Pete module not at this time.

Any errors I note:
Error 10827: No room for function/procedure call.
Same in 6014.
Error 6060: Too many nested structures
Error 6473: Internal error: abort on data transfer at &FC1DE7BC

Modules and routing are present/configured as describe. No sound. I use a PBPro.
Will try a Pi4.

Thanks a lot.

Have you used !Midiplay (pete Everett) alone, or digital CD to read a MIDI file?

I try both settings … SharedSound and DigitalCD.
Midiplay as App works, also Rhapsody with the new instruments.

@Raik,

There are 3 versions of my Synth,
1. MidiPlay is a self contained midi file player and contains Synth.
2. MidiSupport comes with a “driver” module version of Synth.
3. A “MIDI” module version of Synth for those who don’t want to use MidiSupport.
There can only be 1 “MIDI” module loaded at any one time as they all use the same SWI’s. This includes Rick’s USBMidi module which is also a replacement “MIDI” module. MidiSupport also comes with a “MIDI” module, the first 4 entries in the routing window.

So you can either have Rick’s USBMidi OR MidiSynth(module) OR MidiSupport loaded. There may be problems if you are doing tests and swapping between USBMidi and MidiSupport because they both use Timer1 and to disable MidiSupport you must kill all it’s modules otherwise there may be problems when you swap back to use it again. The MTimer module may not be running or the synth may not be reconnecting to the MTimer module. Either way no sound will be produced.
MidiSupport is not an Application so there is no iconbar icon to quit it. MIDIMan is just a front end to the MidiSupport system and does not shutdown the MIDISupport system when quit.

To shut it down completely,

Quit MidiMan
Quit MidiMon (it got renamed MidiSMon and I’ve renamed it again but that’s another story!)

I use an obey file to kill the modules

X RMKill MIDISynth
X RMKill MIDIPlay
X RMKill USBMidi
X RMKill SerialMidi
X RMKill MIDI
X RMKill MTimer
X RMKill MIDISupport

To restart it just run !MidiSupp
From power up, if MidiSupport is started and USBMidi(Rick’s) has never been loaded, it should work.
To check if the timer is running correctly, enter,
*mtimerreport
Do this a couple of times and if “ticks” is increasing, and one of the clients is MIDISynth, it’s ok.

As Jean-Michel said, to get your AKAI keyboard to play through the Synth, all that’s needed in MidiSupport is in the Routing window, connect the Source for MidiSynth to the Destination for the AKAI.
You can use Rick’s USBMidi to work with Rhapsody but not with the MidiSynth module version at the same time because USBMidi and MidiSynth are both “MIDI” modules. The MidiSynth module is only of use to produce sound from an application within the computer i.e. Rhapsody. To get connection from the AKAI to Rhapsody and a Synth at the same time you must use MidiSupport, connecting the AKAI destination to both MIDISynth source and MIDIPort0 source.

For the last year I have been trying, now and then, to create extra sounds for the synth. To this end, I created a few extra applications for MidiSupport and I’ve recently been adding the changes to the synth back into the module version. This involved swapping between MidiSupport and the “MIDI” synth module so I’m well aware of problems that can occur when doing this sort of testing.

Thanks for the detailed lines.

I have try any things with the same setup on various machines.
On Titanium and Pandora no problems. Routing the MIDI input from AKAI to MIDISynth and Rhapsody at the same time is working. Sound is produced.
With the Pinebooks (both, old and pro) no sound. Looks like MIDISynth generally works with Sound but not with the “AKAI routing”. I have no idea what the reason could be.

Thanks for taking the time to try all this out.
I’m guessing it’s a timer issue but that’s only a guess. On the Pinebook, when it’s not producing any sound, what does mtimerreport give?

what does mtimerreport give?

Sorry, not sure what you mean.
Can you give more information?

Thanks a lot.

When you have the no sound problem, open a task window and type mtimerreport, this is what I get,

*mtimerreport
ticks 514067
client 1, period 1ms, call &202C01C4, MIDI
client 2, period 1ms, call &202D1728, MIDISynth
client 3, period 1ms, call &2030068C, MIDIPlay
client 4, period 1ms, call &20328200, SerialMidi
client 5, period 1ms, call &2033D6E0, USBMidi
client 6, period 1ms, call &203FA940, IRcapture
*mtimerreport
ticks 515040
client 1, period 1ms, call &202C01C4, MIDI
client 2, period 1ms, call &202D1728, MIDISynth
client 3, period 1ms, call &2030068C, MIDIPlay
client 4, period 1ms, call &20328200, SerialMidi
client 5, period 1ms, call &2033D6E0, USBMidi
client 6, period 1ms, call &203FA940, IRcapture
*

ticks is the number of milliseconds since the timer module started and the clients are the modules that are called every “period” ms.
Enter the command twice and if ticks increases, the timer is running. The client list should include MIDISynth.

It’s just to prove whether or not it’s a problem with the timer.

Thanks.

Thanks for your support.
Looks like you’r right. Have try with and without MIDIPlay.

SDFS::eMMC.$>*mtimerreport
ticks 0
client 1, period 1ms, call &204D2544 MIDI
client 2, period 1ms, call &204E39EC, MIDISynth
client 3, period 1ms, call &20531078, MIDIPlay
client 4, period 1ms, call &20536740, USBMidi
SDFS::eMMC.$>*mtimerreport
ticks 0
client 1, period 1ms, call &204D2544, MIDI
client 2, period 1ms, call &204E39EC, MIDISynth
client 3, period 1ms, call &20531078, MIDIPlay
client 4, period 1ms, call &20536740, USBMidi
SDFS::eMMC.$>*mtimerreport
ticks 0
client 1, period 1ms, call &204D2544, MIDI
client 2, period 1ms, call &204E39EC, MIDISynth
client 3, period 1ms, call &20536740, USBMidi
SDFS::eMMC.$>*mtimerreport
ticks 0
client 1, period 1ms, call &204D2544, MIDI
client 2, period 1ms, call &204E39EC, MIDISynth
client 3, period 1ms, call &20536740, USBMidi
SDFS::eMMC.$>*

Thanks a lot.

I’ve seen that problem here once or twice recently whilst doing some testing and a restart fixed it for me. I never found out exactly why. I’ll look into it.
Thanks.

I have corrected a couple of errors in the timer module initialisation that might have been causing the problem. Without a Pinebook I cannot be sure.

Anyway, I have uploaded the latest build of Midi Support which includes these corrections, and the module version of the synth. There have been quite a few changes since the last release so it’ll be best to delete or hide the old version.

You can download it all here http://www.forever.onmypc.net