-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AHI Audio via Raspi? #28
Comments
I am also in to trying to create an AHI-device with 14bit paula playback... Stereo mixer in the pi in other words. Also a MHI-device for decoding mp3:s and such would be wonderful. I will try to get my card working tonight, if I am lucky |
Sounds like a great idea! 👍 |
@hgw77: Thank you for the kind words. |
@Eriond: thank you for repsonse, and you are right the internal audio quality of the raspi is not that good but there are a wide range of USB-Soundcards with much better sound quality that you can use instead? :-) By the way, I love the good old |
@hgw77 you can get as much as 14bit stereo at 56kHz (with more exotic screen modes) thats where AHI mixing in the pi comes in, but then shuffle the mixed left/right as 14bit-hack sample data to Paula... it's an AWESOME upgrade without having to buy expensive audio hardware. :) |
@aiobofh: yes thats what I mean with impressed. The |
@hgw77 yeah. But with a314 allowed to write chipmem the CPU usage (for playback) is close to zero om the Amiga side. |
A now I understand the idea! the PI is doing all the preparations so the paula only needs to play :-) On the other side if you have an PI-AHI Device you can use any player on amiga side that supports AHI (like Eagleplayer or AmigaAMP) to play audio on the PI, but than the amiga needs to handle the encoding of an mp3 or playing a mod file by itself and send the audio data to the PI. |
@hgw77 correct. And we could also have a MHI-device (the API used for stand-alone hardware mp3-decoders) too. just shuffle the mp3-data to the pi, let it decode it, and shuffle the 16bit wav back to the Amiga and then AmigaAmp or whatever shuffels it back to the PI using this AHI-device for 14bit stereo encoding. :) There could also be a short-cut raw-allocating paula directly with the MHI device, but it's not as system friendly, but would reduce the traffic between Amiga and Pi with that bidirectional raw 16bit stereo sample. |
... Hm. On second thought. I think MHI is supposed to hijack Paula directly, since it's constructed for stand-alon output devices. But I have not studied the interace enough to be 100% sure. But it would be nice to be able to mix even more audio channels into the end-output, hence my assumption it's possible to get the raw stream back to the Amiga and sent with other 8 or 16 bit sound-streams to the Pi for Stereo mixing and 14bit hack encoding. |
OK, sadly newer AHI versions will probably not compile for a stock A500 with 68000. I guess if one have a 020-or-better accelerator the idea is still on. I will however not have such card in any near future :( |
Have you tried Run68017? It implements many 68020 opcodes and might let your 68000 run AHI compiled for 68020. |
Nope, I have not tried this. Seems a bit of a flimsy solution. Besides... I can't really see why e.g. 6.0 should not work to compile for low-end 68k - at least not for just a simple PAULA mode (other drivers might not compile, but it's not really needed in this case since I've based my patch on the existing PAULA driver). I'll revisit this project... But then again. The Run68017 might be more useful to get any AHI-capable softwares (players) to actually run on 68000 tho. So it's stil a valuable tip. Thanks @nonarkitten :) |
First of all, the a314 is a realy nice idea!
To use the trapdoor expansion slot in that way could bring complete new possiblitys to the Amiga500 :-)
As I read about
piaudio
the first idea was, why it is not the other way? For Amiga500 there is no modern soundcard available so I was thinking it would be very nice to have aahi.device
or something to play amiga audio through the soundcard of the raspi :-)The text was updated successfully, but these errors were encountered: