Why is ACE so much less popular than others?

[hyperscientist]

Wow, this thread became all about pre-routing. It really seem to bother people for a long time I hope u-he people are paying attention!

[Howard]

Wow, this thread became all about pre-routing. It really seem to bother people for a long time I hope u-he people are paying attention!

We prefer to ignore everybody here

[taoyoyo]

If only it had a longer name...

[bmrzycki]

I'd like to chime in and say the pre-routing used to bother me when it first came out. Since then, however, I don't have a problem with it and now I actually like it. Why? It reduces the number of mandatory patch cables. Simple sounds need 0-2 cables (and complex sounds need more). I think it fits a nice middle ground between a fixed layout synth and something more modular like Bazille.

If it really bothers you that ACE is pre-routed you can always create a preset with cables for the pre-routed layout. Then use that init patch as your master template. It's one heck of a busy patch right from the start.


And if you want the init patch, it's here: https://app.box.com/s/mhmsoluj9g61o3zbiwzxn9k69mhjaaex

[MitchK1989]

I still use ace regularly but I wish it had a one page GUI and no pre-routing... Maybe a couple more features...

Basically I want an "analog" equivalent to Bazille (gear porn skin version) based on ACE.

[BBFG#]

[jsp1979]

Just to be clear, ACE isn't monophonic.

[BBFG#]

Just to be clear, ACE isn't monophonic.

Thank you for clearing that up.

[thetechnobear]

If it really bothers you that ACE is pre-routed you can always create a preset with cables for the pre-routed layout. Then use that init patch as your master template. It's one heck of a busy patch right from the start.

Ive done this, and actually you can make it much less 'busy' if you chain the cables, and also colour them according to source... its actually then very clear, and the illustrates why i don't like the pre-routing.
- when its tidy... its not that much extra distraction.
- when you make an explicit link.. id like the default label to be removed (or updated?), as its now 'mis-information'
- the defaults are a bit odd... why use lfo2 and adsr2 for targets.
- it highlights, that there is a fixed chain, where ADSR (or gate) are the last, id like to be able to control volume by using pressure, with no ADSR*
- similarly, FXs are in a fixed point in the chain.

* ok, you can 'rig' this, by using the ADSR and putting pressure as a volume adjustment, but its not ideal.

I do get the point of pre-routing though, to reduce cable clutter, and in particular trying to keep the 'face' and controls of each module clear, so easy to see/use - but I think Id just like it done in a different way... perhaps take cues from the real modulars?
- shared CV bus, like on the make noise system.
- some kind of cable channeling or cable ties? or perhaps hooks on the panels?
( or, and i don't like this so much, a 'shared' bus on the 'rear' of the panels)

all that said, I repeat, I really like ACE... and this certainly does not stop me using it

[Urs]

Well, we'll see where it goes.

There's along standing feature request to swap the labels on the cable inputs to whatever the cable comes from. This is certainly something we've got on our list.

Switching the normalization (=pre-wiring) off isn't a big deal at all. It sounds like a nice addition to the circuit bending section, as does a selector for an alternative filter model. Latter would work much like the engine switch in Hive - if filter model is switched, it'll be for both filters.

There are also more ideas to make ACE more attractive and fun in future. Mind you, ACE has sold very, very well for a soft synth at this time and age.

- Urs

[aMUSEd]

If it really bothers you that ACE is pre-routed you can always create a preset with cables for the pre-routed layout. Then use that init patch as your master template. It's one heck of a busy patch right from the start.

Ive done this, and actually you can make it much less 'busy' if you chain the cables, and also colour them according to source...

I wish it did that automatically instead of random colours. What do you mean by chaining them?

[thetechnobear]

I wish it did that automatically instead of random colours. What do you mean by chaining them?

chaining is attaching other inputs to outputs... (like using stackable plugs in real modulars)
a cool feature, is the ACE will keep the colour as you build the chain, so makes it easy to see whats going on)
... Id quite like it, if perhaps the sources, had a default colour... or even if it was just audio rate vs control rate. (I know conceptual in a virtual modular.. but helps to have LFOs signals coloured differently to the audio path)

here is my default template... I think its a bit easier on the eyes
(there are a couple of other ways you can do this, if you prefer not to have the 'vertical wires' cover panel faces)

BTW: seems like the line styles are not working any more (e.g. thickness, and transparency)... mac OS X 10.10... tried in both Live9 and also VEP5, VST and AU... and bazille same issue?

[bg]

BTW: seems like the line styles are not working any more (e.g. thickness, and transparency)... mac OS X 10.10... tried in both Live9 and also VEP5, VST and AU... and bazille same issue?

Cable styles are working for me: AU, DP 8.07, OS X 10.10.2.

[Urs]

BTW: seems like the line styles are not working any more (e.g. thickness, and transparency)... mac OS X 10.10... tried in both Live9 and also VEP5, VST and AU... and bazille same issue?

Cable styles are working for me: AU, DP 8.07, OS X 10.10.2.

It's a bug in the current release version (rev 3437) - an update with final preferences panel is in the works.

[hyperscientist]

There's along standing feature request to swap the labels on the cable inputs to whatever the cable comes from. This is certainly something we've got on our list.

My humble opinion is: Don't put labels there once cable is connected. At that point we know very well what goes in/out, so let's keep it simple and pretty.