Zupiter: A Web-Based Modular Synthesizer
pointersgonewild.com
Zupiter: A Web-Based Modular Synthesizer
1–10 of 27 posts
Re: Zupiter: A Web-Based Modular Synthesizer
#2OP here. Feedback and questions welcome! Feel free to reply to this comment.
I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
Re: Zupiter: A Web-Based Modular Synthesizer
#3OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
Very cool project! Do you have any plans for a Zupiter API? I'd love to build a utility module or two, maybe even a filter.
Re: Zupiter: A Web-Based Modular Synthesizer
#4OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
Very cool project! Do you have any plans for a Zupiter API? I'd love to build a utility module or two, maybe even a filter.
Thanks. Yes I do have plans for something like that. There's definitely a need for people to create new modules and reusable components, otherwise it gets too messy too fast.
Re: Zupiter: A Web-Based Modular Synthesizer
#5OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
It doesn't seem your oscillators are behaving correctly when you vary their frequency input. You seem to be doing something like phase = freq * time, which will break horribly when freq changes. Instead, you need to accumulate the phase over time based on whatever freq happens to be, like phase += freq * timeOfSingleSample.
Re: Zupiter: A Web-Based Modular Synthesizer
#6OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
It doesn't seem your oscillators are behaving correctly when you vary their frequency input. You seem to be doing something like phase = freq * time, which will break horribly when freq changes. Instead, you need to accumulate the phase over time based on whatever freq happens to be, like phase += freq * timeOfSingleSample.
So you think the oscillators should essentially be stateful? That might explain why I can't seem to implement 303-style slide correctly.
Re: Zupiter: A Web-Based Modular Synthesizer
#7Really nice for quick things, otherwise there is also VCV Rack (https://vcvrack.com/) that is a open source virtual rack with modular synthesizers. It doesn't have the graph UI that Zupiter seems to have, but a more of a skeuomorphic UI.
Re: Zupiter: A Web-Based Modular Synthesizer
#8OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
After fiddling a bit around, I would change the colors of modules that handle CV versus Audio or add even more colors to better comprehend a patch I've just loaded.
I was unable to figure out how to disconnect a cable. I tried alt, ctrl, shift click, right click, but none of it worked. I just wanted to add a second oscillator to the first example.
A larger mixer component would be very useful, like 6 in to 1 out.
Maybe add a highlight to the module I click on so I can use my keyboard to delete, move them around.
Do you plan to add MIDI out?
Really cool to have a "reactor" in the browser, keep it up :)
Re: Zupiter: A Web-Based Modular Synthesizer
#9Really nice for quick things, otherwise there is also VCV Rack ( https://vcvrack.com/ ) that is a open source virtual rack with modular synthesizers. It doesn't have the graph UI that Zupiter seems to have, but a more of a skeuomorphic UI.
VCV rack is pretty awesome, and you can do a lot of things with it that you couldn't with Zupiter. It's much more of a professional tool and as far as I know it's very well-regarded in the modular synth community, and a good way to pick out modules before spending hundreds or even thousands on physical hardware.
However, I think Zupiter is a nice way to get people who've never played with sound synthesis interested, and the sharing feature is one thing that differentiates it from most browser-based music apps out there. You can easily show your friends what you've made, or modify what other people made.
Re: Zupiter: A Web-Based Modular Synthesizer
#10OP here. Feedback and questions welcome! Feel free to reply to this comment. I also created a little subreddit to discuss Zupiter: https://www.reddit.com/r/musictools/
After fiddling a bit around, I would change the colors of modules that handle CV versus Audio or add even more colors to better comprehend a patch I've just loaded. I was unable to figure out how to disconnect a cable. I tried alt, ctrl, shift click, right click, but none of it worked. I just wanted to add a second oscillator to the first example. A larger mixer component would be very useful, like 6 in to 1 out. May…
> I was unable to figure out how to disconnect a cable. I tried alt, ctrl, shift click, right click, but none of it worked.
I will likely implement that later today. Clicking on an input-side port will allow you to reconnect it to something else (or to drop the connection).
> A larger mixer component would be very useful, like 6 in to 1 out.
Agreed.
> Do you plan to add MIDI out?
I've thought about it. Right now, it supports MIDI play/stop/clock output, so you can synchronize it with a drum machine using the ClockOut node.
> Really cool to have a "reactor" in the browser, keep it up :)
Thank you :)