Sampled guitars. One of the few instruments that I never cared for. Indeed, it is a solution for composers that can´t play such instruments. Fortunately I can and love to play guitar, bass, drums, piano and synths... but then again, I do use Orchestral libraries for composing orchestral symphonic music... so, the pratical aplication is similar on both cases. Nice video.
Great video, I have a question that is slightly unrelated lol. Is there a way to link multiple controls to one? And have them offset? For example: if I want to have it’s so that when I turn the knob up for the first half it increases the reverb, and for the second half the reverb doesn’t increase anymore, but it startsto add delay?
Hey, great question (sorry for the slow reply, hope you are still looking for this). It takes a bit of maths to make it work, but it is totally doable. (I assume this is for scripting Kontakt GUIs by the way, so I hope that's right). So, let's say you want to do half of a knob or slider (with a value of 0-1000000) will control the reverb wet/return and then the second half will control the delay wet/return. First, I'd use an if function so that if $knob < 500000 then use the set_engine_par command for the reverb control, else (meaning 500000 and above) use a second set_engine_par command for the delay control. Then, when it comes time to put the value in, typically we put in $knob there so that it just puts the integer value right in so that the control is set to whatever value the knob is. However, this is where our maths comes in. For the first knob, you simply take the $knob value and times it by two. That way, we are doubling the value. This will mean when $knob is 0, the reverb will be 0, but when the $knob is at 500000, this will make it 1000000 (the max of the reverb control). Of course, if you want the max to be 750000, then you would need to times it by 1.5 rather than 2. Hopefully that makes sense. So, for the first one, you would probably get away with just putting in $knob * 2 in the value parameter of the set_engine_par control. For the second, it get's a little tricker, because we have to offset it. Because it starts from 500000, we need to minus 500000 to begin with to bring that value back down to zero, meaning by the time the $knob gets to 1000000, it will be back up to 500000. So, something like ($knob - 500000) * 2 should do the trick. One other thing to note that can be really tricky with equations in KSP is that the knob is only going to accept "integer" values. Anything that results in a "real" number (a decimal point, like 1.5 for example) may cause an error or for it to not work properly. In this case there are some conversion commands. In K6 it is real_to_int() and int_to_real(). That changed in K7 to just int() and real(), but they work the same way. Essentially, you may need to convert the numbers to real, then do the equation, then bring them all back to integers again. For example, if the $knob * 2 equation causes issues, you may have to write it something along the lines of int( real($knob) * 2.0). That changes the $knob value to a real number, times it by a real number (2.0 having the .0 at the end) and then converts everything back into an integer with the overarching int command. Hopefully this all makes sense and helps :).
AcousticSamples Guiatrs are really good. Enjoy the strummer a lot. Very ingenious design and is my main virtual guitar :)
You have got to check out Straight Ahead Samples JB145 it is MILES ahead of any other guitar samples I have ever heard.
Awesome, sounds cool, I'll have to check it out.
Sampled guitars. One of the few instruments that I never cared for. Indeed, it is a solution for composers that can´t play such instruments. Fortunately I can and love to play guitar, bass, drums, piano and synths... but then again, I do use Orchestral libraries for composing orchestral symphonic music... so, the pratical aplication is similar on both cases. Nice video.
Great video, I have a question that is slightly unrelated lol.
Is there a way to link multiple controls to one? And have them offset?
For example: if I want to have it’s so that when I turn the knob up for the first half it increases the reverb, and for the second half the reverb doesn’t increase anymore, but it startsto add delay?
I have the exact same question! Been searching on forums forever! Maybe a great idea for a video @Stephen?
Hey, great question (sorry for the slow reply, hope you are still looking for this). It takes a bit of maths to make it work, but it is totally doable. (I assume this is for scripting Kontakt GUIs by the way, so I hope that's right).
So, let's say you want to do half of a knob or slider (with a value of 0-1000000) will control the reverb wet/return and then the second half will control the delay wet/return. First, I'd use an if function so that if $knob < 500000 then use the set_engine_par command for the reverb control, else (meaning 500000 and above) use a second set_engine_par command for the delay control. Then, when it comes time to put the value in, typically we put in $knob there so that it just puts the integer value right in so that the control is set to whatever value the knob is. However, this is where our maths comes in.
For the first knob, you simply take the $knob value and times it by two. That way, we are doubling the value. This will mean when $knob is 0, the reverb will be 0, but when the $knob is at 500000, this will make it 1000000 (the max of the reverb control). Of course, if you want the max to be 750000, then you would need to times it by 1.5 rather than 2. Hopefully that makes sense. So, for the first one, you would probably get away with just putting in $knob * 2 in the value parameter of the set_engine_par control.
For the second, it get's a little tricker, because we have to offset it. Because it starts from 500000, we need to minus 500000 to begin with to bring that value back down to zero, meaning by the time the $knob gets to 1000000, it will be back up to 500000. So, something like ($knob - 500000) * 2 should do the trick.
One other thing to note that can be really tricky with equations in KSP is that the knob is only going to accept "integer" values. Anything that results in a "real" number (a decimal point, like 1.5 for example) may cause an error or for it to not work properly. In this case there are some conversion commands. In K6 it is real_to_int() and int_to_real(). That changed in K7 to just int() and real(), but they work the same way. Essentially, you may need to convert the numbers to real, then do the equation, then bring them all back to integers again.
For example, if the $knob * 2 equation causes issues, you may have to write it something along the lines of int( real($knob) * 2.0). That changes the $knob value to a real number, times it by a real number (2.0 having the .0 at the end) and then converts everything back into an integer with the overarching int command.
Hopefully this all makes sense and helps :).
Hey, just answered it below, wanted to make sure you got a ping to let you know in case you were still looking for the answer as well.
@@StephenOConnellCmdShiftNew thank you very much, I am still learning but I will try this out.
Have a great day.
I think you may have scooped Westwood's announcement by about an hour or so...
Ooph, hope not. Maybe the had some tech difficulties that delayed the site launch. 😬