using srestore with with DGDecNV & avisynth MT

[crasus]

Dear friends,

I've been trying to use the MT function to wrap srestore in a script I'm currently using but for whatever reason I just keep getting strage errors.

Using SET's avisynth MT 2.5.8 (x86) with the latest srestore (+additional filters) & DGDecNV 2023 on a quad-core cpu.

The same thing happens upong trying to decode with DSS2 (CoreAVC Pro 2.0 being the default decoder).

Current script is :

DGSource("J:\x.dgi")
TDeint(mode=1, order=1)
MT("""
srestore(frate=23.976)
""",4,4)
crop(6,2,-4,-2)
spline36resize(1280,720)

Basicly I want the source to be decoded via the GPU and the rest to use the CPU.

AVSP desplayed error when trying to preview :

http://img689.imageshack.us/img689/8054/clipl.png

Any ideas as to what I'm doing wrong and if what I'm trying to achieve is possible would be greatly appreciated.

Thank you!

[Didée]

I'm not quite sure what that error is or why it comes up, but in any case, it's a particularly bad idea to use the MT() filter with Srestore. Srestore basically is a decimating filter. When the source is split spatially, then it could happen that different parts get decimated differently, which would result in slices from different input frames being combined into one output frame. Imagine that.

Srestore IIRC works correctly with SetMTmode(), that should be OK. But don't use MT().

[crasus]

Thank you Didée,

I did try to use SetMTMode() but that didn't work quite right as well. I had used mode 3 for the decoder (doesn't sound like a good ideea now since it's GPU based...) and mode 2 for the rest. Worked like a charm till about 14% at a wonderfull 8.5fps (x264 encoding) than suddenly dropped to 3.2fps & 30-35% CPU utilization.

Any hints toward how I should edit the script? Much appreciated.

[Didée]

Try mode 5 for the source filter. Also, check in Taskmanager if there's any sign of a memory leak.

[crasus]

I edited the script and tryied according to your suggestion. Yet again, the same thing happened. Up till some 9-10% of the encoding process in x264 it worked with 100% CPU usage and 8-9fps, than it dropped to 3.29fps and 23-24% CPU usage (according to task manager). Memory usage has stayed within 600-850Mb (by x264).

If it helps in any way, system is i5 750, 8Gb DDR3, running on XP 64bit.

Update : It seems that the progress of the encoding has dropped the no of fps even more to 2.29fps. The used memory by x264 has also increased to ~1Gb, than dropped to 200Mb...

[levi]

I agree with didee. If you want to use MT with srestore, you need to use setmtmode & invoke it after the decimation. Don't think you will see a dramatic difference, but try this:

DGSource("J:\x.dgi")
TDeint(mode=1, order=1)
srestore(frate=23.976)
SetMTmode(3,0) # or SetMTmode(2,0) if 3 works & you want to try to make it faster
crop(6,2,-4,-2)
spline36resize(1280,720)

[crasus]

Didée, upon trying the said script with DSS2 (CoreAVC) this time & SetMTMode(2,4), x264 has reached 26.2% of the encoding process, with 2.94fps & 2Gb of ram used ... Than simply stopped at some 34%.

[Blue_MiSfit]

that sounds like a memory leak. 2GB of RAM is the 32 bit process limit, so if you're anywhere near that you're out of RAM :(

Try this:


SetMemoryMax(512) #play with this number
SetMTMode(5)
DGSource("J:\x.dgi")
SetMTMode(2)
TDeint(mode=1, order=1)
spline36resize(1280,720)
srestore(frate=23.976)
crop(6,2,-4,-2)