View previous topic :: View next topic |
Author |
Message |
andrea.giusto n00b
Joined: 02 Apr 2004 Posts: 52 Location: Italy
|
Posted: Fri Jun 18, 2004 11:57 am Post subject: Timidity wont work |
|
|
Hello, I emerged timidity, copied the config file, as suggested in the gentoo alsa guide, but when I pmidi -l I cant find any device nor hear any midi sound...How's that? Thanks |
|
Back to top |
|
|
mholtz Tux's lil' helper
Joined: 04 Feb 2004 Posts: 110 Location: Ohio, USA
|
Posted: Fri Jun 18, 2004 12:31 pm Post subject: |
|
|
Are you running the 2.4 or 2.6 kernel? I could be wrong but I thought I read that 2.6 has Timidity support (virtual sequencer) built in to the kernel with ALSA.
Remember that you have to start timidity as a service, typically after ALSA has been started.
Code: |
# /etc/init.d/timidity start
# rc-update add timidity default
|
Hope that helps. |
|
Back to top |
|
|
andrea.giusto n00b
Joined: 02 Apr 2004 Posts: 52 Location: Italy
|
Posted: Fri Jun 18, 2004 12:56 pm Post subject: |
|
|
I run a 2.6 kernel but the same happened while I was running 2.4...Unfortunately I've already started and rc-updated timidity... |
|
Back to top |
|
|
mholtz Tux's lil' helper
Joined: 04 Feb 2004 Posts: 110 Location: Ohio, USA
|
Posted: Sat Jun 19, 2004 4:09 am Post subject: |
|
|
I just did it on my 2.6.5 kernel.
Code: |
# emerge timidity++
(...)
# emerge timidity-eawpatches
(...)
# emerge pmidi
(...)
# cp /usr/share/timidity/config/timidity.cfg /usr/share/timidity
# nano -w /etc/conf.d/timidity
# /etc/init.d/timidity start
* Starting Timidity Virtual Midi Sequencer... [ ok ]
# pgrep timidity
25574
# rc-update add timidity default
* timidity added to runlevel default
* Caching service dependencies...
* rc-update complete.
# pmidi -l
128:0 Client-128 TiMidity port 0
128:1 Client-128 TiMidity port 1
|
|
|
Back to top |
|
|
seventhguardian Apprentice
Joined: 10 May 2004 Posts: 261 Location: Portugal
|
Posted: Sat Jun 19, 2004 7:00 pm Post subject: |
|
|
same issue here....
when using pgrep nothing is returned (strange??)
and also pmidi doesn't list any availiable ports..........
to make things even stranger, I get an error message while trying to stop timidity:
Code: | # ./timidity stop
* Stopping Timidity...
start-stop-daemon: warning: failed to kill 5758: No such process [ !! ]
|
yet when I make it start it gives me:
Code: | # ./timidity start
* WARNING: "timidity" has already been started.
|
----
I think it could be due to the configuration files: i didn't configure anything related to midi yet.... what should i config?
---- |
|
Back to top |
|
|
mholtz Tux's lil' helper
Joined: 04 Feb 2004 Posts: 110 Location: Ohio, USA
|
Posted: Sun Jun 20, 2004 5:03 am Post subject: |
|
|
What's going on is that Timidity starts, then exits due to an error. the init.d script is notoriously unreliable about reporting on process starts. That's why I like to check with pgrep.
Since Timidity started (but exited), the rc script still thinks that it is running. That's why it is confused when you run Code: | /etc/init.d/timidity stop |
If the proces isn't running, you can always Code: | /etc/init.d/timidity zap | to return the script to a normal state then retry from the beginning.
These are all symptoms, though. The real problem is that Timidity exits immediately after startup -- likely a configuration error. |
|
Back to top |
|
|
seventhguardian Apprentice
Joined: 10 May 2004 Posts: 261 Location: Portugal
|
Posted: Sun Jun 20, 2004 10:50 am Post subject: |
|
|
i found a strange thing when running the timidity command:
You would normaly run from /etc/init.d/ to start the deamon, right? But by mistake ran it without the dot forward slash, and I called the timidity command, what I guess is used to actualy play the midi (dont know for sure..)
It gave me this output:
Code: | # timidity
xgmap.cfg: No such file or directory
timidity: Can't read any configuration file.
Please check /usr/share/timidity/timidity.cfg
|
Can his be the problem? |
|
Back to top |
|
|
Admiral LSD Guru
Joined: 27 Jun 2003 Posts: 522 Location: Northam, W.A., Australia
|
Posted: Mon Jun 21, 2004 5:30 am Post subject: |
|
|
I got this problem too after upgrading to the latest version of timidity.
Yes, it's caused by problems with the config file. What happens is that both timidity and timidity-eawpatches both install timidity.cfg files into /etc but timidity's won't work with the timidty-eawpatches resulting in timidty not working right and all the init funkiness. The solution is to copy the eawpatches version of timidity.cfg from linuxconfig/ inside the eawpatches tarball (in /usr/portage/distfiles) to /etc and then all your troubles with timidty should be fixed. _________________ Wasurenaide...
...watashi ga iru koto o.
Itsudatte soba ni iru yo.
Registered Linux user #319839 |
|
Back to top |
|
|
seventhguardian Apprentice
Joined: 10 May 2004 Posts: 261 Location: Portugal
|
Posted: Mon Jun 21, 2004 11:16 am Post subject: |
|
|
hi!
that makes sense.. but didn't you mean copying the timidity version of timidity.cfg? i installed eawpatches after timidity, so my current /etc file must be the last to be installed, that is eawpatches....
I'll try both ways.... thanks anyway!! |
|
Back to top |
|
|
SirPreme n00b
Joined: 19 Aug 2004 Posts: 25
|
Posted: Sun Oct 10, 2004 5:11 pm Post subject: |
|
|
I have the same problem and this doesn't help for me.. |
|
Back to top |
|
|
TJNII l33t
Joined: 09 Nov 2003 Posts: 637 Location: for(;;);
|
Posted: Thu Oct 14, 2004 8:00 am Post subject: |
|
|
Can someone who has TiMidity++ and TiMididy-eawpatches working please post their timidity config file?
[EDIT]
Got it working. Here's mine.
Code: | ##############################################################################
#
# 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>
#
##############################################################################
# If you've moved things around since compiling, uncomment and edit this to
# point to the library directory:
#
#dir /usr/local/lib/timidity
#
dir /usr/share/timidity/eawpatches/
##############################################################################
# This sets up the default patches in the TiMidity support package
# "timidity-lib-0.1.tar.gz":
#bank 0
# 0 acpiano.pat
# 24 nylongt2.pat
##############################################################################
# If you have Dustin McCartney's "wowpats" patches, you can source the
# config file to set them up for TiMidity:
#
# (Note that later entries in config files always override earlier ones)
#
#source wowpats.cfg
#
##############################################################################
# If you have Dustin McCartney's GS drum sets, you can source the config
# file to set them up for TiMidity:
#
source gsdrums.cfg
#
##############################################################################
# If you have the GUS General MIDI patch set, uncomment the following lines
# and edit the "dir" statement to point to your GUS patch directory.
#
#dir /dos-C/ultrasnd/midi
source gravis.cfg
#
##############################################################################
# If you have the Midia patch set, you can source midia.cfg to set them up.
# Note that midia.cfg sources gravis.cfg in turn, since the filenames are
# almost identical.
#
#source midia.cfg
#
##############################################################################
# Use XG program map.
# "#extension" is keyword on TiMidity++, not comment.
#extension source xgmap2.cfg
source gssfx.cfg
#source xgmap2.cfg
##############################################################################
# End of configuration file |
Note the changes to the gsdrums line and the extension line.
The actual timidity program is invaluable for debugging. Unlike the init script it tells you why it can't work. _________________ Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world! |
|
Back to top |
|
|
jannis Guru
Joined: 05 Dec 2004 Posts: 340 Location: Germany / Bavaria / Aschaffenburg
|
Posted: Sun Jan 16, 2005 8:18 pm Post subject: |
|
|
I got it "working". I hear something but it sounds THAT ugly....
It sounds like the first few notes are super but then it just repeats the last sample over and over again.
Ideas? |
|
Back to top |
|
|
|