Replies: 2 comments 7 replies
-
|
I don't understand a lot of what you said - but pure data looks like dog shit. I haven't had a really good look at vmix, but my impression is that we're best off not shipping it.. but instead setting up a single mix with all the parameters people could want. We should be making the audio stuff simple to use, rather than adding a ton of complexity to it. I kind of feel like the audio customization of the engine is insane and probably out of hand - when compared to other things - like how you have to make a text file to create a texture. |
Beta Was this translation helpful? Give feedback.
-
|
What parameters would you be setting up/exposing? Personally I really liked it after screwing around with it a decent bit (in particular its flexibility and how I could set up my own parameters,) and everyone I've shown it to (especially music producers/sound design people) thought it was pretty cool as well. The only gripes I have with it are some bugs and minor workflow inconveniences. I also haven't gotten the impression that it was tedious to set up or use at all. Sure, it took a little bit of time to figure out, but that's moreso to do with the lack of documentation. Once I figured out how to add audio tracks, figuring everything else out was pretty straight forward, at least it was as someone who has some experience with making music. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know how much game designers want to be messing with all that stuff though? You just want to play sounds, have reverb and echo in big rooms, have it sound all muffled when you're in water. I don't know how vmix fits into sbox. It's not modular, it's defining the mix for the game. Do we let people create their own vmixes and override the global mix? |
Beta Was this translation helpful? Give feedback.
-
|
Actually, I think I was thinking about how Vmix worked the wrong way. I assumed that .vmix files worked pretty much the same as .vsnds/.sounds/sound events on steroids, but in actuality it's just one .vmix file to determine how audio works for everything and sounds are just routed through the tracks you place. I feel kind of dumb for not realizing that earlier, actually... In that case, I think being able to override the default mix with our own .vmix file with additional graphs would be the way to go about this. As far as I can tell, it'd accomplish everything I'd want to do with it. If we go this route it might be a good idea to have a template .vmix file so that we don't have to start at square one and figure out how to set it up correctly for basic audio. |
Beta Was this translation helpful? Give feedback.
-
|
If I want to make a feature request for this, should I just edit this one, or is it different enough that I should make a new one instead? |
Beta Was this translation helpful? Give feedback.
-
|
If it's a different request based on new information I'd close that one and open a new one |
Beta Was this translation helpful? Give feedback.
-
|
Alright, sounds good |
Beta Was this translation helpful? Give feedback.
-
|
I ended up editing the pre-existing issue to better reflect what I want exposed, and also made a new one, since they're not quite asking for the same thing |
Beta Was this translation helpful? Give feedback.
-
I realize that this is pretty forward-thinking and should be tackled much later on once VMix is actually implemented and Facepunch starts working on an SDK/API for the other tools that s&box has, but I've had this stuck in my head for a little while, and I want to see what other people's opinions are.
When VMix gets implemented fully, I think it'd be best for people to be able to make their own effects (and potentially generators like synths and samplers and such) if there's something that VMix doesn't have and distribute that for others to use, instead of making a feature request in here for, say, convolution reverb, or a sampler, or something like that. DAWs have been doing this approach for decades for effects and generators with the VST plugin standard.
However, VST plugins probably aren't the best approach for VMix for a variety of different reasons. Particularly, they aren't made to be redistributed for real-time use at all, they're moreso made to be used by a musician/audio engineer in a DAW and rendered to an audio file after everything's done. Not to mention the complications that would come with paid plugins and redistributing those...
Something that I think would be a better fit for this is Pure Data. It's an open-source and lightweight visual programming language for making pretty much anything audio-related (Or at least, that's the idea I got from everything I've gathered.)
Here's some examples of what you can do with it:
https://youtu.be/DJCoOr4uHD4 - Fuzz, Reverb, Tremolo, Overdrive, Synth/Pitch Tracker, and looper effects for guitar (or any audio input really) with controllable parameters
https://www.youtube.com/watch?v=WQ7ifSykvXU - A synthesizer controllable via MIDI
Ideally the way this could work is that people could import Pure Data patches as nodes, and have that nodes' inputs and outputs set in the patch, probably in a similar way to how the guy in the first example controlled parameters via MIDI.
Beta Was this translation helpful? Give feedback.
All reactions