BUG: Multiple output assignment key combo broken…

[SBP]

Originally Posted by john1192

may i ask what computer you have that this is working on ?? might be one of the differences .. this cannot be a preference !!!

MacMini 2.5Ghz I7 2x2. +OMNI

Tommrow I'm going through 12.8.0 in a bit more detail today has just been about install and quick test... so far looking pretty good.

Cheers

Bruno

[john1192]

Originally Posted by SBP

MacMini 2.5Ghz I7 2x2. +OMNI

Tommrow I'm going through 12.8.0 in a bit more detail today has just been about install and quick test... so far looking pretty good.

Cheers

Bruno

and an HDNative Thunderbolt Box to the Omni ?? right !!!

[SBP]

Originally Posted by john1192

and an HDNative Thunderbolt Box to the Omni ?? right !!!

Yep

[strangepumpkin]

Tested this on my Macbook Pro Mid 2012 OS X 10.12.5, PT 12.8 and it works fine.

[john1192]

Originally Posted by strangepumpkin

Tested this on my Macbook Pro Mid 2012 OS X 10.12.5, PT 12.8 and it works fine.

now this is getting weird that it works for you too

.. i can UnAssign any of these multiple output assignments that were made in 12.7.1 just fine .. but i cannot assign in 12.8 to more than one Selected Track ..

what are we missing here !!!

[john1192]

i just tried this on a 2nd computer .. macbook pro and Still i cannot get it to work .. using 12.8 ..

12.7.1 is fine ..

man, you guys are not screwing with us are you !!! this makes no sense ..

[strangepumpkin]

Originally Posted by john1192

i just tried this on a 2nd computer .. macbook pro and Still i cannot get it to work .. using 12.8 ..

12.7.1 is fine ..

man, you guys are not screwing with us are you !!! this makes no sense ..

Just ran a test and was able to re-create the bug. Originally, I was testing using a session that was created on 12.7.1 and it worked fine. Then I tried again using a template (template was made with an earlier version of PT) and still no issues. But once I created a brand new session from scratch, the bug appeared.

EDIT: And, since I've created a new blank session, even the sessions created on 12.7.1 have the bug. It's weird, it's like opening a blank session switched something in Pro Tools.

[john1192]

Originally Posted by strangepumpkin

Just ran a test and was able to re-create the bug. Originally, I was testing using a session that was created on 12.7.1 and it worked fine. Then I tried again using a template (template was made with an earlier version of PT) and still no issues. But once I created a brand new session from scratch, the bug appeared.

EDIT: And, since I've created a new blank session, even the sessions created on 12.7.1 have the bug. It's weird, it's like opening a blank session switched something in Pro Tools.

whew ... finally ... i can sleep tonight !!! thx for reporting back ... "It's weird, it's like opening a blank session switched something in Pro Tools" yes, agreed ..

[strangepumpkin]

Originally Posted by john1192

whew ... finally ... i can sleep tonight !!! thx for reporting back ... "It's weird, it's like opening a blank session switched something in Pro Tools" yes, agreed ..

I think it was a crash that did it. When I was initially testing between previously created sessions, I thought I should try a blank, when I made one, PT crashed. After that, the bug was present.

[john1192]

anyone here have a PC that they can test this on ???