Ableton Forum

I emailed them about it over the weekend. Also PM'd Bernd (sp?) when 7 was first announced, but he didn;t get back to me. To be honest I didn't expect him to, I figured he most likely innundated with other messages and probably insanely busy considering version 7 had just been announced, so I don't hold it against him.

Still waiting to hear back on the email, but it has only been 2 days. That said, I am pretty sure that this forum is monitored, if not regularly, at-least occasionally by Ableton staff. This thread and others like it have been around long enough that I am sure they know about this problem. This thread was started in July of 2006, when version 6 was announced.

Some sort of response and explanation would be nice. When I hear back from the email I will be sure to post here.

Has anyone else emailed them, if so what was the response?

smutek wrote:I am sure they know about this problem.

they're very well aware of this problem..


a simple yes/no for 7 would be welcome so I could prepare myself for a relief or at least another year of struggling..

Just got this reply in an email from support:

Hello Jimmy,

we are already working on a solution, but at this stage it is too early
to say when and how this will be implemented. I think it should be
possible to find at least a temporary solution in the foreseeable future
- maybe in one of the later Live 7 updates.

Best regards,

Nico Starke
Ableton Support

Maybe a temporary solution in a live 7 update. Keywords "maybe" and temporary" - but it is good to know that they are working on it.

good to hear something..

Nice. Even though there are no promises, at least now we have some feedback what's going on.

I wonder what they mean by temporary. When its solved, shouldn't it be permanent. Like why would they solve the issue in Live 7, and then retract the compitability in Live 8, etc.

Anyhow - this is good news.

Lets keep Ableton in check on this one - Live is too good to let this feature slip away.

thanks smutek!

ok so I've seen the issue dealing with plugin faders and possibly live knobs/sliders but other than that...is Wacom navigation and automation/envelope/midi note "drawing" at least supported or.....seem to work for those using it?

anybody?

Man, I'm sorry. I read your question but didn;t realize it was a question for some reason. You can navigate fine, draw in notes and move clips around. The problem is with drawing automation and adjusting parameters. So it works halfway, kind of, for me it is broken just enough to make it not worth bothering with my tablet when using ableton. It doesn't offer the precision and fluidity you would expect when working with a tablet in any other application - and I have to switch back to my mouse so much that I just end up putting the tablet up.

If that makes sense.

If you are considering purchasing a wacom strictly to use with Ableton I would say don;t do it at this stage, but if you have other applications that you use that would benefit from a tablet then I would say don;t hesitate to pick one up if you can. I'm a graphic artist and use a tablet both at home and at work, for me it is an absolutely indispensable tool.

Thanks smutek-I appreciate the info.

Im planning on getting a Bamboo pretty soon. I really HATE mousing around espescialy in Ableton. Its a creative hinderance. You'd think with all this DAW technology improving by the day we'd be the ones leading the use of this interface

Hell, it seems like WACOM's whole marketing tactic is to get the Bamboo out there for the general public as a mouse replacement (granted much of their optimism seems to rest on the Vista platform...)

Anyhow I thought Ableton was the leader in "thinking outside of the box" in regards to DAW. You'd think they would have been the 1st to pioneer even unique and special features of "expression" with the tablet product but it seems that they are way behind the standard on this one and if it was one thing I thought Ableton WASNT it was "standard".

From what I hear, WACOM support is a given in most all other sequencers. Funny thing is that one of the main reasons I switched to Ableton was because of its hardware support (i.e. BCR2000). It looks like the folks at Ableton might have this working in the "future" (i.e. future versions).

Honestly I think that's pretty shitty... having to pay over $100 in a new "upgraded" version with a bunch of other features you may not even want to get to use a pretty standard function that should have been included long ago.

i can't answer that b/c i won't buy wacom until it supports a tablet. i HATE mouses.. especially live - its a pain to use.

me, along with others will probably just buy a competitor, although unfortunate

I tired to wait.. actually this isn't a feature, it's a bug that is still not fixed. and I can't understand why.

I'm bumping this-it's my new #1 wish. Sick of the mouse!

bump, and up it goes!

strange that from Ableton's reactions on this topic this particular features seems to be almost impossible to implement in Live. All we get is vague "maybe, sometime, temporary, possibly...."
Why is this so hard!?

Bummmmpity!

I'm saving for a Cintiq. These have been out for a little bit, but yesterday for some reason I decided I pretty much have to have one. To be honest I haven't had gear lust like this for a long time....

I know, it isn't music gear. But it's frickin awesome, and I don't earn my living doing music anyway so myaaaaaa.

Either way, my friends at Ableton, I'll be expecting full wacom support by the time I get this beast!