MIDI, Music, Audio

@Pete
Yesterday I have tested your MidiSynthé module and Rick Module with Rhapsody4 and my my application. It’works.
Now I testing your software with Rhapsody4.
With your MidiSynth and USBMidi modules, using the routing Rhapsody4 plays on both the internal MIDISynthe and the expander.
Monitoring with the keyboard works very well.
I was able to test my MGS64 application at the same time and no problem for solo or mute mode, nice.
I just tested a score with multiple staves, I was able to use 2 ports one for each device it works. It’s very interesting I recently edited a score with more than 16 voices with Rhapsody and so I couldn’t hear everything.

All that remains is to update my application to choose the MIDI ports :-)

Well done, I think it will be much appreciated by anyone who wants to try writing or copying music without having an expander and others too.

Recently I have spent so much time writing code that I’ve had no time to improve existing and create additional sounds. I do have a sound set with extra banks and many extra instruments that I’d been playing with a few years ago and the plan is to stop fiddling with midisupport and hopefully bug fixing for a while and get back to sound creation. After all that’s what has always interested me.

Nice, thanks for your work.

Now I testing your software with Rhapsody4

So I downloaded Raspsody4 from Jean-Michel’s website and tried to install the PMS fonts and it came up with errors when trying to merge them:

PMS.Rhp4A: File name ‘.PMS.Rhp4A’ not recognised

Which repeats for the PMS.Rhp4M as well

ARMX6 , 5.29 (20-Nov-22) and latest Hard Disc image

Any ideas?

Hi Doug
I think you are using InstallFonts with the configuration tool. I had no problem installing them.
‘.PMS.Rhp4A’ strange the first dot?
Normally you should find a PMS folder in the !Fonts folder (or !EasiRes depending on your configuration)
The Rhapsody fonts are those of Richard Hallas who designed these for !PMS.
And following his advice, I created the 2 workbooks Rhp4A and Rhp4M, because there may be small differences for certain characters.
In all cases the fonts must be visible with !Chars.
There remains the solution to install the fonts manually in the !Fonts directory , you have to restart for them to be taken into account.
I have the same configuration as you and Rhapsody4 works well.

I think you are using InstallFonts with the configuration tool.

That’s the correct way to do it. And, for what it’s worth, it works. I just tried it on my Pi 2.

’.PMS.Rhp4A’ strange the first dot?

Implies a missing path – something like “<ThisIsCrap$Dir>.PMS.Rhp4A” gets expanded to “.PMS.Rhp4”.
Is there something messing with Font$Dir? Like a font manager/selector utility?

install the fonts manually in the !Fonts directory

Not recommended, and sometimes may plain not work (even after a restart).
Some incarnations of the installer create a special file (!Fonts.Messages IIRC) listing the available fonts, and FontManager will look at that rather than scanning to find them for itself. Because of this, if the desired fonts aren’t in the file, they won’t be noticed even if they exist.

you have to restart for them to be taken into account.

*FontInstall ought to do it, but that just causes a crash in CLib.
Given there’s no C in FontManager, I’m just not gonna…

It was a test, anyway, as the Font Installer works and installs them and they’re immediately available. Restart to install some fonts? Jeez, even Windows wasn’t that bad! :p

And because Chars is written it BASIC, it crashes out saying there isn’t enough memory to build the font list and Chars should be restarted. Hmmm, wouldn’t have killed it to Filer_Run itself before giving up the ghost. ;)

By the way, my MIDI module should go in the “500” directory in !System, not the “310” one.

Literally the first thing it does is check it is running on RISC OS 5, before probing the USB driver!

Is there something messing with Font$Dir? Like a font manager/selector utility?

That would be EasyFontPro and removing it restores normal service so thanks for the pointer Rick.

By the way, my MIDI module should go in the “500” directory in !System, not the “310” one.

Altered the contents of !System to match and MIDI is in 500 directory on my system now.

Some incarnations of the installer create a special file (!Fonts.Messages IIRC) listing the available fonts, and FontManager will look at that rather than scanning to find them for itself. Because of this, if the desired fonts aren’t in the file, they won’t be noticed even if they exist.

Darren Salt’s !FontMsgs is good for (re-)writing the Messages1 file should it get out of sync with the font folder:
http://old-www.moreofthesa.me.uk/progs.utils.html#fontmsgs