Modern D vs Pianoteq vs The People

Just a side clarification. My new for sale libraries (sfz versions) were expanded to include volume controls for multiple mics and release samples. It was made to work only with Sforzando, but apparently the controls also work in SFizz. The libraries are untested with other players and most sfz players don't have GUI controls.

dore_m The cool thing about SFZ is that one can do all sort of neat tricks simply by editing the opcodes in the text file, such as blending different mic perspectives together, finely tuning the samples one by one, optimizing the velocity curve, the volume, the response, and adding filters.

@amc252 yes, but it's not ridiculously intuitive to the masses. We crazy diy era will learn, but most won't. I also wanted to give more options to users without requiring the initial investment of buying kontakt.

Pete14 BTW, has anyone played the “Peole”?

https://en.wiktionary.org/wiki/peole

I don't get it. What's peole supposed to mean? It is supposed to be people, right?.

David B I don't get it. What s peole supposed to mean? It is supposed to be people, right?.

That is correct. I tried to make a (poor) joke out of a mis-spell.

RIP Do you want me to correct the title?

David B Do you want me to correct the title?

Sure, please do.

Hey, what about all us peoles!?

David B Thank you, now my phone and laptop's text-to-speech voices are happy! 🙂 Thanks.

OlivierW

Olivier - the scripts you have written for your VSL-D+Ptq and VI Modern D+Ptq are really impressive. I appreciate that you previously published your Reaper script for the VSL-D/Ptq resonance setup. Could you offer any advice for the Reaper-script equivalent of your Logic 11 script for the ModernD/Ptq setup? Further, I would love to know how you figured out how to code the note-off behavior for you N1X. I have a Casio GP-300 that sends note-off info and I would like to take a crack at that.
Thanks also for sharing your knowledge and presets, etc. I've learned a lot.

doctae Here's a Reaper template that integrates Olivier's script with the VSL Synchron CFX running through Pianoteq's resonator. The site is renaming it to a .txt when I upload it, but I assume you can just change this back to .rpp and open in Reaper.

I'm a total Reaper noob, so I'm not sure if this is the best way to share the settings. Let me know if it doesn't work and I'm happy to try something else.

EDIT: forgot to attach the Pianoteq preset. If you don't have the Steinway, just pick a piano and set the velocity curve to a flat 0 across the whole thing so the hammers never hit the strings, but the dampers mirror what you're playing on whatever sample library you're using. The site renamed that file to cfx-resonance.bin but just change that to cfx-resonance.fxp and it'll load in Pianoteq.

Mindbullets

Thanks I'll check it out when I'm back at the PC, and report back.

Mr. Bullet - I'm familiar with setting up Reaper with VSL pianos and side chaining w/Pianoteq. Olivier had previously shared a reaper script + rpp. Your rpp would be useable except it doesn't include the script file (if different that Olivier's). What I'm inquiring about is coding issues - more details about O's code and Logic > Reaper translation. But more interested in his code itself.

doctae

Oh weird! I didn't realize it didn't save in the project file. Here's the script. It's all the same logic as Olivier's, I think I just renamed a few vars while debugging so it made more sense (to me) what was going on.

desc: Reaper Script to enable silent key for VSL Pianos and disable VSL Sustain samples for use with Pianoteq
desc: 12/3/2023 - Olivier W. Frappier

@init
sustainVal = 0;        // current sustain value from the original MIDI
overrideActive = 0;    // are we currently overriding sustainVal?

minVelocity = 2;       // minimum velocity (anything lower will silent-key)

controlChange = 176;   // status byte 176 = control change
sustainPedal = 64;     // cc 64 = sustain
noteOnCmd = $x90;      // command 0x90 = note on 

@slider

@block
  overrideActive == 1 ? (
    // clear sustain pedal override
    midisend(ts, controlChange, sustainPedal, sustainVal);
    noteOnState = 0;
  );
 
  // intercept MIDI messages
  while (midirecv(offset, msg1, msg2, msg3)) (
    ((msg2 == sustainPedal) && (msg1 == controlChange)) ? (
      sustainVal = msg3;
    );

    // is it a note-on?
    msg1 == noteOnCmd ? ( 
      // override sustain pedal value to 0 to trigger pedal-up (dampers-down) sample
      midisend(ts, controlChange, sustainPedal, 0); 
      overrideActive = 1;
      
      // if the note velocity is below the minimum, drop it to 0 so VSL will silent-key
      msg3 < minVelocity ? msg3 = 0; ( 
        midisend(offset, msg1, msg2, msg3);
      )
    ) : (
      // pass through other events
      midisend(offset, msg1, msg2, msg3);
    )
  );

I ask this out of genuine cusiosity. If Pianoteq is so bad, why do most of the top brands endorse it and let them use names and models, whereas the other VI creators have to make up suggestive names for their instruments?

amc252 easy. Pianoteq pays to those brands because if it bears no real name, nobody will recognize what that sound is, they all sound the same: synthetic. Sampled pianos don’t have to convince you, it’s sure they recorded a real piano, so they can save on royalties.

I don’t believe in the “endorse” theory. If it was true, how come VSL and Garritan were “endorsed” by Yamaha and not Modartt?

BTW, there’s a contradiction with Pianoteq. Everybody tells you that modeling is so powerful, you can tweak it to sound like every piano in the world. Yet, they can keep on purchasing new models, instead of exchanging free presets that can supposedly do the same? Or not? 🧐

amc252
the same reason why we don't label the foods in our fridges, we already know what they are because of how they look, smell and taste like.
but every ptq model sounds like the others so they had to label them to (maybe) avoid confusion.