- January 19, 2007
- 791
- 741
- Home Country
- England
Ahhhhhhh, I get it sorry Kotik I should have read further on in that thread I linked...
I get one
Zap Mad Vr processing failed at 21:39
had to set LAV to Native
This time with Nvidia and not with Intel HD.
3D doesn't work on 90% of the times.
I get one
Zap Mad Vr processing failed at 21:39
had to set LAV to Native
This time with Nvidia and not with Intel HD.
3D doesn't work on 90% of the times.
No worries.
Btw all evening today not a single DXVA Interface error, good job @Sebastiii !!!!
I threw at my setup everything i had SD, HD, progressive, interlaced, not a single error, at least not today.
I will keep testing it.
P.S. Testing was done on v113 with 114 Core on top of it.
I get one
Zap Mad Vr processing failed at 21:39
had to set LAV to Native
This time with Nvidia and not with Intel HD.
3D doesn't work on 90% of the times.
It seems but not sure @100% :
When Tvservice crash : P1: TVService.exe P2: 1.15.0.0 P3: 5774016c P4: gboxplugin.dll
MP get stuck.
So when it will freeze for the next time, could you try to kill tvservice and restart it and wait that MP unfreeze ?
That was happening to me on DXVA2 native. May be you can try like that. On copy back was very stable
3D playback on copy back was unstable and many times didn't start in 3D.
Alex DXVA cannot be used during 3D playback (framepacked 3D), the reason is cause DXVA decoding of MVC is not implemented yet in LAV filter, so it doesnt matter what u select there for decoding,
the "intel H264mvc decoder" will be used and this one is a software decoder running on ur CPU.
So in other words, LAV will always switch to Intel MVC software decoding when u are playing true 3D material. SBS mkvs are not true 3D material, these will use DXVA.
U can confirm this by checking ur CPU usage while running a 3D movie.
Will you mind to check it back?