On Wed, Feb 29, 2012 at 09:32:48AM +0100, David Henningsson wrote:
> >python: malloc.c:2453: sYSMALLOc: Assertion `(old_top == (((mbinptr)
> >(((char *)&((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct
> >malloc_chunk, fd&& old_size == 0) || ((unsigned long) (old_size)
> >>= (unsigned
On Tue, Nov 15, 2011 at 12:13:49PM +1100, Matt Giuca wrote:
> Right, so I tried adjusting the "Reverb" knob in Rosegarden (connected to
> FluidSynth) and didn't hear much difference. I'm not entirely sure what all
> the reverb settings do (there are four), but I found that increasing the
> "room si
On Mon, Nov 14, 2011 at 10:35:44PM +1100, Matt Giuca wrote:
> Any that I missed?
You can also programmatically control almost everything via midi CC
messages and a carefully edited soundfont. That would work in your
case, although it's a bit of a faff to set up.
__
On Sun, Nov 06, 2011 at 02:41:26PM +1100, Matt Giuca wrote:
> Now another possibility is that this problem was not introduced by FS
> between 1.1.3 and 1.1.4, but that you have a problem with the Debian
> packaged version of FS 1.1.4. Note that the Debian packaged versions of
> programs are not alw
On Tue, Oct 25, 2011 at 06:12:12PM +1100, Matt Giuca wrote:
> Or perhaps you mean there's no built-in way to do that (in the MIDI spec),
> but that I could find an unused controller and edit the FluidSynth code to
> make it extend the decay?
Yes, just pick something that isn't magic like sustain.
On Tue, Oct 25, 2011 at 07:33:23AM +0100, Louis B. wrote:
> Obviously that should read "as well as the sustain MIDI signal" as you want
> both MIDI signals to operate at the same time.
No, if you want 'releasing a key' to do anything at all, you need to
not have the sustain switch active, because
On Tue, Oct 25, 2011 at 09:03:00AM +1100, Matt Giuca wrote:
> Well, this Creative Labs page suggests that that feature isn't in the
> SoundFont spec:
> http://www.creative.com/soundblaster/soundfont/tutorials/welcome.asp?articleid=54142&page=7
>
> There is an envelope parameter called "Sustain" bu
On Tue, Sep 13, 2011 at 09:58:56AM +0200, David Henningsson wrote:
> For the first dimension, it is not obvious to me whether we can or
> not, but it seems likely, especially if we, as you say, "bend a
> little or force the letter". So the precondition for taking the app
> down seems to me to be fu
On Mon, Sep 12, 2011 at 11:38:46PM +0200, Pedro Lopez-Cabanillas wrote:
> Likewise, for me it is not only important the letter of the LGPL license, but
> the ethical principles inspiring the libre software movement. For instance,
> the principle of no discrimination that is not part of the LGPL,
On Mon, Sep 12, 2011 at 09:30:50AM +0200, David Henningsson wrote:
> Maybe the section you quoted below is what makes the free-compiler
> question irrelevant then?
For xcode, which is clearly an "OS component", yes. But it's not
really the free-compiler question, just an interesting subset of
comp
On Sun, Sep 11, 2011 at 09:28:31PM +0200, Pedro Lopez-Cabanillas wrote:
> But as I've said, if the compiler and developer tools are "freeware"
> or not is irrelevant from the license point of view, in my
> opinion. These are the same tools used to build all Mac OSX
> applications; any legal restric
On Sun, Sep 04, 2011 at 06:47:10PM +0200, Pedro Lopez-Cabanillas wrote:
> As I've already said: this is a false myth. Jack doesn't improve
> latency if you only send fluidsynth output to the sound card.
>
> For MIDI realtime routing (from your external MIDI keyboard to
> Rosegarden, and from Roseg
On Sun, Sep 04, 2011 at 12:01:48PM -0400, Lane Lester wrote:
> But I'm still curious about whether to stick with alsa or go with jack. What
> do you think?
If you don't know that you need jack, then you probably don't need it.
Jack's main purpose is low-latency. If you are playing a midi file,
yo
On Wed, Aug 24, 2011 at 02:06:49PM -0700, Michael Geis wrote:
> The current idea is to create each sample file by passing fluidsynth a one
> note .mid file,
> outputting the raw wave data to file and then converting to .wav with sox.
>
> The sampler is not very complicated, it essentially applie
On Sat, Aug 06, 2011 at 04:40:02PM +0200, Pedro Lopez-Cabanillas wrote:
> Because the SONAME is part of the file name of the runtime shared
(Is *precisely* the file name; the SONAME field is copied into a
DT_NEEDED entry when linking, and the elf loader searches for a file
by that name to complete
On Sat, Aug 06, 2011 at 04:13:16PM +0200, David Henningsson wrote:
> Thanks for the pointers. As the FLUIDSYNTH_API is already in place,
> if we could make that evaluate to something like __attribute__
> ((visibility ("default"))) on gcc platform, that would be the
> simplest way of solving this pr
On Sat, Aug 06, 2011 at 03:20:54PM +0200, Pedro Lopez-Cabanillas wrote:
> On Saturday 06 August 2011, Andrew Suffield wrote:
> > On Sat, Aug 06, 2011 at 10:00:21PM +1000, Matt Giuca wrote:
> > > - Release FluidSynth 2.0, with soname libfluidsynth.so.2, or
> >
> > It
On Sat, Aug 06, 2011 at 03:05:06PM +0200, Pedro Lopez-Cabanillas wrote:
> On Saturday 06 August 2011, Andrew Suffield wrote:
> > On Sat, Aug 06, 2011 at 02:42:59PM +0200, Pedro Lopez-Cabanillas wrote:
> > > The auto-tools based build system of FluidSynth is deprecated, and
>
On Sat, Aug 06, 2011 at 02:42:59PM +0200, Pedro Lopez-Cabanillas wrote:
> The auto-tools based build system of FluidSynth is deprecated, and
> was using libtool. The new CMake based build system does not use
> libtool.
That's unfortunate. Consider using libtool. This level of shared
library manipu
On Sat, Aug 06, 2011 at 10:00:21PM +1000, Matt Giuca wrote:
> - Release FluidSynth 2.0, with soname libfluidsynth.so.2, or
It is generally unwise to attempt to keep SONAME versions and project
versions in sync. This leads to confusion and inappropriate
compatibility problems. Best practice is to k
On Sat, Aug 06, 2011 at 12:54:20PM +0200, David Henningsson wrote:
> As reported in ticket #98, FluidSynth 1.1.4 dropped one symbol.
> However, this symbol (fluid_defsfont_get_sample) is not part of the
> public API, so no programs should use it anyway.
>
> I don't know how much of a big deal this
On Mon, Jul 11, 2011 at 10:08:58AM +0200, David Henningsson wrote:
> I agree that it feels strange, but question is if it matters?
Yes, that is the question. I can't really tell; there's too much going
on here that I don't fully understand yet.
> For
> release volumes, things should always ramp d
I've been working through the source, and while I don't pretend to
fully understand what's going on here, I've spotted a couple of things
that seem wrong:
fluid_mod_get_value sets range1 and range2 to 127, which are used as
the divisor for linear and bipolar modulators. That means, for a
bipolar
23 matches
Mail list logo
