 |
 |
 |
|
|
|
|
Help
 No sound issue, related to ALSA & Timidity
|
|
| Author |
Message |
|
Daseinhorn
|
|
Post:
Jun 10th 2008 at 1:21 AM |
|
|
My issue is related to sound. I did follow the walkthrough here: http://www.tuxguitar.com.ar/tgwiki/doku.php?id=doc:no_sound , as well as the walkthrough here for ALSA: http://www.tuxguitar.com.ar/tgwiki/doku.php?id=doc:tuxguitar_alsa . I use Ubuntu 8.04 with the Studio desktop and with an Audigy 2. Therefore it has Alsa and Timidity already installed to the latest version.
For some odd reason, I cannot select any sequencer inside TuxGuitar. Therefore I followed the required commands on the ALSA walkthrough.
xavier@Xavier:~$ lsmod | grep snd
snd_rtctimer 5344 1
snd_emu10k1_synth 9344 0
snd_emux_synth 41088 1 snd_emu10k1_synth
snd_seq_virmidi 9984 1 snd_emux_synth
snd_seq_midi_emul 9088 1 snd_emux_synth
snd_hda_intel 440792 2
snd_seq_dummy 5764 0
snd_emu10k1 162656 7 snd_emu10k1_synth
snd_seq_oss 39424 0
snd_ac97_codec 123992 1 snd_emu10k1
snd_usb_audio 100640 1
ac97_bus 4224 1 snd_ac97_codec
snd_seq_midi 10688 0
snd_pcm_oss 48032 0
snd_usb_lib 21248 1 snd_usb_audio
snd_mixer_oss 20352 1 snd_pcm_oss
snd_rawmidi 30240 4 snd_seq_virmidi,snd_emu10k1,snd_seq_midi,snd_usb_lib
snd_pcm 93320 6 snd_hda_intel,snd_emu10k1,snd_ac97_codec,snd_usb_audio,snd_pcm_oss
snd_seq_midi_event 10240 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_page_alloc 13200 3 snd_hda_intel,snd_emu10k1,snd_pcm
snd_util_mem 6656 2 snd_emux_synth,snd_emu10k1
snd_hwdep 12680 4 snd_emux_synth,snd_hda_intel,snd_emu10k1,snd_usb_audio
snd_seq 64256 10 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 28424 4 snd_rtctimer,snd_emu10k1,snd_pcm,snd_seq
snd_seq_device 10644 8 snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd_emu10k1,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 71880 36 snd_rtctimer,snd_emux_synth,snd_seq_virmidi,snd_hda_intel,snd_seq_dummy,snd_emu10k1,snd_seq_oss,snd_ac97_codec,snd_usb_audio,snd_pcm_oss,snd_usb_lib,snd_mixer_oss,snd_rawmidi,snd_pcm,snd_hwdep,snd_seq,snd_timer,snd_seq_device
soundcore 11040 1 snd
usbcore 171952 10 pwc,rtl8187,snd_usb_audio,snd_usb_lib,usb_storage,usbhid,libusual,ehci_hcd,uhci_hcd
Then I try to load Timidity, I get a fail.
xavier@Xavier:~$ /etc/init.d/timidity start
open: Permission denied
* Starting TiMidity++ ALSA midi emulation... open: Permission denied
[ OK ]
xavier@Xavier:~$ sudo /etc/init.d/timidity start
[sudo] password for xavier:
* Starting TiMidity++ ALSA midi emulation... [fail]
Any possible clues on what might be wrong?
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 10th 2008 at 10:33 AM |
|
|
Hi,
> For some odd reason, I cannot select any sequencer inside TuxGuitar.
What you need is select the midi port.
what tuxguitar version do you have installed ?
> Then I try to load Timidity, I get a fail.
try run timidity with this command: "timidity -iA -Os"
and paste here the error log.
if it didn't throw any error, try (without closing the terminal where you run timidity) exec on other terminal: "aconnect -o"
Is there timidity on the list ?
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 10th 2008 at 12:31 PM |
|
|
Version: 1.0rc4
It does not go beyond this
xavier@Xavier:~$ timidity -iA -Os
Requested buffer size 32768, fragment size 8192
ALSA pcm 'default' set buffer size 33868, period size 3760 bytes
TiMidity starting in ALSA server mode
Opening sequencer port: 129:0 129:1 129:2 129:3
I only have ALSA installed as a sound driver; hence I do not think that there is a conflict.
With the other command, here is what I get.
xavier@Xavier:~$ aconnect -o
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 24: 'Audigy 2 ZS [SB0353]' [type=kernel]
0 'Audigy MPU-401 (UART)'
32 'Audigy MPU-401 #2'
client 25: 'Emu10k1 WaveTable' [type=kernel]
0 'Emu10k1 Port 0 '
1 'Emu10k1 Port 1 '
2 'Emu10k1 Port 2 '
3 'Emu10k1 Port 3 '
client 128: 'TiMidity' [type=user]
0 'TiMidity port 0 '
1 'TiMidity port 1 '
2 'TiMidity port 2 '
3 'TiMidity port 3 '
client 129: 'TiMidity' [type=user]
0 'TiMidity port 0 '
1 'TiMidity port 1 '
2 'TiMidity port 2 '
3 'TiMidity port 3 '
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 10th 2008 at 12:45 PM |
|
|
As i see timidity is running
you have 2 timidity instances now ( after timidity -iA -Os, port 129 was openned )
Go to tuxguitar: Tools -> Settings, on Sound option
see at "MIDI Port", don't you see timidity on the select list?
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 11th 2008 at 12:03 AM |
|
|
|
I can now select both instances of timidity, either through Real time or Tuxguitar sequencers. However, none of them provide sound. The volume is up, therefore it is not the issue.
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 11th 2008 at 1:24 AM |
|
|
mmm strange..
try test timidity itself with any midi file ( if you don't have one, you can export it from tuxguitar )
on a terminal:
timidity file.mid
If it don't work, maybe you should try with "fluidsynth"
sudo apt-get install fluidsynth fluid-soundfont-gm
then run fluidsynth as:
fluidsynth /usr/share/sounds/sf2/FluidR3_GM.sf2
And again.. try select the fluidsynth port on tuxguitar
> either through Real time or Tuxguitar sequencers..
forget about sequencers, they don't play sounds (it's a synthesizer who do that) they are just "timers" needed to check "when" the synthesizer should play the sounds.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 11th 2008 at 2:59 AM |
|
|
xavier@Xavier:~/Desktop$ timidity warpzone.mid
Playing warpzone.mid
MIDI file: warpzone.mid
Format: 1 Tracks: 6 Divisions: 960
Outside Tuxguitar it works. There is certainly a way to correct this. Do you want me to supply any other commands before I try to switch midi sequencers?
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 11th 2008 at 11:24 AM |
|
|
Ok, so timidity as midi player works.
now as daemon..
aplaymidi --port 128:0 test.mid
check "aconnect -o" first to know if "128:0" is a real port..
If it sounds, open tuxguitar and make complety sure you have the same port 128:0 selected.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 12th 2008 at 3:40 AM |
|
|
xavier@Xavier:~$ aconnect -o
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 24: 'Audigy 2 ZS [SB0353]' [type=kernel]
0 'Audigy MPU-401 (UART)'
32 'Audigy MPU-401 #2'
client 25: 'Emu10k1 WaveTable' [type=kernel]
0 'Emu10k1 Port 0 '
1 'Emu10k1 Port 1 '
2 'Emu10k1 Port 2 '
3 'Emu10k1 Port 3 '
client 128: 'TiMidity' [type=user]
0 'TiMidity port 0 '
1 'TiMidity port 1 '
2 'TiMidity port 2 '
3 'TiMidity port 3 '
I have a whole bunch of choices inside Tuxguitar for midi ports, but none of them produce sound. Very weird..
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 12th 2008 at 11:09 AM |
|
|
did you test use it with "aplaymidi" ?
aplaymidi --port 128:0 test.mid
It's important to know if that get sounds or not.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 12th 2008 at 11:57 AM |
|
|
xavier@Xavier:~$ aplaymidi --port 128:0 test.mid
Cannot open test.mid - No such file or directory
Is test supposed to be a file of my own (such as I did previously?)
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 12th 2008 at 12:24 PM |
|
|
Yes, test.mid was added by me..
try use an existent MIDI file.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 13th 2008 at 1:16 AM |
|
|
xavier@Xavier:~$ aplaymidi --port 128:0 /home/xavier/warpzone.mid
No sound came out at all. It works as a player but not as a deamon... What should I try now?
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 13th 2008 at 10:45 AM |
|
|
Ok, so there is a problem with timidity as daemon.
but i don't have idea what can be.
I can sugget you try with fluidsynth
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 13th 2008 at 11:51 AM |
|
|
Although I have already Fluidsynth installed
xavier@Xavier:~$ sudo apt-get install fluidsynth fluid-soundfont-gm
Reading package lists... Done
Building dependency tree
Reading state information... Done
fluidsynth is already the newest version.
fluid-soundfont-gm is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It doesn't seem to load properly
xavier@Xavier:~$ fluidsynth /usr/share/sounds/sf2/FluidR3_GM.sf2
cca_open_socket: could not connect to host 'localhost', service '14541'
cca_init: could not connect to server 'localhost' - disabling ladcca
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: ALSA driver: Using format s16, rw, interleaved
FluidSynth version 1.0.7
Copyright (C) 2000-2006 Peter Hanappe and others.
Distributed under the LGPL license.
SoundFont(R) is a registered trademark of E-mu Systems, Inc.
Type 'help' for information on commands and 'help help' for help topics.
When I go in Tuxguitar, now there is nothing I can select :P. An interesting bug, it seems... Do you want me to test anything so that you can include it into the next release?
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 13th 2008 at 12:05 PM |
|
|
TuxGuitar (throught tuxguitar-alsa ) should show you the same as you see on "aconnect -o", what are the output Midi Ports connected to alsa.
So now, you say: "now there is nothing I can select"
You mean MIDI Port -> Empty options ??
of just fluidsynth isn't there ?
When i launch fluidsynth, i see: "Synth input port (11374:0)" midi port on tuxguitar (and on aconnect -o) what is the midi port "129:0" on my PC.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 13th 2008 at 3:18 PM |
|
|
Empty options for Midi ports and sequencers.
I am at work right now, tell me what you want me to do and I will do it at home after.
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 13th 2008 at 3:22 PM |
|
|
Is tuxguitar throwing any error on the terminal ??
if not, did you maybe "diable" tuxguitar-alsa and/or tuxguitar-jsa plugins ??
See at Tools -> Plugins
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 13th 2008 at 5:58 PM |
|
|
Daseinhorn, since this topic has similarity with other discussed topic ( but in spanish language ) on this weeks,
I think you have maybe the same problem..
do you maybe have "pulseaudio" installed/enabled ??
The user on this other topic say he can't run timidity with pulseaudio daemon running.
So i was looking on external forums on the web, and it seems there are a lot of users with this problem (i think same can happen for fluidsynth )
After see all posts, i installed pulseaudio to reproduce the problem, but unfortunatly i couldn't reproduce it because timidity worked without problems on my PC.
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 14th 2008 at 1:17 AM |
|
|
All plugins are installed.
Ubuntu 8.04 comes with PulseAudio I believe. I have Ubuntu 8.04 + studio, therefore all audio components are installed. However, I do not know how to manage them.
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 14th 2008 at 1:25 PM |
|
|
Ok,
i tried to make better tests.
i use Xfce, but as i readed, pulseaudio under ubuntu is launched when gnome start..
so i installed gnome, and configure pulseaudio like a new ubuntu installation does, and i see some problems.
timidity dont' worked as default ( but if i run timidity after gnome loaded, it worked )
fluidsynth definitly don't give me any sound
I don't have idea why it happens.. but you should test if it's really your problem.
try kill pulseaudio just one time.
First found the pulseaudio process:
ps ax | grep pulse
Then, exec:
kill -9 number_of_process
Then try restart timidity:
sudo /etc/init.d/timidity restart
then a little test (make sure again the timidity port is 128:0):
aplaymidi --port 128:0 YourFile.mid
If it works, so it's definitly an "pulseaudio & alsa" problem
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 14th 2008 at 3:55 PM |
|
|
Haha, I have a report for you, it's getting even more interesting.
I have a metronome named GTick which uses midi as well. Just like Tuxguitar, it loads, but there is no sound.
I downloaded a version of Guitar Pro and ran it through wine to see if the results could tell anything. Timidity runs flawless in there, ironically. The fonts however do not work.
If you use instant messaging, add me: xvachon@gmail.com. I think it will be more efficient to try to fix the problem and potentially add content on the website.
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 14th 2008 at 4:23 PM |
|
|
The problem isn't timidity itself.
it seems to be alsa connections when pulseaudio is running.
But however, i can't fix this problem.
tuxguitar isn't a software synthesizer, it just connect to one.
This is how tuxguitar midi works:
TuxGuitar -> Midi api plugin -> Plugin issue..
On plugins, as default we distribute 2 under GNU/Linux:
*TuxGuitar-jsa: this is the java sound api plugin, it use java devices, but some GNU/Linux soundcard drivers don't work fine ( And throw the "Midi system is unavailable" error )
*TuxGuitar-alsa: it's just a native library what connects tuxgutiar with any alsa native port. (like aplaymidi --port [port] does)
On the alsa case (where you have the problem), the plugin is working fine.
how do i know it ?? easy, you don't get sound on tuxguitar but you don't get sound on the external aplaymidi application (you can try with other midi applications, and will have same problem) so the problem is definitly out of my hands.
About wine, i don't know how wine manage the sounds, it maybe use some lowlevel api and don't see the problem.
So in conclusion, i'm trying to help you get your midi sound working, but i definitly can't "fix" it because i'm not a pulseaudio developer (or maybe the problem is on ubuntu configuration files).
I can just try to give you possible temporal solutions..
As i told you on my previous post, i think you should try to disable pulseaudio, only to make sure (ofcourse disabling pulse audio is not a solution).
At last, it's hightly "not" recommended to post your mail on a public forum..
by the way, what protocol (msn, jabber, yahoo, etc) do you use for that mail ?
|
|
| Back to Top |
| |
|
Daseinhorn
|
|
Post:
Jun 14th 2008 at 4:30 PM |
|
|
Oh Ok. I thought you were a developer, my bad.
I gave my mail here because there is no way to send private messages to users (I use jabber and MSN with this account). On the other hand, if the issue is not related to TuxGuitar, I will try to find boards about ALSA and report the problem.
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Jun 14th 2008 at 4:48 PM |
|
|
I'm a "tuxguitar" developer, yes.
what i tried to mean is "i'm not an alsa, pulseaudio or ubuntu developer".
|
|
| Back to Top |
| |
|
joey
|
|
Post:
Jun 15th 2008 at 12:07 PM |
|
|
|
thank you all for youre help!! :)
|
|
| Back to Top |
| |
|
eini
|
|
Post:
Jul 14th 2008 at 8:48 PM |
|
|
Had the same problem with TuxGuitar 1.0 on Debian with an Audigy-Card.
There is a simple solution. Just remove the tuxguitart-alsa and tuxguitar-oss packages and install tuxguitar-jsa.
Strange, but it works.
|
|
| Back to Top |
| |
|
Johnny
|
|
Post:
Jul 15th 2008 at 10:39 AM |
|
|
You don't need to remove those packages.
You installed TuxGuitar-jsa, which enables Java Sound, and then you can choose it in Settings->Sound.
|
|
| Back to Top |
| |
|
cheap watch
|
| | |
