and then go here for a bunch of supported radio streams.
Quote:
AmigaAMP 3.27 (PPC/OS4.x) and (68k/OS3.9) released - More bug fixes and stability improvements
o Streaming: - Added XSPF playlist support. - Fixed playing MP3 files directly via HTTP. - Added HTTPS support via AmiSSL. - Revised stream URL parsing, especially during relocation. - Revised stream connection error display. - Fixed string conversion in case converting from UTF-8 fails. - Fixed connection timeout error requester.
o ReAction: - Revised equalizer button height. - Made left hand side and right hand side buttons in main window the same width. - Time/remain toggle by clicking on time display.
o Skinned: - Corrected display of character 'a-acute'. - Fixed right mouse button handling code.
o OGG: - Fixed error handling while reading OGG files.
o MPEG: - Fixed amp playback of MPEG 2.0 files (smaller frame size).
o GUI: - URL string in URL requester is now static.
o Features: - Added MIDI support by using GUS patches installed in SYS:Utilities/Timi/GUS. - Added raw ADTS (AAC) support for both streaming and file based playback
Have fun!
Thank you @tomsonic for the ongoing development, for always considering feature requests and ideas and thank you for just being a great guy...
Where exactly would you type something in with AmigaAmp?
I have yet to find a window that takes user input (apart from the ASL Requester that lets you choose the music/dirs to be played back, but those would need an overhaul in a system part to work the way you'd like and is out of scope of AmigaAmp)
If you read my previous version of this post disregard it. I overlooked an old version of saved prefs which caused AmigaAmp 3.27 to use mpega.library which doesn't appear to work on my system.
My mpega.library is version 2.4 and is the mpega.library clone v 1.7. Is there another version that I should use??
Edited by xenic on 2020/4/5 17:28:34
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
i "have" a request if possible or if there is a workaround it would be awesome
i am using the last version available on aminet that's the 3.27 for AmigaOS 4.1. I am very happy that now it support midi files with the GUS library but unfortunatly the GUS library must reside in: SYS:Utilities/Timi/GUS As i have few megabytes left in my Sys: partition, is there a way, maybe with an assign to make it points somewhere else? or,even better, to choose the path under the preferences of the program?
For the Assign i tried the following command but without luck:
The first argument of Assign needs to be the (virtual) volume name you want to use. So you can't make an assign that is more than a volume name (i.e. a name followed by a colon, no path after the colon).
Easy workaround: 1) Copy the GUS patches wherever you want 2) Create a timidity.cfg with
##############################################################################
#
# Instrument configuration file for timidity
#
# Specify library directory: dir <directory>
#
# - Multiple library directories may be given. The ones given last will be
# searched first so you can override them in later configuration files.
# Extra configuration files and MIDI files will also be searched in these
# directories.
#
# Set tone bank or drum set to modify: bank <number>
# drumset <number>
#
# Map program number to patch map: <program number> <patch name>
#
# - If the patch can't be found in the library directories, TiMidity will
# search again with ".pat" appended to the name.
# Programs without a loaded patch will be silent, except that for
# banks/drumsets >0, the corresponding patch in bank/drumset 0 will
# be used (if one exists).
#
# Read another configuration file: source <file name>
#
source MyHDD:MyStuff/GUS/Myconfig.cfg
and place it in the directory where AmigaAmp's binary is.
3) Create or copy "Myconfig.cfg" to the GUS patches directory (It consis of all the patches you use and should come with the GUS patches anyway BUT with the path to them pointing to your installed path) e.g.
# Some comments
bank 0
0 MyHDD:MyStuff/GUS/acpiano.pat amp=125
1 MyHDD:MyStuff/GUS/britepno.pat amp=115
2 MyHDD:MyStuff/GUS/synpiano.pat amp=115
...
and so on
Doing it like this since the betas supported MIDI and works like a charm.
May you help me please? i get lost, sorry pal but i am really a newbie about midi and timidy. I just installed Timidy and, if i remember well, i just did an assign and so i can play midi file using gus library(is it correct to call gus directory a library of sound?) and hear midi sound when i play doom.
I didn't know, reading the config file, that I can improve the gus library with better sound fonts??
About AmigaAmp, sorry pal, but I didn't understand exactly what I have to do..
1) I have my Timidity installation with inside the gus directory in the Work2:Musica/Timidity (that's the path)
2) i create a timidity.cfg file with the text you put above and then? where I put that config file?
3) and sorry here i create the myconfig.file and then?
You installed timidity, so you have a timidity.cfg file inside the install dir, I assume?
Copy the following to a file called timidity.cfg and save it into the directory where AmigaAmp's binary resides
# MIDI configuration for AmigaAmp
source Work2:Musica/Timidity/timidity.cfg
Make sure that timidity.cfg (the one from your installation) is really there, or adapt the path.
That's all there is actually. If timidity.cfg (the one from your installation) is correctly set up (and if doom is working for you then I assume it is) you should get MIDI playback from AmigaAmp.
NB: I know that using two timidity.cfg files is pretty puzzling, but unfortunately AmigaAmp relies on the name, as it is built to work (only) with a timidity installation. (Well, not really, if you follow the steps in my earlier post you can use whatever supported patches without the need of installing the whole timidity)
Thanks Raziel, I followed your instructions but still AmigaAmp didn't work for me but at least i discovered how it runs midi files and I discovered that its timidity.cfg file points to gravis.cfg file which pointed to gus library so i edited the path of that gravis.cfg file (it was very easy with the function search and replace) and with one hit of mouse button I replaced the path for all sound and now it works! Thanks
They are called patches. I think it's because, or makes sense since, with MIDI you might be using several of them simultaneously.
No, I think the term originates in modular synthesis. In the world of modulars, you create sounds by patching the various synth modules using cables; the resulting sound is traditionally called a "patch". Non-modular synthesis adopted the term, despite there being no modules or cables.