Quote:

Correct. I plan on finishing the X1000 audio driver before pursuing this further.
Once work on USB audio continues, the USB audio driver will only work on devices that are "Class Compatible". This means they followed the standard for operation instead of making their own format and procedures.
It also depends on the type of USB chip that you are communicating through, though we are known-good with the X1000 and SAM-FLEX (probably all SAMs, testing continues) native USB ports.

I am just beginning to gather data on what works and what does not. It looks like the "Creative XMod" and "Blue Snowball Microphone" do not work (not class compatible), and the "TTUSB turntable" and "Diamond Sound Tube" are working well. There is also a monophonic headphone set that worked, but I never got the name. Last night I also found out that with a slight file modification, I can play back recordings made over USB with the AHI Audio:device quite simply. This makes sound playback as easy as "copy soundfile AUDIO:B/16/C/2/F/48000" for playback of a 16 bit stereo recording. Nice touch.

If you, or anyone, wants to determine if your device is "Class Compatible", there are two options: You can plug it into your Amiga and use sys:utilities/USBInspector. If it shows up there as "Audio Class, Subclass 2" (probably more than once) then it is likely to work. I also have a small program that will attempt to record and play back that you may use for testing. Just PM me with your E-Mail address if you'd like to give it a try.

Lyle

If you get "No suitable recording device found\n", then it's game over, device not class compatible. It MAY also fail if on an unsupported USB type.. since ISO transfers are not supported across the board.. but we know that native X1000 and SAM ports should be OK.

I just played with the alternate setting option, and it may be broken.

But for those who were successful in the past, a line like
USB_Audio_Test r ram:soundfile p ram:soundfile
should record about five seconds, then play it back for you.

It is a VERY early test tool, but it will at least confirm class compatibility.

We can find out if it's class compatible any time you'd like.
Just check your PMs.

Lyle

Quote:

True enough, but that wasn't my intent.

I don't do public announcements with nearly the grace and style of some others, so I play in binary mode, and let Trevor handle the ASCII content.

Trevors Blog

But as I stated twice before. I gave a wrong answer, and I thought it a good idea to own up to it. Mis-information is not good for our community, and I try very hard to keep it as straight as possible. If it weren't for the want to correct my error, I would have just let it all rest until Trevors blog published.

If anyone is interested, there is some further information at the link posted above.

Now back to the compiler for me...

Lyle

Quote:

When I am wrong, I'll admit it. Even though the information I gave was the best knowledge I had at the time.

Personally, as an avid supporter of Music on the Amiga, I have wanted support for USB Audio for a LONG time. And I have said at least a dozen times that if ISO transfers are ever supported, I would gladly write the audio driver myself. (I think it would make a nice match for my existing USB MIDI driver)

Since that post was made, I found out that there is some limited support for ISO transfers, and that this support was added some time ago, but never fully tested.

I can tell you that two of us have successfully recorded and played back audio through USB.. and that further development is planned, AFTER I complete what is in front of me right now.

More details are coming, keep an eye on Trevors blog for more info.

LyleHaze wrote: Quote:

At the time of writing, I believed this to be correct information.

I was wrong.

I tried something with CUPS a few weeks ago..

I installed my Samsung ML1710(cheap) laser printer as a local USB printer on a Raspberry Pi. I set up CUPS to accept remote print jobs. and I was even able to print from WIndowsXP as a Postscript printer! (The printer is way too dumb for that, but CUPS converts nicely).
Sadly, I was never able to get lpr.device on OS4 to see the print server. The best I could get was sending the job without error, but the printer never moved.

It did seem like a good idea, using a $35 pi board as a CUPS server, so that we could reach it from OS4 as a postscript network printer.

But after a few days of almost working, I gave up.
Maybe next time I'll have more luck.

Oh no. "Color Wars" again?

Glad for ya. Whichever color you choose, it's a great machine.

Quote:

The USB HID class is for keyboards, mice and other "Human Interface Devices".. (or anything you can squeeze into that definition)
HID device drivers may use only Control and Interrupt transfers on the USB bus.

Audio devices require a steady information stream to operate. The Audio Class compatibility requires that Isochronous transfers will be used.

At this time, Isochronous transfers are not supported in OS4.

So, it is not currently possible to write a Audio Class compatible driver for OS4.

If you'd like, feel free to Google "USB transfer types" for more information. Or try "Audio10.pdf" for the audio specific details.

KimmoK,
USB sound requires support for Isochronous transfers, which is not yet available.

Thank You!
I'm off to write a quick "News Item" announcing the new software.

LyleHaze

Hello!
I uploaded five packages about two days ago, all related to CAMD.
The two new packages music/play/CAMDPlay.lha and music/play/SoftSyn.lha both posted in the last few hours.. but the three files that are updates of previous releases seem to be stuck. Those are driver/misc/camd.lha, driver/misc/usbmidi.lha, and driver/misc/camdtools.lha.

I'd really like to announce all of these at once if possible.
I checked my current (lylehaze@gmail.com) and my previous (lylehaze@bellsouth.net) and had no emails from the Depot in either inbox.

I am pretty sure I had the right password for the file updates.. I hope so anyway.

If there is anything I can do, any questions I can answer to help you along, please feel free to ask.

Thank You!
Lyle Hazelwood

lylehaze@gmail.com

[edit] sorry folks, I assumed that the OS4Depot channel was not posted to the main window. So much for announcing everything at once!

kas1e is correct, but I noticed you mentioned some ahi code.

Probably because ahi is written for multiple platforms, they default to inline code, unless you
#define _no_inline
in your program. This is kind of backwards from the way most OS4 code works, but once you know what to look for, no problem at all.

Have Fun!
LyleHaze

You might want to try this:
Strohmayer.org

That should got you going.


LyleHaze

Wow. Seven pages of information, and not one MIDI device in sight.
I can fix that. I have an Edirol UM-880 and a Behringer BCR-2000 that are working great. I can confirm that the "sister products" Edirol UM-550 and Behringer BCF-2000 work as well. I've had great reports on a bunch of M-Audio gear with USB ports, but no details at this time.

If you're also keeping notes on the type of equipment, the two Edirol devices are "Multi-port MIDI interfaces", and the Behringer ones are "MIDI control surfaces"

LyleHaze

I had a VIA based PCI card ready to try.
With Update 2 it would only hang the boot process, so I waited for the new update.
Under update 3 it still hangs, just cycling the splash screen repeatedly.
My PCI slot worked fine when I had a SoundBlaster card in there previously, so I don't think it's a slot problem.

It's not a big deal, I'll order a NEC based card the next time I go shopping.

@GrumpyOldMan

As usual, I got here late.

Lots of good information has been gathered here. In the interest of making it just a little more complete:

The Micro boards DO have battery problems. Or at least some of them do. I have found that anything less than a very fresh battery causes instability for me.
A bit of research lately shows that a "BR2032" battery holds it's voltage better than the usual "CR2032". I have one on the way right now. If you have battery issues, it might be worth a try.

If you like to play with MIDI devices, the built-in joystick/MIDI port is useful for MIDI OUT only. the MIDI input problem was never solved. To get a working MIDI IN you can either put a soundblaster card into your open PCI slot (which also gives you a whole new sound board) or you can use any USB MIDI devices that follow the USB-MIDI "class compatible" interface. This is the preferred way to go, and you can have many MIDI ports active at once. More details are in the usbmidi.lha driver package on OS4Depot.

It was mentioned earlier, but you need to be cautious of the serial and USB pinouts on the micro motherboard. The page that #6 mentioned in post 7 is useful for that.

Have Fun,
LyleHaze

@Raziel

So sorry.. I got here late.

It sounds like you've figured it out.. if I understand you correctly.

So, the way usbfd works is not quite like a normal CAMD interface.. It is called by the USB stack, NOT by CAMD.. when it finds a workable MIDI interface, it opens CAMD library just like any other application... NOT the same as the other drivers would. This also has the advantage of allowing the USB interface(s) to exchange complete messages, without CAMD having to parse them from bytes.

So, in reality, it's NOT even part of CAMD, it's just another program that opens CAMD for communication.
SO if your CAMD was not in the library path, it would SEE your interface, but would not be able to register it into the CAMD port list.

Like everything else, it makes sense once you know what it's trying to do.

I regret my slow reply, I have moved, and I am now working a job with ridiculously long hours, sometimes working seven days a week. I just don't have enough time to "play" anymore.

I can tell you that usbfd was developed with a Roland UM-1, and later with an EDIROL UM-880, so it should be completely compatible with them both.

I can also (happily) tell you that I have banked enough to get an A1X1000 as soon as they are available, and my very FIRST install will be CAMD and USBFD.. I have really missed my little playground.

I'm very happy to hear that CAMD and usbfd are still getting good use. I'm hoping to do some more application development once the new Amiga arrives.

Oh, and if someone needs to reach me, my nick at gmail dot com is checked daily.

LyleHaze

Oh, and thanks for the great laugh.. I needed that!
Nice to know I'm not the only one who makes occasional mistakes.

@wizzard_o

The micro boards had the USB header pins wrong.
If you had your case ports working on the micro, then the pins were probably moved around a bit to match the odd micro pinout.

I have NOT played with a Sam or Sam Flex yet, but I did document the odd micro pinning of the USB (and serial) ports in this article:
http://www.ncscaug.us/ua1page1.htm

I hope this helps.

And for the record, USB MIDI ports are WAY more efficient than soundcard ports.. If you use MIDI much at all then USB is the way to go.... That may be just an opinion, but it's one I can back up with facts. :)

LyleHaze

@Kicko

Sorry, I have too much going on right now.
Finding a job is getting near impossible, it looks like I'll be selling my house soon.

Besides, I choose my own projects. You should know that by now Kicko!

I know a lot of people want good trackers for the Amiga, I wish you success with this port.

LyleHaze