Re: [fluid-dev] fluid-dev Digest, Vol 211, Issue 6

[Ruben Gjertsen]

Thank you, this is useful information!

Yes, I have been using the third-party fluidsynth for Max (cycling74). The 
tuning-keys command has been working until recently, and I now know that this 
was implemented by Ircam.
If it’s straight forward to do, I’ll put on the wishlist that you include the 
Ircam implementation of tuning-keys in future versions.
Now I should soon leave this list and find a way to sort this out myself.

I did, by the way, also try to contact you a year ago about this, by writing to 
fluid-dev-owner@nongnu.org .
Element Green responded that he is not involved in fluidsynth any more. The 
same thing happened when I tired again this year. So if you update the owner, 
it may be easier to contact you in the future.

Best
Ruben Gjertsen



> 23. feb. 2021 kl. 18.00 skrev fluid-dev-request@nongnu.org:
> 
> Send fluid-dev mailing list submissions to
>       fluid-dev@nongnu.org
> 
> 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
>       fluid-dev-request@nongnu.org
> 
> You can reach the person managing the list at
>       fluid-dev-owner@nongnu.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of fluid-dev digest..."
> 
> 
> Today's Topics:
> 
>   1. Tuning-keys in recent version of fluidsynth (Ruben Gjertsen)
>   2. Re: Tuning-keys in recent version of fluidsynth (Marcus Weseloh)
>   3. Re: Tuning-keys in recent version of fluidsynth (Tom M.)
>   4. Re: Tuning-keys in recent version of fluidsynth (Marcus Weseloh)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 23 Feb 2021 13:53:00 +0100
> From: Ruben Gjertsen <rubengjertsen@gmail.com>
> To: fluid-dev@nongnu.org
> Subject: [fluid-dev] Tuning-keys in recent version of fluidsynth
> Message-ID: <4442E995-DB80-459F-9221-AFB1C4016732@gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello,
> 
> I tried to write an e-mail to:
> fluid-dev-owner@nongnu.org <mailto:fluid-dev-owner@nongnu.org>
> This did not reach the reach person, so I’m trying again, to this list:
> 
> Hello,
> 
> I’m have been using fluidsynth a indirectly, through externals for Max on 
> Mac. Fluidsynth have been very important for 2 apps for experimenting with 
> microtonal tuning:
> https://sourceforge.net/projects/microtonalorgan/ 
> <https://sourceforge.net/projects/microtonalorgan/>
> https://sourceforge.net/projects/r-udp-player/ 
> <https://sourceforge.net/projects/r-udp-player/>
> 
> But, in the latest 64-bit Max external, the command 'tuning-keys' has stopped 
> working as before. This was to me a very important feature, as you may define 
> a non-standard tuning for every single note on the keyboard, and even 
> continous interpolations between tuning systems, as a stepwise glissando. 
> This effect is more complex than using pitchbend on all keys at once in the 
> same direction, and I have based pieces on it.
> 
> Did you remove this function, and could you consider bringing it back? This 
> could then eventually spread to a new Max external which allows me to 
> continue using my instrument on new computers. As I have nothing to do with 
> the development of the Max external, I do not have insights in where the 
> changes have happened.
> 
> And if 'tuning-keys' is still available, but in a different syntax, I would 
> be interested in seeing some documentation. Then perhaps minor adjustments 
> could fix my instruments.
> 
> Best,
> Ruben Gjertsen
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://lists.nongnu.org/archive/html/fluid-dev/attachments/20210223/6b0fe45f/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 23 Feb 2021 14:18:52 +0100
> From: Marcus Weseloh <marcus@weseloh.cc>
> To: FluidSynth mailing list <fluid-dev@nongnu.org>
> Subject: Re: [fluid-dev] Tuning-keys in recent version of fluidsynth
> Message-ID:
>       <CAGNoLaO1iAVwdAyF6VpZwsKNzLBFOT17Q9fP3iKL5UbejEztmg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> Hi Ruben,
> 
> please give us a little more information about the problem, otherwise
> it is difficult for us to help you solve it.
> 
> What exactly does it mean that it has "stopped working"?
> Do you have any error messages we could look at?
> Which version of FluidSynth works and which doesn't?
> And what exactly is a "Max external" and where did you get it from?
> 
> Cheers
> Marcus
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 23 Feb 2021 16:31:09 +0100
> From: "Tom M." <tom.mbrt@googlemail.com>
> To: FluidSynth mailing list <fluid-dev@nongnu.org>, Marcus Weseloh
>       <marcus@weseloh.cc>
> Cc: rubengjertsen@gmail.com
> Subject: Re: [fluid-dev] Tuning-keys in recent version of fluidsynth
> Message-ID:
>       <CADHnbahfnZnW9R8+RRwwSpGL_n3ddpRYibdMOEWn=BZr65TOrA@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Ruben is probably referring to fluidmax a binding for Max/MSP that we used
> to ship with the source code up until 1.1.11. I removed that binding from
> the codebase in June 2018 because
> 
> * it hasn't received any code changes since 2009,
> * it used functions from private fluidsynth headers, and
> * I really don't think it is fluidsynth's job to maintain bindings to
> various applications out there.
> 
> The fact that now, more than 2.5 years later someone finally complains,
> confirms to me that this binding isn't cared about much.
> 
> My best guess is that Ruben kept using fluidsynth 1.x, now he upgraded to
> 2.x and, expectedly, it doesn't work anymore.
> 
> If somebody is willing to maintain this binding, just grep the source code
> from back then, adopt it to fluidsynth's current API, get rid of all
> private headers, internal functions, etc., and put that binding in some
> repository ideally with CI pipelines for Win + Mac.
> 
> P.S.: That 'tuning-keys' command has always been commented out, because
> it's lacking an implementation. I don't see how this could have ever
> worked:
> https://github.com/FluidSynth/fluidsynth/blob/v1.1.11/bindings/fluidmax/fluidmax.c#L1619
> 
> Tom
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://lists.nongnu.org/archive/html/fluid-dev/attachments/20210223/6eaf4a8a/attachment.html>
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 23 Feb 2021 17:57:21 +0100
> From: Marcus Weseloh <marcus@weseloh.cc>
> To: "Tom M." <tom.mbrt@googlemail.com>
> Cc: FluidSynth mailing list <fluid-dev@nongnu.org>,
>       rubengjertsen@gmail.com
> Subject: Re: [fluid-dev] Tuning-keys in recent version of fluidsynth
> Message-ID:
>       <CAGNoLaMJGCVzjMbXymmYVN_oRA2em8fzTcqq3en3V4gWAZQagw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> I see. thanks.
> 
> There seems to be a fluidsynth MAX/MSP plugin that is a little newer
> and with a working tuning-keys command:
> https://forge.ircam.fr/p/fluidsynth4max/source/tree/master/src/fluidmax.c
> 
> So if there is somebody willing to maintain that binding, that would
> maybe be a better starting point.
> 
> Cheers
> Marcus
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> fluid-dev mailing list
> fluid-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fluid-dev
> 
> 
> ------------------------------
> 
> End of fluid-dev Digest, Vol 211, Issue 6
> *****************************************