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. |
|
|
Thread Tools | Search this Thread | Display Modes |
4th May 2018, 19:28 | #262 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,374
|
|
30th December 2018, 13:14 | #264 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,361
|
I'm trying to load 32-bit plugins in avs+ x64 latest build 2772 without success, I put the content of MP_Pipeline 0.18 64 folder into plugins+64 and try to preview the next script with AvsPmod.v2.5.1_x64 (also tried vdub2).
Did more tests with other code explicitly loading x86 avisynth dll. Code:
MP_Pipeline(""" ### platform: win32 LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins+\JpegSource.dll") jpegSource("D:\Profiles\Usuarios\Administrador\Desktop\147.jpg",length=1) ### ### """) Code:
MP_Pipeline: Unable to create slave process. Message: Script error: Cannot load a 64 bit DLL in 32 bit Avisynth: 'C:/Program Files (x86)/AviSynth+/plugins64+/firstfoundplugin_x64.dll'. Last edited by Dogway; 30th December 2018 at 18:46. |
31st December 2018, 20:34 | #265 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,361
|
I have doing more tests and I'm still unable to mix 32 and 64 bit plugins.
Here's my clean scenario. Installed avs+ r2772 both x86 and x64, x86 through Avisynth Repository Current registry paths: Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth] @="D:\\Rip\\workshop\\Front_Ends\\AvisynthRepository\\AVSPLUS_x64" "PluginDir2_5"="D:\\Rip\\workshop\\Front_Ends\\AvisynthRepository\\AVSPLUS_x64\\plugins" "PluginDir+"="C:\\Program Files (x86)\\AviSynth+\\plugins64+" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avisynth] @="D:\\Rip\\workshop\\Front_Ends\\AvisynthRepository\\AVSPLUS_x86" "PluginDir2_5"="D:\\Rip\\workshop\\Front_Ends\\AvisynthRepository\\AVSPLUS_x86\\plugins" "PluginDir+"="C:\\Program Files (x86)\\AviSynth+\\plugins+" Code:
plugins+ folder: ConvertStacked.dll DirectShowSource.dll ImageSeq.dll MtModes.avsi Shibatch.dll TimeStretch.dll VDubFilter.dll plugins64+ folder: ConvertStacked.dll DirectShowSource.dll ImageSeq.dll MP_Pipeline.dll MP_Pipeline.dll.slave.exe MP_Pipeline.dll.win32 MP_Pipeline.dll.win32.slave.exe MP_Pipeline_readme.avs MtModes.avsi Shibatch.dll SmoothAdjust.dll TimeStretch.dll VDubFilter.dll This is my script loaded in AvsPmod 2.5.1 x64 from this link. Plugin Autoload Folder in AvsPmod is set to: C:\Program Files (x86)\AviSynth+\plugins64+ Code:
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") MP_Pipeline(""" ### platform: win32 imageSource("D:\Profiles\Usuarios\Administrador\Desktop\147.jpg") ### ### """) Code:
MP_Pipeline: Unable to create slave process. Message: Script error: Cannot load a 64 bit DLL in 32 bit Avisynth: 'C:/Program Files (x86)/AviSynth+/plugins64+/ConvertStacked.dll'. Code:
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") MP_Pipeline(""" ### platform: win32 ### dll: "C:\Windows\SysWOW64\AviSynth.dll" imageSource("D:\Profiles\Usuarios\Administrador\Desktop\147.jpg") ### ### """) Code:
MP_Pipeline: Unable to create slave process. Message: Unable to load "C:\Windows\SysWOW64\AviSynth.dll", code = 126 Last edited by Dogway; 31st December 2018 at 20:37. |
7th January 2019, 18:38 | #266 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
The combo works find for me (r2772 and MP 0.18). What program are you trying to load the script with? It looks like you're trying to load your script with a x86 (32-bit) program. This causes AVIsynth+ to try to load your 64-bit script in the x86 version and it fails.
Have you tried loading the script with the 64-bit version of VD2 or AVSmeter? |
7th January 2019, 18:51 | #267 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,361
|
My setup is posted above. r2772 yes, MP 0.18 yes 64bit AvsPmod, VD2, avsmeter64... and so on.
I had to fix the registries because AvisynthRepository was messing with them bad time but still no luck. Now they are: Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth] @="C:\\Program Files (x86)\\AviSynth+\\plugins64+" "plugindir2_5"="C:\\Program Files (x86)\\AviSynth+\\plugins64" "plugindir+"="C:\\Program Files (x86)\\AviSynth+\\plugins64+" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AviSynth] @="C:\\Program Files (x86)\\AviSynth+\\plugins+" "plugindir2_5"="C:\\Program Files (x86)\\AviSynth+\\plugins" "plugindir+"="C:\\Program Files (x86)\\AviSynth+\\plugins+" It can't even load an avisynth.dll Code:
### dll: C:\Windows\SysWOW64\AviSynth.dll MP_Pipeline: Unable to create slave process. Message: Unable to load "C:\Windows\SysWOW64\AviSynth.dll", code = 193 Last edited by Dogway; 7th January 2019 at 18:59. |
8th January 2019, 18:44 | #268 | Link |
Registered User
Join Date: Oct 2011
Posts: 275
|
Hello,
Not sure if it will help anything but I have both x86 and x64 version of avisynth, also on Win7 SP1 x64 , installed via the AviSynthPlus-MT-r2772.exe installer provided by pinterf here One thing that ticks me in your script is " LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") " Why program files x86 ?, the x64 version should be in "Program Files", the x86 version of avisynth is the one that should be in Program Files (x86), according to your reg entries the "plugins+" & " plugins64+ " are located at the same place for both x86 and x64 version, both in Program Files (x86), seems strange, unless i'm not seeing clear tonight it looks like both your avisynth installs are locate at the same place in program files x86 I checked and i do not have any "plugins64+" folder in the x86 version at "C:\Program Files (x86)\AviSynth+", only a "plugin+" folder is present there. My reg entries : Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth] @="C:\\Program Files\\AviSynth+" "plugindir2_5"="C:\\Program Files\\AviSynth+\\plugins64" "plugindir+"="C:\\Program Files\\AviSynth+\\plugins64+" Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AviSynth] @="C:\\Program Files\\AviSynth+" "plugindir2_5"="C:\\Program Files\\AviSynth+\\plugins" "plugindir+"="C:\\Program Files (x86)\\AviSynth+\\plugins+" Code:
MP_Pipeline.dll MP_Pipeline.dll.slave.exe MP_Pipeline.dll.win32 MP_Pipeline.dll.win32.slave.exe MP_Pipeline_readme.avs My x64 version of avisynth is installed at C:\Program Files\AviSynth+\ My x86 version of avisynth is nstalled at C:\Program Files (x86)\AviSynth+\ also with avisynth+ you don't need to call the Mp_pipeline dll at the start of the script , it is auto loaded so this line should not even be needed in the script. Tested also within the 2.5.1 x64 version of AvsPmod that is, unless i make an error, the same as yours, there again no need to use the " LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") ", only this to load a pic . Code:
MP_Pipeline(""" ### platform: win32 imageSource("F:\My Pic.png") ### ### """) Good luck, took me a while before getting MP_pipeline to work, hopefully the forum good souls helped me at this time Last edited by Yanak; 8th January 2019 at 18:47. |
8th January 2019, 19:10 | #269 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,361
|
Thanks for the help. I just preferred to have all my plugins in the same location for practical purposes, I investigated if this made a difference (like not taking advantage of 64bit features) and it seems it doesn't. The location of 64-bit executables is unrelated to their performance (despite some saying otherwise). BUT it could be MP_Pipeline wasn't designed in this particular way, I should have a look at what line 193 says in the source. I use MP_Pipeline since years ago, but recently just switched to avs+ x64 and after some hurdles this issue is pretty much the only thing irking me.
I'm finishing a project so I will have a deeper look in a few days. Maybe installing though the official installer this time. |
8th January 2019, 19:24 | #270 | Link |
Registered User
Join Date: Oct 2011
Posts: 275
|
I see, maybe it is not liking it this way indeed, i have not looked into the code plus I am not a coder so i don't know much more than this sadly.
The very last thing that come to my mind and might help figure out thing is in avspmod to only do this as script, without using the LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") that is not needed anymore with avs+ ( it is needed inside the win32 or win64 loops of mp_pipeline as this nice tool can't auto-load plugins sadly ), anyways : MP_Pipeline(""" ### platform: win32 Version() ### ### """) And after the same with win64 variant MP_Pipeline(""" ### platform: win64 Version() ### ### """) and see what the preview window returns you for the versions of avisynth+ it is using, this is if it managed to load anything at all with mp_pipeline. good luck |
8th January 2019, 20:55 | #271 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
I'm assuming you mean that the Universal Installer messed with your registry entries. That shouldn't happen if you set up the batch file correctly. Can you describe the problem in more detail?
__________________
Groucho's Avisynth Stuff |
8th January 2019, 21:59 | #272 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
try put those in plugins64 folder not the + one
Code:
MP_Pipeline.dll MP_Pipeline.dll.slave.exe MP_Pipeline.dll.win32 MP_Pipeline.dll.win32.slave.exe Code:
MP_Pipeline.dll MP_Pipeline.dll.slave.exe MP_Pipeline.dll.win64 MP_Pipeline.dll.win64.slave.exe and make sure that you dont use teracopy or whatever since it did some problems back then for my friend, to check that try to load avs dll using ### dll: from other location
__________________
See My Avisynth Stuff |
8th February 2019, 17:40 | #273 | Link |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,904
|
I just wanna report that Planar RGB 16bit (RGBP16) produces a green clip. Converting it back to yuv in the same block "solves" the issue.
Code:
MP_Pipeline(""" FFVideoSource("I:\Production\RAW\test8K.mkv") ### ### Crop(0, 0, -0, -630) ### ### AddBorders(0, 314, 0, 314) ### ### Spline64Resize(848, 480) ### ### trim(1081, 5220) ### ### ConvertBits(16) ### ### ConvertToPlanarRGB() ### ### Cube("C:\Programmi\AviSynth+\LUTs\void_null.cube", cpu=1, fullrange=false) Converttoyuv420() """) Code:
MP_Pipeline(""" FFVideoSource("I:\Production\RAW\test8K.mkv") ### ### Crop(0, 0, -0, -630) ### ### AddBorders(0, 314, 0, 314) ### ### Spline64Resize(848, 480) ### ### trim(1081, 5220) ### ### ConvertBits(16) ### ### ConvertToPlanarRGB() Cube("C:\Programmi\AviSynth+\LUTs\void_null.cube", cpu=1, fullrange=false) Converttoyuv420() ### ### """) |
21st October 2019, 18:00 | #275 | Link |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,904
|
Any chance for someone to pickup the project, work on it, make it Avisynth+ compatible (modern high bit depth formats) and support audio?
It would be a very good thing to have it working properly. It's been years since the last release... Even just audio support would be a big plus. |
21st October 2019, 18:39 | #276 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
22nd October 2019, 08:42 | #277 | Link | |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,904
|
Quote:
It could be because of plugins that have not been ported yet or perhaps because of people having dual boot OS which includes a relatively modern x64 OS and an x86 one. I've seen many people having Windows 7 x64 and XP x86. I myself have Windows 10 Pro x64, however I still have my Win XP x86 machine up and running and having completely separate workflows (x86 and x64) would be a compatibility nightmare 'cause I know that x64 variants may be slightly different. Besides, it's still very common to switch between Avisynth versions, that's why Groucho's Universal Avisynth Installer was very welcome when he released it. In other words, having x86 filters loading inside x64 Avisynth or Avisynth x86 being able to allocate more than 2 GB of memory it's still very useful, especially in a world where high bit depth and ultra high resolutions are common. An example? Satellite feeds in FULL HD are still interlaced, but you would almost definitely run out of RAM if you use QTGMC on a x86 system. And... sure, there are other deinterlacers like tdeint, yadif, Bob() itself and so on, but they're beyond what I'm trying to say here. What I'm trying to say is that we're not living in an utopia in which everything is x64, perfectly multi-threaded, 16bit planar and we're living in a nirvana. Just look at 16 bit stacked and interleaved: years and years after the planar regular high bit depth support inside avisynth, stacked and interleaved are still very much alive due to the lack of compatibility with some older plugins that have never been ported. Anyway, that's my opinion on why it's relevant. |
|
22nd October 2019, 12:22 | #278 | Link | |
Registered User
Join Date: Feb 2012
Posts: 82
|
Quote:
It just takes sometime to set it up for your system and your script. And yes you can still include audio outside the pipeline script, which works well. Not ideal but better than nothing. |
|
22nd October 2019, 13:42 | #279 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
aside from that adding avs+ high bit depth support should be in C api (like x264, ffmpeg and avspmod) to avoid losing older avs support since mpp can load different avs in every block by ### dll: path
__________________
See My Avisynth Stuff |
|
22nd October 2019, 15:09 | #280 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,374
|
Quote:
I've had 80-90% slower with mp_pipeline |
|
Tags |
avisynth, multi-process, pipeline |
Thread Tools | Search this Thread |
Display Modes | |
|
|