Hello SuSE folk, Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2 I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things. Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages. Hints?? Ideas??? Thanx, Bob S.
On June 9, 2004 22:23, Bob S. wrote: Are you sure you have an FM synthesizer? Most onboard sound chips don't have one, in which case Timidity is pretty much useless. Otherwise check your sound driver. Also run Timidity from the command line it may tell you why its crashing.
Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages.
Hints?? Ideas???
Thanx, Bob S.
Saskman
On Thursday 10 June 2004 06:23, Bob S. wrote:
Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2
I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things.
Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages.
Did you try to run it from a terminal window, like Konsole? Post any error messages you then get. Cheers, Leen
I run mount -t msdos /dev/sdaX /media/sdaX, mount -t vfat /dev/sdaX /media/sdaX or any similar, I get "/dev/sdaX is not a valid block device" 755 for /dev/sdaX & /media/sdaX Running cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: LITE-ON Model: LTR-48327S Rev: PQS3 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: USB Model: Flash Drive Rev: 1.12 Type: Direct-Access ANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: Prolific Model: USB Flash Disk Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 Running Dmesg Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table I/O error: dev 08:00, sector 0 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table Please HELP!
There is kde 3.2.3 on the suse ftp ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/ So, how I can upgrade my 9.0 usien YaST ? Jul.
Julo wrote:
There is kde 3.2.3 on the suse ftp ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/ So, how I can upgrade my 9.0 usien YaST ?
Jul.
To Julo: Went to the url in question and found several files, problem is which one is the download file needed to upgrade to kde 3.2.3?
I'm using 9.1 but it should be very similar for 9.0. - Go to YaST -> Change source of installation - Add a new source, using the URL you indicated but add subdirectory yast-source. For my setup, I get ftp://ftp.gwdg.de/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1/yast-source I guess your URL will be ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source (maybe take another mirror though). Make sure this source is enabled ;-) - Close this YaST module and start the 'Install and Remove Software' module. Just hunt down the packages you have that have an update available and install. That should be it. I did this for KDE 3.2.2 and it went like a breeze. About ready to do it for KDE 3.2.3. HTH, Eric On Thursday 10 June 2004 20:53, John Boyle wrote:
Julo wrote:
There is kde 3.2.3 on the suse ftp ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/ So, how I can upgrade my 9.0 usien YaST ?
Jul.
To Julo: Went to the url in question and found several files, problem is which one is the download file needed to upgrade to kde 3.2.3?
On Thu, 2004-06-10 at 00:23, Bob S. wrote:
Hello SuSE folk,
Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2
I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things.
Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages.
Hints?? Ideas???
Thanx, Bob S.
Hi Bob, On my 9.0 system, TiMidity seems to require to following command line options to run: "CheckHardware --sound /usr/bin/timidity -iat" (no quotes & verify your path) This could be worth a try. regards, - Carl
On Thursday 10 June 2004 10:05 am, Carl Hartung wrote:
On Thu, 2004-06-10 at 00:23, Bob S. wrote:
Hello SuSE folk,
Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2
I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things.
Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages.
Hints?? Ideas???
Thanx, Bob S.
Hi Bob,
On my 9.0 system, TiMidity seems to require to following command line options to run:
"CheckHardware --sound /usr/bin/timidity -iat" (no quotes & verify your path)
This could be worth a try.
regards,
- Carl
Thanks Carl, Saskman, & Leen for replying. I had tried to run it in
Konsole. All I got was some dumb message about timidity. ( Posted at
the bottom if really interested) But then after Leen's reply I ran what
he had suggested. Here is the result.
----------------------------------------------------
Bob@linux:~> sux
Password:
linux:/home/bob # cd /usr/bin
linux:/usr/bin # CheckHardware --sound /usr/bin/timidity -iat
ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device or resource busy
Can't open pcm device 'default'.
Couldn't open ALSA pcm device (`s')
linux:/usr/bin #
------------------------------------------------------------
Some progress and a reason?? I have a Soundblaster PCI with the Ensoniq
ES1370 chip if that will shed some light. I have no idea what the pcm
device is. Seems to be something in Alsa & /proc In the INFO CENTER
it shows the ensoniq card and a little ways down the list it shows :
Midi devices:
0: ES 1370
Looked in /usr/share/alsa/pcm and there is no ("s") I then looked in
alsa.config and it means nothing to me.
Then I went into Yast and looked at the Ensoniq card. There is a message
on the left that states:"Check Start Sequencer to load modules for
playing MIDI during boot. These modules can be loaded on demand"
The "Start Sequencer" is checked.
What's next?
and thanks again
Bob S.
----------------------------------------------------------------------
linux:/ # timidity
TiMidity++ version 2.12.0-pre1 -- MIDI to WAVE converter and player
Copyright (C) 1999-2002 Masanao Izumo
On Friday 11 June 2004 06:44, Bob S. wrote:
On Thursday 10 June 2004 10:05 am, Carl Hartung wrote:
Hello SuSE folk,
Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2
I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things. ... On my 9.0 system, TiMidity seems to require to following command line
On Thu, 2004-06-10 at 00:23, Bob S. wrote: options to run:
"CheckHardware --sound /usr/bin/timidity -iat" (no quotes & verify your path) ... - Carl
Thanks Carl, Saskman, & Leen for replying. I had tried to run it in Konsole. All I got was some dumb message about timidity. ( Posted at the bottom if really interested) But then after Leen's reply I ran what he had suggested. Here is the result. ---------------------------------------------------- Bob@linux:~> sux
I did not use sux. Just open a Konsole window, and enter the command below:
Password: linux:/home/bob # cd /usr/bin linux:/usr/bin # CheckHardware --sound /usr/bin/timidity -iat ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') linux:/usr/bin #
Thanks to Carl I discovered this: timidity -iat -Os Click on 'File', select a file, Click 'OK' Click on [ > ] -> file starts playing Optio -Os means: Output to ALSA Please do mind: Usually KDE uses aRts. aRts suspends 5 seconds or so after the last music file played. You have to wait for aRts to suspend before you can play a file with ALSA. Cheers, Leen
The Friday 2004-06-11 at 00:44 -0400, Bob S. wrote:
Bob@linux:~> sux Password:
I generally use "sux -", to get the full roots environment. But notice that the desktop (kde, gnome, whatever) is probably using sound as your normal user.
Then I went into Yast and looked at the Ensoniq card. There is a message on the left that states:"Check Start Sequencer to load modules for playing MIDI during boot. These modules can be loaded on demand"
The "Start Sequencer" is checked.
It means that the "sequencer" has MIDI in use by the time timidity wants it. So, you either tell timidity to use alsa, or disable that checkmark. -- Cheers, Carlos Robinson
On Friday 11 June 2004 06:11 am, Carlos E. R. wrote:
The Friday 2004-06-11 at 00:44 -0400, Bob S. wrote:
Bob@linux:~> sux Password:
Hello Carlos & Lee, Thanks for replying
I generally use "sux -", to get the full roots environment. But notice that the desktop (kde, gnome, whatever) is probably using sound as your normal user.
Carlos, Yes, that is true. But I get no response in either of these modes. sux just give me more output about the problem
Then I went into Yast and looked at the Ensoniq card. There is a message on the left that states:"Check Start Sequencer to load modules for playing MIDI during boot. These modules can be loaded on demand"
The "Start Sequencer" is checked.
It means that the "sequencer" has MIDI in use by the time timidity wants it. So, you either tell timidity to use alsa, or disable that checkmark.
OK, but not sure I understand what you are telling me. I disabled that option without any success. How do you tell timidity to use alsa ? Is it that iat-Os thing? If so how do you get Kong or Mozilla to play those files? Lee, you state:
Bob, You say you are running 8.2 SuSE right? I'll not be able to help explain why it's not working for you right now, sorry, but will mention, that until 9.1, I don't think I had ever seen a gui interface for timidity! Oh, I could use it from the command line, Konqueror would use it for any midi equipped site, but opening a Timidity window to play a midi never happened until 9.1 for me. KMid always opened ok and many times played the song, but I never get any sound from it now and that may be due to the sound setup not loading soundfonts. Don't know if that is fixed in 9.1 yet or not, but I digress.
Well, I mention a GUI because that is what I see for a split second while it is attempting to open. I really don't care about it if Konq or Mozilla would open and play a midi when it shows on a webpage. That is what I want. I would rarely open an application to just play midi files. Yes I am running 8.2 (not sure I want to make the leap yet :-) ) And, I am running an older version of timidity ( 2.12.0-172 ) It is the newest version in the 8.2 archives.
I am running timidity-2.13.0-42 presently, not sure what you have, but it's older on 8.2, unless you have compiled your own. My thoughts are that it's a bug in the older Timidity, but that's just a guess.
Hmmmm.....a bug??? Hope not. Don't really want to downlod an src and recompile. Bob S.
The Sunday 2004-06-13 at 01:19 -0400, Bob S. wrote:
OK, but not sure I understand what you are telling me. I disabled that option without any success. How do you tell timidity to use alsa ? Is it that iat-Os thing? If so how do you get Kong or Mozilla to play those files?
Er... :-? -ir Launch timidity as MIDI server. -iA Launch timidity as ALSA sequencer client. Leendert said: "timidity -iat -Os". I can't find "-ia", only "-iA". The "t" is an interface option: t Toggles trace mode. In trace mode, TiMidity attempts to display its current state in real time. For the Linux sound driver, this is accomplished through the use of short DMA buffer fragments, which can be tuned via the -B option. Then, "-O?" is for mode, but I can't see any "-Os". Only d,s,u,a, or w - and I have SuSE 8.2, same as you. I would try simply "-iA", or possibly "-iAt". Then, if your intention is to provide a MIDI server for other applications, because you card does not have MIDI (that's my case as well) then add "-ir" -- Cheers, Carlos E.R.
On Sunday 13 June 2004 22:03, Carlos E. R. wrote:
The Sunday 2004-06-13 at 01:19 -0400, Bob S. wrote:
OK, but not sure I understand what you are telling me. I disabled that option without any success. How do you tell timidity to use alsa ? Is it that iat-Os thing? If so how do you get Kong or Mozilla to play those files?
Er... :-?
-ir Launch timidity as MIDI server.
-iA Launch timidity as ALSA sequencer client.
Leendert said: "timidity -iat -Os". I can't find "-ia", only "-iA". The "t" is an interface option:
t Toggles trace mode. In trace mode, TiMidity attempts to display its current state in real time. For the Linux sound driver, this is accomplished through the use of short DMA buffer fragments, which can be tuned via the -B option.
leen@cc22149-a:~> timidity --version | cat TiMidity++ version 2.13.0-rc2 man timidity | manual_cutter ;P -ia X Athena Widget interface t, --[no-]trace -Os Output to ALSA man timidity is your friend Cheers, Leen
The Monday 2004-06-14 at 04:08 +0200, Leendert Meyer wrote:
Leendert said: "timidity -iat -Os". I can't find "-ia", only "-iA". The "t" is an interface option:
t Toggles trace mode. In trace mode, TiMidity attempts to display its current state in real time. For the Linux sound driver, this is accomplished through the use of short DMA buffer fragments, which can be tuned via the -B option.
leen@cc22149-a:~> timidity --version | cat TiMidity++ version 2.13.0-rc2
cer@nimrodel:~> timidity --version timidity: invalid option -- - Try timidity -h for help cer@nimrodel:~> timidity -h |grep -i version TiMidity++ version 2.12.0-pre1 (C) 1999-2002 Masanao Izumo So, you see, mine doesn't even accept "--version".
man timidity | manual_cutter ;P -ia X Athena Widget interface t, --[no-]trace -Os Output to ALSA
man timidity is your friend
My man page doesn't mention "-Os" - this is SuSE 8.2. In fact "-Os" produces an error. "-ia" is accepted, though: cer@nimrodel:~> timidity -ia Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 32768, period size 8192 bytes -- Cheers, Carlos Robinson
On Monday 14 June 2004 21:22, Carlos E. R. wrote:
leen@cc22149-a:~> timidity --version | cat TiMidity++ version 2.13.0-rc2 cer@nimrodel:~> timidity --version timidity: invalid option -- - cer@nimrodel:~> timidity -h |grep -i version TiMidity++ version 2.12.0-pre1 (C) 1999-2002 Masanao Izumo ... So, you see, mine doesn't even accept "--version". ... My man page doesn't mention "-Os" - this is SuSE 8.2. In fact "-Os" produces an error. "-ia" is accepted, though:
I use SuSE 9.1. So there's a difference in both timidity version as well as OS version. The different timidity version explains it. Perhaps there are newer versions floating around. Cheers, Leen
On Monday 14 June 2004 03:22 pm, Carlos E. R. wrote:
The Monday 2004-06-14 at 04:08 +0200, Leendert Meyer wrote:
Leendert said: "timidity -iat -Os". I can't find "-ia", only "-iA". The "t" is an interface option:
t Toggles trace mode. In trace mode, TiMidity attempts to display its current state in real time. For the Linux sound driver, this is accomplished through the use of short DMA buffer fragments, which can be tuned via the -B option.
leen@cc22149-a:~> timidity --version | cat TiMidity++ version 2.13.0-rc2
cer@nimrodel:~> timidity --version timidity: invalid option -- - Try timidity -h for help
cer@nimrodel:~> timidity -h |grep -i version TiMidity++ version 2.12.0-pre1 (C) 1999-2002 Masanao Izumo
So, you see, mine doesn't even accept "--version".
man timidity | manual_cutter ;P -ia X Athena Widget interface t, --[no-]trace -Os Output to ALSA
man timidity is your friend
My man page doesn't mention "-Os" - this is SuSE 8.2. In fact "-Os" produces an error. "-ia" is accepted, though:
cer@nimrodel:~> timidity -ia Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 32768, period size 8192 bytes
Carlos & Leen, AS you both know, I am running 8.2. Since I still cannot get timididity to play a midi file, I have watched your discussion with interest and tried some of your commands. Here is a copy from my console. Note the last few lines. Bob@linux:~> timidity -ia ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') Bob@linux:~> Bob@linux:~> timidity -iat ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') Bob@linux:~> Bob@linux:~> timidity -ia -Os ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') Bob@linux:~> Bob@linux:~> timidity -iat -Os ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') Bob@linux:~> timidity -iat -Os Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 32768, period size 8192 bytes X connection to :0.0 broken (explicit kill or server shutdown). I waited about a minute between the 4th & 5th command thinking arts may have something to do with the resource busy thing. The 5th command opened a GUI similar to a CD player? It was labeled TiMidity++ 2.12.0-pre1 My command line never returned like when the system is working on something. The GUI had several rows of horizontal boxes and to the right of each line was a line of keyboard or piano keys. Wouldn't do anything though. My man timidity does show an -O option called mode with 4 or 5 other modifiers. The option -iA should open use of alsa but I still get the device or resource busy thing. Oh, and by the way, the -iat -Os thing doesn't always work; only about 50% of the time. Very confusing. Don't seem as though I will ever get to hear a midi file. Bob S.
The Tuesday 2004-06-15 at 00:05 -0400, Bob S. wrote:
Carlos & Leen,
AS you both know, I am running 8.2. Since I still cannot get timididity to play a midi file, I have watched your discussion with interest and tried some of your commands. Here is a copy from my console. Note the last few lines.
Mmmm... are you using kde or gnome? Try from the other. Alternatively, before login in X, login at a text console, and start timidiy there (I use "timidity -iA -B2,8 -Os -q0/0 -k0"). Then start X. -- Cheers, Carlos Robinson
On Thursday 17 June 2004 07:22 am, Carlos E. R. wrote:
The Tuesday 2004-06-15 at 00:05 -0400, Bob S. wrote:
Carlos & Leen,
AS you both know, I am running 8.2. Since I still cannot get timididity to play a midi file, I have watched your discussion with interest and tried some of your commands. Here is a copy from my console. Note the last few lines.
Mmmm... are you using kde or gnome? Try from the other. Alternatively, before login in X, login at a text console, and start timidiy there (I use "timidity -iA -B2,8 -Os -q0/0 -k0"). Then start X.
Hi Carlos. Using KDE. Don't have Gnome installed since at least 7. Will try your alternative and post back with the results. Bob S.
On Friday 11 June 2004 12:44 am, Bob S. wrote:
On Thursday 10 June 2004 10:05 am, Carl Hartung wrote:
On Thu, 2004-06-10 at 00:23, Bob S. wrote:
Hello SuSE folk,
Been a SuSE user for several years. Now running 8.2 with KDE 3.2.2
I have never been able to make Timidity work on any of the distros. Not a big deal but one of those "needs to be solved" things.
Whenever I try to open it, it starts to load and I get a split second view of a Timidity window. Then it just dies. Never to be seen again until the next time I try. Would love to hear some of those stupid midi songs on some web pages.
Hints?? Ideas???
Thanx, Bob S.
Bob, You say you are running 8.2 SuSE right? I'll not be able to help explain why it's not working for you right now, sorry, but will mention, that until 9.1, I don't think I had ever seen a gui interface for timidity! Oh, I could use it from the command line, Konqueror would use it for any midi equipped site, but opening a Timidity window to play a midi never happened until 9.1 for me. KMid always opened ok and many times played the song, but I never get any sound from it now and that may be due to the sound setup not loading soundfonts. Don't know if that is fixed in 9.1 yet or not, but I digress. I am running timidity-2.13.0-42 presently, not sure what you have, but it's older on 8.2, unless you have compiled your own. My thoughts are that it's a bug in the older Timidity, but that's just a guess. Regards, Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
participants (10)
-
BandiPat -
Bob S. -
Carl Hartung -
Carlos E. R. -
Eric Seynaeve -
Jason Lim -
John Boyle -
Julo -
Leendert Meyer -
Saskman