Hello Christa!
It's been a long time since I used them. I mostly used it for fixing
velocity (note). I just tried it with pbend and got no effect on fluidsynth
1.1.3.
Still to fix the cpress (channel aftertouch, if I'm not mistaken), you
should do something like:
router_begin cpress
Hi all!
If there is some original content material - as in not the SF standard pages
for download and summary - I could check them for accessibility and include
accessibility features.
Kindly yours
Julien
Music was my first love and it will be my last (John Miles)
Hello again Laurent!
As I know: fluidsynth itself doesn't have that feature. But one of the
frontends does. Was Qsynth? I think so. Qsynth can start more instances of the
engine and thus assign different instruments to different audio outputs.
Hope that helps!
Friendly regards
Hi Joshua!
I don't a know anyway to do this with fluidsynth alone. But if you take an
outside midi router, it would be possible. If you can use and are willing to
use a Graphical User Interface (GUI) there should be moe than enough
aplications to do yor bidding. If you use the console only,
Hello everyone!
I just stumbled across something ugly. Fluidsynth appends its PID to the
ALSA sequencer client name, which can be nasty, when trying to do a connect
by name.
Would it be possible to consider theaeolus approach? First aeolus is named
aeolus and then -01 is appended to the
Evening Joshua!
Just what I asked a mail ago. The problem is: Fluidsynth just has one
Client_name fluidsynth. So if another fluidsynth tries to get its
client-name setup, JACK is annoyed. Reason: There already is a client named
fluidsynth.
Workarounds: Use qsynth. Qsynth can start more
OK, so I missed it. Then I believe pat of my other post regarding
fluidsynth ALSA sequencer port naming is irrelevant.
Thanks Joshua!
Kindest regards
Julien
Music was my first love and it will be my last (John Miles)
FIND MY WEB-PROJECT AT:
OK. This complete post is not too interesting. I've seen that there is of
course midi.alsa_seq.id which you can set to any name, which solves the
problem connecting by name easily. But still my suggestion stays on: Why not
choosing a more consisent client-name like always appending a
Hi Steve!
I've never looked at the MIODI-Player of fluidsynth and I've never used it
intensely. But: I think, that fluidsynth's MIDIfile-player was mostly for
smaller jobs or for testing. Fluidsynth is best suited to playing live. For
playback, with soundfonts or GUS-patches, better use
Hi!
I'd like to plea for a feature, which I would have found helpful for the
last two years and it becomes more obvious to me, that this would be very good
to my work.
Could you route different note groups to different jack-output ports. So I
could have some kind of configuration looking
Hi!
So would you say, that I as a not vry experienced programmer could move the
code out of qsynth and put it into the readline frontend or somewhere else.
Unfortunitely I can't use qsynth. But this sounds interesting. Very much so!
Kindest regards
Julien
Music was my
Hi!
You look for what kind of preset? Do you need preset for the channels? Or
preset for effects? Or what?
To my knowledge there are no files for presets. At least not for fluidsynth.
For qsynth perhaps.
Kindest regards
Julien
Music was my first love and it will be my
Hi Josh!
This is super cool. Sorry tok me sometime to grab it. but it works fine! Of
course I didn't notice too much of the chorus and other effect issues, because
first thing, I turn them off. Not because they sound bad, but because I like
to add effects later in my recordings, so it all
Hi all!
Just recently this started. When ever I connect fluidsynth (1.0.6 or 1.0.7)
to my soundcard it says once something like:
WARNING: alsamidi sequencer buffer overflow!
When I switch on my synth, which has active sensing), this message repeats
over and over again. The sound works fine, but
14 matches
Mail list logo
