Rupert, thanks for the offer, I was still there at 7 in the morning! I hear the situation has been mitigated by connecting the nearline to a 3gb/s switch and upgrading the z840s to v7s. I was at Evos so maybe you have a relationship with them?
I'm not very familiar with networking ins and outs, would it be a bandwidth thing that was bottlenecking the switch or just a flakey switch? Network monitor suggested about 16MB/s usage whilst transcoding the video portion, more with audio. Time to take some courses. You guys don't do any do you?
Andi
To: Avid-L2@yahoogroups.com; kwikpasta@hotmail.com
From: Avid-L2@yahoogroups.com
Date: Tue, 16 Jun 2015 06:30:05 +0000
Subject: RE: [Avid-L2] OT: Monitoring network connectivity...
To: Avid-L2@yahoogroups.com; kwikpasta@hotmail.com
From: Avid-L2@yahoogroups.com
Date: Tue, 16 Jun 2015 06:30:05 +0000
Subject: RE: [Avid-L2] OT: Monitoring network connectivity...
Andi
One in the morning ? Ouch.
Give us a call – I think we may be able to help; depending on where it is you are working, of course ;-)
Rupert Watson
+44 7787 554801
www.root6.com
From: Avid-L2@yahoogroups.com [mailto:Avid-L2@yahoogroups.com]
Sent: 16 June 2015 01:04
To: Avid-L2@yahoogroups.com
Subject: [Avid-L2] OT: Monitoring network connectivity...
I'm getting an error that I've seen before but never got to the bottom of.
Scenario is I am transcoding multiple 2 hour long EVS streams to 15:1s Avid media. The rushes are XDCAM 50mb/s mxfs stored on nearline storage and I'm transcoding to an ISIS 5500. I'm using 3 HP Z840s with 32GB RAM in each. Avid version is 6.5.4.6. There is plenty of space on everything.
I keep getting the error "Exception: SWCompCvtr::ReleaseLocateBuffer timed out waiting for compressor to stop". The transcode crashes out and I have to start again. It seems random and sometimes the clip that previously crashed will go through fine with the next attempt.
I'm at a large facility and the rushes are stored on a nearline server which I have mounted as a Network drive. I'm beginning to wonder if it's not an Avid problem at all but rather that their network is a bit dodgy and is possibly losing it's connection thus interrupting Avid's transcode and causing the crash.
Is it possible to produce a log of any problems that a network might experience in order to cross reference timings with transcode crashes? I won't be doing this but I want to suggest it to them for the morning (night shift, freelance) to see if it's the problem. Does anyone feel this is a possibility? Or has anyone encountered this issue before and solved it?
Andi
http://www.root6.com/blog/
For all our latest news and info as it happens-
Registered in the UK at: 4 Wardour Mews, London W1F 8AJ
Tel: +44 (0) 20 7437 6052
Company No. 03433253
[Non-text portions of this message have been removed]
One in the morning ? Ouch.
Give us a call – I think we may be able to help; depending on where it is you are working, of course ;-)
Rupert Watson
+44 7787 554801
www.root6.com
From: Avid-L2@yahoogroups.com [mailto:Avid-L2@yahoogroups.com]
Sent: 16 June 2015 01:04
To: Avid-L2@yahoogroups.com
Subject: [Avid-L2] OT: Monitoring network connectivity...
I'm getting an error that I've seen before but never got to the bottom of.
Scenario is I am transcoding multiple 2 hour long EVS streams to 15:1s Avid media. The rushes are XDCAM 50mb/s mxfs stored on nearline storage and I'm transcoding to an ISIS 5500. I'm using 3 HP Z840s with 32GB RAM in each. Avid version is 6.5.4.6. There is plenty of space on everything.
I keep getting the error "Exception: SWCompCvtr::ReleaseLocateBuffer timed out waiting for compressor to stop". The transcode crashes out and I have to start again. It seems random and sometimes the clip that previously crashed will go through fine with the next attempt.
I'm at a large facility and the rushes are stored on a nearline server which I have mounted as a Network drive. I'm beginning to wonder if it's not an Avid problem at all but rather that their network is a bit dodgy and is possibly losing it's connection thus interrupting Avid's transcode and causing the crash.
Is it possible to produce a log of any problems that a network might experience in order to cross reference timings with transcode crashes? I won't be doing this but I want to suggest it to them for the morning (night shift, freelance) to see if it's the problem. Does anyone feel this is a possibility? Or has anyone encountered this issue before and solved it?
Andi
http://www.root6.com/blog/
For all our latest news and info as it happens-
Registered in the UK at: 4 Wardour Mews, London W1F 8AJ
Tel: +44 (0) 20 7437 6052
Company No. 03433253
[Non-text portions of this message have been removed]
__._,_.___
Posted by: Andi Meek <kwikpasta@hotmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
this is the Avid-L2
.
__,_._,___
No comments:
Post a Comment