Also there is signal interpolation in msp standard, what you could have done is use a mc.scale~ object with the arguments 0 1 for the input min and max, with a value from 0 to 1 in the first inlet, then the start frequency in inlet 4 and the end frequency in inlet 5. You could even then use the 6th inlet to add a curve to the interpolation to make the gliss sound more natural.
I'm confused by what you said about mc.gen~ crashing and another file being deleted. What you said implied that you just saved another patch with the mc.gen object in it, correct? Did you know that you can save the .gendsp files which would never be deleted and then can just be reloaded?
The .gendsp file can in fact also be deleted through this sort of crash. I have had instances where the contents of a loaded .gendsp file got deleted. Hope this clears it up for you!
This is my favourite note on youtube.
Nice job n this! Certainly sounds like an "in movie" experience. Thanks for sharing!
Also there is signal interpolation in msp standard, what you could have done is use a mc.scale~ object with the arguments 0 1 for the input min and max, with a value from 0 to 1 in the first inlet, then the start frequency in inlet 4 and the end frequency in inlet 5. You could even then use the 6th inlet to add a curve to the interpolation to make the gliss sound more natural.
Clever use of mc.scale~!
I'm confused by what you said about mc.gen~ crashing and another file being deleted. What you said implied that you just saved another patch with the mc.gen object in it, correct? Did you know that you can save the .gendsp files which would never be deleted and then can just be reloaded?
The .gendsp file can in fact also be deleted through this sort of crash. I have had instances where the contents of a loaded .gendsp file got deleted. Hope this clears it up for you!