Re: [fluid-dev] New branch

2009-01-29 Thread Josh Green
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

[fluid-dev] New branch

2009-01-29 Thread Bernat Arlandis i Mañó
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 in 1.0.9 (or later versions) in the stable branch, since we're near a new stabl

Re: [fluid-dev] New development

2009-01-29 Thread Josh Green
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

Re: [fluid-dev] New development

2009-01-29 Thread Josh Green
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 > > > already succesfully tested it on Linux.

Re: [fluid-dev] New development

2009-01-29 Thread Pedro Lopez-Cabanillas
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 > > already succesfully tested it on Linux. > > > > I have a problem with ASIO, though. First, I don't like the license

Re: [fluid-dev] New development

2009-01-29 Thread Pedro Lopez-Cabanillas
Hi, > Hi Pedro, > > I can understand your dislike of the Steinberg license terms! ASIO is, > however, the best general low latency audio for Windows users. > > Would it be possible for you to create/update a > How-To-Build-Fluidsynth / Qsynth in windows using mingw with the ASIO > information (onc

Re: [fluid-dev] New development

2009-01-29 Thread Josh Green
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:

Re: [fluid-dev] New development

2009-01-29 Thread Pedro Lopez-Cabanillas
Josh Green wrote: > 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.

Re: [fluid-dev] New development

2009-01-29 Thread Josh Green
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

LADSPA and LV2 was "Re: [fluid-dev] One output per channel"

2009-01-29 Thread Ebrahim Mayat
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

Re: [fluid-dev] One output per channel

2009-01-29 Thread Ebrahim Mayat
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

Re: [fluid-dev] One output per channel

2009-01-29 Thread Bernat Arlandis i Mañó
Ebrahim Mayat escrigué: Also, I've fixed the reverb and chorus effects in multichannel mode so they're applied to every channel, instead of mixing the effects separately. This would be a powerful feature allowing for inserts directly from fluidsynth into a live mix. Would this entail a sig

Re: [fluid-dev] invalid instrument/drum selection

2009-01-29 Thread jimmy
Hi Josh, Thinking some more about hardware and software designs, I believe the safest thing to do when encounter an invalid request is to ignore it, not blindly follow the request/instruction that will cause the system to misbehave. I think FS misbehaves in this case, although it is just my o

Re: [fluid-dev] One output per channel

2009-01-29 Thread Ebrahim Mayat
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

Re: [fluid-dev] New development

2009-01-29 Thread ggoode.sa
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), but if you email me your build I'm willing to try it in WinXP. Alternatively one could test this with the WineASIO driver and WINE (which then patches into JACK).

Re: [fluid-dev] New development

2009-01-29 Thread Josh Green
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

Re: [fluid-dev] invalid instrument/drum selection

2009-01-29 Thread jimmy
> 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