On Oct 31, 2012, at 3:28 AM, S. Christian Collins wrote:
I've downloaded them all... every single SoundFont-compatible VSTi I
could find, and not a single one of them comes anywhere close to the
accurate SoundFont reproduction of FluidSynth. Apparently, nobody else
bothers to support SoundFont
On Jul 11, 2012, at 08:41 AM, Matt Giuca wrote:I really don't want to fuel the fire here, but I'd just like to speak with some experience on both sides of the patch/pull game.You and Pedro seem to stick with only what you prefer with the Soundfont specs and GS-specs, both of which only deal with 1
On Jul 09, 2012, at 02:36 PM, Pedro Lopez-Cabanillas wrote:On Monday 09 July 2012, Ebrahim Mayat wrote: > You ignored my post by not answering a simple question. I had no obligation to answer, and much less to do so within a time frame of your convenience. PedroAt least have the courtesy
On Jul 09, 2012, at 01:08 AM, Peter Eastman wrote:I didn't come here to argue. I'm suggesting ways to make FluidSynth a better program. If you don't want my help or ideas, just say so and I'll go away. Peter PeterI would be delighted to have your help and I'm sure that there a many others who fee
On Jul 09, 2012, at 12:34 AM, Pedro Lopez-Cabanillas wrote:> Once again, do you know of any sequencer applications that use "qmidinet" > ? Qmidinet is a gateway between the network and native MIDI applications for Linux (ALSA and Jack). Any Linux sequencer using ALSA sequencer or Jack can be u
Pedro
Once again, do you know of any sequencer applications that use "qmidinet" ?
E
Sent from my iPhone
On Jul 8, 2012, at 4:37 PM, Ebrahim Mayat wrote:
>
>
> On Jul 08, 2012, at 10:24 AM, Pedro Lopez-Cabanillas
> wrote:
>
>> An alternative for transpor
On Jul 08, 2012, at 10:24 AM, Pedro Lopez-Cabanillas wrote:An alternative for transporting MIDI over a network is RTP MIDI, with drivers included in both Mac OSX and iOS. Pedro, I haven't used "RTP MIDI" but that also sounds interesting. Do you know of any sequencer applications that use "qmidine
On Jul 08, 2012, at 10:09 AM, Stefan Sauer wrote:On 07/08/2012 03:24 PM, Ebrahim Mayat wrote:Hello all While MIDI (GM, sysex etc.) is great (after all these years), it would be a pity to exclude OSC. One thing is evident about OSC: OSC is a kind of "wireless MIDI" which would be a gre
Hello allWhile MIDI (GM, sysex etc.) is great (after all these years), it would be a pity to exclude OSC. One thing is evident about OSC: OSC is a kind of "wireless MIDI" which would be a great feature. Using both MIDI and OSC is great to have: lots of sequencer applications now do this; for exampl
On Mar 28, 2012, at 8:55 AM, Antoine Schmitt wrote:
Ok !
Cross-reading your answer, adn Ebrahim's, I figured that I needed to
include all the closure of the dependencies along with my delivery :
glib and gthread, but also iconv and intl, and use install_name_tool
to modify all mutual inte
On Mar 27, 2012, at 6:47 PM, Antoine Schmitt wrote:
Thanks Ebrahim.
This is incredibly complex !
I cannot believe that I am the only one having this problem. How do
you people deploy fluidsynth-based executables on machines that do
not have glib installed ? Or is glib installed on all linux
On Mar 25, 2012, at 5:48 PM, Antoine Schmitt wrote:
Hi list,
coming back on this. I stippped down my dependencies, and now my
Xtra only depends on glib and gthread.
But now I am stuck again, trying to not depend on these shlibs.
- I used Sven install_name_tool idea, which seems to work and l
On Saturday 10 March 2012, Antoine Schmitt wrote:
Hi list,
I'm currently porting my fluidsynth Xtra (name for Adobe Director
plugin, i.e. a shared library that is dynamically loaded into the
final executable) to fluidsynth 1.1.5. Previously, it was on 1.0.7.
(visible on www.schmittmachine.com/flu
On Oct 14, 2011, at 12:45 AM, Jason Vasquez wrote:
Hello all,
I just built fluidsynth 1.1.5 for the first time on MacOS Lion, and
thought I'd pass this along. I had to make a couple changes from the
build process I used previously for 1.1.3 on Snow Leopard, so I'm not
100% positive as to which
On Sep 13, 2011, at 3:58 AM, David Henningsson wrote:
There are two dimensions here. First, there is the issue of whether
we can take action against App Store, and that depends on how we
interpret the LGPL, and second, whether we actually proceed with
taking that action, which depends on o
On Sep 7, 2011, at 12:42 AM, David Henningsson wrote:
Ok, good point. Maybe there are a usage cases for both?
Thanks also to Pedro and Orcan for looking up the current situation
in major distros. Let me summarise:
Debian (and derivatives such as Ubuntu):
Directory: /usr/share/sounds/sf2
Fil
On May 17, 2011, at 10:58 AM, David Henningsson wrote:
On 2011-05-14 13:05, Ebrahim Mayat wrote:
Would it be possible to post your presentation video in an
alternative
format somewhere on the net ? (mp4, avi,… or even YouTube ?) :-)
Many thanks for sharing,
Feel free to do so. (I assume
On May 13, 2011, at 4:02 AM, David Henningsson wrote:
When I held my LAC presentation, I got some feedback saying that
FluidSynth is a well working program that was useful to a lot of
people in the room. And so I would just want to relay that feedback
to all of you who have contributed to
On Apr 15, 2011, at 6:53 PM, Pedro Lopez-Cabanillas wrote:
On Thursday 14 April 2011, Ebrahim Mayat wrote:
What happens when you try and render a MIDI file using FluidSynth ?
(I
I can't reproduce your problem when rendering MIDI files in my Mac.
But again, I don't have acc
On Apr 14, 2011, at 4:25 PM, Sven Meier wrote:
BTW why is it that the resulting shared library is named
"Fluidsynth"? Wouldn't libfluidsynth.dylib be more appropriate?
Sven
Many thanks for your testing earlier.
If you build with the enable-framework option you will build an OS X
framewor
On Apr 13, 2011, at 5:25 PM, Pedro Lopez-Cabanillas wrote:I've attached a document containing the terminal output and the qsynth console output when lauching qsynth with the following commands:$ export DYLD_PRINT_LIBRARIES=1$ open qsynth.appPedroThe Terminal.app outputs from both your setup and min
On Apr 11, 2011, at 5:04 PM, Pedro Lopez-Cabanillas wrote:
I assume you mean that it doesn't work *in your system*.
I can only test it in my own intel mac, where it runs just fine.
Please note that Qsynth-0.3.4 and fluidsynth-1.1.3 work fine with
*all
the same soundfonts*.
the package co
On Apr 10, 2011, at 2:25 PM, Pedro Lopez-Cabanillas wrote:
Try with other soundfont files, renaming that file, or moving it to
another location.
*No soundfont files work with qsynth-0.3.6 on OS X.*
Please note that Qsynth-0.3.4 and fluidsynth-1.1.3 work fine with *all
the same soundfonts*
On Apr 10, 2011, at 1:37 PM, Pedro Lopez-Cabanillas wrote:
On Sunday 10 April 2011, Ebrahim Mayat wrote:
Okay, I tried with coreaudio but I still cannot load a soundfont
The app bundle does not include any soundfont file. You must provide
one, and configure its location in qsynth/setup
On Apr 10, 2011, at 1:09 PM, Pedro Lopez-Cabanillas wrote:
I've not included jack, midishare, libsndfile, or any other optional
dependencies. Only coreaudio and coremidi drivers, and of course the
required libraries glib and gthread are bundled into qsynth.app,
along with Qt4.
Regards,
P
On Apr 10, 2011, at 3:38 AM, Pedro Lopez-Cabanillas wrote:
Hi,
I've uploaded a Mac OSX package to SourceForge with an universal
bundle of QSynth 0.3.6, that should work in Intel and PowerPC Macs
without external dependencies. It uses the new FluidSynth framework
build type from trunk.
On Mar 27, 2011, at 4:14 PM, Bastien Dejean wrote:
Hi,
I thought by reading the man page that I could just plug my USB MIDI
Keyboard, launch fluidsynth with a soundfont as argument and play.
But it seems I'm missing something.
I tried 'fluidsynth -d -m coremidi x.sf2' but I don't see any MI
On Dec 3, 2010, at 9:28 AM, Felix Krause wrote:
I'd like to have FluidSynth to generate sound output and at the same
time write the audio output to a file. So I tried to create a "file"
audio driver and a "coreaudio" audio driver with the same
synthesizer as parameter. Turns out this doesn
On Nov 15, 2010, at 5:49 PM, Matt Giuca wrote:
It still works fine for me, on Ubuntu 10.04.
Are you on a Mac? I'm guessing you might be, because the commit log
for r388 (which you claim to be the start of the breakage) is "Mac
CoreAudio driver adapted to AuHAL."
Hello Matt
That is corre
Hello again
While testing revision 393 I realized that MIDI files could not be
rendered. Investigating further, I found that the MIDI file rendering
function in fluidsynth revisions 388-393 is broken while MIDI file
rendering works in revisions 387 down to 385.
Regards
Ebrahim
__
On Nov 14, 2010, at 4:32 AM, David Henningsson wrote:
True or not true - that discussion belongs to fink or cmake lists
rather than this one.
Good Day David
I agree. In fact, I was not the one who brought up this topic since
this is not an issue for me. The "cmake" message was forwarded a
On Nov 10, 2010, at 9:08 PM, David Henningsson wrote:
May I kindly ask you to bring the issue of CMake's packaging issues
in Fink, to the fink list instead of the fluidsynth list? It seems
more likely to reach the right people.
IMHO, CMake has done some things better than autotools [1], an
On Nov 9, 2010, at 4:15 PM, Pedro Lopez-Cabanillas wrote:
and talking about harmony and friendship, let's see this quote from
a recent thread in fink-devel:http://article.gmane.org/gmane.os.macosx.fink.devel/19876
On Oct 12, 2010, at 8:01 PM, Daniel Johnson wrote:
I tried updating audaciou
On Nov 8, 2010, at 4:06 PM, Pedro Lopez-Cabanillas wrote:
The curses based "ccmake" is fine, too. But I wonder that you are
using a top class graphical system, Mac OSX, and at the same time
you prefer a terminal based tool instead of the modern cmake-gui,
much more in the line of your favor
On Nov 8, 2010, at 4:06 PM, Pedro Lopez-Cabanillas wrote:
The curses based "ccmake" is fine, too. But I wonder that you are
using a top class graphical system, Mac OSX, and at the same time
you prefer a terminal based tool instead of the modern cmake-gui,
much more in the line of your favo
On Nov 8, 2010, at 12:38 PM, Pedro Lopez-Cabanillas wrote:
There are other options whose names are defined in uppercase,
though. Be careful. You shouldn't need to write the variable types
(BOOL). To avoid headaches, use the GUI front-end and the mouse to
check/uncheck nice checkboxes.
$
Hello Pedro
Working with revision 393,
$ cmake .. -DENABLE_PORTAUDIO:BOOL=ON -DENABLE_FRAMEWORK:BOOL=OFF
//
**
Summary:
libsndfile:yes (with ogg vorbis support)
D-Bus: yes
PulseAudio:no
JACK:
On Nov 4, 2010, at 5:23 PM, Pedro Lopez-Cabanillas wrote:
Hi,
Here is a summary of the latest changes I've made in FluidSynth and
QSynth
Subversion repositories.
* CoreAudio driver now uses the HAL output AudioUnit. I hope this
solves the
problems reported by Victor Lazzarini last month
Hello fluidsynth users on OS X
I have provided two fluidsynth packages for the 1.1.3 version.
The first one called "fluidsynth" is the autotools-built version of
fluidsynth which is recommended for end-users. In addition to
coreaudio support, portaudio support will also be compiled into the
On Oct 9, 2010, at 6:33 AM, James Le Cuirot wrote:
On Fri, 8 Oct 2010 19:34:12 +0200
"Pedro Lopez-Cabanillas" wrote:
The autotools build system uses libtool, and these funny numbers are
a consequence of the libtool numbering scheme. The numbers are
absurd, BTW. What means the current version
On Oct 8, 2010, at 5:01 PM, Ebrahim Mayat wrote:
On Oct 8, 2010, at 3:34 PM, David Henningsson wrote:
Good. I've started to prepare the 1.1.3 release, see
https://sourceforge.net/apps/trac/fluidsynth/wiki/ChangeLog1_1_3
Hi David
I would also like to acknowledge the contributio
On Oct 8, 2010, at 3:34 PM, David Henningsson wrote:
On 2010-10-08 20:00, Pedro Lopez-Cabanillas wrote:
On Friday 08 October 2010, David Henningsson wrote:
I get the feeling that trunk is in quite good shape now, with just
low-regression-risc bugfixes since 1.1.2, so perhaps we should
relea
On Oct 8, 2010, at 1:34 PM, Pedro Lopez-Cabanillas wrote:
Then, you shouldn't allow to upgrade packages created with both
build systems.
This is a packaging problem. One solution may be to add an "epoch"
number,
like Debian does sometimes, to the package created using the CMake
build
sys
On Oct 8, 2010, at 2:00 PM, Pedro Lopez-Cabanillas wrote:
All major distributions have adopted the CMake build system in 1.1.2
without
finding obstacles, but I would keep the old one during some more time.
Yes, I agree.
Ebrahim
___
fluid-dev mai
Please find attached the proposed patch.
Regards,
Ebrahim
synth.h.patch
Description: Binary data
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
On Oct 7, 2010, at 4:10 PM, Pedro Lopez-Cabanillas wrote:
On Thursday 07 October 2010, Ebrahim Mayat wrote:
I don't see any problem in removing the comma.
perl -pi -e 's/R = 7,/R = 7/' include/fluidsynth/synth.h
You are proposing a perl one-liner instead of a standard uni
Hello
What are the cmake equivalents of the following configure options:
--disable-static
--docdir
--libdir
--infodir
--datarootdir
--includedir
--mandir
--bindir
and also fluidsynth-specific options like --disable-alsa
Thanks in advance,
E
___
fluid
On Oct 2, 2010, at 1:27 AM, Orcan Ogetbil wrote:
On Tue, Sep 28, 2010 at 2:01 PM, Orcan Ogetbil wrote:
On Tue, Sep 28, 2010 at 4:45 AM, Ebrahim Mayat wrote:
Before I post a bug report on Bugzilla:
1) Is anyone else having the same problem ?
Yes, this issue has been reported on both the LAU
Hello again
In the transition from autotools to cmake on OS X, I came across
version number compatibility issue for the libfluidsynth shared
library..
The names and version numbers of libfluidsynth are:
1. using autotools for the previous version of fluidsynth-1.1.1
/sw/lib/libfluidsynth.
EDT
To: Ebrahim Mayat
Cc: Fink Developers Mailing List
Subject: Fwd: [cvs] dists/10.4/unstable/main/finkinfo/sound
fluidsynth.info, 1.7, 1.8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi. There was an extra comma in an enum field in fluidsynth/synth.h
which caused scummvm (and likely other
On Sep 24, 2010, at 6:16 AM, Victor Lazzarini wrote:
Hi everyone,
I have installed version 1.1.12 and yes, the preset-reset is not
there anymore, thanks. It works fine now.
Glad to hear that!
Except for the coreaudio driver.
Here is the description of the bug:
1. with this command-line
On Sep 23, 2010, at 3:26 PM, victor.lazzar...@nuim.ie wrote:
Regarding the first problem, I have identified in my first e-mail
the API function that uses the
reset-presets parameter. All you need to do is implement an option
for the command-line to
set that parameter. I can suggest the code
On Sep 23, 2010, at 2:16 PM, victor.lazzar...@nuim.ie wrote:
Sorry, but my midi file has plenty of PCs in it. With my own
fluidsynth client (and other
software) it plays as expected. The problem is the reset-presets
parameter in the sfont loading function.
For starters, you could send your
On Sep 23, 2010, at 10:33 AM, Victor Lazzarini wrote:
Hi everyone
there seems to be a couple of bugs with fluidsynth (1.1.1, command-
line program):
1. It resets all channes to prg 1, so when you play a midifile, all
we get is piano from GM soundfonts. I have asked about this here,
but
On Aug 5, 2010, at 1:33 PM, Pedro Lopez-Cabanillas wrote:
Fixed in SVN revision 334.
Pedro
Thanks, works for accurately rendering a couple of MIDI files that I
have.
It was not a problem related to CMake, by the way.
Yes, I had indicated the source of the error (fluid_rtkit.c) in my
Hello
I have the dbus headers installed
-- checking for module 'dbus-1>=1.0.0'
-- found dbus-1, version 1.2.16
...but I still get the following error
[ 97%] Building C object src/CMakeFiles/libfluidsynth.dir/bindings/
fluid_filerenderer.c.o
Linking C shared library libfluidsynth.dylib
On Wed, 2010-03-31 at 10:35 -0700, j...@resonance.org wrote:
> Hello FluidSynth developers and users,
>
> I will be moving FluidSynth services off of the resonance.org domain.
> I wanted to ask if there are any opinions or ideas on options for the
> various hosted components of the FluidSynth
On Fri, 2010-01-22 at 23:11 +0100, Sebastian Biallas wrote:
> Hello,
>
> I'm using fluidsynth to play piano using rosegarden and an old MIDI
> keyboard (technics KN440).
>
> Since fluidsynth 1.0.9 the sound output is way too dynamic. If I press a
> key soft it's barely hearable and if I press it
On Jan 3, 2010, at 10:44 PM, j...@resonance.org wrote:
Quoting Graham Goode :
Hi Guys,
This is not for the 1.1.1 RC release, but perhaps more a question for
1.2 or 2.0...
Will fluidsynth use the LV2 audio plugin standard? (LV2 is a simple
but extensible successor of LADSPA - http://lv2plug.in
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 which alternative you would prefer.
Regards,
Ebrahim
On Nov 18, 2009, at 2:13 AM, David Henningsson wrote:
//
I'm not sure about the fifth (I/O procs) thread, is that something
used internally by libraries we use? What does it do?
My sketchy idea about this is that this thread is kernel-related (at
least on OS X); it is created by the hard
On Tue, 2009-11-17 at 16:57 -0800, j...@resonance.org wrote:
> Hello Ebrahim,
//
>
> It sounds as if you may have multiple audio interfaces? I notice that
> the FluidSynth coreaudio driver doesn't currently have support for
> specifying which audio device to use. Seems a call to
> AudioDev
On Nov 16, 2009, at 12:47 AM, David Henningsson wrote:
While the recent thread safety improvements are much better than the
previous handling (since the previous had unpredictable crashes),
the recent postings, the shadow variable workaround, and the multi-
core support got me thinking. See
Hello again
I just tried 271 and sound driver function has changed as follows:
If Jack is linked during compilation, fluidsynth can be run with jack
as the audio driver but it cannot be run with the coreaudio driver:
$ fluidsynth -a coreaudio ~/sf2/GeneralUser_GS_FluidSynth_v1.43_RC1.sf2
F
On Nov 14, 2009, at 6:03 PM, David Henningsson wrote:
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 re
On Sun, 2009-11-15 at 00:03 +0100, David Henningsson wrote:
> 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 t
On Sat, 2009-11-14 at 23:44 +0100, Pedro Lopez-Cabanillas wrote:
> On Saturday, November 14, 2009, Ebrahim Mayat wrote:
> > Perhaps you could
> > try something more realistic: like Rachmaninoff, Liszt or even Chopin
> > solo pieces, maybe Paganini...or even Keith Eme
Message to be forwarded to LAU.
>
> Asunto: Re: [LAU] Fluidsynth, soundfonts, jack, and latency
> Fecha: Saturday, November 14, 2009
> De: Guru Prasad
> Para: lau
>
> -- Forwarded Message --
>
> Asunto: Re: [LAU] Fluidsynth, soundfonts, jack, and latency
> Fecha: Saturday, N
On Sat, 2009-11-14 at 21:56 +0100, Pedro Lopez-Cabanillas wrote:
> On Saturday, November 14, 2009, Ebrahim Mayat wrote:
> > On Sat, 2009-11-14 at 12:29 +0100, Pedro Lopez-Cabanillas wrote:
> > > -- Forwarded Message --
> > >
> > > Asunto: Re
On Sat, 2009-11-14 at 12:29 +0100, Pedro Lopez-Cabanillas wrote:
> -- Forwarded Message --
>
> Asunto: Re: [LAU] Fluidsynth, soundfonts, jack, and latency
> Fecha: Saturday, November 14, 2009
> De: Guru Prasad
> Para: lau
>
> Hello everyone,
> Finally! Here's a quick update
Hello all
I happened to stumble upon a way to make the new fluidsynth crash.
This is a minor bug which I can live with but I'll report it anyway.
Fluidsynth can be launched and executed to obtain audio output from my
computer's speakers. But when I try to patch the computer's audio
output
On Nov 4, 2009, at 10:53 AM, Felix Krause wrote:
I'm on Snow Leopard 10.6.1.
host-triplet: i386-apple-darwin10.0.0
libtoolize: (GNU libtool) 2.2.6
automake: automake (GNU automake) 1.10
autoconf: autoconf (GNU Autoconf) 2.61
Felix
My working setup:
aclocal (GNU automake)
On Nov 3, 2009, at 10:26 AM, Felix Krause wrote:
Hi all,
I'm trying to compile fluidsynth from svn source on MacOSX.
autogen.sh gives me the following output:
libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DI
On Mon, 2009-10-12 at 13:17 -0700, j...@resonance.org wrote:
> No, FluidSynth doesn't parse .scl directly. What we've added is
> support for SYSEX commands embedded in MIDI data. So you could add
> the proper MTS SYSEX commands into a MIDI file. This is better than
> the pitch bender hack
On Oct 11, 2009, at 12:11 AM, j...@resonance.org wrote:
Its called the MIDI Tuning Standard. There are 2 different forms of
it. The older one doesn't properly support tuning bank #s. They
created a second revision of it to fix that oversight and provide
some additional things (such as o
On Thursday, 27 August, 2009, at 10:51PM, wrote:
>
>Autotools is one of the things that gets blamed sometimes for making
>builds difficult on Windows, which is why I mentioned it. Most users
>building software just want to use some sort of IDE, without having to
>have a Unix like environm
On Aug 26, 2009, at 3:03 PM, j...@resonance.org wrote:
Indeed, the platform maintainers deserve much credit! We should
start by officially appointing the positions.
Ebrahim Mayat has been from the beginning the OS X maintainer.
As for Windows, there have been contributions from many
On Aug 3, 2009, at 12:00 PM, Felix Krause wrote:
Hi all,
I want to compile a universal binary of the FluidSynth library on my
Intel Mac. To get a PPC binary, I tried
./configure --host=powerpc-apple-darwin7.0.0
but it still compiled an Intel version. How do I make it compile a
PPC versi
On Wed, 2009-07-08 at 16:34 -0700, j...@resonance.org wrote:
> I agree, especially since a given Reverb value is implementation
> dependent as to how it affects the sound. I doubt many people design
> MIDI songs that rely on the default reverb being 40. Depending on how
> the FluidSynth Re
On Wed, 2009-07-08 at 11:53 -0500, S. Christian Collins wrote:
> SoundFont synths that I have used over the years (such as the EMU10K1
> synths) seem to put the default reverb at 0. Personally, I think this
> is preferred. I think reverb (like chorus) is one of those settings
> that should be lef
On Tue, 2009-07-07 at 16:41 -0400, Randy S Miller wrote:
> Sir,
>
> I have been attempting to install FluidSynth on my Mac. When I
> attempt to use fink to install fluidsynth, I get the message "Failed:
> no package found for specification 'fluidsynth'." I have not been
> able to find flui
be installed by simply invoking :
"fink install qsynth"
Ebrahim Mayat
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
On Wed, 2009-06-17 at 06:16 +0200, laurent schwartz wrote:
> Hi,
>
> Can we define or set one jack audio channel output per MIDI instrument
> used ?
>
> It could allow me to apply a custom effect on each instrument.
>
> Is there a plan to develop this functionality ?
In addition to Pedro's sugg
peak meters refresh rate.
- MIDI and audio device names are now user selectable options through
respective drop-down lists on each engine setup dialog.
- New knob style: Skulpture.
Further details can be found in the README document packaged with the
qsynth application.
Cheers && En
On May 26, 2009, at 3:04 PM, Graham Goode wrote:
Hi Ebrahim,
He has a Macbook Pro 2.4 Ghz Intel core duo Running OS X 10.5.7 with
4 GB 667 MHz DDR 2 SDRAM. Do you need any more info?
Thanks!
GrahamG
Graham
I am sending off-list, the tarball containing the universal binary of
fluidsynth.
On May 26, 2009, at 2:13 PM, Graham Goode wrote:
Hi,
I don't use OS X (I use Windows and Linux), but I have a friend who
wants to use fluidsynth on his Mac. Does anyone have a package for the
Mac or could someone create a zip of their build so that I could send
it to him? Preferably with Qsynth
On May 3, 2009, at 2:29 PM, Felix Krause wrote:
Hi,
I tested the current unstable fink package of fluidsynth 1.0.9 and
found both the command line tool and the library compiling and
working properly on MacOSX 10.5.6 Intel. I'm looking forward to a
stable release.
Sure.
But I also have to
Felix
The following link should be of help in the meantime.
http://www.finkproject.org/faq/usage-fink.php?phpLang=en#unstable
HTH.
E
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
On Apr 20, 2009, at 1:07 AM, Josh Green wrote:
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
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
compiling from source.
On 64studio 64bit:
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 with this 'studio file' makes rosegarden work seamlessly with
fluidsynt
Lopez-Cabanillas for implementing support for the OS X-native CoreMIDI
driver in fluidsynth.
Details regarding installation and program execution will be outlined
in the README-OSX document of the next release.
Ebrahim Mayat
___
fluid-dev
On Feb 28, 2009, at 12:20 PM, 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 with your help.
On Sunday, February 22, 2009, at 04:11AM, "Butrus Damaskus"
wrote:
>Hi!
>
>Could someone, please, explain to me, what is the "tunings" good for? I
>Greped the source and was a little bit confused of what it is aimed for.
>
>(My Idea was to implement some other tuning systems than the "Equal
>te
List readers
I forgot that LADSPA headers are required for compiling the DSSI host
which in turn is required for the dssi-vst plugin wrapper for VST
effects. So LADSPA is not exactly disposable (no pun intended).
E
___
fluid-dev mailing list
fluid-de
On Thu, 2009-01-29 at 16:32 +0100, Bernat Arlandis i Mañó wrote:
> It scales pretty well, the reverb/chorus processing time multiplies by
> the number of channels, but still acceptable. With all 16 channels I got
> around 70% CPU load in my tests with an AMD64 2Ghz. There's some room
> for impr
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.
>
Excellent idea. I'm all for it. Then it would also be easy to prepare a
midnam file (for the General Users
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
samples of two different soundfonts from the two MIDI ports.
Also worth noting, is that I could also use the CoreMIDI driver in
SWAMI after selec
On Jan 27, 2009, at 8:36 PM, Josh Green wrote:
I just successfully registered an account and was able to at least
preview changes in the ticket system (didn't actually submit
anything).
What is the issue in particular? Any error messages?
I just logged in successfully and ticket #18 is no
On Jan 27, 2009, at 3:18 PM, Pedro Lopez-Cabanillas wrote:
Not sure what this means. QSynth is not yet ready to understand the
options
for the new coremidi driver. It knows the Jack audio driver, though.
Jack
requires a different client name for each instance, QSynth being
aware of
this and
1 - 100 of 146 matches
Mail list logo
