After switching to Bitwig I never used Surge again because the grid is so much easier to edit while also being much more powerful and allowing you to make unique synthesis innovations nobody has done before, which Surge is not capable of doing. The only reason to use Surge is for "low CPU", but its performance isn't that much better than the equivalent grid patch, so there's just no point to use it, especially since it's so much more tedious/cumbersome to edit than the grid. The grid's like a direct unhindered translation from synthesis concept into implementation, when I think of any idea I can build it within seconds... with Surge can't do anything like that, I have to fight to translate the concept into something Surge can do with its limited architecture, restricted UI switching through tabs/pages of oscillators, etc, and that wastes time that should otherwise be creative.
You might have a point there; still I believe it's a very personal matter; I like Grid, just as I like tools like Zebra or PhasePlant, but on the other hand, unless I'm making something weird, I really don't need all that flexibility, would you really use the grid for making a patch like the one in the video?
Now there are so many VST, but there is not enough experience, time to understand whether a particular VST is worth the space it occupies on the hard disk or not. The nature of sound is very complex, and each VST plugin is unique, but how not to drown? If you have any thoughts, I would listen to them.
Hey, I’m glad to see more videos coming from you.
This result from a negative feedback is very interesting. I definitely didn’t expect that.
Me neither, but hey... Whatever gets it sounding right :D
Great to see you back man!
Nice to see you, again!
Thanks 😌
That's pretty fire!
Thank you.
I have 1 million questions but I can't choose.
Well... you have a chacacter limit for every comment, but you can write as many comments and questions as you like...
After switching to Bitwig I never used Surge again because the grid is so much easier to edit while also being much more powerful and allowing you to make unique synthesis innovations nobody has done before, which Surge is not capable of doing. The only reason to use Surge is for "low CPU", but its performance isn't that much better than the equivalent grid patch, so there's just no point to use it, especially since it's so much more tedious/cumbersome to edit than the grid. The grid's like a direct unhindered translation from synthesis concept into implementation, when I think of any idea I can build it within seconds... with Surge can't do anything like that, I have to fight to translate the concept into something Surge can do with its limited architecture, restricted UI switching through tabs/pages of oscillators, etc, and that wastes time that should otherwise be creative.
You might have a point there; still I believe it's a very personal matter; I like Grid, just as I like tools like Zebra or PhasePlant, but on the other hand, unless I'm making something weird, I really don't need all that flexibility, would you really use the grid for making a patch like the one in the video?
What are the techniques for creating guitar sounds? Especially the DI Signal, so that the waveform is as close as possible to the real guitar.
This is hard, but somehow easier, my idea on the topic is that Karplus and Strong are your best friends
Now there are so many VST, but there is not enough experience, time to understand whether a particular VST is worth the space it occupies on the hard disk or not. The nature of sound is very complex, and each VST plugin is unique, but how not to drown? If you have any thoughts, I would listen to them.
That's indeed a very good question :)