would likely move the file releases to
SourceForge and possibly also the mailing list too, just to bring it
all to one place.
Any thoughts or opinions on this?
Hello Josh
It would be logical to migrate to Sourceforge.net since this is *the
home* of literally hundreds of thousands of FOSS
involved in commits, so as long as all of those users have SourceForge
accounts, I don't think it will be too difficult to rename the
commits. Though I have not previous experience with this.
Regards,
Pedro
So.. Work in progress. Thanks for the input!
Josh
also the mailing list too, just to bring it
all to one place.
Any thoughts or opinions on this?
Cheers!
Josh Green
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hello Pedro,
Committing to trunk sounds fine to me. Thanks for adding this.
Cheers!
Josh
Quoting Pedro Lopez-Cabanillas :
Hi,
I'm testing a CMake-based build system for FluidSynth. See ticket#38:
http://fluidsynth.resonance.org/trac/ticket/38
This means adding several files to the s
hOnIphone
Best regards,
Elimar Green (AKA Josh)
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
n the priorities list. It would
be interesting to know what the age distribution is of FluidSynth
users. Perhaps we could use some more in the old farts category :)
KEVIN FISHBURNE
Cheers.
Elimar Green (AKA Josh)
___
fluid-dev ma
the debug and release builds.
Regards,
Josh
Quoting Graham Wykes :
Hi
Building 1.1.1 on Windows with Visual Studio 2008 using the project
files in Winbuild.
Once I sorted the glib and dsound issues, the Debug version builds
without issues. However, the Release versions gives me linking erro
for your bug reports and providing patches. I'll make sure
they are part of the next release for sure.
Best regards,
Josh Green
Quoting Laurent Blume :
Hi all,
Just a simple question: I've opened a couple of defect reports about
one month ago, 73 & 74. They're very basi
hich would help keep
track of it.
Best regards,
Josh
Quoting "0o.sound.o0" <0o.sound...@gmail.com>:
Hello,
there is a bug somewhere in the code (currently I am trying to find
the proper portion of code) which is causing that when a soundfont
consists of various samples named i
windows. It seems the WITHOUT_SERVER doesn't exclude the
related code though, so its still trying to build it. You might just
have to include the windows Winsock lib, but I'm not sure exactly what
that entails. It seemed to work OK for me though. Are you using the
included VS p
hange this.
After all its a volunteer effort and should be fun to work on! :)
Hi Josh, glad you're back and feeling better. Ironically my ten year
"vacation" from computer obsession involved a lot of drinking and
substance abuse, so now sitting in front of the computer half the
clarify that in my own mind, it would be much appreciated :)
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
o for another reason or there is a
bug. If you could attach the full output of FluidSynth that would
probably help greatly.
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
tors for all loaded SoundFont files. You could then
define a new velocity to attenuation modulator which would replace the
default. How does that sound?
Created a ticket for it here:
http://fluidsynth.resonance.org/trac/ticket/71
Josh
___
fluid-dev mai
rsion 1.1.1
Thanks,
Sebastian
I'm curious what you mean by "disables sustain". Do you mean the
sustain portion of the envelope doesn't work? Sounds like there might
be a bug there, just want to get a better idea of the detai
Hello,
It probably makes sense to add a FluidSynth setting to disable the
EMU10K1 compatibility mode, like synth.volenv = "compliant" or "emu",
with "emu" as the default. I've added a ticket for this:
http://fluidsynth.resonance.org/trac/ticket/70
Josh
nswering some of the past fluid-dev emails in my queue and
then I think the next step would be to start discussing how to fix the
event re-ordering issues. I welcome any thoughts on this.
Cheers.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.or
em. Maybe someone else will beat me to it,
as far as creating a new one.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
e anything obvious. Its a bit difficult to fix a problem
that can't be reproduced! Perhaps some of the recent thread safety
changes fixed whatever issue was there.
Regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.non
Synth could be improved a lot in regards to having
better defaults for different drivers and an "auto" option for
audio.driver.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
something like that? I'd be fine with what you suggested also though.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
urning to some of
these issues come next week. If someone wants to investigate a little
more what the problem is or some of the symptoms, that might help.
Have a happy new year!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.no
e.org/trac/wiki/ChangeLog1_1_1
Cheers!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
issues. There are synthesis related
issues though, but that is already obvious, from previous versions.
// David
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ounds like you got the full range out of the reverb
and chorus now! It seems like the Chorus depth parameter works in an
inverse fashion though. Not sure why or if it is a FluidSynth issue
or not. I didn't give the problem much time, so it might be something
ks.
So its a go then! :)
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
-
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Anxious to release it! :) Let me know if the
fluid_synth_system_reset() issue seems like a show stopper.
Cheers!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman
to reverb/chorus
value ranges, that is a bug and should be fixed.
bbl
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
27;t
any other errors/warnings.
More info about the problem might be helpful.
Regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
r: 0 - 99
level: 0.0 - 1.0
speed: 0.29 - 5.0
depth_ms: 0.0-21.0 is safe for sample rate values up to 96KHz
Looks like QSynth goes up to 100 on the "nr" parameter and 10.0 on the
level parameter. The other ones seem OK though.
Cheers!
Josh
e
state of doing the chorus processing outside of the synthesis thread.
Long term, it should just be replaced.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
nctions or something.
Or maybe I didn't understand what exactly you are experiencing. Do
you have any reproducible steps I could use to observe the problems
you are seeing?
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@
would have, is that
if a future program change was received it would use the old bank
number.
Josh
Quoting Rui Nuno Capela :
On 12/14/2009 08:26 AM, Rui Nuno Capela wrote:
On Sun, 13 Dec 2009 20:00:35 -0800, j...@resonance.org wrote:
Hello Rui,
I just committed what I hope are fixes to the
() setting should also now be retained until
a program change occurs.
Please test and let us know how it goes!
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hello David,
I've just been fixing the last 2 remaining issues today in regards to
QSynth. I'll get that done, checked in and provided it all works
well, call it 1.1.1. Can you wait a few more days? ;)
Josh
Quoting David Henningsson :
I've updated the Debian packaging
hange MIDI event, a call to fluid_synth_program_change(), etc, then
it will no longer be unset and might become assigned (if there is a
matching preset).
Cheers!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/ma
ynth svn trunk r275)
Yes, lets get these resolved before 1.1.1 release.
cheers
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Thanks for your patience on this. It hasn't been an easy task making
FluidSynth thread safe and trying to remain com
ck to just processing the effect
changes in the calling thread, but I'm not sure what multi-thread
consequences this could have, but it would probably just be as it was
before.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.non
new preset, assuming the bank/program matches one.
Does that sound OK?
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
uidsynth svn trunk r275)
Yes, lets get these resolved before 1.1.1 release.
cheers
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hey Rui,
No problem about the delayed responses. Do let us know if you see any
other issues or have any other feature requests for a future release.
Cheers!
Josh
Quoting Rui Nuno Capela :
On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
Hello Rui,
I committed some changes
Hello Nils,
Yes this is definitely planned. I'd like to see it as part of the
next release following 1.1.1. Here is the related ticket:
http://fluidsynth.resonance.org/trac/ticket/6
Best regards,
Josh
Quoting Nils Hammerfest :
Hi there,
is it planned that Fluidsynth
1) lear
most welcome,
success or failures. Thanks!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
We build with GUB, and this is how we do it:
http://github.com/janneke/gub/blob/master/gub/specs/fluidsynth.py
Attached is the dsound.h we use.
Nils
Ok, I'll give the build a try with that file. Are there any other
dependencies that you have installed or
the
SDK installed and can test with it and then try your dsound.h.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
older versions of FluidSynth by checking the version constants.
With the other changes I just committed and provided no one complains,
version 1.1.1 should be released shortly. Speak up if there is
something I overlooked, that you think should be in 1.1.1.
Cheers!
Josh
diff -ru qsynth-0.3.4
ntly only program changes and SYSEX tuning events don't comply,
which might be solve-able with the current API.
// David
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
.1 real soon now :) I'll just revert
the program change stuff and we'll just have to live with some small
holes in our real-time safety, but then only in certain cases. Big
deal.
// David
Josh
___
fluid-dev mailing list
flui
f accessing the SoundFont
list, when searching for a preset? A secondary shadow SoundFont list
owned by the synth thread, which is synchronized via the queue, might
work. Seems slightly messy though and I know how much you hate those
shadow variables ;)
Maybe its not worth trying to
Can't it have support for both?
Josh
Quoting Ebrahim Mayat :
Fellow Readers
I will be preparing a fink package for the new version of fluidsynth in
a short while. Since I have the option of preparing this package with
either coreaudio or jack support, I would like some feedback as to
Thanks Rui for your report :)
Josh
Quoting Rui Nuno Capela :
On 11/21/2009 07:13 PM, David Henningsson wrote:
Hello,
anybody using fluidsynth-dssi on this list?
The reason I'm asking is that we (as in the FluidSynth developers)
released a new version which was incompatible with QSynth
ssues though.
- Finalize API for getting channel info (sfont ID, bank, program and name)
- Add function to unset the preset on a channel
- Add API for setting threading mode
I'm going to defer the channel mute option to a future version, since
I just want to get a nice usabl
are now, it just
assumes it is multi-threaded, which means slightly less efficiency.
// David
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
it it, or was it somehow reverted? Anyway, its recommitted now; I
hope it stays that way.
// David
Not sure how that happened. Lets hope it stays fixed :) Thanks!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
and I was thinking of making that one
of the main items on this next development cycle, in addition to
improving performance as a result of the thread safety changes.
I think that change is a good bandaid for 1.1.1.
Josh
___
fluid-dev mailing list
f the fluid_synth_handle_midi_event this could
be used for that purpose.
At the moment, I can't think of any cases where this would be an
issue. But I haven't fully thought it through yet.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.
Quoting Ebrahim Mayat :
Hello Josh
Well, I do not own a Firewire device yet but since the use of these
devices is now coming into the mainstream on both Linux and OS X, I
thought this is one point you might consider as a possible feature
addition in the near future.
I tried running fluidsynth
sure why that would happen though, but perhaps
its using the wrong audio device? The driver could be improved to
display what the particular failure is which would help diagnose the
problem.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
htt
Quoting Graham Goode :
Josh,
Just a quick work of thanks for all the work that you (and all the
other guys) have done and are doing on fluidysynth. While the 1.1.0
release might have revealed some issues resulting from the thread
safety work, it is also a major step forward. Having release
at maybe (still) part of user's performance
and not of engine's structural configuration, which i'm trying to address.
just my .02
cheers
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Makes more sense to me now. Will add it.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
n whip this thing into shape though, its just a
matter of identifying any additional problem areas. I think we are
getting very close. Its been a rather humbling experience indeed.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ssigned program, and separating both states would be more useful.
Regards,
Pedro
Good point. Couldn't mute be accomplished by simply setting the
volume MIDI controller to 0 though?
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
htt
tty good
state. Perhaps not the best architecture, but I think its fairly
efficient, thread safe and much better as far as organization.
// David
Cheers!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
program numbers.
Why can't we reset it to 0/-1/something and use that as a null value?
// David
Do you mean set the channel's program number to -1 so that it remains
unset, even if a fluid_synth_program_reset() occurs?
Josh
___
reset() gets called, then
it will get re-assigned with whatever matching preset that corresponds
with.
byee
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Cheers!
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
a private function called
fluid_synth_set_preset, which could be used to set the preset to NULL,
which would have the effect of setting it to unassigned, but that
isn't much help in your case. How do you see this being useful?
byee
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
,
optimization, voice stealing improvements, etc. But limit the amount
of new functionality or code overhaul.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
on is
minimal and the lock would not be held for long. It could be a
problem though, if the lower priority thread doesn't get elevated when
there is contention.
Josh
#define FLUID_PRESET_INFO_NAME_LENGTH 32
/**
* Preset information structure.
* @since 1.1.1
*/
struct _fluid_p
ompanion of the opposite gender rammed an ax into my synth
keyboard. I am happy to say that I can still use this synth for MIDI
sequencing. :-))
Crazy! Seems that synth has some added character then.
Thanks for the testing!
Josh
___
fluid-dev mailing
in the soon to be released 1.1.1.
try it for yourselves: http://www.nilsgey.de/denemo-beta-0.8.11.exe
Fluid Team: Feedback for the whole software is happily accepted.
I'll give this a try, next time I boot up my VirtualBox environment
and remember to enable the virtual sound ca
Quoting David Henningsson :
I've just committed a small patch which updates the synthesis thread
variable at every call to fluid_synth_one_block, which should fix
Ebrahim's thread-jumping problem. Assuming Ebrahim confirms that it is
fixed, perhaps it is time to release a bugfixed ver
noticed that TiMidity++ will switch
interpolation algorithms to less CPU intensive ones when CPU usage
gets high. Something like that might also be nice.
The voice stealing algorithm also needs improvement.
This sounds like it could be a good focus of the next major versi
le this with the current
FluidSynth API, I'm all ears!
Cheers,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
bers. It doesn't solve
retrieving the Preset name though.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
f need
be.
cheers
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Cheers
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
How about adding a size field to, so that there can be
potential future extensions to fluid_preset_info_t. Example:
fluid_preset_info_t info;
fluid_synth_get_channel_preset_info(synth, chan, &info, sizeof (info));
Cheers
Josh
___
fluid-de
nothing new. Older versions of FluidSynth
could potentially crash QSynth if a program change occurred at the
right moment.
Any ideas or preferences?
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
there weren't really any guarantees that the API was synchronous. I
have every intention of making FluidSynth 1.1.1 as compatible as
possible and still have improved multi-thread safety too. So I'll
look into fixing these incompatibilities.
Ciao!
Josh
(man page fix, thanks Lintian!). I've also rewritten the rules file to
use CDBS and Quilt.
Josh, I noticed that r264 did not apply cleanly, it seems like the
changes to fluid_alsa.c were already applied in 1.1.0, but not in SVN
at the time of release, is that correct?
That does seem to
major itches.
a 1E+6 thanks
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org
Great to hear! Version 1.1.1 coming shortly. May wait another day to
make sure the dust has settled. If anyone finds any major issues,
nows the time to speak up!
Best regards,
Josh
e, I
think we should revert the const char * stuff for callbacks (which I
have done in my local copy as well) and release a 1.1.1 ASAP, once we
are sure that all QSynth related incompatibilities are resolved.
I put a note on the FluidSynth home page for now about the issues
round when trying to set them, etc. Are you polling the values that
are being assigned? I'll probably have to delve into the QSynth code
a bit to see what is going on.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.non
eporting your experience with the build. It seems there
are still some things that need to be fixed for a seamless Visual
Studio build.
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
fluidsynth release.
:-(
first of all build fails due to (const char *) api change.
Right, I'll let Josh answer to this, I thought he only changed the input
API, not the callbacks. But that is easily fixed in QSynth, I can supply
a patch against qsynth if you like.
no need for that
Quoting Joshua Higgins :
synth.polyphony = 32 did the trick!
I'm surprised at the performance of fluidsynth on this machine, and the
voice stealing is hardly noticable.
Thanks very much.
--
joshua higgins
--
Glad to hear it!
Josh
eloper API documentation for
more details:
http://fluidsynth.resonance.org/docs/api/index.html#NewIn1_1_0
Contributors
Josh Green
David Henningsson
Pedro Lopez-Cabanillas
Ebrahim Mayat
And many others!
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
new ones. This logic currently needs some improvement in FluidSynth,
since sometimes voices are turned off which aren't ideal.
--
joshua higgins
--
Hope that helps!
Josh Green
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
e they are in the API reference.
Josh
Quoting Pedro Lopez-Cabanillas :
On Wednesday, October 28, 2009, j...@resonance.org wrote:
During the process of going over a lot of the API, I realized that
there were still some undocumented functions. I had assumed that
Doxygen would report missing
Quoting Pedro Lopez-Cabanillas :
On Wednesday, October 28, 2009, j...@resonance.org wrote:
> * I had a look at the dev docs and corrected some minor things, looks
> much better now that Josh has got rid of all the internal stuff, good
> work. "Data structure index" looks fun
Consider it done. Thanks for pointing this out.
Josh
Quoting "Louis B." :
Yep, chaining the example I think would be a good idea as this I think
that is a better default (as I followed the example rather blindly
when writing my code -- but it was _very_ easy to integrate with Pia
8
Phone: + 353 1 4024788
Email: bryan.dug...@dit.ie
Web: http://www.comp.dit.ie/bduggan
Web: http://tunepal.org
Web: http://seriousgames.ie
Best of luck to you.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
NSIS.
Regards,
Pedro
Regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Quoting David Henningsson :
* I had a look at the dev docs and corrected some minor things, looks
much better now that Josh has got rid of all the internal stuff, good
work. "Data structure index" looks funny though with only F and _ as
letters. :-)
Lets blame Doxygen for that. F
bank/program change
messages sent) which may cause new instruments to get used from the
loaded SoundFont. Perhaps the example should just be changed to pass
TRUE as the 3rd parameter.
Thanks
Louis
Regards,
Josh
___
fluid-dev mailing l
sing docs. I
think at this point though all public API stuff is documented.
Best regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
is utility (Dependency Walker) may be handy to verify or diagnose
dependency
problems: http://www.dependencywalker.com/
Regards,
Pedro
Regards,
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hello Graham,
Thanks for the tip on the installer application. Looks like it would
do the trick. I have not yet built FluidSynth in Windows with
Jackdmp, but I imagine its just a matter of providing the libraries
and headers. I'll be building it with MinGW.
Josh
Quoting Graham
fe to the project.
It seems like along with this next release, it should be pretty simple
to package up a Windows binary .zip file. This would include all the
required libraries. Anyone know how to make a windows installer .exe?
Cheers!
gards,
Josh
Quoting ?? ? :
Hello.
I want to compile FluidSynth with last changes [227] on Windows platform
with Visual Studio 2008.
I don't need multicore. I need to test SysEx messages (my be I need only
some files to update from fluidsynth 1.0.9).
First problem is GLIB. I downlo
ck MIDI or audio driver
will be remembered and when another driver is created it will be
paired together if its using the same Jack server and FluidSynth data
instance. This should handle the case where multiple FluidSynth
instances are created or multiple Jack audio or MIDI drivers are
1 - 100 of 633 matches
Mail list logo
