Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
20th April 2016, 08:42 | #1402 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
'Kay well I gave 1847 a shot but it just crashes MPC_BE x86 (build 1417) instantly with exception code 0xc0000005 when passed through ffdshow (4533) Even with nothing in the Avisynth field it still happens. No problems with Avisynth-MT.
|
20th April 2016, 09:36 | #1403 | Link | |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,308
|
@pinterf
First, thanks for your work, i think a lot of people appreciate what you did, even if they stay silent. And... Do you think, by any chance, you can take a look at this issue, if it can be fixed ? You can see the whole thread here, but the most important point is this information : Quote:
|
|
20th April 2016, 11:17 | #1405 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
Quote:
And thank you, I like silence only when it means that things are working fine. |
|
20th April 2016, 15:00 | #1409 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
Finally someone who puts his butt into use. I'll do some testing of replacing AVS 2.6 with this version for encoding and let you know how it goes. The previous version wasn't working with all filters. According to my first tests, however, it seems that L-MASHSOURCE lags on some videos, even when CPU isn't fully used, whereas with 2.6 it worked fine. This would require more testing to see where that's coming from. |
|
20th April 2016, 16:04 | #1410 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Does it actually work? I gave up on MT Avisynth a long time ago. I couldn't get satisfactory results no matter how I tweaked the settings for FHD material. It would crash well before you could encode an entire ~2 hour movie with it. I had much better luck using MP_Pipeline to separate different high CPU usage filters into their own threads. Using MP_Pipeline and splitting the source across several simultaneous lossless intermediate files (usually 4) that were joined and then encoded worked best for me.
IE: If I have a 100,000 frame source, I generate a lossless intermediate file from 0-25010, another from 24990-50010, another from 49990-75010, and another from 74990-100000. I would do that with four simultaneous Virtualdub jobs each generating an AVI file. Trim the overlap areas in an AVIsynth and use that to do my 2 pass x264 encode. |
20th April 2016, 16:37 | #1411 | Link |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
For me AviSynth 2.6 MT has been working well. Perhaps there are a few filters that are more unstable with MT but those I use were working well. This AviSynth+ appears to be very stable so I'm sure it will work fine although I have to try first. The previous version of AviSynth+ MT wasn't working with some filters such as NNEDI3.
|
20th April 2016, 17:46 | #1412 | Link | |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Stereodude,
You are recommending Overlap again despite your acceptance that it is unnecessary, here (final edit):- http://forum.doom9.org/showthread.ph...39#post1714239 EDIT: Quote:
EDIT: The "MakeMultiPartScripts.avs" script given earlier in that thread generates multi-part scripts to avoid making mistakes in your Trim frame numbers. [EDIT: Post #15 in that thread]
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 20th April 2016 at 17:57. |
|
20th April 2016, 18:14 | #1413 | Link |
Registered User
Join Date: Apr 2008
Posts: 1,106
|
Hi, I tried avisynth+ a few times in the past and have just put together a new PC and am wondering is it worth using it for SVP usage performance wise or not now with the latest versions? If theres a significant performance difference I will look at the steps to get SVP working with avisynth+ instead of Sets MT version of avisynth.
|
20th April 2016, 18:22 | #1414 | Link | |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Quote:
Last edited by Stereodude; 20th April 2016 at 18:26. |
|
20th April 2016, 18:32 | #1415 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Yep, I keep a close track on all of your posts just so I can do a little nit picking
Nah, I was gonna point out that thread and discovered (to my joy and delight) that it was you who was on the other end of conversation, hehe. My previous favorite similar lil ol correction was in this post:- http://forum.doom9.org/showthread.ph...22#post1729222 EDIT: In response to fvisagie.
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
20th April 2016, 19:20 | #1416 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
http://www.svp-team.com/forum/viewtopic.php?id=3270 I find it to be the fastest and most stable so far. Memory usage is TWICE LOWER. As for the videos that would lag with L-SMASH Source, playing with the threads fixes it. In fact, I am now able to use LWLibavVideoSource for real-time playback without using MT. MT wasn't recommended for this plugin but it was the only way to prevent lag according to my test. With AviSynth+, no MT works perfect So far. I'll have to try with a wider variety of videos. |
|
20th April 2016, 21:05 | #1417 | Link | |
47.952fps@71.928Hz
Join Date: Mar 2011
Posts: 940
|
Quote:
I'll have to dedicate some time to getting AVS+ set up again (Groucho's switcharoo setup). I'm currently still using 260_MT to play. I remember liking old AVS+ for awhile, but for non-SVP things, it was naturally unstable to use in AvsPmod (even with updates to APM).
__________________
Win10 (x64) build 19041 NVIDIA GeForce GTX 1060 3GB (GP106) 3071MB/GDDR5 | (r435_95-4) NTSC | DVD: R1 | BD: A AMD Ryzen 5 2600 @3.4GHz (6c/12th, I'm on AVX2 now!)
|
|
20th April 2016, 21:05 | #1418 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
Do not fear of MT mode and use 64 bit, there may be more x64 filters than you would think before!
If you have enough memory, don't limit your script using it, even if avs+ occupies much less memory footprint than at the beginnings. You can test the peak memory need with SetMemoryMax(bigvalue) and watch AvsMeter/AvsMeter64. As for MT, set default mt mode to 2, for source filters 3, Prefetch(8) then rock'n'roll. OK, fps-wise on my i7 processor Prefetch(7) or Prefetch(8) is not scaling well compared to Prefetch(6), but is still faster a bit. This night an AVS+ x64 with SetMemoryMax(6000), UHD (3840x2160) colorbars + QTGMC(Fast) + Prefetch(8) is trying to kill my PC in the office. (Fast i7 with 8G RAM, now it's at more than 4 fps and is working hard at 80% CPU since 3 hours). Wondering, at what memory consumption would this UHD source script stabilize itself if I didn't put that 6G limit. So, which volunteer has 24G RAM? That should be more than enough for the test I think. Last edited by pinterf; 20th April 2016 at 21:09. Reason: typo |
21st April 2016, 00:21 | #1419 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
Quote:
As CPU usage goes it's very close for me just using a couple of filters, the dynamic CPU clock almost looked to be a touch lower. Might be time to finally give 64 bit a go. Gave it a shot and get instant crashes on playback. Replaced AVS+ with the 64 bit version, ffdshow 64 bit, MPC-BE 64 bit with the 64 bit VS2015 redistributable installed also. Removed all filters and it still crashes. Last edited by ryrynz; 21st April 2016 at 02:47. |
|
21st April 2016, 04:10 | #1420 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
Ok. So at least one component needs polishing. It is 2016 now, 64 bit things should work*. We can exclude the redistributables Remains: avs+, a remaining filter, source filter, mpc, ffdshow, interaction between them
*or let's be sarcastic: it's 2016 now, higher than 8 bit color spaces should be supported natively in the whole workflow.... er ...not for current avisynth. But we should think about it seriously. Opinions? Biggest obstacles? I know there is VapourSynth with plenty of high-bit-depth filters, but I'd like to have spare batteries also |
Thread Tools | Search this Thread |
Display Modes | |
|
|