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. |
26th August 2014, 02:06 | #821 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
Quote:
And for obviousness' sake, you did already run the video through DGIndex or ffmsindex, right? The .d2v/.ffindex files do exist, is what I'm saying. Last edited by qyot27; 26th August 2014 at 02:09. |
|
26th August 2014, 03:19 | #822 | Link |
Registered User
Join Date: Jul 2014
Posts: 55
|
I'm talking command line x264 it works just fine. Yes, I did run them through those 2, one is a DVD and the other is a Bluray. The .d2v/.ffindex were made before I installed AviSynth+ though but it should be unrelated. I can open the files just fine for previewing with 2.6.0a5 MT but AviSynth+ just doesn't play nice for some reason. I was hoping to take advantage of some of AviSynth+'s features once I could actually load a video but so far even running those import lines by themselves causes both programs to hang.
|
26th August 2014, 21:14 | #825 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
Quote:
mpv is a media player: http://mpv.io Like most/all mplayer variants, it's typically started from the command line: Code:
mpv test.avs How are you switching between the 2.6 MT and AviSynth+ dlls? How did you install AviSynth+? If it was from the .7z file, did you also install the MSVC 2012 Runtime? Put DGDecode and FFMS2 in AviSynth+'s plugins folder and remove the LoadPlugin lines from the scripts - does that do anything? |
|
26th August 2014, 22:36 | #826 | Link |
ангел смерти
Join Date: Nov 2004
Location: Lost
Posts: 9,558
|
Try Process Explorer, as well. You can open up the process and look at the threads, where you might see which plugin is the one that isn't initializing properly. If it's not using any CPU, that probably means you hit a deadlock, though, which would be weird to see consistently. If all the cpu is in avisynth.dll itself, then you might have to get Visual Studio Express and compile it yourself with debugging on to find out why (ugh), since the Avisynth+ installers don't include debugging info.
|
17th September 2014, 02:39 | #828 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
17th September 2014, 10:21 | #829 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Replace the avisynth.dll and the devil.dll in SysWow64 with the files from this archive. |
|
17th September 2014, 12:36 | #830 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
17th September 2014, 12:47 | #831 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Edit: The only "official" version is the one on Sourceforge. All other flavours (SEt's MT, my ICL build, AVS+) can be used and are probably just as stable in most cases. Last edited by Groucho2004; 17th September 2014 at 12:50. |
|
17th September 2014, 13:07 | #836 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
17th September 2014, 15:13 | #837 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
Quote:
Although for that matter, anyone that takes a look at AviSynth's development history will see very quickly that things have always been a bit scattershot with the main development. The developers involved often change a lot between the different trees that sprouted up - the original BRG version, the patched versions in the 1.0 series after BRG left (various authors), the development on 2.0 and 2.5.0-2.5.5 (sh0dan, et al.), 2.5.6-2.5.8 and 2.6 (increasingly IanB) are all technically distinct dev branches - 2.0-2.6 simply had the benefit of a single main repository, and just changed lead developers. Had AVS3.0 not died back in 2007, it would have exhibited the same properties - the devs in charge of it were different too, and the SVN repo for it was separate from the CVS repo for 2.0-2.6. 2.5/2.6 only coalesced as 'official' because it became widely used and was updated consistently for a few years, not because the devs that worked on it have a steering committee that gets to decide what 'official' is over the entire AviSynth ecosystem, only in the context of their own branches. AviSynth+ is hardly a deviation from that, and has its own 'official' (or more accurately, 'stable') builds - currently 0.1 r1576, with 'unofficial' ('dev') builds from the main/MT branch, which is up to r1699. |
|
17th September 2014, 16:20 | #839 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
24th October 2014, 21:58 | #840 | Link |
Registered User
Join Date: Mar 2012
Location: Saint-Petersburg
Posts: 239
|
Is it dead or alive? o_O
In other words, if I think I found a bug - should I try to fix it myself or post here and wait for support? === Short version of issue is: x64 MT version of AVS+ doesn't free memory so if I want to run some memory consuming script inside MPC-HC x64 + ffdshow x64 it will eat some amount of memory on each seek. enter simple script into ffdshow: Code:
SetFilterMTMode("",2) SetFilterMTMode("ffdShow_source",3) ffdShow_source() BilinearResize(3000,1500) BilinearResize(1920,1080) Prefetch(10) === and it's not an issue with 32-bit version
__________________
SVPflow motion interpolation Last edited by chainik_svp; 24th October 2014 at 22:15. |
Thread Tools | Search this Thread |
Display Modes | |
|
|