Wish List

[Tom Graham]

Originally Posted by Stereo Missile

Hi Drew,

Not yet, only on the DUC here. It was suggested that I should use my support code to report the bugs, but I think that's a bit unfair, I'd like to keep my support code for if or when I actually need support!

I will give the guys from Avid Australia a call when I get a chance to discuss, they have been very helpful.

Is anyone else experiencing these bugs?

BTW I still love the console, its awesome! Every new high tech product is bound to have a few teething issues to begin with, the important thing is that they get fixed.

:)

Steve - you have a full year of support included with your S6. If you feel you have a bug, call it in and get the support crew started on solving the issue - it helps other people as well to use the official channels.

Thanks,
Tom

[Stereo Missile]

Originally Posted by Tom Graham

Steve - you have a full year of support included with your S6. If you feel you have a bug, call it in and get the support crew started on solving the issue - it helps other people as well to use the official channels.

Thanks,
Tom

Thanks Tom,

As it turns out so far these bugs have been ironed out by the PT 1.2.2 and S6 1.3 update, fingers crossed! I have a new issue with the S6 though, which I have spoken with Stuart at Avid Australia about and he is looking into it.

On startup of the S6, the display modules are loading up with the "wireframe" graphics ready for display, but are then unresponsive. When I go into the "Surface" page on the S6 master module, the display modules are coloured red indicating they have crashed. After I then reboot them manually from the surface page everything is fine. It's not a huge deal in terms of loss of function as it only takes a minute to reboot them at the start of the day, but something I thought you guys should know about so you can investigate. Anybody else had this issue?

Stuart suggested we may need to re-image the drives on my display modules. i tried redoing the update process for the modules but the problem still persists.

Thanks again!

Cheers,

Steve :)