We purchased the new Symphony Nitris DX 3.0 when it was released and since day one we have had one very annoying problem with the system. Everytime we render a sequence it renders pixelerrors into the top of the image. The only way to avoid this is to tell the Symphony to render using only the software and bypassing the DNA. We do this by writing a command in the console.

Everyone else I've talked to, who also owns the new DX system, is experiencing the same problem. I would assume Avid were giving this issue high priority but they haven't released an update since the release of the system. The Bug has been repoted to our local Avid office. Any comments from the Avid development team regarding this?

Avid Symphony Nitris DX V. 3.0

HP XW8600, 4 gig Ram, Win XP Pro 32

 Let me make sure they have this covered. Could you please tell us the type of project, the resolution and the frame rate please? How was the footage aquired? How was it ingested?

I've been cutting on a Nitris DX since Beta and haven't seen this (I'm on a Mac though) so let's make sure it's something Avid knows about.

This error occurs in every project type we have used: HD 1080 50i, SD PAL 25P, SD PAL 50i.

The formats we have used 15:1 - DVCAM DV25 420 - 2:1 - 1:1 - 1:1 10b - XDCAM HD 720p 25 - DNxHD 185 x - XDCAM HD 1080 50i.

Ingested using SDI in: 15:1 - 2:1 - 1:1 - DNxHD 185 x

Ingested using firewire: DVCAM DV25 420

Imported as MXF from hard drive: XDCAM HD

An important note: Some of these projects was originally cut in our MC Adrenaline suites, using the same projects, media etc. without any problems at all.

Let me know if you need any additional info.

Thanks

Michael

Storage?

 We have tried using a Lanshare EX 4.1.5 and local LVD and Quietdrives.

 Btw. we have also tried a couple of different Nvidia drivers, but no changes so we installed the recommended driver version again (don't remember which version that is).

As soon as we bypass the DNA render, it renders fine. But we have to run the command each time we have restarted the app. Very annoying when you realise you forgot to type in the command before you started the rendering over night

Ok, I've sent it up to Avid. We'll see what they say. Any chance you can post a screen grab so we can see what you are talking about? 

 Actuallly, it isn't possible to make a screen grab of the error because the error only shows on the ext. monitor (sdi output) and NOT in the preview window in the Symphony. Sorry, I should have mentioned that from the start, but somehow I didn't think of it.

To sum up: The error occurs only in rendered material. In every resolution, format and framerate. It only shows on the ext. monitor and not in the Symphony previewmonitor.

However, I will take a photo of the ext. monitor by monday when the suite is available.

I appreciate the help, thanks! 

 This issue was fixed by the new 3.0.5 upgrade

But thank you guys for your help

Regards

Michael