Article: v5 - n546 - rev 5 - 6 output on new mac pro

[blamelewis]

I do, and would expect the OS to remember I've given Catalyst permission for network connections... It doesn't seem to remember though as the same dialogue appears each time... However I've turned the OS firewall off for now while the machine's on a show.

I've been able to launch n541 (and I'm about to try n543 too) but have found a weird yellow flickering on movie playback (though not always) - is that the display glutting you're talking about in the original post? I've yet to look at the debugHUD to see if that solves it... The files are PrRes 422, in case that's relevant.

Cheers!

Tim

[samsc]

I do, and would expect the OS to remember I've given Catalyst permission for network connections... It doesn't seem to remember though as the same dialogue appears each time... However I've turned the OS firewall off for now while the machine's on a show.

I've been able to launch n541 (and I'm about to try n543 too) but have found a weird yellow flickering on movie playback (though not always) - is that the display glutting you're talking about in the original post? I've yet to look at the debugHUD to see if that solves it... The files are PrRes 422, in case that's relevant.

Cheers!

Tim

you using 10.10?

debug HUD isnt yellow flashing-
thats some kindof memory leak in quicktime - unresolved

[blamelewis]

Yeah, 10.10.2

I've been trying all the flavours of v5 that I've had today but all are proving unstable with the setup for this show - so I've reverted to the v4 version 466 and all seems to be working fine with that...

The system was:
- two PTDX100 projectors fed out of Thunderbolt ports via apple MiniDP to VGA adaptors
- programming monitor out of another Thunderbolt port and sent to an Adderlink X200 KVM
- Decklink Intensity Extreme capturing HDMI into a further Thunderbolt port

and after initially all setting up fine I started experiencing crashes - and those yellow playback flashes (the crashes weren't simultaneous with the yellow flashes, they seemed to be separate issues - the app began to crash seemingly at random, usually not long after launch.

- so I tried various things: swapping in different v5 builds into the same folder and launching (to preserve the presets I'd programmed etc.) and then in case that was contributing to the trouble I built a completely new show from scratch - but this too began crashing.

so eventually I dug out a dual head and switched to m466 and all seems well... feels like the old fashioned way

Sorry I haven't more detail for the crashes - heading into tech so it's just about making it work now But I could post another console / crash log if it's useful?

[samsc]

Yeah, 10.10.2

The system was:
- two PTDX100 projectors fed out of Thunderbolt ports via apple MiniDP to VGA adaptors
- programming monitor out of another Thunderbolt port and sent to an Adderlink X200 KVM
- Decklink Intensity Extreme capturing HDMI into a further Thunderbolt port

thanks-
please email me pdf profile from catalyst- running this version
it contains the crash logs-

[samsc]

please try n546 - it reduces memory use which seems to help flashing and glitching in low memory conditions

[tylerr]

What are you using for hard drives in this setup? What video resolution and codec are you testing at?

[tylerr]

So i blew up my first Mac Pro. Literally killed it with 4 screens looping 4K video for 24 hrs. On to #2. One think that i am seeing now that i am using the star tech active adaptors is that the screens do not ID correctly in the Catalyst software. For example Screen 1 is mapped to screen 1, 2 to 2, 3 to 3, and 4 to 4. If i switch 2 & 3 in the catalyst software they both now want to work on screen 2 and i can't assign anything to screen 3. I have tried a new set of preferences with no luck. I would think with the way you have set this up you wanted to allow us to fix a bad screen assignment by an easy software swap.

[samsc]

So i blew up my first Mac Pro. Literally killed it with 4 screens looping 4K video for 24 hrs. On to #2. One think that i am seeing now that i am using the star tech active adaptors is that the screens do not ID correctly in the Catalyst software. For example Screen 1 is mapped to screen 1, 2 to 2, 3 to 3, and 4 to 4. If i switch 2 & 3 in the catalyst software they both now want to work on screen 2 and i can't assign anything to screen 3. I have tried a new set of preferences with no luck. I would think with the way you have set this up you wanted to allow us to fix a bad screen assignment by an easy software swap.

dont change screens assignment in catalyst - it doesn't work

all screen setup and assignment needs to be done without catalyst running-
as OS makes all sorts of hidden changes

all screen setup and assignment is done by OS - in whatever order it chooses - not me - i can't control any of this

[samsc]

allow us to fix a bad screen assignment by an easy software swap

you just can't do this! OS controls everything

[samsc]

new build n561 posted