3 ms·

I disagree. I think there is room for both. I own two Volcas, and don't use them much unfortunately. The problem with hardware is it's extremely difficult, or

by bambax 5y ago

I disagree. I think there is room for both. I own two Volcas, and don't use them much unfortunately. The problem with hardware is it's extremely difficult, or downright impossible, to save state. On a physical modular synth, the only way to remember what you did is to write it down or (maybe) take pictures. On a virtual modular synth all you have to do is Save As. I'm sure OP-1 can save its patches, but that doesn't address the problem of the whole chain, or backups.

capableweb 5y ago
Eh, that's not at all true. Being able to recall state is something that has been solved for a long time, but not all synths have that functionality, I'll give you that. As two examples of synths I own that can do this: - Moog Sirin supports Program Change MIDI messages, so I save the state of the current settings via MIDI on my Octatrack, and can recall that same state whenever I want without touching the hardware of the Sirin - Novation Summit allows you to save patches with your own name + putting it in a category. Recalling the same patch is a matter of turning the knob until you arrive there. Not sure how you arrived to the conclusion that saving state is "extremely difficult, or downright impossible".
- bambax 5y ago
  > Not sure how you arrived to the conclusion that saving state is "extremely difficult, or downright impossible". I was thinking about modular synths mostly, and patching cables (also: Volca Modular). Yes, individual synths can save/export settings, but if you want to save a whole combination with different machines it's a big headache; whereas in a DAW it's so trivial you don't even think about it. But ok, we are sliding into the "hardware vs software" debate, which won't be solved here or there, or ever.
  - capableweb 5y ago
    > I was thinking about modular synths mostly, and patching cables (also: Volca Modular). Ah yeah, I don't use modular synths myself (and that reason is one of them, patching cables manually seems like a hassle). > Yes, individual synths can save/export settings, but if you want to save a whole combination with different machines it's a big headache; whereas in a DAW it's so trivial you don't even think about it. As mentioned earlier, Program Change MIDI messages solve this. I have about 10 hardware devices I use for music making, and all of them responds to Program Change messages. Everything is driven by the Octatrack, so changing the project/pattern on the Octatrack makes every device in my studio load the right patch instantly. Once you've setup the audio/MIDI routing with your hardware, it's actually pretty easy to use. > But ok, we are sliding into the "hardware vs software" debate, which won't be solved here or there, or ever. Agree :) For some, hardware is better, for others software is better. Truth is probably somewhere in-between and/or both depending on context.
varispeed 5y ago
Why do you need to save state? If you don't, it helps you finish the project and move onto the next one. And if you do it every day, then you could likely dial in any settings from your own memory quicker that it would have taken to menu dive and load from disk.
- bambax 5y ago
  I need to save state because I don't finish projects in one sitting, and I don't have enough room (or money) to have different instances of the same machine lying around forever. MIDI controllers are great (and I even built a couple myself) to let one interact physically with an instrument. But I'm not sure I get the appeal of physical synths. To each their own though. I'm not trying to convince anyone. I'm just saying the key to more music is not necessarily more physical objects; more software is also great.

by bambax 5y ago

capableweb 5y ago

Eh, that's not at all true. Being able to recall state is something that has been solved for a long time, but not all synths have that functionality, I'll give you that. As two examples of synths I own that can do this: - Moog Sirin supports Program Change MIDI messages, so I save the state of the current settings via MIDI on my Octatrack, and can recall that same state whenever I want without touching the hardware of the Sirin - Novation Summit allows you to save patches with your own name + putting it in a category. Recalling the same patch is a matter of turning the knob until you arrive there. Not sure how you arrived to the conclusion that saving state is "extremely difficult, or downright impossible".

bambax 5y ago
> Not sure how you arrived to the conclusion that saving state is "extremely difficult, or downright impossible". I was thinking about modular synths mostly, and patching cables (also: Volca Modular). Yes, individual synths can save/export settings, but if you want to save a whole combination with different machines it's a big headache; whereas in a DAW it's so trivial you don't even think about it. But ok, we are sliding into the "hardware vs software" debate, which won't be solved here or there, or ever.
- capableweb 5y ago
  > I was thinking about modular synths mostly, and patching cables (also: Volca Modular). Ah yeah, I don't use modular synths myself (and that reason is one of them, patching cables manually seems like a hassle). > Yes, individual synths can save/export settings, but if you want to save a whole combination with different machines it's a big headache; whereas in a DAW it's so trivial you don't even think about it. As mentioned earlier, Program Change MIDI messages solve this. I have about 10 hardware devices I use for music making, and all of them responds to Program Change messages. Everything is driven by the Octatrack, so changing the project/pattern on the Octatrack makes every device in my studio load the right patch instantly. Once you've setup the audio/MIDI routing with your hardware, it's actually pretty easy to use. > But ok, we are sliding into the "hardware vs software" debate, which won't be solved here or there, or ever. Agree :) For some, hardware is better, for others software is better. Truth is probably somewhere in-between and/or both depending on context.

varispeed 5y ago

Why do you need to save state? If you don't, it helps you finish the project and move onto the next one. And if you do it every day, then you could likely dial in any settings from your own memory quicker that it would have taken to menu dive and load from disk.

bambax 5y ago
I need to save state because I don't finish projects in one sitting, and I don't have enough room (or money) to have different instances of the same machine lying around forever. MIDI controllers are great (and I even built a couple myself) to let one interact physically with an instrument. But I'm not sure I get the appeal of physical synths. To each their own though. I'm not trying to convince anyone. I'm just saying the key to more music is not necessarily more physical objects; more software is also great.