HDV M2T files play laggy 9.40.4896

[createmedia]

Project 1920 by 1080 50p.

Event recording.

Main Camera Sony FS7 set to 50p XAVCL 4:2:2.

The audience cam Sony Z7 was an HDV camcorder with a CF card writer.

Recording 1440 by 1080 50i M2T files.

With Edius 9.40 latest I did not expect the CPU's to go at maximum trying to play the M2T footage back as I have done this in 50p projects before in earlier versions of Edius.

The main camera audio breaks up (not playing in real time) when those M2T clips are above V1 on V2

The XAVCL 4:2:2 50p footage is playing back perfectly.

What's changed?

Mike

[antonsvideo]

can you make sure that you have not set optical flow as a default, because this would slow things down drastically and optical flow will kick in in your case because of using different frame rates in the same project

[Liverpool TV]

Hi Mike.

If Anton's suggestion isn't the solution, are you using the system specs in your signature? I only ask as I'm unfamiliar with those CPUs and don't know if they are QS capable.

I have a fairly powerful older system that struggles with certain codecs as it's not got QS. While your Z7 is likely to be MPEG2 from what I can remember, your FS7 is h.264 and would be helped by QS.

Maybe you have QS but it's not active?

Cheers,
Dave.

[createmedia]

Not using optical flow, M2T footage plays laggy in player window with CPU's at 100%.

System 4 in signature

No, CPU's are not QS capable

Yes the Sony Z7 footage is MP2 1440x1080 anamorphic 50i in Project 1920 by 1080 @ 50p plays Laggy CPU's @ 100%

Sony FS7 XAVCL 50p 1920 x 1080 plays perfectly OK with 5 layers: video plus title and on screen graphics inserts [email protected]% when buffer filled.

This used to work ok

Mike

[trillium]

My experience in Edius before I had QS enabled was what you have described. Until I got QS enabled on my system, converting MTS files to the Grass Valley HQ and HQX formats stabilized my timeline. It's a workaround with little or no loss of quality. Sorry if my response is an apples and oranges comparison.

[createmedia]

Hi Trillium

Those of us with Xeon sytems can't enable QS.

System 4 CPU's are clocked at 2.3GHz base (2.8GHz turbo speed)

In Daum PotPlayer on the Desktop playing the M2T files back the CPU's are only at 2.3% but in Edius both CPU's were at 100%, but there is no frame size conversion going on live or bit depth conversion the Daum player is playing the original file "as is".

Setting up a test Project on system 4 as 1920 50i 10Bit system 4 plays back the M2T footage with the CPU's at 10% once the buffer is full.

So what happens in Edius WG 8 on a much slower dual Xeon PC? (8 logical cores as opposed to 64 but clocked at 3.4GHz)

Same project settings 1920 x 1080 50p 10 Bit. in 10Bit CPU's 80% when buffer is full but plays fine, 8Bit (using the Rec Window drop down) 48% CPU.

Hmm.... those gremlins again! After a fresh boot today system 4 is working as expected. In 8Bit 50p CPU's are at 48% and 52% in 10Bit What all that struggling was about I don't know - unless Edius was tied up drawing the audio wave forms - there is 6 hours of XAVCL and 6 hours of M2T files. I wonder if that was it?

Mike

[trillium]

Wish I new, I'm a bit of a novice when analyzing complex system behaviors. My problems in Edius started suddenly and unexpectedly after the new system had been up and running a few months but was easily "fixed" after some crash analysis by members here and the ongoing discussions about QS.

[tingsern]

Hi Trillium

Those of us with Xeon sytems can't enable QS.

System 4 CPU's are clocked at 2.3GHz base (2.8GHz turbo speed)

Mike

I am a bit puzzled here - my P72 laptop has an Intel XEON CPU - but I have no issues with QS - it is working fine here.

[antonsvideo]

I am a bit puzzled here - my P72 laptop has an Intel XEON CPU - but I have no issues with QS - it is working fine here.

His PC does not have QS, he is using an X series mobo/CPU and as such, there is no QS, my PC also has no QS

[BernH]

I am a bit puzzled here - my P72 laptop has an Intel XEON CPU - but I have no issues with QS - it is working fine here.

For QS to work, the CPU has to have an integrated GPU core and the motherboard has to support it.

Most XEON's don't have a GPU core, but a few do, such as some of the laptop XEON's

[tingsern]

Thank you. I was not aware of that. I thought all Intel CPUs should come with a low level GPU these days :-).