Hi Ben and others RPi2 developper
in the aim to compile FluidSynth v 1.1.6 from git repository
1) I have prepared a RPi2 jessie in the aim to compile FluidSynth v
1.1.6 using the compiler from the jessie image.
2) I have done the same thing on another machine running Debian.
3) I have done the
Hi all.
I loaded the changed file, and rebuilt.
The problem is fixed. I tried all presets in legatomode 3 and cc 68 127,
both with and without chorus and reverb. The CPU usage climbed to 30+%
while playing (with reverb/chorus) then fell back to 4% when I stopped
playing.
Thanks
Ben
On 07/
Hi Ben,
Thanks a lot for your contribution you have done a good job.
After looking the result of the compiler you have posted on your site, I
have found
some differences that strike me.
You will find below an new attached file: fluid_synth_mono.c.
Please may you:
1) substitute the one you hav
Hi all.
When I said "are there any tests...?" I didn't expect so many!
Nevertheless, I have completed the tests, and I have put all the
resulting files in:
http://gonzos.net/fluid-dev
Also in that directory are the soundfont, and other files I have
referenced in this discussion.
cmakelog.t
Hi Ben,
>Is there any test I could run on the Pi
While i'm preparing my RPi2, could you please:
Describe and localize when you see excess CPU usage. followings the
tests below:
0)Building steps:
0.1) Which options did you choose at cmake time (please send the summary
log or put it to you
Hello Element,
Thanks, for your memory and useful tips and link.
Best regards
jjc
Le 05/07/2016 20:55, Element Green a écrit :
Hello,
I'm not sure if it could be the issue or not. But I remember a long
while back (many years) FluidSynth used to have issues with denormal
numbers causing exc
Hi all.
Is there any test I could run on the Pi that would help you analyse the
problem?
Ben
On 06/07/16 04:55, Element Green wrote:
Hello,
I'm not sure if it could be the issue or not. But I remember a long
while back (many years) FluidSynth used to have issues with denormal
numbers cau
Hello,
I'm not sure if it could be the issue or not. But I remember a long while
back (many years) FluidSynth used to have issues with denormal numbers
causing excessive CPU usage. That would be floating point numbers which
are very small, but not 0. I don't know if ARM processors deal with
den
Hi Ben,
On Windows, using your soundfont (gonzos-20160702.sf2), in mono mode i
haven't expererienced absolutely no cpu excess usage, on alls 6 presets.
I have look inside the preset. Each preset make use of 2 simulateneous
voices maximum. So this is a very low CPU usage soundfont.
Normally on a
Hi Ben and RL Horn,
Thanks to R.L Horn to adapt the polymono patch the right way.
I am sorry for the wasted time. I am reading the patch coming from
http://lists.nongnu.org/archive/html/fluid-dev/2016-07/msg00011.html
to understand the right way:
What i understand is
assuming,
./fluidsynth-1.1.
Hi
I downloaded the git snapshot, used the patch from Mr(?) Horn
(thankyou), and re-complied.
I'm still experiencing the CPU runaway. It happens a) if I put the
channel I'm using into MONO or b) if I use cc ch 68 127 (legato on). It
doesn't matter which setlegatomode I am using for the chan
On Sat, 2 Jul 2016, Ben Gonzales wrote:
patch < fluid_polymono-0001.patch
This prompted me for each file to patch, and I typed in the path to each file
I don't know how Jean-Jacques generated his patch, but the diff should be
against a complete source tree so this isn't necessary. I've combi
Hi.
I have now successfully re-compiled FluidSynth with the patches. It
works, but there is a problem. First, I will note the process needed to
re-compile:
Patching:
I put the patch file in the src directory
I ran:
patch < fluid_polymono-0001.patch
Hi,
Theses 2 new files have be forgotten: fluid_synth_mono.c,
fluid_synth_polymono.c.
Theses are parts of the complete poylymono-patch.
For the 2 news file (fluid_synth_mono.c, fluid_synth_polymono.c) , i
assume that it sufficient to put them in
the initial source directory fluid_synth-1.1.6/
Pardonnez moi, je devrais avoir expliqué (high-school French)
I did the patch successfully (I think) on all files except the synth.h
where I got the error:
"Invalid cross-device link "
I don't know what it means.
Ben
On 01/07/16 19:49, jean-jacques.ceresa wrote:
>Tried that,
Sorry, as you d
OK, I fixed the error below, I then ran cmake and make, and got an error.
See the full make log on:
http://gonzos.net/ewi/makelog.txt
Suggestions please...
Ben
On 01/07/16 20:08, Ben Gonzales wrote:
Pardonnez moi, je devrais avoir expliqué (high-school French)
I did the patch successfully (
>Tried that,
Sorry, as you don't explain what you are trying i can't understand ?
jjc
Le 01/07/2016 10:30, Ben Gonzales a écrit :
Aah... found it
Tried that, but got this:
../include/fluidsynth/synth.h: Invalid cross-device link
Help...
Ben
On 01/07/16 17:35, jean-jacques.ceresa wrote:
Hi
On 01/07/16 18:48, jean-jacques.ceresa wrote:
Hi, Ben
>The implication of this is that I could put the synth into mode 3 and
turn legato on for all my playing.
As legato mode 0 is more "percussive" than legato mode 3, so it is
probably suited to string instrument played in "picking manner".
Hi, Ben
>The implication of this is that I could put the synth into mode 3 and
turn legato on for all my playing.
As legato mode 0 is more "percussive" than legato mode 3, so it is
probably suited to string instrument played in "picking manner".
What does the action "turn legato on". Is it a se
Aah... found it
Tried that, but got this:
../include/fluidsynth/synth.h: Invalid cross-device link
Help...
Ben
On 01/07/16 17:35, jean-jacques.ceresa wrote:
Hi,
>Hmmm... I can't find the synth.h file (the last one actioned in the
patch file). I patched the rest of them OK.
This is the ma
Hi,
>Hmmm... I can't find the synth.h file (the last one actioned in the
patch file). I patched the rest of them OK.
This is the main header file for API in the following path:
fluidsynth-1.1.6/include/fluidsynth.
If anyone want to write an application using fluidsynth library, this
file is t
Hmmm... I can't find the synth.h file (the last one actioned in the
patch file). I patched the rest of them OK.
Ben
>> Hi, Ben
>> 1)After a quick search on the Web, the command to apply a patch is
>> simply 'patch'.
>> You need to apply this command on each original source file concerned
>> (th
Hi Jean-Jacques
Thanks for that comprehensive answer. I was going to ask you for those
instructions on how to use it - you beat me to it.
I have a Akai Professional EWI-USB. It is the simplest and cheapest of
the Akai models, and doesn't have some of the more sophisticated
functions of the 4
Hi Ben,
Apart grammar and others spelling errors there are 2 typos error in my last
post.
1) Please replace"Mode 0 is perceived less legato then mode 0" by "Mode 0 is
perceived less legato then mode 3"
2) Please replace "channel 5 to 16 (11 channels)" by "channel 5 to 15 (11
channels).
jjc
Hi Ben,
>the legato commands. For a EWI, I think legato should be on all the
time if you are playing wind instruments. If you want to imitate a
guitar, then probably you would want it off. Correct?
Well, it is necessary to be not confused by the terms.
>For a EWI, I think legato should be o
Hi Jean-Jacques.
Thanks for that info. I will try it.
Re:the legato commands. For a EWI, I think legato should be on all the
time if you are playing wind instruments. If you want to imitate a
guitar, then probably you would want it off. Correct?
Ben
On 29/06/16 22:53, jean-jacques.ceresa w
Hi, Ben
1)After a quick search on the Web, the command to apply a patch is
simply 'patch'.
You need to apply this command on each original source file concerned
(the list is given in the pdf).
2)For the 2 news file (fluid_synth_mono.c, fluid_synth_polymono.c) , i
assume that it sufficient to
Hi Ben
A) The protocol principle.
As far i know, the development protocol is straightforward.
- 1) Anyone can propose a "patch". A patch is the result of diff between
the original source file(s) and the new modified file(s).
- 2) Than this patch is posted to sourceforge by opening a ticket.
At
Could someone provide instructions re how to load the patch please? I've
compiled before, but not installed patches. I'd like to try this with my
EWI and RPi2 running Jessie.
Ben
On 25/06/16 19:31, Ben Gonzales wrote:
Hi Jean-Jacques.
I haven't participated in this sort of development before
Hi Jean-Jacques.
I haven't participated in this sort of development before, so I don't
know the protocols. I re-read a lot of the PDF and I think there are
some errors/typos. How are they normally handled? Feedback on the forum?
Private e-mail?
One item immediately: In section 3.1.3, "Playin
Hi Ben
>I've read the pdf doc and understand a lot of it, but I don't understand the
>need for the "base" channels.
1)"Basic channels" is a MIDI specification.In short this allows to split the
whole set of synthesizer channels in distinct MIDI channels groups.
Each group is composed of continus
Hi Jean-Jacques.
I've read the pdf doc and understand a lot of it, but I don't understand
the need for the "base" channels. Does it mean you need less cpu to run
Fluidsynth?
The legato effect looks really useful. How do I test this patch?
Download the latest git and re-compile? Add the patch
Hi,
A patch to add poly/mono functionality to FluidSynth has been posted.
https://sourceforge.net/p/fluidsynth/tickets/160/.
This is the result of a thread [Help about EWI behavior] 30 Apr 2015.
http://lists.nongnu.org/archive/html/fluid-dev/2015-04/msg00011.html
At this time, Louis B. followed
33 matches
Mail list logo
