fluid-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] rendering midi to pcm in memory (Tom M.)


From: Roberto Panerai Velloso
Subject: Re: [fluid-dev] rendering midi to pcm in memory (Tom M.)
Date: Fri, 14 Feb 2020 14:35:43 -0300

Hi,

I have this example in my fork of fluidsynth (I haven't changed the original API):

https://github.com/rpvelloso/fluidsynth#example-converts-midi-to-16-bit-stereo-pcm 

I'm rendering PCM in memory and writing to disk. You can change it to render entirely in memory or whatever you need. 


Em sex., 14 de fev. de 2020 às 14:00, <address@hidden> escreveu:
Send fluid-dev mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.nongnu.org/mailman/listinfo/fluid-dev
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of fluid-dev digest..."


Today's Topics:

   1. No reverb, no chorus with 2.1.0 (midi-pascal)
   2. Re: No reverb, no chorus with 2.1.0 (Ceresa Jean-Jacques)
   3. Re: rendering midi to pcm in memory (Tom M.)


----------------------------------------------------------------------

Message: 1
Date: Thu, 13 Feb 2020 16:29:30 -0500
From: midi-pascal <address@hidden>
To: address@hidden
Subject: [fluid-dev] No reverb, no chorus with 2.1.0
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi,

The reverb and chorus do not work at all using libfluidsynth release
2.1.0, either in my app or in QSynth.

However they work perfectly using the release 2.0.2 (Same code, just
re-linked the apps).

Am I missing something?

I was happy to see there are new reverb and chorus in 2.1.0, but it
looks like they do not work.

The fluid_synth_set_reverb*() API calls return FLUID_OK

I followed the API calls with the debugger, and the functions do not
exit prematurely.

I am on Ubuntu 18.04 LTS, if this can be relevant.

Did I hit a bug?

Regards

Pascal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nongnu.org/archive/html/fluid-dev/attachments/20200213/9274f944/attachment.html>

------------------------------

Message: 2
Date: Fri, 14 Feb 2020 12:34:49 +0100 (CET)
From: Ceresa Jean-Jacques <address@hidden>
To: FluidSynth mailing list <address@hidden>
Subject: Re: [fluid-dev] No reverb, no chorus with 2.1.0
Message-ID: <1907004584.3876.1581680089864.JavaMail.www@wwinf1m08>
Content-Type: text/plain; charset="utf-8"

Hi, Pascal

>The reverb and chorus do not work at all using libfluidsynth release 2.1.0, either in my app or in QSynth.

Here the reverb and chorus work using the fluisynth application console. Did you try this application before any other one ?

jjc.

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nongnu.org/archive/html/fluid-dev/attachments/20200214/9157ea32/attachment.html>

------------------------------

Message: 3
Date: Fri, 14 Feb 2020 14:11:16 +0100
From: "Tom M." <address@hidden>
To: address@hidden
Cc: FluidSynth mailing list <address@hidden>
Subject: Re: [fluid-dev] rendering midi to pcm in memory
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="UTF-8"

The best starting point for you would be to use the fast file renderer example:

http://www.fluidsynth.org/api/index.html#FileRenderer

However, instead of using the file renderer's
fluid_file_renderer_process_block(), you would directly call a
rendering function of the synth, as mentioned in this small section:

http://www.fluidsynth.org/api/index.html#UsingSynth


Tom



------------------------------

Subject: Digest Footer

_______________________________________________
fluid-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fluid-dev


------------------------------

End of fluid-dev Digest, Vol 199, Issue 11
******************************************

reply via email to

[Prev in Thread] Current Thread [Next in Thread]