Excellent!
I have details.
First, I truly regret confusing you. My instructions were poor.

The "Nemo" camd interface is NOT the serial port, it's the "second" serial port header on the motherboard.. That was also my mistake. Using that requires a small circuit, just a couple resistors and an optocoupler.. but the result is a CAMD in and out, which you have now already with them USB MIDI interface.

If the Miracle driver "hits the serial port directly" things get a bit tricky. If it writes at the "device level" it just MIGHT .. but there's a lot more questions first. Deeper than I should dig right now.

"Blue Ribbon Soundworks" was Todor Fay. In his earlier career he wrote Soundscape, then opened Blue Ribbon and wrote Bars&Pipes. He was eventually bought out by Microsoft and did considerable work on their multimedia layers. I believe his latest company is "True Blue", but I could be mistaken.

I was able to download the miracle disks (3). I was able to run disk 0 ONCE, it locked up at the banner.. I was never again able to unpack the ADF files. Apparently I have no idea what am doing.

BUT HERE"S THE GOOD PART: If the Miracle software, or ANY program tries to open ANY camd port, IT WILL SHOW UP IN CLUSTERLIST.
That's your HUGE indication that the program is CAMD capable. And yes, we can easily "patch" from and to any way we want.

Finally, if at any time you'd like to rename "U2MIDI Pro" to "MiraclePiano", or just "Piano", or anything else, I'll send you a file that will make the change for you. Just tell me what you want.

Suggestions:
You need to figure out if the Miracle Keyboard can be used by a MIDI player. It MIGHT also work as a sound module, OR it might only be an input device.. Easiest way: Download CamdPlay, and download a few MIDI files. Open CamdPlay, select "U2MIDI Pro.out.0" as the destination, then open a MIDI file and press play.
I read Somewhere that audio out is only a metronome click.. I don't know. That seems like an odd choice. But then, who knows?

Congrats on getting connected. There is a public "BArs&Pipes" with camd connections, and "Horny" is another sequencer. And if you need a sound module, Timi is free and works fairly well too.

Don't be afraid to email me personally if you have questions about CAMD.. lylehaze at gmail dot com

This is good news.
So far, the biggest failure is my instructions.

The point I failed to explain is that I don't know WHAT your interface would call itself. I used SOMETHING and ANYTHING as examples to be replaced with whatever you find. But I failed to explain that clearly.

I see that you have installed the nemo CAMD driver. _IF_ the original MIDI cable that shipped with the Miracle keyboard fits the serial port on your X1000, then this driver should work. I didn't mention it, my mistake.

Let me try again:
type into a shell the following line
MidiWatch "U2MIDI PRO.in.0"

If you got the capitalization exactly as you saw it in ClusterList,
you'll now see stuff flying by as you press and release each piano key.
Note the quotes, needed because of spaces in the name.
That last character is a ZERO, not a Letter o.

If you DON'T spell it right, you'll see a new cluster with your
misspelled version show up at the bottom of the list. Ctrl-C
in the shell to exit and try again.


Whether or not that works.. here's a no-typing test;
Run "ShowKeys", and select
U2MIDI PRO.in.0
from the largest gadget on the top.
Play piano, watch the showkeys window.

Put simply, the notes you play on your piano will arrive
at "U2MIDI PRO.in.0"

And IF your miracle keyboard will convert outgoing MIDI
to audio, it can be played at "U2MIDI PRO.out.0"

If you ever add another identical interface, it will show up as
"U2MIDI PRO.in.1" and "U2MIDI PRO.out.1"

There IS a way to make it show up as MiraclePiano.in
and MiraclePiano.out. But we will save that for another day.

Here's my ClusterList, always open on my workbench:

** CAMD Cluster List **
MIDI IN 1
MIDI IN 2
MU90R1 response
EDIROL UM-880.in.3
MU90R2 response
EDIROL UM-880.in.5
EDIROL UM-880.in.6
MBMixer response
UM-880 response
MIDI OUT 1
MIDI OUT 2
MU90R1 Bank 1
MU90R1 Bank 2
MU90R2 Bank 1
MU90R2 Bank 2
EDIROL UM-880.out.6
MBMixer control
UM-880 control
UMC404HD 192k.in.0
UMC404HD 192k.out.0
VU
mix
HD404
out

Right now the piano and (new) drumkit are not connected.
SOME of these are their branded interface names,
SOME are translated to what is using them, like the
two MU90R Synthesizers, with two banks of 16 each.
And some are NOT interfaces, but just meeting points
for programs to combine and share MIDI controls, like
"mix", which combines MIDI controls from a bunch of
different places, and routes them all to my MIDI controlled
audio mixer. (MBMixer Control).

My point is that CAMD can do a LOT of neat stuff, WAY
more than just connecting to a MIDI interface.

I'm SURE the U2 MIDI pro will work, because the driver
has accepted it and put it in the list. Sorry for the confusion,
I hope this has sorted you out.

edit: corrected "U2 MIDI PRO" to U2MIDI Pro"

In anticipation of your new tools, here's a quick start guide.

Download and unpack https://os4depot.net/share/driver/misc/camdtools.lha

Open a shell and run "ClusterList" with no arguments. slide this shell aside where you can keep an eye on it. It will likely say ** CAMD Cluster List **
and not much else.
Now connect your new MIDI interface, If all goes to plan, you'll see two new entries pop up in the cluster list. SOMETHING.in.0 and SOMETHING.out.o

Obviously SOMETHING could really be ANYTHING.. or whatever..

Connect interface IN to Keyboard OUT, connect interface OUT to keyboard IN.
power up the keyboard. in another shell type
midiwatch SOMETHING.in.o
details: cluster names are case sensitive, and if there's any spaces, put quotes around it.

play the keyboard, you should see a lot of text flying by.. this is a really good sign.

Run "ShowKeys" from shell or mouse. Click on the largest gadget across the top, select "SOMETHING.in.0"

Play the (real)keyboard again. you'll see your playing drawn in ShowKeys, and if you left the MidiWatch shell open, you'll still see it there too.


Now we have fully tested the IN. _IF_ the miracle keyboard also supports MIDI to Audio, then you can test it by downloading CamdPlay, select SOMETHING.out, and play a few MIDI files.. I don't know what the miracle keyboard supports there.

You can unstall Timi from the extras disk and use it as a soft synth if you like.

Details: It IS possible to "alias" friendly names in place of whatever your interface calls itself.. Somewhere deep in the readme or ask if you'd like.

ClusterList puts almost ZERO load on the system, it literally wais for a signal from CAMD that triggers only when the list should change. So leaving it open is a great way to see what's currently connected.

ShowKeys can show any combination of 1 to 16 channels, can be run multiple times to show different instrument parts, different MIDI streams, whatever.

There's also a "Midi Active" tool that shows instrument activity per-channel.. Useful for watching a MIDI file play.

There are lots more tools than what's in CamdTools. I write new ones and rewrite old ones all the time. If you have requests or suggestions, just ask. I might well have it already.

Have Fun!

Edit: ClusterList is not included. The old "ShowClusters" is there instead.
It only shows what's there when it runs, I don't think it automatically updates.
I need to update and submit new tools one day.
Just getting everything organized could take a good part of a day.
Might as well wait until I have the Cluster Requester replacement that I'm working on now ready too.

Edit2:
https://os4depot.net/share/driver/misc/clusterlist.lha
Clusterlist is a separate submission. Throw out ShowClusters, use ClusterList

Score is .. stalled.
I have LOTS of excuses. I've been really busy, I've had a major heart attack, I've been caring for my wife as she recovers from stage 3C cancer, I've had two changes of employment. and I'm exhausted 95% of the time.

