Page 1 of 1

Moving a soloed track unarms the solo

Posted: Fri Nov 04, 2005 12:08 am
by amo
Hi,

-I've got two tracks soloed, in non exclusive mode.
-move one of the tracks
-solo is no more on that very track.

Donno how far this a bug or consequence of some logic, happens all the time though.

Regards,
amo

Posted: Sat Nov 05, 2005 12:33 pm
by amo
What about that one ? Happening on your systems or do I do something wrong ?

Posted: Sat Dec 10, 2005 12:50 pm
by amo
Hi,

I thought I would bump that one since Alex is very much around...
Alex, just in case you missed it !

Kind regards,

amo

Posted: Sat Dec 10, 2005 1:13 pm
by hoffman2k
Confirmed on osx

Posted: Sat Dec 10, 2005 1:54 pm
by Alex
Hi amo and hoffman2k

seems to happen with every "soloed" track independent of exlusive mode.
Very probably it behaves the same in all previous versions of Live :)

However, we'll check that one.

regards,
/Alex

Posted: Sat Dec 10, 2005 2:00 pm
by amo
Alex wrote:Hi amo and hoffman2k

seems to happen with every "soloed" track independent of exlusive mode.
Very probably it behaves the same in all previous versions of Live :)

However, we'll check that one.

regards,
/Alex
Yes it does, I guess... Only noticed it lately, and it's *such* a big issue, but still, doesn't look good :)

Best,
amo

Posted: Sat Dec 10, 2005 2:05 pm
by amo
Oh, just one more thing:
From here, it looks quite easy to fix, right ? :lol:

*sorry* :oops:

Posted: Thu Dec 15, 2005 5:26 pm
by Alex
As you very probably already know, this one should be fixed within the latest beta, Live 5.0.3b6:
http://www.ableton.com/forum/viewtopic.php?t=31022

regards,
/Alex

Posted: Thu Jan 19, 2006 6:05 pm
by peeddrroo
i've noticed that after deleting a soloed track, all the remaing tracks stay muted until you solo/unsolo one of them.

bug or feature?

i mean, it's just strange to have all the tracks "muted" without having any of them soloed...

Posted: Thu Jan 19, 2006 6:18 pm
by Alex
Hi Pierre,

This bug is also reported here:
http://www.ableton.com/forum/viewtopic.php?t=32148

It should be fixed within the next bugfix update.

regards,
/Alex