Re: [fluid-dev] Determining what's wrong with a soundfont

2021-04-08 Thread Mark Raynsford via fluid-dev
noisetype, then you already > had the right idea about two years ago ;-) > https://github.com/io7m/jnoisetype/issues/4 Doh! Thank you! It has been about two years since I created a font, and I'd forgotten this bug existed. Time to fix that one... -- Mark Raynsford | https://www.io7

[fluid-dev] Determining what's wrong with a soundfont

2021-04-07 Thread Mark Raynsford via fluid-dev
ate what the actual problem is. Is there some way to get it to tell me what I've done wrong? Editors such as Polyphone seem to accept the font without issue, but then I don't know if they're correct in doing so! -- Mark Raynsford | https://www.io7m.com pgp4ycyhjas

Re: [fluid-dev] Pitch bend range/pitch wheel sensitivity?

2019-03-13 Thread Mark Raynsford
e amount in order to get +- 12 semitones in Fluidsynth. I'm assuming this is due to the full size of the range being 24 semitones, minus two at both ends of the range. -- Mark Raynsford | http://www.io7m.com pgpwHWy9O_val.pgp Description: OpenPGP digital signature

[fluid-dev] Pitch bend range/pitch wheel sensitivity?

2019-03-12 Thread Mark Raynsford
he spec is somewhat less than helpful on this point. -- Mark Raynsford | http://www.io7m.com pgp9BPVm8naeL.pgp Description: OpenPGP digital signature ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Slightly OT: Parsing SF2; duplicate pbag entries?

2019-02-24 Thread Mark Raynsford
ignore them. It uses them internally to determine numbers of records and the like. It's just that the programmer using the parser doesn't see the terminal record; they just receive a (possibly empty) list of the available non-terminal records. -- Mark Raynsford | http://www.io7m.com

Re: [fluid-dev] Slightly OT: Parsing SF2; duplicate pbag entries?

2019-02-24 Thread Mark Raynsford
t makes it clear that implementations should do this though... What am I missing? -- Mark Raynsford | http://www.io7m.com pgp5MyjQpagyb.pgp Description: OpenPGP digital signature ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Slightly OT: Parsing SF2; duplicate pbag entries?

2019-02-23 Thread Mark Raynsford
On 2019-02-22T21:29:05 + Mark Raynsford wrote: > > Thanks, this helps a lot. I see what it means now... wGenNdx points to > the first index (in the same style as PBAG) and I'm actually supposed > to parse n values starting at that index. The way I was interpreting it >

Re: [fluid-dev] Slightly OT: Parsing SF2; duplicate pbag entries?

2019-02-22 Thread Mark Raynsford
In other words, for each PBAG value, I look up the corresponding PGEN value. With the arrangement of PBAG values I showed in basic.sf2, that would obviously mean that I'd miss the all-important Instrument PGEN! -- Mark Raynsford | http://www.io7m.com pgp_sN6gb00z_.pgp Description: Open

[fluid-dev] Slightly OT: Parsing SF2; duplicate pbag entries?

2019-02-22 Thread Mark Raynsford
ot pgen[0] and pgen[1] as I would expect. I've inspected the data in a hex editor and those duplicate entries are definitely present. Multiple SF2 implementations (including Fluidsynth) parse and play them correctly. How do I interpret those presets such that I can correctly link them to the instr

Re: [fluid-dev] Override envelope release time?

2018-04-11 Thread Mark Raynsford
4.html > > @Marcus + JJC: Is this use-case worth to keep absolute generators? Or is > there any other way of achieving what Mark is asking for? -- Mark Raynsford | http://www.io7m.com pgp2kAFWRiovq.pgp Description: OpenPGP digital signature ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

[fluid-dev] Override envelope release time?

2018-04-11 Thread Mark Raynsford
Hello! I'm using the standard FluidR3_GM.sf2 soundfont. I'm curious: Is it possible to override the ADSR envelope R time without editing the soundfont? I'd like to set the R time to 0 globally so that notes immediately cut of when their respective note-off event is received. --