My Amiga work for a while shifted from MIDI work to the Audio driver for Tabor/A1222(+). It was working great for me but refused to work for most other people, I spent two years trying to figure that out. Turns out that MY board was "to specification", but almost all others were shipped with 4G of RAM, and kickstart was not configured correctly. I had no way to figure this out until I was loaned another board. It only took a few weeks from there to at least figure out what was wrong. Steve worked hard on getting that right for me.

RIGHT NOW I am not doing any more drivers. I AM working on CAMD tools (all weekend, Happy Fathers Day!) I still poke around in Score occasionally, and I am working on a CAMD recorder that would be a great bit of code to add in to Score.

And I HAVE to mention, my wife got me a most interesting MIDI toy today, look up "AeroBand PocketDrum 2 MAX", better yet search it in YouTube.
I've not even connected it yet, but it will definitely make the MIDI recorder a lot of fun to play with.

SO, Score is still a private project, and progress is too slow to describe.
Best estimate: "Two More Weeks".. (sorry, I couldn't resist)

@sacc-dude

Sorry for the late reply. The network filters at work are not friendly with this site.
I looked over the popular shopping website, and if a 6 foot lead is long enough, I can recommend the "U2 MIDI Pro" from CME. While I cannot clain "tested", it clearly states "Class Compatible", and it's a reputable company to work with. Cost is about $20.

The big interface I wrote the driver on is no longer available, and wirth eight ins and eight outs, I have enough open ports that I have not needed to buy new MIDI interfaces for a while. Also, much newer equipment is direct to USB, so they just plug in.

Of course, the "extra" software with the interface won't run on Amiga, but I suspect CamdTools can do all that and more for you.

About the "Miracle Keyboard".. If it is the Amiga version, the software will only see the keyboard if it uses camd.library. I don't know the software well enough to tell.

Let me know how things work out!
Lyle

Any USB to MIDI device that does not require "special" software should work. We have had "class compatible" USB to MIDI driver for a long while now.
The driver supports any CAMD aware programs.

@boabster
I am not the author, but I THINK this new USB auidio driver is for Audio Class 1 devices only.

In past projects of my own, I had a lot of trouble explaining that Audio Class 1 and Audio Class 2 are not compatible.

So I recenly wrote "AudioClassID", to at least make it easy to TELL which is which. When you run it with no other arguments, the last line of each interface says "USB Audio Class Compliance: " followed by 01.xx or 02.xx

Since I'm digging into details, here's the back story:
Audio was the very first USB Class. When the Audio class was laid out, there were a few details that were not defined properly. So manufactuirers each decided how to fill in the blanks. This made the driver more complicated, and the worst part is that the "fancy" bits have no documentation.

Eventually they decided to re-design the standard. Part of the changes meant changing descriptors, structures, and sometimes even used the same names for changed parts. At least it's all documented now, but there's a LOT of class 1 devices already out in the wild.

So the driver has to check this "Class Compatibility" when they attach to a new device. The Class 2 drivers know to check. Older Class 1 drivers were not expecting a redesign, so they are often unaware of the need to check this.

And that's probably way more than you wanted to know. I THINK he said this driver is for class 1 devices only. I also recall you said your device said class 2. I think you might find the problem with that mismatch.

I do have a class 2 driver in the works, but like many of my projects it's not been worked on in a while, and I don't plan on connecting it to AHI. Most likely it will go directly to AudioLink.library instead. (AudioLink is another unfinished project, I have a lot of those)

Again, too much information, but it'll give the people just browsing something to read today.

I hope this answered some questions.

@Boabster

You are running multiple audio drivers.

Open Prefs/AHI
Select "Music Unit" , then select the new USB Audio driver
Select "Unit 0", then select the new USB Audio Driver
Select "Unit 1", then select the new USB Audio Driver
Select "Unit 2", then select the new USB Audio Driver
Select "Unit 3", then select the new USB Audio Driver
Select "Save"

I never cared for the GUI design of AHI Prefs.
I think having tabs for each unit would be more visually clear.


Let us know how that works out,
Lyle

My micro-A1 has been feeling poorly.
Today I replaced the thermal pad between the processor and the heatsink, and the machine seems much more stable now.

OK, this is no great surprise, but perhaps this might be a useful reminder for others with Se / Xe / Micro machines.

And another question on the same topic: My X1000 is still as solid as a rock, but at what point should I consider repacking the CPU heatsink on it?

It's nice to be in a community where our machines can outlive a CR2032.
But that's another topic entirely.

Version 2.1 now plays test beep on Creative Play3!

The sound breaks up a bit, but it plays, it completes, and that's a great bit of progress.

It's a good day for good news.

Excellent!!

As it happens, one of my three current projects is also USB audio.

So much to talk about.. I also have some working code for Audio2,
written for the Behringer 404HD.

There are quite a few challenges to making AHI work for USB. I hope you beat them all and I'll help if I can in any way.

There are a few things in Audio1 that were left undefined, so there's a few different ways of doing things. My latest code is for one specific device, on the thinking that if I get one "just right" then release the code it might grow from there. I was/am writing for the creative SoundBlaster Play3. Nothing particularly special about it except it's a name brand and should be available everywhere.

I suspect you're already past where I am right now. I look forward to downloading and testing tonight if I get a chance to do so.

///////////////////////edit/////////////////////////////
The Play3 is recognized, but when I play a test sound
everything stops..
Also it offers 7.1, which is not a supported mode in this adapter.

But I am very enthusiastic. It wouldn't hurt my feelings at all
if your driver is ready before mine is.

My "Amiga Time" is very limited, perhaps this weekend
I'll find a NULL modem cable and grab some debug for you.

//////////////////Another Edit ////////////////////////////
Based on Sashimi output, it all looks good until it tries to set
interface 1 to alternate 1. That is the correct choice, but immediately
after that everything stops.

That stop is from the libusb code..

I might be all wrong, but I don't have a null modem cable handy
tonight, it'll, have to wait for the weekend.

Good Luck! We're all rooting for you.

Niels:
Thanks very much for your information.
I'm still muddling through this on the X1000.
As I understand it, CFE loads AmigaBoot.of which makes the list of available boot volumes.

A few questions:
Do we have any documentation on amigaboot.of?
is 54.15 the "current" version of amigaboot.of?
what disk formats are supported as bootable?

Yes, very basic questions, I'm just trying to figure out how I broke it.

This is all right on target for me.
Affected machine is X1000, I could no longer select the boot volume.

And I'm not quite fixed yet.

Here's what I have now:
8.WB:> nvgetvar MENU_3_LABEL
Boot Select Menu
8.WB:> nvgetvar MENU_3_COMMAND
setenv os4_bootdevice auto; boot -fs=amigafs ide0.1:amigaboot.of

This goes off to a boot select screen that never shows a menu, just a short delay before telling me that I get my default boot volume, which is presumably ide0.1

Yes, I'm too clumsy today, I'm not anxious to break my primary machine. So what should my MENU_3_COMMAND look like to get the selection menu?

And yes, I think this was broken by an update, I'm not sure which one.


Many Thanks for a helpful community,
Lyle

@AlexC

" If you want I can send you one as I really only need one, if I ever get around to using it."

Thank You. At this time I am just too busy with "real life".
I'll spare you the list, but it looks to be getting worse instead of better.

I DO finally have an X5000, and I also replaced my dead A1222. So I'm setting myself with four working NG Amigas now. (possibly preparing for retirement??)

But I have more projects than I can handle, and not nearly enough time to make it happen.

Thank you though kindly for the offer.

" if I understand correctly, the xena resource doesn't really do much setup, but rather acts a semaphore. "

Exactly correct. It might also check machine type, and you can see how well THAT idea worked out. ;)

