The files std.o3 and drums.o3 should be installed along with sbiload when emerge:ing alsa-tools. Reproducible: Always Steps to Reproduce: 1.emerge alsa-tools 2.search for std.o3 and drums.o3 3. Actual Results: The files needed didn't get installed Expected Results: Installed the files I'm also following this up in Forum thread 16200, "Midi on Awe 64 value edition" Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25-gentoo) ================================================================= System uname: 2.4.25-gentoo i586 AMD-K6(tm) 3D processor Gentoo Base System version 1.4.3.13 distcc 2.13 i586-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=k6-2 -O3 -pipe -fomit-frame-pointer" CHOST="i586-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k6-2 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ ftp://trumpetti.atm.tut.fi/gentoo/ http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dfx 3dnow X aalib alsa apm arts avi berkdb crypt cups dga encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jabber java jikes jpeg libg++ libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl slang spell ssl svga tcltk tcpd truetype video_cards_3dfx voodoo3 x86 xml2 xmms xv zlib"
do you have the right tools in your ALSA_TOOLS variable?
According to Gentoos' ALSA guide the ALSA_TOOLS variable is for emerging only the tools needed for a specific soundcard/chipset. I tried setting it to sbawe or something of the sort but it didn't go well with the ebuild. Not having the variable set and emerging should only have resulted in ALL tools in alsa-tools being installed. I don't really see why that would be a problem?
if you could update a fix to the ebuild, that would help out emminsely as I'm going to be swamped for the next month or so...
std.o3 and drums.o3 don't come with alsa-tools... they're only mentioned in sbiload's readme as examples.
Oops! I thought I saw the .o3 files in a filelistsomewhere but I guess not.. However, I did find the FM instrument files (.o3 and .sb) contained in the source package for Playmidi. The ebuild doesn't install them but maybe someone (perhaps me if I ever get around to it) could modify the alsa-tools ebuild so that it extracts the .o3 and .sb files from Playmidi's sources and installs them somewhere. It'd be better than having to emerge kdemultimedia anyway.
Hm. Even better, the ebuild could download the files from here: http://www.alsa-project.org/alsa/tools-source/seq/sbiload/
forgive my bit of ignorance with dealings in MIDI/soundfonts/synthesis, etc... how does this process differ from loading soundfonts with awesfx? Is it an alternative? Something additional?
Soundfonts are actually sound samples whereas the files loaded using sbiload I think are sort of instructions on how to modulate a base frequency.. I'm not sure where they're loaded but we ARE talking about two different things here: - Wavetable MIDI (by loading soundfonts using sfxload/asfxload) - FM MIDI (by loading .sb or .o3 files using sbiload) Have you ever played an old game on an old SB->SB Pro 2 card? The music playing is most likely FM based. Some old weirdos like me still want that FM sound now and then. I wish the recent polyphonic mobile phones would have used FM instead of that crappy wavetable they have now. Or even better - the SID chip from the Commodore 64!
thanks for the response... sorry for the delay... I'm busy moving =( I'd actually like to put this note in the alsa-guide rather than the ebuild itself. Could you suggest wwere might be the best place to add the appropriate information (and perhaps wording as you seem more experienced with MIDI than I am). There is a MIDI-HOWTO section in that guide that I wrote, so perhaps that can be updated to include this distinction somehow... Thanks, Jeremy
Created attachment 31853 [details] Modified/updated suggestion for the MIDI section in Gentoo's ALSA-docs Hey, don't worry about taking your time to reply! The internet has a time of it's own, and hey - I'm a happy camper with MIDI working on my AWE64 machine :) I'm submitting this to the 49792 bug chain as well. Suggestions and changes are written in red. The instructions are a bit vague but at least it's something.
Comment on attachment 31853 [details] Modified/updated suggestion for the MIDI section in Gentoo's ALSA-docs changing mime type so i can see it
Comment on attachment 31853 [details] Modified/updated suggestion for the MIDI section in Gentoo's ALSA-docs changing to abiword type... can you please post it as plain text... I don't use abiword =(
*** This bug has been marked as a duplicate of 48733 ***
