I'm well used to the Adrenaline latency, but I remember SN being a bit snappier. (v1.7.7 on ISIS)

Even with playlength on it takes about 1.5 secs to respond to a play command - turning render on the fly off seems to help it (as does rendering all effects) but it's still like a soggy bit of string to edit with.

Also every time I hit play the blue position line leaves a ghost where it was. Corrects itself if I resize timeline or switch to a different app and back.

'Core unable to do' - had a few of those today, a room down the corridor was plagued all day with these.

I'm supposed to put my Symphony Nitris on our ISIS Friday would you recommend holding off ?

we're dropping frames laying back to tape from ISIS/Interplay with our Symph/DS Dual Boot Systems.

DNxHD 145 (video media on local storage), but ISIS connection active to view sequence at offline resolution for reference.

disabling the network connection to ISIS solves the issue - haven't bothered to check if operating wholly from the ISIS does.

known issue. currently being escalated at Avid. unless you absolutely need to, i would wait.

are you running SD or HD? which codecs?

Overall using SN in SD on ISIS has been OK. One place I work is 2:1 OMF (with occasional 15:1s MXF after a reboot for some reason) another uses MPEG50 MXF with other resolutions disabled. The latter has Interplay too for some jobs. Both have some issues, but no show stoppers that I am aware of.

Frame chase editing using Interplay is very cool if you have tight turnaround.

Depends on what you need to do

Dropped frames are occurring here with all flavors DNxHD --  1080p/23.98 & 1080i/59.94  as well as SD 1:1.

We use our local drives on the Symphony, so no high resolution media is used via ISIS & Interplay, at least not yet.

I always disable the network connection to ISIS after I have referenced the offline for the master conform. When that connection is enabled, dropped frames occur during both normal playback and DigitalCut, no matter the resolution from the local drives, not ISIS.

FWIW.

Brian

OK further to this... The more effects and layers in the sequence the soggier the piece of string becomes. I duplicated the sequence back into itself a number of times and it would take up to a minute to respond to play or stop command.

I am suspecting the fact that we are using 2:1 (MXF) rather than 1:1 is giving the processors lots to do.

Playlength command improves everything enormously also.