This might be "old news", but is does show one useful application:

I added an SD card and a serial port level shifter to a Xorro card. From the XMOS community I borrowed code fort a serial port and a filesystem for the SD card.

I set it up to capture and save all incoming text to the SD card, filename was generated by date and time. Then I hooked it up to the debug output of the X1000. Once it's "running", all debug output gets saved automatically.

You could browse and import the saved files to the Amiga or remove the card and read it from anything that can read SD cards.

Because it's independent of AmigaOS, it's capable of saving it all off even when the OS is having troubles.

Now, to make this more interesting: Both the X1000 serial port AND the serial on Xena are capable of WAY higher baud rates. The limiting part are the voltage level shifters. There's a small pin header on the X5000 that will let you pick up the serial output before that shifter, so it SHOULD be possible to run the serial speeds up as fast as the SD write routines can handle. I assume the X5000 serial port can also run faster..

Unfortunately I loaned out the Xorro board and it was never returned, so you'll have to take my word for it.

Granted it's not "rocket science", but saving debug without a second machine, and the possibility to run the debug so fast that any slowdown would be minimal.. Well, it's at least useful to programmers and beta testers!

@NinjaCyborg

The "Amiga Community" is a LOT of passionate people, with a LOT of different ideas about what is best.

Some communities are built on arguments about how things should be done. Some communities take a hand in moderating comments that are not constructive.

