TapTools and M4L -> experiencing issues

[tsutek]

Hi,

I've been demoing taptools because I want to use the potential of
Max4Live to its' fullest.

You no doubt understand what I mean by this: Yeah, sure, I can build
the M4L delay in the tutorials, but the feedback path sounds terrible.
This was the thing I feared about M4L the most - I will be able to
make instruments and effects in the MSP domain, but it will all sound
like SynthEdit '95 ....

I started looking for a solution, found taptools, got the demo. Ok, I
replace the default filter I've been using (onepole) with taptools
butterworth, and the whole machine comes alive :) I'm thinking "great,
so if I just cough up a little more dough I can make this work with
the aid of 3rd party MSP modules!"

However I have been running into bugs when using taptools (demo) in my
patches. The butterworth filter module has been about the only one
I've gotten to work as it is intended.

I haven't exactly been able to conduct thorrough tests (since many of
the taptools modules are designed to do stuff that's above my
capabilities so far), but I can make M4L crash everytime by using
certain taptools modules. Especially the combfilterbank.

So my question to the taptools team is - How extensively have you
tested taptools in M4L? And do you think that my problems with
taptools will be solved (if not by you then perhaps by ableton/c74?)

I'd love to get taptools but right now I'm holding off my purchase
(afraid it won't work). Been a bit depressed about M4L's progress in
general - there still seems to be bugs, especially with floating
windows-related things..

[Trond Lossius]

Hi,

tap.tools is maintained by Tim, so I can't answer on his behalf, but I think it would be most valuable if you are able to post crash logs and preferably also the patch that crashed, if possible, as well as info on version of Max, M4L, tap.tools and operation system.

It makes it much easier to track down what's happening when it crashes.

Best,
Trond

> --
> You received this message because you subscribed to the Electrotap group.
> To unsubscribe from this group, send email to electrotap-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/electrotap?hl=en
>
> Electrotap -- http://electrotap.com/
> Tools for Innovative Music, Media, and Art

[Timothy Place]

Hi,

There are currently zero known-issues with crashing in Max for Live.  So...  I'm interested knowing what is happening on your computer.  

Trond is correct that it is helpful to have as much information about your system, OS version, applications versions, Tap.Tools versions, etc.  For crashes (especially for delays and filters) it is also important to know your sample-rate, vector-size, is overdrive turned on or off, etc?

If you are on a Mac (I can't tell) then, as Trond says, crash logs are invaluable (search your computer for files ending with the '.crash' extension).  The most helpful thing is a patcher with a set of steps to reproduce the crash.

Sorry to hear of your trouble -- it'd be great if we can get it hammered out.

best,
 Tim

[tsutek]

Hello taptools,

Thank you for addressing my concerns!

I think my 30 day demo period has already expired, so I don't know how
to proceed.. But I still appreciate your response (considering how
much of a noob I am with this environment)

C74 has released an update for Max, DLing it right now.. I'm trying to
get back on the horse during the next few weeks.. So I'l see how
things work out - maybe I'll just get your tools without demoing next
time (I'm now assuming I can count on your support if problems
arise ;) )

Cheers

[Timothy Place]

If you do find any crashes or problems please let us know, as we are preparing a (free) update to Tap.Tools and would like to make sure that all known problems are addressed.

best,
 Tim

--