FilterscapeVA improvement poll

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

Shall I improve VA or shall I preserve automation data?

Yes - improvement is good
131
98%
Nope - I already have too many automation tracks
2
2%
 
Total votes: 133

RELATED
PRODUCTS

Post

manix24 wrote:[a lot of things...]
Err... so?
There are 3 kinds of people:
Those who can do maths and those who can't.

Post

i voted for the improvement

i think the wisest approach for people with tracks in the works is to not upgrade your plugins 'till your track is done :) or get your act together and finish your track so you can upgrade

really let's not be luddites here, and our unfinished masterpieces should't get in the way of progress imo

thanks as always Urs :)

Post

lol

landslide? :)
worst signature evar

Post

I'm a Live4 user, so I whole heartedly agree with the improvements to automation. I wish Ableton would figure out a better way to handle massive amounts of automation parameters, but they haven't yet so thank you for thinking of us, Urs.
-="I beat the Internet...the end guy is hard"=-

Post

Sascha Franck wrote:Urs, why would applying a new ID result in older presets not being loadable?
I can only compare to Kontakt 1-2. Kontakt 2 will load all my Kontakt 1 presets just fine, without any sonic differences.
Well, hehe, I could make them loadable over the interface, but I'm not yet at the point of having kinda "importer objects". The current version would reject any preset that was saved with a plugin that has a different ID. And of course, hosts would not load them either...

I've planned this stuff for Zebra2 tho...

;) Urs

Post

OK, point taken, Urs. So, it seems people will prefer improvements over backwards compatibility.

Uh... but then... add some Podolski preset compatibility :)
There are 3 kinds of people:
Those who can do maths and those who can't.

Post

Yep, I am also after improvemnts.
And maybe some kind of document describing "which parameter in old FS should be mapped to which in new FS" , would make the switch a little easier to some folks? (that way they could just convert the automation data)

cheers,
Bart

Post

Sascha Franck wrote:Uh... but then... add some Podolski preset compatibility :)
WhaddayathinkIamdoinhere?!? :x

:hihi:

Why add 3 filter types with Click & FilterFM + ArpModulator if not for Podolski compatibility?!? But I'll probably have to convert them with a batch script rather than build a full blown compatibility layer...

Cheers,

;) Urs

Post

FEV wrote:Yep, I am also after improvemnts.
And maybe some kind of document describing "which parameter in old FS should be mapped to which in new FS" , would make the switch a little easier to some folks? (that way they could just convert the automation data)
Yep, that's a good idea! Kinda look up table... :)

Cheers,

;) Urs

Post

Urs wrote: WhaddayathinkIamdoinhere?!? :x
No idea... watching soccer?
Getting some booze?

If so, continue! I love boozed soccer watching programmers! And yes, that's got to be the most honest statement ever! I'll gladly deal with any sort of update delay in case someone's watching soccer!
There are 3 kinds of people:
Those who can do maths and those who can't.

Post

Who voted against?
Resons why?
Image"You blow in this end of the trombone, and sound comes out the other end and disrupts the cosmos." Roswell Rudd Check out my music: http://www.pbone.org/

Post

Urs wrote:
Sascha Franck wrote:Uh... but then... add some Podolski preset compatibility :)
WhaddayathinkIamdoinhere?!? :x

:hihi:

Why add 3 filter types with Click & FilterFM + ArpModulator if not for Podolski compatibility?!? But I'll probably have to convert them with a batch script rather than build a full blown compatibility layer...

Cheers,

;) Urs
This has to be the best reason for going with the way Urs wants to do it. :)
I did get a life,once...but it was faulty, so I sent it back.

Post

Do we get any new presets in this update and/or the AU presets i keep hearing about being ported?
Image

Post

Urs wrote:
FEV wrote: And maybe some kind of document describing "which parameter in old FS should be mapped to which in new FS" , would make the switch a little easier to some folks? (that way they could just convert the automation data)
Kinda look up table... :)
Ha ha...
I wouldn't have to read who is the author of this post, to know that he is a developer :D :D :D

cheers,
Bart

Post

The arpeggiator steps will still be automatable in some hosts, right? I ask because I like this capability. (Of course, providing "arpeggiator snapshots," like the eq snapshots, would be an attractive feature for a future update.)

Post Reply

Return to “u-he”