Hi @HISEnberg, thank you for your reply.

I tried the AI already and checked it with @d-healey and the result was "wild guessing" as he said...

I'm not using faust at the moment because it would complicate things since I'm a beginner. Anyway I tried the search on github as you suggested but I get no results at all... Am I doing it wrong?

Honestly I have no idea at all on how to use the scriptonodes and the documentation doesn't help (at least for my level).
Neither was I able to find anything about Drive - Tremolo - AutoWah on the forum besides the fact that @hisefilo and @virtuscapeaudio built the rhodes and used Drive and Tremolo therefore @d-healey suggested me to ask them o the forum.

@HISEnberg Since you were so kind to send me the example, would it be too much trouble to give an example for Drive, Tremolo and AutoWah made with the HISE's stock FX?

I think they could incorporate these ones in the stock list as well since they are kind of basic FX you use for EP, and it would be great for newbies to have them available before digging into faust.

Maybe a community effort? Am I asking too much? :)

Thank you again for your time :)

Hi guys, I'm quite new here and I don't know much about scripting.
I'm playing around with a simple project based on the rhapsody template.
I already talked with @d-healey who doesn't deal with FX that much and suggested me to ask the two of you who already build this type of instrument:

@hisefilo and @virtuscapeaudio

Did you use the stock effects or wrote scriptnodes?

because I checked the stock list and I couldn't find the Drive and the Tremolo which I saw you used. And it would be nice the Auto-Wah as well.

As I said I don't know much about scripting so if there is any simple solution you can help me with I'd appreciate it.

Sorry for bothering you and thank you in advance

@d-healey @Lindon

Hi guys, sorry for my late response and thank you very much for your advices.
I understand that my idea of building a solo instrument is to be considered a complex plugin by itself cause of all the features involved and then I thought I could start with an acoustic piano instead? Using only one sampler and David's tutorial I could try to switch sample maps for a couple of pianos through a combo box.
I'd appreciate your advices to start building it and avoid complexity I might not realize therefore my following questions:

AHDSR - Reverb and velocity modulator are sufficient for a nice sounding acoustic piano or would you guys consider to use any other inbuilt fx?

Since I'd like to use it as starting point and keep building on it (like after accomplish this 1st plugin adding an extra layer for pads, textures and strings for example), would you guys link the envelops to the global modulator or directly link the parameters to some controls on the GUI?

Please, let me know what's the simplest way to start with and I'll follow it :)

@d-healey said in Sofia Woodwinds on github:

The velocity modulator will be in the Attack Time section of the envelope. The modulator has a table that you can use to map velocity values to the attach time.

Since we only want to add a fade in to the sustain when the velocity is above 64 (if that's the lowest value you want to trigger the overlay) then you can use the table to provide a lower attack time when the velocity is below this threshold, and a longer attack time when it's above. You'll need to play around with the values to find out what attack time works best for your samples.

Thanks, I'm going to test it and start assigning some knobs on the gui to the parameters I'm using to tweak the sample in order to practice this simple task :)

In a tutorial of yours I remember you suggested to use the muter in the midi processor to turn off a sampler, so if I want to use only the sustain or only the staccato I can link the muters to some buttons in the gui instead of using key switches, right?

@d-healey said in Sofia Woodwinds on github:

I think you're referring to a velocity modulator to control gain here? Which is separate from the velocity modulator that's controlling attack time.

Yes I was thinking about the gain, but you can suggest any other easy solution to allow controlling the velocity range for the staccato, if there is any easy way of course :)

@Lindon

@Lindon said in Sofia Woodwinds on github:

.... that indicates you should really be working on simpler HISE projects. Until you understand the fundamental approach of HISE I would recommend you stay away from the "more complex" approaches to delivering products...

Hi Lindon, thank you for joining the conversation :)
I'm sorry guys but I already told David I'm completely new and need some help to understand how it works. I watched and still keep watching David's tutorial but I need to ask questions for explanations to understand the fundamental approach and then eventually discard the more complex ones.
As I already told David I'm not interested in delivering a product to the market but simply understanding how I can use the software for my personal needs because I'm absolutely away from a professional business level...

I think an instrument using sustain, staccato and release samples is a normal routine I need to learn building. To achieve it I ask how I can do things and I can only realize its complexity after the relative explanation.
If you have any specific suggestion I'll be happy to hear it since I'm here asking for help :)

@d-healey said in Sofia Woodwinds on github:

also my scripts have UIs that you can tweak the parameters...

Right, I saw your legato and it looked very similar, my problem is that I've been looking at your instruments at it's quite overwhelming. Sorry if I ask so many questions but it's the only way to understand what can result too complex and then discard that option in order to look for an easier solution. For example I know I can assign knobs to control parameters but I'm not sure for each use case the way it works...

Like the knob patch we discussed to switch the sample map involves some more scripting in your version and I need to find a simpler way to start with instead.

As long as it doesn't require any particular scripting I think I can accomplish to overlay staccato and sustain through velocity

@d-healey said in Sofia Woodwinds on github:

If you want to overlay a staccato sample then probably the best approach would be to put the staccatos in a separate sampler, mapped to the velocity you want them to trigger at. And in the sustain sampler add an envelope with an attack time that provides a nice crossfade between the staccato and the sustain and add a velocity modulator to the envelope so it only affects the same velocity range you are using for the staccatos

In this advice, when you say: "add a velocity modulator to the envelope so it only affects the same velocity range you are using for the staccatos" you mean that if I map the staccato to be triggered at 64-127 for example, I should set the min velocity of the modulator at 64 in the sustain sampler (if it iso I don't think I got it)?
Furthermore, if I want to change the velocity range for the staccato in the gui, in order to adapt it to the keyboard you're playing with, shouldn't it be easier to add a velocity modulator to the staccato sampler and control the velocity range from the gui?
This way I can map both sustain and staccato to all the velocity (1-127) and add a knob on the gui allowing to control the attack time for the sustain to crossfade with the staccato while for the staccato I can add a table on the gui to modify the velocity range and curve.

Does it make sense or am I completely wrong?

@d-healey said in Sofia Woodwinds on github:

A lot of it is influenced by Big Bob's work in Kontakt with SIPS and WIPS

I know these tools but they are kind of easier to use on kontakt because you make some tweaks on the gui till you find what you need.

@d-healey said in Sofia Woodwinds on github:

I can't remember what process I used with Sofia, it's possible that I'm overlaying a staccato note when playing at a higher velocity. With my Rhapsody libraries though there is no overlaying.

When I tested the Sofia Woodwinds the sustain and release worked quite well but the staccato didn't have have enough gain to be heard probabily due to the missing module pointed in the console:

@d-navarra said in Sofia Woodwinds on github:

Interface:! Line 140, column 44: Unknown function 'set' {SW50ZXJmYWNlfHw0OTI0fDE0MHw0NA==}
overlayController:! Line 3, column 52: liveEnvelopeVelocity was not found. {b3ZlcmxheUNvbnRyb2xsZXJ8b25Jbml0KCl8MTQ5fDN8NTI=}
overlayController:! Line 3, column 52: liveEnvelopeVelocity was not found. {b3ZlcmxheUNvbnRyb2xsZXJ8b25Jbml0KCl8MTQ5fDN8NTI=}

Lets experiment with the overlay anyway because it can be useful for some other instruments I want to work on later:

@d-healey said in Sofia Woodwinds on github:

If you want to overlay a staccato sample then probably the best approach would be to put the staccatos in a separate sampler, mapped to the velocity you want them to trigger at.

What velocity would you suggest? Is there a way to add a knob on the gui allowing you to change this velocity or is it to complex?

@d-healey said in Sofia Woodwinds on github:

add a velocity modulator to the envelope so it only affects the same velocity range you are using for the staccatos

Can you better explain this suggestion of yours?

Regarding the hidden knob to switch samplemaps:

@d-healey said in Sofia Woodwinds on github:

It's the patch knob. It does a lot more than just changing sample maps. I've completely re-written it's implementation in my current project because the version I've been using is a bit inefficient and over engineered. You'll find the code for the knob here - https://codeberg.org/LibreWave/RhapsodyBoilerplate/src/branch/main/includes/Patches.js#L23

All the modules and scripts which are involved in this patch are already available in the boilerplate or should I make all the other scripting in order to use this patch?

@d-healey

Would you explain how your "performance" patch works, and eventually how could I use this overlay method if you think it might be efficient or suggest a different approach which would allow me to get both a normal sustain preset and one with a reinforced attack?

@d-healey said in Sofia Woodwinds on github:

Do you mean you want to trigger a different sample set when a "short note" is played? I don't know how you'd do that because you don't know the note is short until after it's been played.

Not exactly... I mean like in your Sofia Woodwinds, you get a kind of staccato feeling without using key switches. Maybe cross fading the sustain and staccato samplers so that they play together but don't sound like 2 voices?

@d-healey said in Sofia Woodwinds on github:

The legato system I use doesn't require transition samples at all - it's not "true legato" - however with some instruments that have a little bit of wetness to the samples it sounds better to have a little release sample during the legato and that's what the transition sampler is for.

Ok, let's start building the samplers first then. I'm testing with the ldk violin and I have sustain, short and release (only one set of samples for each and one velocity).
I don't like key switches and I'd rather focus on a "performance" patch using your legato, getting the realese playing on note off and maybe reinforcing it on retrigger with legato using your transition method. The main point is how to get the staccato when playing short notes?
could you suggest me a structure and maybe some modules or scripts I could use?

@d-healey said in Sofia Woodwinds on github:

Not off the top of my head, I'd need to go back to the projects and see what I did. There will be different group configurations depending on the number of RRs and articulations and stuff like that. I may have integrated the group switching for articulations into the RR handler or I may be using a separate group switcher. There's no one size fits all so each project is tailored to the specific instrument and sample sets.

Ok, I'm trying to understand the logic behind your method of using modules and scripts. The emerald flute uses the same structure as the other flute while I've noticed in the free trumpet you don't use the transitions, is this due to your new version of legato which doesn't require the transition sampler?