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. |
12th September 2017, 18:12 | #3623 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
The "Universal Installer" hosts 7 different Avisynth versions from which you can choose via batch file. Switching from one version to another is very simple. Even if you don't want to play around with various versions, the installer has the latest AVS+ version and you don't have to mess around with copying files to the system directories.
The r2294 installer is a "classic" installer which only installs AVS+. |
12th September 2017, 18:25 | #3624 | Link | |||
Registered User
Join Date: Jan 2012
Posts: 104
|
Quote:
Quote:
Quote:
|
|||
19th September 2017, 11:41 | #3625 | Link | ||
Registered User
Join Date: Jan 2012
Posts: 104
|
How to convert RGB48 to YUV ?
Quote:
When doing output of z instead of x: 1. there is an error message in AvsPmod "Error trying to display the clip..." 2. When encoding with RipBot264 I get strange colors and the video shows only the left half (stretched) of original tif picture. In info it says for z: colorspace=YUV444P16 So I assume there is one problem in AvsPmod and another one in Avisynth+. Edit1 Insert Quote:
Last edited by george84; 19th September 2017 at 15:58. Reason: Edit1 |
||
19th September 2017, 16:59 | #3626 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
As for ripbot, no idea. Can it even encode 444P16?
__________________
Groucho's Avisynth Stuff Last edited by Groucho2004; 19th September 2017 at 17:12. |
|
19th September 2017, 18:10 | #3627 | Link | |
Registered User
Join Date: Jan 2012
Posts: 104
|
Thank you for fast response. It is really AvsPmod which confused me.
Actually I need 10 bits. So I inserted Quote:
I now did the encoding without RipBot, reimported the result with vapoursynth to check the precision of colors. Everything is perfect. For further work and test, I plan to use AvsPmod and on the very last output statement I will create a stack. I have huge avs scripts and want to adapt them for Rec2020 and high bit depth. I was evaluating vapoursynth but currently prefer Avisynth+. |
|
19th September 2017, 20:34 | #3628 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,810
|
In case if you need simple installer here is my installation script.
http://www.mediafire.com/file/489x44...T_Installer.7z
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
20th September 2017, 07:45 | #3629 | Link | |
Registered User
Join Date: Jan 2012
Posts: 104
|
Access violation in AVSMeter
Quote:
Problem is not important for me. |
|
20th September 2017, 08:00 | #3630 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,773
|
Might be placed better in the thread for AVSMeter if it is specific (well, leave it here, no need to double) ... but the author (Groucho2004) would surely be interested in the script, possibly as well in the output of "AVSMeter -avsinfo" (which checks DLL dependencies first).
|
20th September 2017, 08:35 | #3631 | Link | |
Registered User
Join Date: Jan 2012
Posts: 104
|
I didn't find AVSmeter thread. Here is output of -avsinfo. Script > 1400 lines. So would be difficult to isolate error.
Quote:
|
|
20th September 2017, 09:13 | #3633 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,773
|
|
20th September 2017, 10:25 | #3634 | Link |
Registered User
Join Date: Jan 2012
Posts: 104
|
Continued in thread » AVSMeter 2.6.5 «
|
1st October 2017, 04:20 | #3635 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
So in the interest of trying to resolve this issue that's been (at least partially) holding up the Linux work, here's a few builds:
FFmpeg r87486 FFMS2 C-plugin r1145+104 AviSynth+ r2510 (VS2017) AviSynth+ r2509 (GCC 7.2.0/MinGW-w64 5.0.2) Includes both 32-bit and 64-bit in all packages. Windows XP supported by all builds. The 32-bit MSVC build of AviSynth+ and the FFMS2 C-plugin can be used on non-SSE2. The GCC builds of AviSynth+ require SSE2. THE GCC BUILD IS FOR TESTING. The issue I was referring to above is that the 32-bit GCC build cannot be used by FFmpeg, because of the weirdness that comes with 32-bit builds, calling convention differences on Windows, and function decorations between GCC and MSVC. It's even a tiny lie that the 32-bit build can't be used by FFmpeg; there is a way that it can be made to work, but doing so would make that build of FFmpeg incompatible with the MSVC builds of AviSynth+ (with the possible exception of MSVC builds of FFmpeg being able to use MSVC builds of AviSynth+, but I don't know that for sure). The build of FFmpeg above is a standard build, and will work with the standard MSVC builds of AviSynth+ as well as the 64-bit GCC build of AviSynth+. This only ever affects Windows, since the underlying problems causing this are Windows-specific. Additionally, the GCC builds of AviSynth+ shouldn't be able to use MSVC-built C++ plugins just due to the incompatibility between C++ implementations, but it is possible for the 64-bit build to use the 64-bit FFMS2 C-plugin (and likely, any other C plugins with 64-bit versions). AVISource also works, so there are at least two source filters that can be used with it. My ability to test under 64-bit Windows is almost non-existent, because I have to run it under a VM on a Silvermont under Ubuntu, running off an external USB 2.0 port. My tests with it under 64-bit Wine are what this information was gleaned from. I'd like to be able to fix this properly so 32-bit GCC builds can be used with FFmpeg without breaking compatibility with MSVC. My attempts at forcing this have failed thus far. Trying to build as 32-bit with __stdcall ends up breaking compilation, and nothing I tried to force the function decorations into line worked. I'd assume it's actually that if we can fix the code so GCC doesn't choke when using __stdcall on 32-bit builds, it'd probably be okay (so long as I could get the decorations correct, and it wouldn't screw up building under MSVC or the 64-bit GCC build). I'm also really tired of trying to do so, so there's also a part of me that would probably be totally okay with it if we don't support building 32-bit AviSynth+ with GCC on Windows (as I said before, it's a Windows-specific issue; any future Linux support could use 32-bit with no problem, even if the market share for 32-bit Linux is dwindling pretty fast too). |
1st October 2017, 22:14 | #3636 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Japanese friend (he is not the Developer) give me this mod of avs+ that use CUDA
QTGMC Core i7-6700 https://i.imgur.com/gs5WsEM.png CUDA版(KTGMC) GeForce GTX 1060 6GB https://i.imgur.com/kRc7bhg.png KTGMC: QTGMC for CUDA https://github.com/nekopanda/AviSynt...lters/releases AviSynth+CUDA https://github.com/nekopanda/AviSynthPlus/releases well, I don't has nvidia gpu so I can't test that
__________________
See My Avisynth Stuff |
2nd October 2017, 03:49 | #3637 | Link | |
Registered User
Join Date: Oct 2016
Posts: 111
|
Quote:
Without CUDA: https://i.imgur.com/W2WFT9R.png With CUDA: https://i.imgur.com/aE1SbfM.png I tried to remove DumpfilterGraph and it still work but no FPS change. If I remove Prefetch then FPS go down to 48 and time go up to 2 min. I put "OnCUDA" on all filteres but it's not work, except "OnCPU" work with source filter and FPS not change. Last edited by tuanden0; 2nd October 2017 at 03:51. |
|
2nd October 2017, 03:59 | #3638 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,351
|
Quote:
Thanks, looks interesting! Just a suggestion, but should this fork and it's testing be moved to a separate thread ? The readme's are in Japanese ,but google translate does an ok job I think |
|
2nd October 2017, 04:52 | #3639 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,351
|
I got the kqtgmc , knnedi3 , working with avisynth+cuda .
Some quick tests on a gtx860 were consistently slower than avisynth+mt for KQTGMC, and KNNEDI3 (ie. avisynth+mt on CPU was about 1.2-1.4x faster using the normal CPU versions QTGMC and NNEDI3), maybe a faster card would put it over the top . I didn't test validity/quality results yet. The same .dll was able to run the "normal" avisynth+mt script as is too (ie. with prefetch(x) ), with the same speed Quote:
Did you notice no speed change ? What about GPU-z ? monitor GPU card usage, or try device_index=x to swap GPU# (take out KNLMeansCL for testing now, because that will use GPU too) Im guessing not all filters are accelerated, or maybe your card is as fast as CPU processing ? Last edited by poisondeathray; 2nd October 2017 at 04:59. |
|
2nd October 2017, 05:05 | #3640 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,351
|
@tuanden0 - you have the same card as the developer, but a 3GB model instead of 6GB. He got 83.43fps vs. 27.33fps for QTGMC on "fast" preset
Just try the exact same script for now, to see if there is a speed difference for you |
Thread Tools | Search this Thread |
Display Modes | |
|
|