24 Jul
2006
24 Jul
'06
5:43 p.m.
Hello together,
I'm using Debian-Testing with KDE for my sound stuff. I found swami as a good
editor for SF2-Soundfonts.
At the moment I have two problems:
- How can I increase the size of the used fonts?
I can't neither find any hint in the *cfg-Files nor while searching with
google.
The fonts are so small that I hardliy can use the program.
- Fluidsynth doesn't react on events from swami.
When I connect vkeybd to fluidsynth - all is ok.
I hope someone can give me a hint where to look for. Thanx.
Regards Helmut
(mlist(a)hk-vision.de)
24 Jul
24 Jul
6:58 p.m.
Le 24 Jul à 21:42, mlist ecrivait:
At the moment I have two problems:
- How can I increase the size of the used fonts?
Hi.
As far as I understand Swami and soundfonts, you can't. Swami lets
you edit the way samples are transformed in a soft synth, not what they
are. If your sample weights 3k, you can't improve (nor reduce) its
quality.
I can't neither find any hint in the *cfg-Files
nor while searching with
google.
The fonts are so small that I hardliy can use the program.
Maybe start searching for fluid soundfont on hammersound.net or
something ?
-rw-r--r-- 1 yves users 142M avr 5 21:49 FluidR3_GM.SF2
- Fluidsynth doesn't react on events from swami.
When I connect vkeybd to fluidsynth - all is ok.
Do you see the green light lit in swami ? If not, I suspect the
bug, or the Debian packager's choice, not to activate fluidsynth support
when building swami. The only solution I have found was to grab the source
and compile it myself, installing tons of normally, in Debian, useless
developpement librairies. It was a couple of months ago and I dont have a
Debian audio system anymore to check if this problem remains in the
package available in testing. This was one strong reason for me to
move to gentoo...
HTH,
Y.
25 Jul
25 Jul
1:52 p.m.
Hello Yves,
thank you for the quick response.
yes. Therefore the
fluidsynth-support should be integrated.
May be there is a wrong configuration in the options field.
Here my configruation:
Audio driver:
- type = auto, alsa, jack, oss (no difference)
- device = empty field (standard)
MIDI-driver:
- type = alsa (no entry in qjackctl)
- type = alsa_seq (a new MIDI-input-device entry [fluidsynth] in qjackctl)
- device = empty field (standard)
Could there be a problem with udev?
The main problem seems to be to get audio-out from the fluidsynth to alsa_pcm.
This is done automatically when I start the qsynth-frontend for fluidsynth.
There I get Audio-Ports to connect via qjackctl.
Regards Helmut
(mlist(a)hk-vision.de)
> - How can I increase the size of the used fonts?
This question is formulated in a way to be misunderstood. I'll try to clearify
it:
I'm meaning the character fonts for displaying the GUI of swami, not the
soundfonts. I can't find Information, how to change this values (e.g. 4pt to
10pt).
Maybe start searching for fluid soundfont on
hammersound.net or
something ?
-rw-r--r-- 1 yves users 142M avr 5 21:49 FluidR3_GM.SF2
Thany for this hint.
I've downloaded this and will test it the end of the
week.
- Fluidsynth
doesn't react on events from swami.
When I connect vkeybd to fluidsynth - all is ok.
Do you see the green light lit in swami ?
3:02 p.m.
Le 25 Jul à 17:52, mlist ecrivait:
OK. Normally, you can click on this little green light to switch
fluidsynth on and off. This means swami is compiled with fluidsynth support.
This question is formulated in a way to be
misunderstood. I'll try to clearify
it:
I'm meaning the character fonts for displaying the GUI of swami, not the
soundfonts. I can't find Information, how to change this values (e.g. 4pt to
10pt).
Sorry :). It's a FAQ about Debian / GTK 1, and as Ismael said it
should be corrected if you install the three transcoded fonts packages
(base, 75 dpi and 100 dpi). If it doesn't work, it's a bit a hassle but
you can put something like that :
style "user-font"
{
fontset="-adobe-helvetica-medium-r-normal-*-12-*-*-*-p-*-iso8859-1"
}
widget_class "*" style "user-font"
in a ~/.gtkrc, or better in /etc/gtk/gtk.iso-8859-1 (backup this
file before changing anything in it). It's explained for example there :
http://forums.debian.net/viewtopic.php?t=2186&sid=006b9fe606b30055e2b85…
or in Google with keywords « font size gtk 1 ».
But again, normally, the transcoded fonts must resolve this issue.
Do you
see the green light lit in swami ?
yes. Therefore the fluidsynth-support should be
integrated. May be there is a wrong configuration in the options
field.
Here my configruation:
Audio driver:
- type = auto, alsa, jack, oss (no difference)
I have jack.
- device = empty field (standard)
Yes. It's completely weird that a new fluidsynth doesn't apper in
qjackctl audio panel if you load a soundfont, see it appear in swami, and
then click on a sound in the soundfont panel. You need to click on a sound
again to reactivate the audio output each time you restart the drivers,
click on the green light or touch something in the config.
MIDI-driver:
- type = alsa (no entry in qjackctl)
- type = alsa_seq (a new MIDI-input-device entry [fluidsynth] in
qjackctl)
Well if you connect a midi out to it, it should work but of course
won't produce any sound as long as a fluidsynth doesn't appear in
qjackctl's audio panel.
Maybe also remove the ~/.swami directory to get rid of previous
tries...
Could there be a problem with udev?
The main problem seems to be to get audio-out from the fluidsynth to alsa_pcm.
This is done automatically when I start the qsynth-frontend for fluidsynth.
There I get Audio-Ports to connect via qjackctl.
For me, as long as fluidynth works with its qsynth frontend, the
only problem is in swami, not in the system, especially not in udev. Swami
and qsynth are interfaces to the same fluidsynth...
Good luck,
Y.
8:50 p.m.
Hello Yves,
screen fonts: ==> Solved
Sorry :). It's a FAQ about Debian / GTK 1,
and as Ismael said it
should be corrected if you install the three transcoded fonts packages
(base, 75 dpi and 100 dpi).
I've installed the packages
- xfonts-100dpi
- xfonts-100dpi-transcoded
- xfonts-75dpi
- xfonts-75dpi-transcoded
- xfonts-base
- xfonts-encodings
- xfonts-konsole
- xfonts-scalable
In Debian-testing there is no package xfonts-base-transcoded. Only the normal
xfonts-base-package exists.
If it doesn't work, it's a bit a hassle but
you can put something like that :
style "user-font"
{
fontset="-adobe-helvetica-medium-r-normal-*-12-*-*-*-p-*-iso8859-1"
}
widget_class "*" style "user-font"
in a ~/.gtkrc,
Does not exist for my normal user.
A first test with this entry in ~/.gtkrc doesn't change anything. When I
increase the font size to 20pt a remarkable change is to see. For my desktop
14pt is a valid size.
or better in /etc/gtk/gtk.iso-8859-1
On
my machine changed entries in /etc/gtk/gtkrc.iso-8859-15 show the same
result as ~./gtkrc.
sound: ==> work round
When I use the audio driver type auto or alsa without starting jackd I get
sound.
As long as I start jackd before swami nothing works.
Jackd stopps with errors, when I try to start it after swami. This is because
the audio device is captured by swami.
Could this result of a special setting in the swami-sources while compiling
for Debian?
Regards Helmut
(mlist(a)hk-vision.de)
11:15 a.m.
mlist escribe:
- How can I increase the size of the used fonts?
I can't neither find any hint in the *cfg-Files nor while searching with
google.
The fonts are so small that I hardliy can use the program.
I am afraid you mean fonts, not soundfonts, so go apt-get install
xfonts.*transcoded and restart your X server.
Cordially, Ismael
--
When I grow up I will go there.
1:52 p.m.
Hello Ismael,
You're totally right!
- How can I
increase the size of the used fonts?
I can't neither find any hint in the *cfg-Files nor while searching with
google.
The fonts are so small that I hardliy can use the program.
I am afraid you mean fonts, not soundfonts, so go apt-get install
xfonts.*transcoded and restart your X server.
This doesn't make a difference.
Regards Helmut
(mlist(a)hk-vision.de)
6747
days inactive
6748
days old
linux-audio-user@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Ismael Valladolid Torres -
mlist -
yves_p＠nnx.com