Improvements!

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

rlahalla wrote:Hey Urs, any news on Filterscape?
I would like to know too. And MFM?

Post

bmrzycki wrote:
Vectorman wrote:I'm sure there are all sorts of uses for them that I haven't thought of.
Here's one I stumbled across a while back: http://www.kvraudio.com/forum/viewtopic ... 58#3498558. :)
I do wish that could be applied to mmix modules cause they are hard to visualize

Post

xx JPRacer xx wrote:
rlahalla wrote:Hey Urs, any news on Filterscape?
I would like to know too. And MFM?
Always thinking about these.

MFM2 is almost perfect tho for what I want it to be. Apart from adding some more feedback fx and presets there's hardly anything one can do. It's the oldest concept I ever had, and the most thought out one. We'll see what's possible.

Regarding Filterscape... sheeh... that's a hell of a stable product. I'm almost afraid that anything I could do would interfere with its "structural integrity". I have some more filter types (both VA and Filterscape itself) and I have some more separate plugins in mind. An update will happen at some point (been talking about it for a couple of years) and it'll probably be as striking as MFM1.0 -> MFM2.0. It just takes time to work it all out.

Cheers,

;) Urs

Post

Urs wrote:
xx JPRacer xx wrote:
rlahalla wrote:Hey Urs, any news on Filterscape?
I would like to know too. And MFM?
Always thinking about these.

MFM2 is almost perfect tho for what I want it to be. Apart from adding some more feedback fx and presets there's hardly anything one can do
What about the ability to change the GUI size (like Zebra). I find it too small. Or maybe I need new glasses...

Post

firepile wrote:What about the ability to change the GUI size (like Zebra). I find it too small. Or maybe I need new glasses...
MFM2 was the first plugin that supported gui resize... just check the [look] control...

Post

Urs wrote:
firepile wrote:What about the ability to change the GUI size (like Zebra). I find it too small. Or maybe I need new glasses...
MFM2 was the first plugin that supported gui resize... just check the [look] control...
Ha. Don't know how I could miss that :?

Post

Feature request for Uhbik:
Arrow keys can select presets on the patch window. Scrolling + clicking on each one sucks, especially with this laptop's touch pad.

Thanks!
-x
noise and beats: Negutyv Xeiro do people actually click these?
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al

Post

pdxindy wrote: I do wish that could be applied to mmix modules cause they are hard to visualize
It would be nice, or maybe a module something like Runciter's or Zebrify's envelope meters on an MMix that can track a single modulation source?

Using the MMix amplitude to modulate the amplitude of an unused LFO w/ mode set to user, all segments at max and then choosing that as MMap modulation source works, but feels a little too tricky /shrug.

Post

With the fast growing patch libraries in Zebra I sometimes forget where the Initialize patch is :) Would it be difficult to implement a Init button in the Preset scroll menu? Like this: "Local | Init"

Cheers

Replicator

Post

replicator wrote:With the fast growing patch libraries in Zebra I sometimes forget where the Initialize patch is :) Would it be difficult to implement a Init button in the Preset scroll menu? Like this: "Local | Init"
Cheers
Replicator
Good idea.
The best way to avoid that is to create your own new init patch and save it to the folder you use most. That's what I do anyway. If you name it 1init, it will always be the 1st patch in the list too.

Post

MCnoone wrote:
replicator wrote:With the fast growing patch libraries in Zebra I sometimes forget where the Initialize patch is :) Would it be difficult to implement a Init button in the Preset scroll menu? Like this: "Local | Init"
Cheers
Replicator
Good idea.
The best way to avoid that is to create your own new init patch and save it to the folder you use most. That's what I do anyway. If you name it 1init, it will always be the 1st patch in the list too.
Thanks for your tip MCnoone I have thought in a similar way. 1init will list the patch on the top. Guess AAinit will do the work to.

Cheers

Replicator

Post

Hey Urs, have you ever considered adding an option to 'apply' the xy's? Meaning, the settings you've tweaked are now propagated to the modules, and the xy's are back in the middle.
Hope this makes sense to you, it's just something I found myself wanting while tweaking a few times now.
Image

Post

Mighty Pea wrote:Hey Urs, have you ever considered adding an option to 'apply' the xy's? Meaning, the settings you've tweaked are now propagated to the modules, and the xy's are back in the middle.
Hope this makes sense to you, it's just something I found myself wanting while tweaking a few times now.
Yeah, I have considered it, but havn't had any time to implement it...

Post

Good to hear, though. It would give the xy's a second life in patch-making, rather than just live tweaking :)

Another thing I considered that I'm afraid is horribly complex (and in some cases just impossible): convert an mseg's values onto an env module. This is just a pipedream, but given how much I prefer graphical envelopes, I'm almost thinking of just using those all of the time >__>
In which case, I'd want a way to transfer them back onto envs when I might want to clear up the mseg's for more intricate stuff, haha.
Image

Post

Mighty Pea wrote:Hey Urs, have you ever considered adding an option to 'apply' the xy's? Meaning, the settings you've tweaked are now propagated to the modules, and the xy's are back in the middle.
Hope this makes sense to you, it's just something I found myself wanting while tweaking a few times now.
+1

Post Reply

Return to “u-he”