On Sat, 2009-04-25 at 23:04 +0200, David Henningsson wrote:
> Josh Green skrev:
> > On Mon, 2009-04-20 at 22:08 +0200, David Henningsson wrote:
> >>> I like the use of '-' to indicate stdout. That is common to many
> >>> applications and woul
On Sat, 2009-04-25 at 21:30 +0200, David Henningsson wrote:
> About the buffer, first I think it should be an additional component
> between the "producer" and the synth. We don't want to introduce the
> overhead of thread safety when we don't need it, e g when using fast
> midi-file rendering or i
On Sat, 2009-04-25 at 10:18 +0200, David Henningsson wrote:
> > On Mon, 2009-04-20 at 20:59 +0200, David Henningsson wrote:
> >> But I've recently come to think of a disadvantage as well. If we're
> >> low-latency, it's important that fluid_synth_one_block finishes as soon as
> >> possible. If we
On Wed, 2009-04-22 at 21:30 +0200, David Henningsson wrote:
> Josh Green skrev:
> > Any suggestion on what licenses are most
> > appropriate for documentation?
>
> That's seems to be a difficult question. I tried to do some research and
> currently it seems like Crea
ro
>
This all sounds great! I got an email back from Peter Hanappe
confirming that we can change the license to whatever seems appropriate.
I'm not certain what would be the best though. Any suggestions?
Best regards,
Josh Green
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
On Mon, 2009-04-20 at 22:08 +0200, David Henningsson wrote:
> Josh Green skrev:
> > I agree that render fits the function of what FluidSynth is doing
> > (rendering SoundFont instruments and MIDI files to audio). I'd just as
> > well do away with the file writer driver
On Mon, 2009-04-20 at 20:59 +0200, David Henningsson wrote:
> The callback I'm talking about is mainly the same thing as the as the
> sample timer, i e the possibility to receive notification before/after
> fluid_synth_one_block, and from the "audio thread" (or more correctly -
> whatever thread wh
On Mon, 2009-04-20 at 19:13 +0200, Pedro Lopez-Cabanillas wrote:
> I would create a third bug report. Maybe a request for enhancement, because
> it
> seems that the player would need a new function to handle position set/reset.
> I guess that the notes can be muted by the client program using
>
On Fri, 2009-04-10 at 15:09 +0200, David Henningsson wrote:
> What first was a quick fix that took an hour or two to write, expanded
> to fix ticket #15, and should also be expanded to fix the sequencer. And
> now I'm about to suggest that timing should be a separate
> component/subsystem.
>
> Fir
On Sat, 2009-04-04 at 16:59 -0400, Ebrahim Mayat wrote:
> Hello
>
> To 64-bit Debian users, I am forwarding this message that I received
> off-list. It would be appreciated if anybody could assist/test on
> 64-bit Linux.
>
> The latest svn (r168) has a persistent make error, when
>
ject (never created one before, so we'll see how it
> goes). Right now I'm going through a divorce, so it might be a bit
> before I get around to it, though.
>
> -~Chris
>
> Josh Green wrote:
> > On Mon, 2009-03-16 at 09:48 -0400, Ebrahim Mayat wrote:
> >
On Mon, 2009-03-16 at 09:48 -0400, Ebrahim Mayat wrote:
> Josh, Pedro and Bernat
>
> As a service to Linux users, I propose that the 'GeneralUser GS
> FluidSynth v1.43.rgd" file written by S Christian Collins be made
> available as part of the new release distribution. Configuring
> rosegarden wit
On Sun, 2009-03-22 at 06:46 +0100, David Henningsson wrote:
> > * fluid_renderer* is another bad name. It is not rendering anything, in the
> > sense of translation, like the verb used in "rendering SVG into bitmap
> > graphics". The proposed functions are only audio file helpers, because you
>
On Wed, 2009-03-25 at 07:49 +0200, Graham Goode wrote:
> Hi,
> Is there a cutoff frequency effect in Fluidsynth like the TVF Cutoff
> Frequency effect in Creative Cards where you set up the NRPN
> controller with:
> 176,99,1
> 176,98,32
> and then send CC 6 to apply the cutoff filter, like so:
On Thu, 2009-04-02 at 23:07 +0200, Pedro Lopez-Cabanillas wrote:
> Felix Krause wrote:
> > Hi all,
> >
> > I'm using the fluidsynth library (current unstable Mac version from
> > fink) and tested the midi file player. It behaves very strange:
> >
> > - fluid_player_set_loop doesn't seem to have any
On Sun, 2009-04-05 at 00:07 +1100, D.Bartolec wrote:
>
> I've discovered it after playing some MIDI files that would send bank
> LSB:0 for drum channel without sending bank MSB at all.
> This would cause drum tracks to change to MSB:0 LSB:0.
> Here is the fix:
>
Its likely those MIDI files ar
On Sun, 2009-04-05 at 08:08 +0200, David Henningsson wrote:
> D.Bartolec skrev:
> > I've discovered it after playing some MIDI files that would send bank LSB:0
> > for drum channel without sending bank MSB at all.
> > This would cause drum tracks to change to MSB:0 LSB:0.
>
> I've taken a quick
On Sun, 2009-04-05 at 11:14 +0200, David Henningsson wrote:
> David Henningsson skrev:
> > Otherwise I think it makes sense - LSB setting does not affect MSB
> > setting, and the other way around.
> >
> > A question to the audience: Why do we have variables for banknum and
> > prognum in fluid_cha
Hello David,
On Sat, 2009-04-04 at 20:55 +0200, David Henningsson wrote:
> Pedro Lopez-Cabanillas skrev:
> > David Henningsson wrote:
> >> Pedro Lopez-Cabanillas skrev:
>
> > It is something that only Josh can
> > do, and he is not answering mails right now.
>
> That is a problem.
>
By all m
Hello David and Bernat,
On Sun, 2009-04-19 at 13:28 +0200, Bernat Arlandis i Mañó wrote:
> David Henningsson escrigué:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524566
> >
> > To get back on topic, I'm not demanding that fluidsynth should be more
> > Debian-friendly in the future, b
when
a new API is developed.
That is my current perspective on project direction. I would like to
extend an invitation to Bernat in particular, to communicate his
thoughts on his work with 2.x and how we can develop a team strategy to
move forward. I also encourage others to be a part of this
To help make things a bit more organized I will set forth a plan for the
1.1.0 development cycle. This is not set in stone and is open for
input.
Development cycle will be 3 months, which means FluidSynth 1.1.0 will be
released around July 12th. Feature freeze will occur 2 weeks before.
June 28
Hello Esben,
Yes indeed, its a problem. Its on the list for the next release.
Ticket #6 if you want to track it:
http://fluidsynth.resonance.org/trac/ticket/6
Cheers!
Josh
On Wed, 2009-04-15 at 03:03 +0200, Esben Stien wrote:
> Running fluidsynth-1.0.9, which is really nice, thanks;),
Hello Jimmy,
On Tue, 2009-04-14 at 15:56 -0700, jimmy wrote:
> It seems we are all looking forward to 2.0, while 1.0 is agreed as legacy
> code base.
>
> I don't know how far along the code refactoring (FS 2.0) is. Can we get a
> status update, or current functions available. What's missing c
Hello David,
On Tue, 2009-04-14 at 18:06 +0200, David Henningsson wrote:
> > With all this big changes and new plans, I'm wondering where does lie
> > the 2.0 branch? I could have done some work these holidays but I have
> > the feeling that we're diverging and I prefer to wait for the water to
>
Hello Bernat,
On Tue, 2009-04-14 at 11:00 +0200, Bernat Arlandis i Mañó wrote:
> First, I sent this message but it didn't get to my mailbox and it seems
> to be ignored by everyone so I guess it didn't reach your mailbox
> neither, I think it's interesting:
> http://lists.gnu.org/archive/html/fl
Hello,
Its been really nice reading the introductions.. There are no specific
qualifications on this, so if anyone else feels inspired to introduce
themselves, please do. I know there are several other people on this
list who have been long time FluidSynth contributors and users.
The next step
Hello!
Glad to have you on board. I wonder how many other people have been
lurking on the list without saying anything, despite having interest in
contributing to the project :)
I think the next step at this point, is to decide on what tickets should
be slated for completion by the 1.1.0 milesto
Hello David,
On Mon, 2009-04-13 at 15:21 +0200, David Henningsson wrote:
> > So not sure what that is all about. Hmm, it just occurred to me. It is
> > one thing to have your program link with a GPL library and its another
> > to have it in turn link with other programs, perhaps that is the
> >
On Mon, 2009-04-13 at 09:45 +0200, David Henningsson wrote:
> Done. Anything else I should know when it comes to comitting patches?
>
I don't think we should be too hesitant about committing changes, or at
least not afraid to. Communication is a good thing and tracking things
with tickets in Tr
Hello FluidSynth list,
As I mentioned in a previous email, it seems like a good idea to
introduce ourselves a little and describe our interests in FluidSynth.
The project has been pretty dormant for some time now until recently, so
many of the recent personalities on the list are new. It would be
Hello David,
On Sun, 2009-04-12 at 12:26 +0200, David Henningsson wrote:
> Josh Green skrev:
> > So, its official. The long overdue FluidSynth 1.0.9 "A Sound Future"
> > has been released.
>
> Thanks! \O/ Select your favorite MIDI song, launch FluidSynth an
nnovation and direction.
Stay tuned.
Cheers!
Josh Green
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ttle), then its time for a release. Please speak up now, if there
are any outstanding issues that should be resolved before hand.
Seeing how release names seem to be all the rage these days.. How about
"A Sound Future" for 1.0.9, in reference to the new development
interest.
Cheers!
basic preset fallback selection. So I've closed
Ticket #23. Please let me know if this functionality works as expected.
http://fluidsynth.resonance.org/trac/ticket/23
Best regards,
Josh Green
On Sat, 2009-02-07 at 07:31 -0800, jimmy wrote:
> Hi Josh,
>
> One more try. This
Hello Joshua,
As you mentioned in your other email, there is no MIDI output ports from
FluidSynth. When you say "midi out on another channel" what MIDI driver
are you using? If it was the ALSA sequencer or JACK MIDI, you could
just have your MIDI source be a MIDI output port which gets connected
Hello David,
First off I'd like to say, thanks for your work in this area of
FluidSynth. Its been a long time wish of mine to be able to render MIDI
files to audio, in a faster than realtime fashion and with the same
output every time. This patch looks like the right direction to realize
this.
while the output meters are enabled.
>
> http://fluidsynth.resonance.org/trac/ticket/21
> http://sourceforge.net/tracker/index.php?func=detail&aid=2538954&group_id=93509&atid=604538
>
> On Tue, Mar 10, 2009 at 1:00 AM, Josh Green wrote:
> > On Mon, 2009-03-09 at 23:53 +, R
On Mon, 2009-03-09 at 23:53 +, Rui Nuno Capela wrote:
> Josh Green wrote:
> > I just committed support for Jack MIDI to SVN. I tested this with
> > jack_midiseq. Also tested with alsaseq2jackmidi by connecting up my
> > MIDI keyboard to FluidSynth using tha
I'm
not sure if tomorrow will end up being the day for the release of 1.0.9,
due to limited free time, but I think we should try and make it happen
real soon. Testing and feedback would be great!
Cheers!
Josh Green
___
fluid-dev ma
Hello,
I didn't feel that Max's input was particularly arrogant or disdainful.
It was some strong criticism but it seemed to be rather constructive as
well. There are indeed many shortcomings of FluidSynth and the project
hasn't really been all that active since I took over maintainership of
it.
Hello Pedro,
On Sat, 2009-02-28 at 22:55 +0100, Pedro Lopez-Cabanillas wrote:
> Anyway, I would like to ask what do you think about a new stable release
> 1.0.9
> from trunk, soon. I really like all the new drivers, and also interesting
> bugfixes. I would like to be able to fix tickets #22 and
Hello Bernat,
On Sun, 2009-03-01 at 01:46 +0100, Bernat Arlandis i Mañó wrote:
> I don't want to do a rewrite, I'd like to be conservative about changes
> except where absolutely necessary to reach the goals. I would even delay
> libInstPatch or any other library integration if that meant a lot
Hello,
On Sat, 2009-02-28 at 18:20 +0100, Bernat Arlandis i Mañó wrote:
> Hi.
>
> Sorry for the long wait but I'm a bit busy lately. This is how it's
> gonna be since this is something I have to do on my spare time so there
> will be ups and lows inevitably, but I'm firmly decide to get there w
On Sat, 2009-02-28 at 18:24 +0100, Bernat Arlandis i Mañó wrote:
> The attached image I promised. :)
>
> Josh, I couldn't upload this image to the wiki, here:
> http://fluidsynth.resonance.org/trac/wiki/newdesign
>
Did you get an error? Or did it just not give you the option to attach
it? I w
On Wed, 2009-02-04 at 16:05 +0900, KO Myung-Hun wrote:
> Of course, there are many people to want to use FluidSynth on OS/2. If
> there was no people, would I port it ? In addition, FluidSynth is
> important as a lib as well as a stand-alone program. The reason I ported
> FluidSynth at first was al
yes" -a "$DART_FOUND" = "yes"; then
> + AC_DEFINE(DART_SUPPORT, 1, [whether or not we are supporting DART])
> + DART_SUPPORT=1
> +fi
> +
> +AM_CONDITIONAL(DART_SUPPORT, test "$DART_SUPPORT" = "1")
> +AC_SUBST(DART_CFLAGS)
> +AC_SUBST(DART
On Tue, 2009-02-03 at 16:27 +0100, Bernat Arlandis i Mañó wrote:
> Josh Green escrigué:
> >
> > The new2 driver stuff is not obsolete. Its used in particular by QSynth
> > to intercept the audio for meters. I definitely think this mess should
> > be overhauled for Fl
On Mon, 2009-02-02 at 23:39 +0100, Bernat Arlandis i Mañó wrote:
> Pedro Lopez-Cabanillas escrigué:
> >
> > I would like to see this fix (ticket #21) into trunk, if it can be
> > backported
> > without breaking 1.x API.
> >
> >
> >
> It deals basically with the Jack driver, I've replaced the o
On Sun, 2009-02-01 at 12:23 -0800, jimmy wrote:
> Hi folks,
>
> I know Miguel(???) was working on a reimplementation of FS using CPP. Plus,
> some folks here are looking to modularize FS. You may want to use some kind
> of dictionary, or table look up for some of the structures (objects) used
Hello Pedro,
On Sun, 2009-02-01 at 02:05 +0100, Pedro Lopez-Cabanillas wrote:
> I've checked in some changes to the PortAudio driver.
>
> - PortAudio enumerates devices having input only ports. As we need audio
> output devices, I've changed the enumeration to ignore devices with less
> than 2
On Fri, 2009-01-30 at 10:14 -0600, S. Christian Collins wrote:
> I'm used to the following behavior when using MIDI on a Creative card:
> when I select an instrument not present, such as bank 8 program 20,
> the MIDI track will sound using bank 0 program 20 instead. This seems
> like a simple and
Hello,
On Fri, 2009-01-30 at 02:05 +0100, Bernat Arlandis i Mañó wrote:
> Hi.
>
> I've started the new branch and committed the changes I was doing. Not
> much new, just playing around trying to learn and fix some things. You
> might want to review it for possible inclusion of some of the fixes
On Thu, 2009-01-29 at 22:46 +0100, Pedro Lopez-Cabanillas wrote:
> I have a problem with ASIO, though. First, I don't like the license terms
> from
> Steinberg: they don't allow to redistribute their sources (that are available
> free of charge for registered developers). Second, they ask for an
On Thu, 2009-01-29 at 23:29 +0100, Pedro Lopez-Cabanillas wrote:
> Josh Green wrote:
> > On Thu, 2009-01-29 at 22:46 +0100, Pedro Lopez-Cabanillas wrote:
> > > Thanks, Josh!
> > >
> > > I will try to find some time this week end to play in Windows. I've
>
On Thu, 2009-01-29 at 22:46 +0100, Pedro Lopez-Cabanillas wrote:
> Thanks, Josh!
>
> I will try to find some time this week end to play in Windows. I've already
> succesfully tested it on Linux.
>
> I have a problem with ASIO, though. First, I don't like the license terms
> from
> Steinberg:
Hello,
Good point about WineASIO, I didn't actually know such thing existed.
Best regards,
Josh
On Thu, 2009-01-29 at 11:28 +0200, ggoode.sa wrote:
> Hi Josh,
>
> I don't have a build environment in Windows at the moment and probably
> won't for a few more weeks (in the middle of a move
On Thu, 2009-01-29 at 00:12 +0100, Pedro Lopez-Cabanillas wrote:
> > Seems to me like it is definitely worth improving the existing PortAudio
> > driver. Any idea what this would entail?
> > Josh
>
> Briefly:
> * Detect and define PORTAUDIO_* in the build system. I've done that using
> pkg-c
On Wed, 2009-01-28 at 22:37 +0100, Bernat Arlandis i Mañó wrote:
> What do you think about fixing ticket #21 for 1.09? Without this,
> multi-channel output cannot be enabled from QSynth.
>
I'm looking at this now. I must admit, I've never quite figured out why
there are 2 sets of drivers (drive
Hey guys,
I enabled the Trac ticket details on the Timeline, since this was
mentioned as a desired feature. Make sure the "Ticket details" toggle
is on in the Timeline settings box.
Cheers.
Josh
___
fluid-dev mailing list
fluid-dev@nongnu.o
On Wed, 2009-01-28 at 11:34 +0100, Antoine Schmitt wrote:
> Hello,
> I'm not sure that the problem can be ignored for Midi file playback,
> because a large driver buffer will miss some midi events, which will
> then happen late in the audio stream.
>
> About my patch, the fact is that I haven'
Hi Jimmy,
Just keeping the already selected instrument when an invalid selection
is received seems strange to me. Do you think that would create the
desired effect in most MIDI files? It is a case of the MIDI file
expecting an instrument to be present, which is not, right? I'm not
convinced tha
Great to hear. Thanks as always for your testing efforts. Cheers!
Josh
On Wed, 2009-01-28 at 09:16 -0500, Ebrahim Mayat wrote:
> Hello
>
> Following up from yesterday, I just tried the new enhanced CoreMIDI
> feature with a dual port MIDI interface and sure enough I can trigger
> sa
On Tue, 2009-01-27 at 21:59 +0100, Pedro Lopez-Cabanillas wrote:
> I don't think so. Seems that the PortAudio driver would be useful only to
> Windows users, where FluidSynth has only a DirectSound driver with huge
> latency problems. For this platform PortAudio provides ASIO and WinMM audio
>
On Tue, 2009-01-27 at 21:18 +0100, Pedro Lopez-Cabanillas wrote:
> > Hello Pedro
> >
> > I am unable to add any feedback on the ticket referred to above.
>
> Trac requires to log in with your user/password to edit tickets. If you
> provided it, then there is a problem with the site. Josh, can you
Hello Jimmy,
I remember discussing this issue way back when, but kind of left it for
later, since I wasn't really sure what the best solution was. I should
probably read over the older thread, since I think I did have some good
ideas of how to resolve it then (something about determining whether
I probably shouldn't say too much, until I see what Antoine's solution
is.. But..
On Tue, 2009-01-27 at 03:04 +0100, Bernat Arlandis i Mañó wrote:
> > It makes sense to me to
> > process the audio based on the audio playback. This would lead to
> > identical playback between successive renders
On Tue, 2009-01-27 at 01:12 +0100, Bernat Arlandis i Mañó wrote:
> > About new development, there is an improvement to fluid that I had
> > worked on two years ago in a private branch that I think should be
> > integrated inside the main code base. I don't know if it should be
> > integrated
On Mon, 2009-01-26 at 15:10 -0500, Ebrahim Mayat wrote:
> ...and while we are on the topic of new development...one thing that has
> been on my mind for a while is the subject of effects plug-ins. For the
> last few releases, I have chosen not to add the option of LADSPA for the
> simple reason tha
On Mon, 2009-01-26 at 09:43 +0100, Antoine Schmitt wrote:
> Le 25 janv. 09 à 23:14, Josh Green a écrit :
> > Things for the new 2.x branch:
>
>
> About new development, there is an improvement to fluid that I had
> worked on two years ago in a private branch t
On Mon, 2009-01-26 at 22:52 +0100, Pedro Lopez-Cabanillas wrote:
> I would like to find more time to work on the PortAudio driver, as it was my
> plan for ticket #19. I will try, but don't hold your breath.
>
> You are right: there is already a PortAudio driver, but it doesn't compile
> with Por
On Mon, 2009-01-26 at 12:06 +0100, Bernat Arlandis i Mañó wrote:
> Still, keep in mind that it's not my main goal splitting into separate libs
> but having good modularization to the point this would be really easy and
> practical.
>
Sounds good.
> > libInstPatch *does* handle 24 bit audio and f
On Mon, 2009-01-26 at 01:47 +0100, Bernat Arlandis i Mañó wrote:
> Specifically, on the modularization aspect I'd like to break FS down in
> several libraries that could build separately if needed. This libraries
> might be, guessing a bit: fluid-synth (the synthesis engine),
> fluid-soundfont (
On Sun, 2009-01-25 at 09:27 -0500, Ebrahim Mayat wrote:
> By "break compatibility backwards", do you mean that old soundfont files
> could not be parsed successfully ?
>
> Perhaps you are talking about the linking of FS libraries to other
> programs like SWAMI, MAX/MSP and fluid~ ?
>
> Thanks
Hello Bernat,
On Sun, 2009-01-25 at 13:41 +0100, Bernat Arlandis i Mañó wrote:
> This is concerning ticket #11.
>
> I'm thinking on a lot of changes to take FS forward as I review the
> source code and fix some things, but most of these changes would break
> compatibility backwards. Maybe we sh
Hello,
Great that you added channel pressure. I wish I had a keyboard that
could test it out ;)
As for the velocity to filter cutoff issue. There is a version field in
SoundFont files (ifil chunk). If there are SoundFont files out there
which assume the broken velocity to filter cutoff modulat
en
>
>
> --- On Wed, 1/21/09, Bernat Arlandis i Mañó wrote:
>
> > From: Bernat Arlandis i Mañó
> > Subject: Re: [fluid-dev] A new beginning for the Resonance Instrument
> > Database
> > To: "Josh Green"
> > Cc: "FluidSynth Devel
back would be great. I
wanted to give it a little testing before announcing it on the Linux
Audio Announce list. Submitting your favorite freely distributable
instruments, either ones you created or off the net, would also be very
helpful.
Best regards,
Josh Green
http://sounds.res
It has also been on my mind to add Jack MIDI support. Maybe someone
will beat me to it? ;)
Josh
On Sat, 2009-01-10 at 17:56 -0500, Ebrahim Mayat wrote:
> Hello again
>
> Both jack-0.116.0 and jack-keyboard compile successfully on OS X and
> Linux. So, I was wondering if it would be possi
On Sat, 2009-01-10 at 17:59 +0100, Bernat Arlandis i Mañó wrote:
> Hi.
>
> I've copied the fluidsynth man page to the wiki for a start. Although it
> gets duplicated I think it will be easier to access it and review it
> there. I've formatted it for the wiki without changing the section
> layou
On Fri, 2009-01-09 at 21:02 +0100, Bernat Arlandis i Mañó wrote:
> Josh Green escrigué:
> >
> > Really? Seems pretty standard to me. Toplevel is branches/, tags/ and
> > trunk/. Under trunk is the fluidsynth/ directory. What did you have in
> > mind?
> >
>
Hi Ebrahim,
On Fri, 2009-01-09 at 08:37 -0500, Ebrahim Mayat wrote:
> Hello Pedro
>
> My deep gratitude for the CoreMIDI implementation. I managed to
> compile and run fluidsynth with CoreMIDI.
>
>
> There are a couple of minor bugs that need to be ironed out.
>
>
> 1. I had a slight proble
On Fri, 2009-01-09 at 00:28 +0100, Bernat Arlandis i Mañó wrote:
> I think this would ease development in the long term by reducing the
> amount of code. If you all agree we can entirely drop that "no external
> dependencies" requirement unless there's some problem.
Changing the code to use glib
On Thu, 2009-01-08 at 21:23 +0100, Pedro Lopez-Cabanillas wrote:
> Josh Green wrote:
> > On Wed, 2009-01-07 at 20:19 -0500, Ebrahim Mayat wrote:
> > > One workaround that I had suggested to Josh was to add CoreMIDI support
> > > to fluidsynth.
> > >
> &g
On Wed, 2009-01-07 at 20:19 -0500, Ebrahim Mayat wrote:
> On Wed, 2009-01-07 at 23:19 +0100, Pedro Lopez-Cabanillas wrote:
>
> > I think that the best solution would be to properly package Fluidsynth,
> > maybe
> > as a Fink package, and also the applications depending on it. Not sure why
> >
Ebrahim Mayat (also on this list) has been providing testing and
documentation for FluidSynth on Mac OS X for some time now. He
submitted a Fink package a while back, I'm not sure what the status of
that is though. Maybe Ebrahim will chime in?
Regards,
Josh
On Wed, 2009-01-07 at 23:19 +
Yes. Should be added to the ticket tracker. If no one gets around to
it by this weekend, I'll add it.
Josh
On Wed, 2009-01-07 at 18:02 +0100, Bernat Arlandis i Mañó wrote:
> In this case this should go to the ticket tracker for future
> implementation. Anyone for confirmation?
>
> Ken E
gt;
Sounds good to me! You seem to be a good candidate for a FluidSynth
subversion account. If you are interested, email me personally your
desired login information.
Happy new year to you as well.
Josh Green
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hello Bernat,
Great to hear that it is working for you! As for debugging, if you pass
the ./configure script --enable-debug, then it will build it with
debugging symbols turned on. I think it turns off optimization too,
which will make for a rather significantly un-optimized build of
FluidSynth.
Hello Bernat,
I added support for the following RPNs:
00: Bend range (MSB only, in semitones)
01: Fine tune (MSB and LSB +/- 50 cents, center at 8192)
02: Coarse tune (MSB only +/- semitones, center at 64)
I did not test them though. If you could try them out and let me know
if they work as expe
Hello,
It looks like FluidSynth currently supports SoundFont 2.01 NRPN numbers
for setting any effect generator in realtime (well most generators at
any rate), which you could use to set the fine and course tuning
parameters. I looked at the code though and there is no handling of the
General MID
I don't think these messages are supported, although I seem to remember
seeing some FluidSynth code which dealt with tuning messages. Just to
clarify though, are you referring to the MIDI Tuning specification?
http://www.midi.org/about-midi/tuning.shtml
This uses RPN dumps though and not control
Hello Bernat,
I agree that major changes aren't really needed or necessary at this
point. I would like to add additional features though, in a backwards
compatible manner when possible (24 bit audio, sample streaming, faster
than realtime MIDI rendering, etc).
I began documenting all functions w
io driver or maybe the reverb
> settings? The bass seems weak. Are there eq settings?
>
> Thank you.
>
> May the Lord bless you,
> Philip
>
>
> Josh Green wrote:
> > Hello Philip,
> >
> > When using the ALSA sequencer MIDI driver there is the
Hello Philip,
When using the ALSA sequencer MIDI driver there is the option of setting
channels to a multiple of 16 (synth.midi-channels), which will create
one ALSA MIDI port per 16 channels.
As for setting panning on a per note basis.. This is possible to do
with the SoundFont loader API in Fl
Hello,
Swami (http://swami.resonance.org) does its own instrument handling
using the FluidSynth SoundFont loader API. You could have a look at
src/plugins/fluidsynth.c to get an idea of how this works, although it
might be difficult to sort out the parts you want versus the rest of the
code. All
Hello Gerald,
On Tue, 2008-10-14 at 11:18 +0100, Edenyard wrote:
> I had the same problem when putting together a system using Fluid and
> Jorgan and I devised a Bash script to make the necessary connections
> after loading Fluid but before loading Jorgan. (I've shown the script
> below between
Hello,
As Pedro suggested, you could control FluidSynth via TCP/IP. If you
want finer grained control over FluidSynth and don't mind writing C
code, then you could use FluidSynth as a shared library. This is how
Swami and QSynth use FluidSynth.
Best regards,
Josh
On Sun, 2008-10-12 at
Hey Julien,
Just some more clarity on licenses.. First, FluidSynth is under the
LGPL. Indeed the GPL does not forbid incorporation in a commercial
product, as long as the source code is not linked or included directly
in another program (i.e., it is used as a stand alone application). The
LPGL
Hello Peter,
I just wanted to make sure you are aware of some of the implications of
using software under the LGPL, like FluidSynth, in a commercial
application. Since some of these things are overlooked at times. The
LGPL allows commercial applications to link to it as a shared library.
However
1 - 100 of 370 matches
Mail list logo
