Solved "Help" a driver is missing to be able to port Bars&Pipes: AROS FORUMS

Solved "Help" a driver is missing to be able to port Bars&Pipes

Last updated on 1 year ago

AROS

development

Track thread Print

Amiwell79Distro Maintainer

Posted 1 year ago

#20

hitchhikr it is also possible to have the midi driver for 64-bit aros

Amiwell79Distro Maintainer

Posted 1 year ago

#19

Alfred told me that the software works very well after the latest fixes also to the camd.library thank you all

"Now it is possible to address so-called multi-port USB-MIDI interfaces.
This means that theoretically 16x16 = 256 independent MIDI channels
(different instruments) can be addressed simultaneously"

Edited by Amiwell79 on 23-02-2024 09:39, 1 year ago

2 users reacted to this post

aha, miker1264

Amiwell79Distro Maintainer

Posted 1 year ago

#18

ok many thanks

hitchhikrSoftware Dev

Posted 1 year ago

#17

Yes, the latest version is here: https://hitchhikr...sbmidi.lha

There was a bug in camd.library i fixed as well.

Mr. Faust confirmed that everything is now working properly.

f.

2 users reacted to this post

miker1264, aha

Amiwell79Distro Maintainer

Posted 1 year ago

#16

I personally don't even have the equipment apart from the software to test the new changes but maybe someone else can do it

Amiwell79Distro Maintainer

Posted 1 year ago

#15

i must inform alfred faust but he is using icaros desktop and it is obsolete at the moment we have no midi software to test deadwood

deadwoodAROS Dev

Posted 1 year ago

#14

Hi,

I integrated changes to camd.library and camdusbmid.class into ABIv0 build. Please see the attached patch:

https://axrt.org/...-1-P01.zip

Let me know if the changes work correctly.

1 user reacted to this post

aha

Amiwell79Distro Maintainer

Posted 1 year ago

#13

testing continues alfred is working on porting bars&pipes

2 users reacted to this post

aha, Argo

hitchhikrSoftware Dev

Posted 1 year ago

#12

Yes remove the older one (mididriver).

AMIGASYSTEMDistro Maintainer

Posted 1 year ago

#11

hitchhikr wrote:

- Copy "usbmidi" into devs:midi (and remove any file that may be there before).
.

If I understand well it has to be removed into devs:midi also the file named "mididriver"

AROS One All Thread
AROS One Home Site
AROS One Facebook

Amiwell79Distro Maintainer

Posted 1 year ago

#10

ok hitchhikr

hitchhikrSoftware Dev

Posted 1 year ago

Hopefully the last version of the driver (renamed usbmidi); there were two other bugs in SysEx messages sending.

https://hitchhikr...sbmidi.zip

Same deal:

- Copy "usbmidi" into devs:midi (and remove any file that may be there before).
- Replace "camdusbmidi.class" from SYS:Classes/USB with the one included in the archive.
- Reboot.

I sent a copy of this to Alfred Faust.

f.

1 user reacted to this post

deadwood

Amiwell79Distro Maintainer

Posted 1 year ago

we await the release of the software

Amiwell79Distro Maintainer

Posted 1 year ago

Everything works thank you I heard Alfred Faust and the tests he did with the midi sequencer Bars&Pipes are positive

Edited by Amiwell79 on 16-02-2024 10:41, 1 year ago

1 user reacted to this post

aha

Amiwell79Distro Maintainer

Posted 1 year ago

thank you I will inform alfred in fact has problems it seems to me

Edited by Amiwell79 on 15-02-2024 10:34, 1 year ago

You do not have access to view attachments

hitchhikrSoftware Dev

Posted 1 year ago

I found out that there are two bugs in camdusbmidi.class.c which prevent from sending several midi messages in the function nParseMidiOut() :

Code Download source

 

 switch(cmd>>4)

 {

 case 0x8:

 case 0x9:

 case 0xa:

 case 0xb:

 case 0xe:

 if(len < 3)

 {

 len = 0;

 break;

 }

 len -= 3;

 *out++ = cmd|chan; <<<< should be: *out++ = (cmd >>4)|chan;

 *out++ = cmd;

 ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask;

 *out++ = buf[ca->ca_TXReadPos];

 ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask;

 *out++ = buf[ca->ca_TXReadPos];

 ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask;

 goodpkt++;

 break;



 case 0xc:

 case 0xd:

 if(len < 2)

 {

 len = 0;

 break;

 }

 len -= 2;

 *out++ = cmd|chan; <<<< should be: *out++ = (cmd >>4)|chan;

 *out++ = cmd;

 ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask;

 *out++ = buf[ca->ca_TXReadPos];

 ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask;

 *out++ = 0;

 goodpkt++;

 break;

A fixed version is now included within the archive: https://hitchhikr...driver.zip

So to install the whole stuff:

- Copy "mididriver" into devs:midi (and remove any file that may be there before).
- Replace "camdusbmidi.class" from SYS:Classes/USB with the one included in the archive.
- Reboot.

f.

Edited by hitchhikr on 15-02-2024 04:44, 1 year ago

2 users reacted to this post

retrofaza, miker1264

Amiwell79Distro Maintainer

Posted 1 year ago

we await news from Alfred

Amiwell79Distro Maintainer

Posted 1 year ago

no problem i can't test the driver properly i don't have the equipment nor the software i'll pass the file to Alfred hopefully it will work thanks for the help

1 user reacted to this post

miker1264

hitchhikrSoftware Dev

Posted 1 year ago

Hi,

My bad, I didn't check the out going data code assuming it would work but of course it didn't and made AROS to crash.

I upload another version which doesn't crash ( https://hitchhikr...driver.zip ), i also added MidiThru (which forwards messages from a port to another) and MidiSendC (which sends a middle C to a given port) shell commands.

The MidiWatch tool logs the out going port properly so the data is sent but i'm not sure that it reaches the Midi device itself.

Sorry for the inconvenience,
f.

Edited by hitchhikr on 14-02-2024 19:48, 1 year ago

Amiwell79Distro Maintainer

Posted 1 year ago

Alfred writes:

What I've done:

1. Connect USB-MIDI-Interface: Edirol UM-1 - success
(is bound via camdusbmid.class to Poseidon-USB-stack, poseidon.library,
showen in Trident Prefs for Poseidon)

2. Start BarsnPipes - success

3. Set MIDI-connection: connect to cluster "mididriver.out.0" - success
(this is done via camd.library)

4. Send a simple NoteOn-event
BarsnPipes->mididriver.out.0->camdusbmidi.class->UM-1 - failed
(this results in a total crash)

there is something wrong with the driver unfortunately

Edited by Amiwell79 on 14-02-2024 17:41, 1 year ago

You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.

Moderator: Administrator, Moderators

Users who participated in discussion: deadwood, AMIGASYSTEM, Amiwell79, Jeff1138, hitchhikr