Synth is here:
https://www.dropbox.com/scl/fo/vp5bhxjh ... 8uom7&dl=0
This time around you dial in the effects you want on the wave. The first section is wavetable based design. What is drawn goes to different sections of the wavetable. The others are added effects ideas. I included a pad which is just to support the main sound. Its a long GUI in terms of screen coverage. The included presets were just made with the randomize feature of the MXXX.
The main default in the folder once imported is WaveStepFX...it has the latest adjustments. I noticed the sounds can get kinda loud so I added the option to reduce volume a bit more. Make sure the main limiter on MXXX is engaged.
best,
-cd
WaveStepFX another synth for MXXX
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
-
- KVRist
- 285 posts since 18 May, 2020
Someone needs to stop this guy. I am doing nothing else, but testing synths! Which are just fire!
@CMDess, can you check the dropbox folder please? I don't see the synth, only the preset file. Thanks
@CMDess, can you check the dropbox folder please? I don't see the synth, only the preset file. Thanks
C.M.Dess wrote: ↑Thu Mar 21, 2024 7:34 pm Synth is here:
https://www.dropbox.com/scl/fo/vp5bhxjh ... 8uom7&dl=0
Last chance
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
Tyrs wrote: ↑Thu Mar 21, 2024 8:29 pm @CMDess, can you check the dropbox folder please? I don't see the synth, only the preset file. Thanks
C.M.Dess wrote: ↑Thu Mar 21, 2024 7:34 pm Synth is here:
https://www.dropbox.com/scl/fo/vp5bhxjh ... 8uom7&dl=0
Many thanks, those presets load the the synth on my system. The main "engine" is the WaveStepFX preset. That preset has the latest version of the device. The way devices store presets is a little iffy on my end so each preset is being saved as the entire engine. They should be importable through the global presets engine into a folder. The device should be visible when not in edit mode.
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
Here's a video with examples and an overview!
https://youtu.be/LsWgFp8QaFI
https://youtu.be/LsWgFp8QaFI
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
I added a file with just the WaveStepFX Engine.
-
- KVRist
- 285 posts since 18 May, 2020
Somehow I am not able to load it, same for Groove Shadow. I did get only the Acid Synth to run, where you shared the .mActivePreset file. Which steps are needed to get the device loaded with the .mpresets file only?
Also in case you don't know it yet - there is an alternative way to share a preset by copying it from the section on the right in the main window view (little button with an arrow and a "file"). Then you can post it here as a code.
Also in case you don't know it yet - there is an alternative way to share a preset by copying it from the section on the right in the main window view (little button with an arrow and a "file"). Then you can post it here as a code.
Last chance
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
Thansk for the info, I put an Mactive for the WaveStepFX in the same dropbox folder. Groove Shadow coming next. Got it, it's in the GS dropbox folder! Generally I've been able to import these things through the browser. One method is using import from the browser and another is dropping into your MXXX active presets folder (the users version on mac). It looks like for the "active" preset that needs to be dropped into the folder for MXXX as the browser doesn't see it.
-
- KVRer
- Topic Starter
- 27 posts since 21 Jul, 2005 from Florida
Nize
Another I've been tinkering with is "Articulator"...I wanted to create an effect that could be used to rearticulate. It's really wild how many directions one can go with this concept. There are so many articulations. Perhaps at some point I can make them in groups, then later have a method to merge them through MRatio/MMorph. This version works good for really taking sounds deeper I put it on the back burner because the process these things takes a chunk out of the cpu for the really powerful stuff. In essence taking dsp into a more physical direction.
The main vision is that the engineers and producers etc...run through sessions looking for things to improve where as the "Articulation" maestro could run through the those to change things up. It gets more expansive when you think about running it over groups and sums. This ones just an example.
https://youtu.be/_S1vcy0pGcc
Another thing I thought of today is the concept of making the source swappable for these things. So that one can use the system as an effect or as a synth. If you leave the first row of inserts blank, this enables the potential to add a section where the plugin allows for the insertion of an instrument. In this way one can make a determination if there's a way to develop the plugin from effect backwards into synth, meaning it doesn't rely on the synth engine and uses the similar effect modules to develop the core sound design. Even better to leave the first 2 rows blank so you can insert a mixer to plug in to the various columns as needed, perhaps containerizing with modular when more modules are needed.
Another I've been tinkering with is "Articulator"...I wanted to create an effect that could be used to rearticulate. It's really wild how many directions one can go with this concept. There are so many articulations. Perhaps at some point I can make them in groups, then later have a method to merge them through MRatio/MMorph. This version works good for really taking sounds deeper I put it on the back burner because the process these things takes a chunk out of the cpu for the really powerful stuff. In essence taking dsp into a more physical direction.
The main vision is that the engineers and producers etc...run through sessions looking for things to improve where as the "Articulation" maestro could run through the those to change things up. It gets more expansive when you think about running it over groups and sums. This ones just an example.
https://youtu.be/_S1vcy0pGcc
Another thing I thought of today is the concept of making the source swappable for these things. So that one can use the system as an effect or as a synth. If you leave the first row of inserts blank, this enables the potential to add a section where the plugin allows for the insertion of an instrument. In this way one can make a determination if there's a way to develop the plugin from effect backwards into synth, meaning it doesn't rely on the synth engine and uses the similar effect modules to develop the core sound design. Even better to leave the first 2 rows blank so you can insert a mixer to plug in to the various columns as needed, perhaps containerizing with modular when more modules are needed.
