[Csnd-dev] Question about fluidLoad

[Csnd-dev] Question about fluidLoad

Date	2021-11-07 19:59
From	Eric Nassen
Subject	[Csnd-dev] Question about fluidLoad
	The manual states : “Invoke fluidLoad in the orchestra header, any number of times. The same SoundFont may be invoked to assign programs to MIDI channels any number of times; the SoundFont is only loaded the first time.” The problem is that every time I recompile (csoundCompileCsd() – api), the soundfont is reloaded in memory. So, if a soundfont is p.e. 100MB, my RAM gets quickly full… Any idea how to prevent this? Br, Eric

Date	2021-11-07 20:31
From	Tarmo Johannes
Subject	Re: [Csnd-dev] Question about fluidLoad
	Hi! I have had the same experience via CsoundQt, wher Csound is is used as a lilbrary via API. I asked in the forum once and seems that there is something wrong with freeing the memory in fluid opcodes. Unfortunately I don't know how to overcome this... tarmo Kontakt Eric Nassen (<eric.nassen3@telenet.be>) kirjutas kuupäeval P, 7. november 2021 kell 21:59: The manual states : “Invoke fluidLoad in the orchestra header, any number of times. The same SoundFont may be invoked to assign programs to MIDI channels any number of times; the SoundFont is only loaded the first time.” The problem is that every time I recompile (csoundCompileCsd() – api), the soundfont is reloaded in memory. So, if a soundfont is p.e. 100MB, my RAM gets quickly full… Any idea how to prevent this? Br, Eric

Date	2021-11-07 20:42
From	john
Subject	Re: [Csnd-dev] Question about fluidLoad
	That part of te manual predates compilation on the fly so it is possible that the memory of already loaded soundfont files gets reinitialised. Or tere is a bug te te checks to see if the file alrwady available. knowing wich is the problem would ep. I also notice tat from 6.17 fkuidsynth is a plugin and ma not esupported -- it isalsio in C++. ==Jon ff On Sun, 7 Nov 2021, Eric Nassen wrote: > > The manual states : > > > > “Invoke fluidLoad in the orchestra header, any number of times. The same > SoundFont may be invoked to assign programs to MIDI channels any number of > times; the SoundFont is only loaded the first time.” > > > > The problem is that every time I recompile (csoundCompileCsd() – api), the > soundfont is reloaded in memory. > > So, if a soundfont is p.e. 100MB, my RAM gets quickly full… > > > > Any idea how to prevent this? > > > > Br, > > Eric > > > > > > > > > > >

Date	2021-11-08 06:02
From	Eric Nassen
Subject	Re: [Csnd-dev] Question about fluidLoad
	Memory of loaded soundfonts isn’t freed when recompiling with the API (csoundCompileCSD()) Was that your question? Van: john Verzonden: zondag 7 november 2021 21:43 Aan: CSOUND-DEV@LISTSERV.HEANET.IE Onderwerp: Re: [Csnd-dev] Question about fluidLoad That part of te manual predates compilation on the fly so it is possible that the memory of already loaded soundfont files gets reinitialised. Or tere is a bug te te checks to see if the file alrwady available. knowing wich is the problem would ep. I also notice tat from 6.17 fkuidsynth is a plugin and ma not esupported -- it isalsio in C++. ==Jon ff On Sun, 7 Nov 2021, Eric Nassen wrote: > > The manual states : > > > > “Invoke fluidLoad in the orchestra header, any number of times. The same > SoundFont may be invoked to assign programs to MIDI channels any number of > times; the SoundFont is only loaded the first time.” > > > > The problem is that every time I recompile (csoundCompileCsd() – api), the > soundfont is reloaded in memory. > > So, if a soundfont is p.e. 100MB, my RAM gets quickly full… > > > > Any idea how to prevent this? > > > > Br, > > Eric > > > > > > > > > > >

Date	2021-11-08 09:50
From	Victor Lazzarini
Subject	Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] Question about fluidLoad
	yes, fluidsynth is a plugin and any bug reports need to be put to the plugin repository. No maintainers means this might not be addressed very quickly. ======================== Prof. Victor Lazzarini Maynooth University Ireland > On 7 Nov 2021, at 20:42, john wrote: > > Warning > > This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe. > > That part of te manual predates compilation on the fly so it is possible > that the memory of already loaded soundfont files gets reinitialised. Or > tere is a bug te te checks to see if the file alrwady available. knowing > wich is the problem would ep. > > I also notice tat from 6.17 fkuidsynth is a plugin and ma not esupported > -- it isalsio in C++. > > ==Jon ff > > On Sun, 7 Nov 2021, Eric Nassen wrote: > >> >> The manual states : >> >> >> >> “Invoke fluidLoad in the orchestra header, any number of times. The same >> SoundFont may be invoked to assign programs to MIDI channels any number of >> times; the SoundFont is only loaded the first time.” >> >> >> >> The problem is that every time I recompile (csoundCompileCsd() – api), the >> soundfont is reloaded in memory. >> >> So, if a soundfont is p.e. 100MB, my RAM gets quickly full… >> >> >> >> Any idea how to prevent this? >> >> >> >> Br, >> >> Eric >> >> >> >> >> >> >> >> >> >> >>

Date	2021-11-09 06:20
From	Eric Nassen
Subject	Re: [Csnd-dev] Question about fluidLoad
	Hi Tarmo, You can use a dummy instrument just to load the fluid engine / soundfont and invoke this instrument only once in your Host. Br, Eric Van: Tarmo Johannes Verzonden: zondag 7 november 2021 21:31 Aan: CSOUND-DEV@LISTSERV.HEANET.IE Onderwerp: Re: [Csnd-dev] Question about fluidLoad Hi! I have had the same experience via CsoundQt, wher Csound is is used as a lilbrary via API. I asked in the forum once and seems that there is something wrong with freeing the memory in fluid opcodes. Unfortunately I don't know how to overcome this... tarmo Kontakt Eric Nassen (<eric.nassen3@telenet.be>) kirjutas kuupäeval P, 7. november 2021 kell 21:59: The manual states : “Invoke fluidLoad in the orchestra header, any number of times. The same SoundFont may be invoked to assign programs to MIDI channels any number of times; the SoundFont is only loaded the first time.” The problem is that every time I recompile (csoundCompileCsd() – api), the soundfont is reloaded in memory. So, if a soundfont is p.e. 100MB, my RAM gets quickly full… Any idea how to prevent this? Br, Eric