Getting moderated doesn't mean you are wrong, it just means that community is working to reduce .."less productive discussions".

The moderation is a thankless but absolutely necessary part of keeping some sites better than others.

But that's just my opinion, and it's worth exactly as much as I was paid for it.

@jaokimQuote:

Quote:

The XTools were originally written be Segher Boessenkool. (I always misspell that, sorry!) from the community around those chips. I ported the tools to the X1000. As I mentioned before, the X5000 had to completely change the way the Xena chip is attached to the localbus.
As far as I know, the XTools were not ported to the X5000 platform.

The port was not at all difficult. I had only the "Technical Reference" of the X1000, I suspect the X5000 manual has the necessary information. If you look over the source code of the XTools, all the Amiga specific stuff is in a single file, and hopefully easy to understand.

The nature of the difference: The X chips were "designed" to be connected directly to a localbus, but were never used that way before the X1000 came along. Possibly due to "die shrinks", where silicon is reduced to the smallest working footprint for production, the transistors driving the localbus are not strong enough to drive the bus load. This means on the X1000 we can write TO the chip, but reading FROM it requires way too much time to be reliable (and a few other ugly tricks as well)

So, my limited understanding of the X5000 is that some other chip is now between the two, and we read and write from registers of that device, no direct connection to the Xena chip.

All these years, and I never had an X5000 to work on, so I couldn't really figure it out. I got an X5040 just a couple months ago. At this time I'm not able to take on any new projects, but I can test or advise anyone who doesn't mind waiting a few days between replies.

To be honest I've only JUST got it up and running, I still spend most of my limited Amiga time on the X1000.

I can confirm that the interface between the chip and the bus is different on X1000 and X5000.
It's fair to call the X1000 interface "broken", at least in one direction.

I could get deeper on exactly what and why, but I'm at work right now.

This looks like an excellent resource. I would love to dig deeper if I can find the time.. Time for me is always the most difficult part.

Also worth mention is the purpose and intention of the "Haze-Xorro" pins on the X5000 boards. these should allow you to catch debug output at rates that would normally be impossible. I had put together a card to do this on X1000.. Having this on the X5 series makes it MUCH easier. All that's left is some sort of storage to save it on to. I was using an SD card.

But I'm not here to rehash an old project. This is good news, and I'll offer whatever help I can if asked to do so.

Lyle

You can make an A1222+ mixer with nothing more than MIDI messages through camd.library.

In fact you can completely take over the audio chip with MIDI messages. ALL register accesses to the audio chip are done through camd, even by the driver.

This made driver writing SO MUCH easier. I could literally "fiddle around" with the audio chip live from a GUI.

But you already know I play with MIDI a lot.