Live 4.0.3 and Tassman.......

Kas. · Post by **Kas.** » Wed Sep 22, 2004 9:55 pm

.......don´t like eachother.

Particularly 4.0.3 has introduced a big problem with Tassman not sticking to the preset it should stick to. It fails to load the preset it was set to when the set was last saved and though you can get the correct preset up, it will revert to some other once you hit "stop". I´m all in favour of a continuous workflow without ever stopping the audio but this is a bit too much, forcing me to step back to 4.0.1..

I believe this to be a problem on Live´s side of things since at least that works fine in 4.0.1 while Tassman hasn´t changed and the implementation of how Live deals with presets of plugins is know to have been improved.

I already reported to the kind people at A.A.S. that something is going wrong with the way Tassman interacts with Live concerning parameters that can be automated (Live only shows a dummy "parameter1"), in fact i wrote a whole paragraph to them on why the combination of acoustic sounds and loopbased composing is inherently a Good Idea and encouraged them to contact you guys.

If I may be so free; please open some channel of communications, the people at A.A.S. are very nice and dedicated and research has shown that 68% of all audio engineers have a desperate need for graindelays over imaginary acoustic instruments ;¬). Right now my two favourite audio aplications are not talking to eachother in a meaningfull way and what would seem to me like a match made in heaven is turning into a nightmare of glitches, slowdown and the occasional crashed computer.

Please contact me if you need more information, some of the symptomes are fairly vague and may be related to me building quite large patches with lots of weighted randomness but i may be able to pinpoint some of the problems that are less vague and less my fault.

yours,
Kas.

Frank Hoffmann · Post by **Frank Hoffmann** » Thu Sep 23, 2004 11:33 am

I can't reproduce that here. Tassman 4 load it's presets and settings just fine here with Live 4.0.3 on Mac OS X. Please try to explain exactly how to reproduce the problem. Please also tell me which version of Tassman you use and on which operating system you are on.

Frank

Kas. · Post by **Kas.** » Thu Sep 23, 2004 6:00 pm

i´m sorry about that.

i´m on win xp pro sp1 on a pc.
i use tassman build 4.0

after the weekend i´ll have the time to examine under what exact conditions this does and does not happen. strangely when i tried to document it just now all worked fine though i was fighting with it for most of last night. it wasn´t some fluke either, it kept happening, even after closing and reopening live and the project a few times.

it might be that i originally saved the project that gave me the problems under live 4.0.1, that might explain some of it?

kas.

Frank Hoffmann · Post by **Frank Hoffmann** » Thu Sep 23, 2004 6:53 pm

I don't think that this is the problem. Live sets saved with 4.0.1 should open normaly with Live 4.0.3 and normaly do.

Frank

Kas. · Post by **Kas.** » Thu Sep 23, 2004 9:20 pm

i´ll look into it, if i can´t reproduce it in a simplified new set, i´ll comunicate about sending you the .als file since this project consistendly does this if opened in 4.0.3, at least here it does.

yours,
Kas.

Kas. · Post by **Kas.** » Tue Sep 28, 2004 4:43 am

Found the problem. somehow program change settings got to be in my midi loops, all refering to ""bank; none, subbank; none, program; 1", instead of "none, none and none" as i think it should be (at least for that project). but there are some loops that don´t have those settings.

I have no idea where these came from, I certainly didn´t change all those for all those loops manually. Strange. it´s beyond me why this set would play differently in 4.0.1 and 4.0.3 too, it did, but at the least there is no fundamental problem between Live and Tassman there. I figure that if I stick to 4.0.3 from now on all will be well, patch change wise.

Sorry to waste your time, but before I found the cause. it was extremely frustrating. Let´s blame pilot error unless it happens again. :oops:

Yours,
Kas.

hyerstay · Post by **hyerstay** » Tue Sep 28, 2004 6:53 am

Were you playing with record on while changing patches?

jh

Kas. · Post by **Kas.** » Tue Sep 28, 2004 2:28 pm

i thought of that too, but no. all the midi was pregenerated in a algorithmic program, then imported. i only used record to sequence the loops into a composition.

i´m mistified by this, but at least it apears to be a one time only problem.