AMidi anyone?

[Xanxi]

Hi.

In order to play some MIDI files, i have installed AMidi on my A1200.
Install instructions say that software rendering needs a PPC board, so i use instead the other option called "CMAD", or something like that, that output the midi to an external player. This external player could be, still according to the instructions, any MIDI hardware or the software package available on aminet GMPlay.
So i installed too GMPlay.

Unfortunately, PlayMidi gives me the error message "can't open amidi.device", which of course is present in DEVS:

Any idea? As i have OS 3.1, i can't use the Prefs which use Reaction and i have no clue where is the prefs file for non Reaction OS that is mentionned by the instructions.

Thanks for your help.

PS: AHI v6 is installed too and working.

[Matt_H]

I can't remember how I have my setup configured, but you should be able to get the prefs tool working if you install ClassAct.

[Xanxi]

So, your setup is actually able to play MIDI?

EDIT: well, i do have Classact up to date, and it is not Reaction enough.
The prefs program asks for resource.library. I have added this lib, but then i get a guru.

[Matt_H]

Ah, you're right - rereading the readme I see that it will need OS 3.5 for the GUI.

It's been about a year since I experimented with AMidi, trying to remember how I had it working...

There are no software instruments in the install archive. Does one of the docs say anything about TiMIDIty instruments? That might be what you need for software playback, but it might be PPC only. For hardware playback, you need an external device and CAMD. In that case, AMidi serves as a wrapper for CAMD.

I don't think it's possible to map AMidi to GMPlay... although maybe it can use GMPlay's software instruments.

[Xanxi]

Yes i have installed the CAMD option.
But the doc says that we can use GMPlay with CAMD, so i have installed this package too.

Here is what i get with a SnoopDOS. I think i need to access this configuration file to edit it by hand but i do not know where it is...


Count Process Name       Action     Target Name                 Options Res.
----- ------------       ------     -----------                 ------- ----
1     C:PlayMidi         LockScreen Workbench                           OK  
2     C:PlayMidi         ToolType   DEFAULTIMAGE                        Fail
3     ramlib             Load       DEVS:amidi.device                   OK  
4     ramlib             Open       DEVS:amidi.device.info      Read    Fail
5     ramlib             Open       ENV:AMidi/AMidi.prefs       Read    OK  
6     ramlib             Load       DEVS:AMidi/Drivers/Software         Fail
7     ramlib             Open       DEVS:AMidi/Drivers/Software Read    Fail
8     ramlib             Load       LIBS:Software                       Fail
9     ramlib             Open       LIBS:Software.info          Read    Fail
10    ramlib             Load       LIBS:libs/Software                  Fail
11    ramlib             Open       LIBS:libs/Software.info     Read    Fail
12    C:PlayMidi         LockScreen Workbench                           OK  
13    C:PlayMidi         LockScreen Workbench                           OK

[Matt_H]

Based on that SnoopDOS output, the config file is ENV:AMidi/amidi.prefs.
Remember to copy it back to ENVARC:AMidi when you're done editing.

[Matt_H]

Okay, I've now got my setup in front of me, and I can't get PlayMIDI working either. Simon2Jukebox works, though...

The config file should be usable out of the box, and you do need GUS patches to go in DEVS:AMidi/Patches. WarpOS is required for the software driver.

That's what the docs say, at least. I could swear I had this working before...

EDIT: Okay, now it's working. I set the AMIDI_PATCHPATH env var, rebooted, and Blue Danube is now pouring out of my speakers. Not sure if the env var did it, or what, but there you have it.