Time & Timbre crashes

[4am]

Hi

Time & Timbre makes Ableton Live crash.

Is anyone experiencing the same problem?

Thank you

Cheers

[störgeräusche]

really crashy here and having conflicts with push.
I hope an update will be out soon -not a cheap pack so I really hope a quick fix will be delivered soon

[4am]

I've noticed that the price of the device has decreased.
I'm wondering about the reason.
It's because the device is buggy?

[sbx]

hi, could you please detail? what system / live version / max version are you on?
please make sure that you use max 6.1.9, and downloaded the latest version (should be 1.02 if you right click on the time device and show max monitor)

feel free to contact us - support (a-t) skinnerbox (d-o-t) de

thanks

[störgeräusche]

my setup:
Win7 Pro 64bit
Live 9.1.7 64 bit
Max 6.1.9
T&T 1.0.2 Downloaded 02/17/2015

Thanks

[4am]

hi sbx

thanks for replying.

i have exactly the same setup as störgeräusche

my setup:
Win7 Pro 64bit
Live 9.1.7 64 bit
Max 6.1.9
T&T 1.0.2

lg

[sbx]

hi both, thanks for your reply, we will do our best to get a hold of a windows system asap and check this issue,

best

sbx

[störgeräusche]

thanks sbx.i'll be sending crash reports to ableton. do you need a copy?

[sbx]

we dont need the logs, never the less, is it possible for you to test if it crashes on 32 bit mode as well?

thanks and sorry for the inconvenience,

[störgeräusche]

hi sbx

i dont have a 32 version installed. if i find some time i will install the 32 bit versions of live and max, test and report.

[Because789]

Might be the same issue:

Ableton developers pointed out in the beta forum that there is one crash situation on Windows which they do recognize (and are working on - so it was reported):

At M4L initialization (that is: when you start M4L for the *first time* since Live was open, so with the *black* Max for Live logo popping up) things can go wrong.
In particular on Windows 7 OS. M4L requires some windows dll library to start. With large M4L devices those libraries may called before fully loaded causing a Live crash. It is a matter of timing (therefore the unpredictable aspect).

A workaround (not a solution) they suggested is to load the simplest Max for Live device possible first.
For instance load first the empty "Max Midi Effect" device, which you can find in Live browser under Max for Live // Max Midi Effect.
Wait then a few seconds (yes it sounds stupid, but they said it allows all dll's to be loaded). This has the effect of starting up Max for Live engine with no such issues.
After that it should be possible to load complex M4L devices without crashes.

My own experience kind of confirms this workaround does indeed help.

viewtopic.php?p=1652340#p1652340

[4am]

it is definitely the same issue.
when i start live opening another project it doesn't crash.
thank you for pointing this out.

[sbx]

@4am, thanks for posting that, its a good start,
could you both confirm that TnT is stable if the these steps are taken?

best
sbx

[störgeräusche]

thanks for this tip. I am going to try it out next time I'll be in the studio.

The last crashes I had (4 in a row) happened when hotswapping the preset while device was running (3x) and with the device stopped (1).
No other crashes to report.
I'll be sending the reports tonight to Ableton.

[4am]

@4am, thanks for posting that, its a good start,
could you both confirm that TnT is stable if the these steps are taken?

best
sbx

i did some more tests and i can confirm that starting m4l with another project solves the problem.
sometimes, if i maltreat the device with lots of quick commands, it crashes. but this does not happen often.

there are also a couple of projects i've made with time & timbre that do not crash, even if i open them directly.

the device itself is visionary and very interesting, i hope a fix can be found soon.

thank you

andres