Re: [fluid-dev] About Supporting 2GiB+ Soundfonts on Windows

On Mar 17, 2020, at 04:44, Tom M. via fluid-dev wrote: > latter doesn't really make sense in practice, because long long is an > intrinsic type guaranteed to be at least 64 bits wide. And because > long long must be available, int64_t will also be available.) That describes int_least64_t. In an

Re: [fluid-dev] About Supporting 2GiB+ Soundfonts on Windows

On Mar 16, 2020, at 09:57, Tom M. via fluid-dev wrote: > The current workaround is to build fluidsynth with CygWin, which has "long" > set to 64bit. > > Any ideas how to solve this? Opinions on C99? If you decided to require C99, I would think you would want to use int64_t and its relatives fo

Re: [fluid-dev] Adding C++ as mandatory dependency?

On Jan 21, 2020, at 13:50, Carlo Bramini via fluid-dev wrote: > > From my experience, C++ is not a good idea sometimes, especially when you > want to maximize the performance and minimize the memory usage. Please don't take offense at this, but demonstrating that it is possible to write a poo

[fluid-dev] Homebrew package

Is there anyone here who is (or is willing to become) involved with updating the Homebrew (for macOS) fluidsynth package? It's currently providing 2.0.8, which segfaults consistently on startup. Regards, — Dan ___ fluid-dev mailing list fluid-dev@n

Re: [fluid-dev] Bpm

On Apr 15, 2019, at 12:06, Ceresa Jean-Jacques wrote: > May be one thing feasable and useful would be to have FluidSynth working in 2 > tempo modes (external/internal): > 1)In tempo mode "external" (default), fluidsynth reads tempo messages coming > from the MIDI file. > 2)In tempo mode "intern

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

On Nov 10, 2018, at 01:39, sqweek wrote: > > There's no analogous way to survey paths in use on Windows/OSX that I'm aware > of. Looking on the application side, MuseScore has its own paths: For macOS, you might wish to survey Fink , Homebrew , an

Re: [fluid-dev] Use of midi keyboard without user configuration

On Mar 1, 2018, at 21:16, Paul Cohn wrote: > > I've recently set up fluidsynth in a C++ program on OSX to accept midi inputs > from a keyboard, but it requires the use of midi patchbay to manually > connect. Each time the virtual port is different so on running the program I > have to go into

Re: [fluid-dev] Fixed key numbers --> note stays on

On Oct 1, 2016, at 19:52 , Ceresa Jean-Jacques wrote: > Yes this is a bug in FluidSynth, generators , KEY_NUM (and GEN_VELOCITY > too!) coming > > from SoudFont are ignored and replaced by (keyNum and velocity) coming from > MIDI input. > > The right behavior should be the reverse case. >

[fluid-dev] Fixed key numbers --> note stays on

When an instrument uses fixed key numbers, Fluidsynth never releases its notes. I’m using 1.1.6 on macOS. N.B. Check your volume before trying the attached example. Regards, — Dan FixedKeyTest.mid Description: MIDI audio FixedKeyTest.sf2 Description: Binary data _

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 13, 2016, at 13:45 , Ceresa Jean-Jacques wrote: > This is not the expected result in substractive synthesis practice. In many > case certains frequencies need to be resonant (woods, and horns instrument) > but not necessary to to the detriment of others frequencies. I'am pretty sure >

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 13, 2016, at 13:45 , Ceresa Jean-Jacques wrote: > > It seem that we are out of the scope of initial question ?! > Not very. The effect of the filter contributes to the impression that exclusiveClass does not work as expected. — Dan ___ fl

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 12, 2016, at 09:32 , S. Christian Collins wrote: > The problem isn't the envelope, it's the excessive amount of filter Q you are > using on that layer. What appears to be happening is that the 96 dB of > resonance amplifies the resonant frequency to a super-high level, which seems > to

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 12, 2016, at 09:32 , S. Christian Collins wrote: > > On 09/12/2016 08:13 AM, Dan Eble wrote: >>>> Say I have an instrument with a release time of 2 seconds. Fluidsynth >>>> sounds as if it is playing the sound at constant volume for 2 seconds >&g

Re: [fluid-dev] SoundFont exclusiveClass

>> Say I have an instrument with a release time of 2 seconds. Fluidsynth >> sounds as if it is playing the sound at constant volume for 2 seconds after >> the end of the note, then stopping abruptly. According to the SoundFont >> spec, the volume should instead decrease linearly to zero. > I h

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 11, 2016, at 17:44 , S. Christian Collins wrote: > > On 09/10/2016 04:08 PM, Dan Eble wrote: >> Making this worse, Fluidsynth does not seem to ramp down the during the >> release portion of the volume envelope (see “releaseVolEnv” in the SoundFont >> spec). &

Re: [fluid-dev] SoundFont exclusiveClass

On Sep 10, 2016, at 13:48 , Dan Eble wrote: > > 2. If the sound of the instrument has not naturally decayed by the time > Fluidsynth decides to cut it off, there is a distracting click. Making this worse, Fluidsynth does not seem to ramp down the during the release portion of t

[fluid-dev] SoundFont exclusiveClass

The SoundFont spec (version 2.04) describes the “exclusiveClass" option this way: "when this note is initiated, any other sounding note with the same exclusive class value should be rapidly terminated.” I hear this effect when I use the synthesizer included in the editor I’m using (Polyphone),