Artillery2 automation in Ableton.

Official support for: sugar-bytes.de
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi there!

I'm absolutely in love with Artillery2 right now. I've been playing with the demo and am just on the verge of buying it.

I just have a quick question:
When I change presets in ableton live, the parameters available for automation do not update to reflect the new chosen effect devices. The parameters in Live available for automation/midi mapping (when you unfold the device box) still represent the set of effect parameters that was one the first preset when loaded, so either the parameters are named wrong or don't represent anything (since, for example, that particular effect is no longer there) Of course, I couldn't try saving a different preset and re-opening to check if the parameters in ableton had switched to the new preset, since it's the demo.

So I guess I'm wondering: When you load artillery with a different preset, will the parameters for those effects now be available?

Also, any plans make it so that ableton gets an updated parameter set when the effects change in Artillery.

Being able to automate parameters in ableton is definitely crucial so I sure hope it can be done.

Thanks guys!

Post

I'm definitely still curious about this. The only thing that's keeping me from pulling out the plastic right now I'd say.

Did what I was said in my first post make sense?

Even if the parameters in ableton's extended device box didn't update immediately to represent the effects loaded in Artillery whenever the effects changed, it would still be sufficient if they were accurate every time Artillery itself was loaded with a different preset. (However the former would be ideal).

Regards,

rjw

Post

Hi Rj,

I just tested this in Live 6, which version do you use?

I opened the expanded parameter view in Live, then opened the Artillery Gui.
Whenever I loaded a global preset or assigned different fx, the parameter view
of Live immediately updated.

There are some update problems when effects become deleted though, something
that will be improved in the 2.0.4 update, planned for march.

Best regards,
Robert Fehse
www.sugar-bytes.de

Post

Hi, thanks for the reply!

I should have mentioned that I'm using Live 7 under OSX 10.5.2.

Could it be a Live 7 specific thing? I've also seen a post over at the ableton forum about how someone couldn't get some midi mapped parameters in Artillery to respond to movements from the controllers or automation, although in the same device some of them did work. My guess was that some effects had been changed and the ones that were still there would work but the new ones loaded would not. For example if one preset had reverb > delay > compression, and that was changed to distortion > delay > reverb, all the parameters in Live's extended device wouldn't update, so the delay would still work because it was left there, but when you move or map the reverb parameters they wouldn't control the new reverb, and there would be no parameters for the distortion. Just an example, but that seems to happen for any effect change or preset change. And that's what I thought was probably also what the other persons problem was that I noticed.

But it's great to hear that it works as it should in Live 6, gives me confidence you guys will figure out the issue in Live 7. I'll definitely be buying it when that's sorted out, these effects sound really nice and the low cpu usage is just fantastic!

cheers

Post

Hi, it should be no problem to get that done until
the update in march ;)
best, robert

Post

I just checked it in Live 7 under OSX 10.5.2 and i think i now know whats the problem. You used the AU Version right ? Because in the VST Version everthing works flawlessly. I'll have a closer look whats going on in the AU world.

Please try out the VST version.

best, Robert

Post

Yes, you're right, I am trying the AU version. I pretty much just use AU's because I also use Logic Studio (which doesn't take VSTs). So it's much easier to have all my user presets/settings just for one type of plug-in.

Will the issue with the AU version be fixed in the coming update? That would really be great!

Cheers

Post

Since the buglist of Artillery is quite small i am sure that i have time to fix this.

Robert

Post

Sugar Bytes wrote:Since the buglist of Artillery is quite small i am sure that i have time to fix this.

Robert
I sincerely hope that this small bug list to be fixed includes the bug where deleting the plug-in often likes to crash the host, as is present with vogue and effectrix. (In Ableton Live anyways).

I'm really looking forward to trying out the demos of these three after the updates. I'd buy them immediately if they didn't crash whenever I removed them from a track.

Post

Hi,

just wondering how the update to Artillery is coming along. I ended up purchasing it anticipating an update soon. You mentioned that March was the goal for the update, but we're almost in May. So just curious if we're close to seeing it? The full version has been fairly stable, but it would be nice to be able to automate the parameters after changes effects etc.

cheers

Post

Hi,

we have a little delay in the development. We are currently working on the Unique update, then we will do the Artillery update.
I think 2-4 weeks and it's there.
If it's not released in may i'll give you a product for free ;)

sorry for the delay and a nice weekend
Robert
www.sugar-bytes.de

Post Reply

Return to “Sugar Bytes”