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.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 Encoder GUIs

Reply
 
Thread Tools Search this Thread Display Modes
Old 4th January 2020, 13:11   #1841  |  Link
deco20
Registered User
 
Join Date: Sep 2012
Posts: 17
Lord_Mulder, I have a problem with determining clip properties. It fails on "Get source info" step, but it seems that the command that is used is ok.
When I run it manually, I get following response:
K:\dg.avs: 1280x534, YV12, 8-bits, progressive, 24000/1001 fps, 154508 frames

From what I saw in the code, this step is about extracting some of these values using regex. Is my output somehow different from the one that is expected by the regex?
deco20 is offline   Reply With Quote
Old 4th January 2020, 14:47   #1842  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Quote:
Originally Posted by deco20 View Post
Lord_Mulder, I have a problem with determining clip properties. It fails on "Get source info" step, but it seems that the command that is used is ok.
When I run it manually, I get following response:
K:\dg.avs: 1280x534, YV12, 8-bits, progressive, 24000/1001 fps, 154508 frames

From what I saw in the code, this step is about extracting some of these values using regex. Is my output somehow different from the one that is expected by the regex?
Your output from the manual invocation of Avs2YUV looks normal to me. Also, I tried with a similar setup and it seems to work fine for me:
https://i.imgur.com/7k1LJ48.png

I suspect something is going wrong with the Avs2YUV invocation that happens inside Simple x264 Launcher (maybe AVS script fails to load for some reason), so can you please post the complete log from Simple x264 Launcher?
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 4th January 2020 at 14:53.
LoRd_MuldeR is offline   Reply With Quote
Old 4th January 2020, 15:42   #1843  |  Link
deco20
Registered User
 
Join Date: Sep 2012
Posts: 17
The script itself looks like these:
DGSource("K:\ToEncode\00000.dgi")
Crop(0, 140, 0, -140)
Spline36Resize(1280, 534)


It is correctly interpreted by AvsPmod and I used to do similar things before.

As for the log, there it is:
Code:
[2020-01-04][15:39:30] --- SYSTEMINFO ---
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] Binary Path : C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2
[2020-01-04][15:39:30] Avisynth    : Yes
[2020-01-04][15:39:30] VapourSynth : No
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] --- SETTINGS ---
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] Encoder : x264 (AVC/H.264), 64-Bit (x64), 8-Bit
[2020-01-04][15:39:30] Source  : Avisynth (avs)
[2020-01-04][15:39:30] RC Mode : CRF
[2020-01-04][15:39:30] Preset  : veryslow
[2020-01-04][15:39:30] Tuning  : <None>
[2020-01-04][15:39:30] Profile : High
[2020-01-04][15:39:30] Custom  : --level 4.1 --sar 1:1 --no-fast-pskip --no-dct-decimate --no-mbtree --deblock -3:-3 --ipratio 1.2 --pbratio 1.1 --psy-rd 1.1 --aq-mode 3 --aq-strength 0.7 --aq2-strength 0 --aq2-sensitivity 0 --aq3-mode 0 --bframes 12
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] --- CHECK VERSION ---
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] Detect video encoder version:
[2020-01-04][15:39:30] 
[2020-01-04][15:39:30] Creating process:
[2020-01-04][15:39:30] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x264_x64.exe" --version
[2020-01-04][15:39:30] 
[2020-01-04][15:39:31] x264 0.159.2991+49 524a90c t_mod_New [0-bit@all X86_64]
[2020-01-04][15:39:31] (libswscale 5.5.100)
[2020-01-04][15:39:31] (libavformat 58.29.100)
[2020-01-04][15:39:31] (ffmpegsource 2.31.0.0)
[2020-01-04][15:39:31] built on Dec 21 2019, gcc: 9.2.1 20191212
[2020-01-04][15:39:31] x264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] libx264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] x264 license: Non-Free
[2020-01-04][15:39:31] libswscale/libavformat/ffmpegsource license: nonfree and unredistributable
[2020-01-04][15:39:31] WARNING: This binary is unredistributable!
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] Detect video source version:
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] Creating process:
[2020-01-04][15:39:31] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe"
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] Avs2YUV 0.24bm6
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] > x264 revision: 2991 (core #159) - with custom patches!
[2020-01-04][15:39:31] > Avs2YUV version: 0.24.6
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] --- GET SOURCE INFO ---
[2020-01-04][15:39:31] 
[2020-01-04][15:39:31] Creating process:
[2020-01-04][15:39:31] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe" -frames 1 K:\dg.avs NUL
[2020-01-04][15:39:31] 
[2020-01-04][15:39:34] 
[2020-01-04][15:39:34] FAILED TO DETERMINE CLIP PROPERTIES !!!
deco20 is offline   Reply With Quote
Old 4th January 2020, 16:03   #1844  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Well, according to your log, Avs2YUV did not produce any text output at all. This means it either ran into some kind of error (but in that case we'd expect to see at least some sort of error message) or it just crashed.

Does that exactly same .avs file open correctly (and seek properly) in the 32-Bit (x86) version of VirtualDub?

Also, please check the following: Does this problem only appear with Avs2YUV 0.24bm6, i.e. is this a new problem in the latest TEST build, or did the same thing already happen with Avs2YUV 0.24bm5?
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 4th January 2020 at 16:08.
LoRd_MuldeR is offline   Reply With Quote
Old 4th January 2020, 16:45   #1845  |  Link
deco20
Registered User
 
Join Date: Sep 2012
Posts: 17
Quote:
Originally Posted by LoRd_MuldeR View Post
Does that exactly same .avs file open correctly (and seek properly) in the 32-Bit (x86) version of VirtualDub?
Yes, no problems.

Quote:
Originally Posted by LoRd_MuldeR View Post
Also, please check the following: Does this problem only appear with Avs2YUV 0.24bm6, i.e. is this a new problem in the latest TEST build, or did the same thing already happen with Avs2YUV 0.24bm5?
It didn't work in the earlier version neither. That's why I updated it to see if it works in the latest one.

Last edited by deco20; 4th January 2020 at 16:52.
deco20 is offline   Reply With Quote
Old 4th January 2020, 17:01   #1846  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 762
Maybe some coincidence under changed circumstances ? Win10, nVidia driver, that route ?
A lead, maybe...

https://forum.videohelp.com/threads/...ith-KNLMeansCL
http://rationalqm.us/board/viewtopic.php?f=8&t=436
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're working on that issue. Synce invntoin uf lingöage..."
Emulgator is offline   Reply With Quote
Old 4th January 2020, 18:02   #1847  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Quote:
Originally Posted by deco20 View Post
It didn't work in the earlier version neither. That's why I updated it to see if it works in the latest one.
Quote:
Originally Posted by Emulgator View Post
Maybe some coincidence under changed circumstances ? Win10, nVidia driver, that route ?
Yeah, the problems with bugs, especially memory corruptions, is that they often lead to undefined behavior – which means that things may seem to work 99% of the time, but then, all of a sudden, they stop working.

In this situation, every little (seemingly unrelated) change is like rolling the dice again...

What you can try: Strip down your Avisynth script to the bare minimum (e.g. source filter only) and try again. If the problem still appears with the minimal script, try another source filter.

Also: Which exact version of Avisynth are you using? In my experience, the official "v2.6.0 ST" (32-Bit) build is the most reliably. The "MT" builds may introduce all sorts of random hiccups, so try switching back to "ST" if you are using "MT".

(In addition to that, try removing every plug-in DLL from your Avisynth "plugins" directory that is not actually needed, just to be sure!)
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 4th January 2020 at 18:12.
LoRd_MuldeR is offline   Reply With Quote
Old 4th January 2020, 21:45   #1848  |  Link
deco20
Registered User
 
Join Date: Sep 2012
Posts: 17
Thanks for suggestions, but none of it worked unfortunately.
I have AviSynth 2.6.0 ST 32-Bit installed. I tried to run it with only source filter in the script, I tried to run with only necessary plugins in AviSynth.
I updated also DGDecNV and NVidia drivers, still the same.

If you work with m2ts files, what source filter do you use?
deco20 is offline   Reply With Quote
Old 4th January 2020, 22:10   #1849  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Quote:
Originally Posted by deco20 View Post
If you work with m2ts files, what source filter do you use?
I tend to re-mux M2TS files with MKVToolnix, and then just load the resulting MKV with FFMS2
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 4th January 2020, 23:05   #1850  |  Link
deco20
Registered User
 
Join Date: Sep 2012
Posts: 17
Quote:
Originally Posted by LoRd_MuldeR View Post
I tend to re-mux M2TS files with MKVToolnix, and then just load the resulting MKV with FFMS2
Ok, will try that, thank you very much for your help and of course, for your app, it's great.
deco20 is offline   Reply With Quote
Old 5th January 2020, 16:31   #1851  |  Link
tormento
Acid fr0g
 
tormento's Avatar
 
Join Date: May 2002
Location: Italy
Posts: 1,047
Quote:
Originally Posted by LoRd_MuldeR View Post
Here is a new TEST build that has the latest x264 and Avs2YUV versions included
Working here.

__________________
@turment on Telegram
tormento is offline   Reply With Quote
Old 5th January 2020, 18:40   #1852  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 963
Quote:
x264 license: Non-Free
[2020-01-04][15:39:31] libswscale/libavformat/ffmpegsource license: nonfree and unredistributable
[2020-01-04][15:39:31] WARNING: This binary is unredistributable!
Is this correct?
gonca is offline   Reply With Quote
Old 5th January 2020, 21:44   #1853  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Quote:
Originally Posted by gonca View Post
Is this correct?
Where do you see this? Did you replace the x264 binaries that were included with the Simple x264/x265 Launcher?

With the x264 binaries that currently ship with Simple x264/x265 Launcher, I see:

Quote:
x264_x64_launcher\res\toolset\x64\x264_x64.exe --version
x264 0.159.2991 1771b55
(libswscale 5.6.100)
(libavformat 58.35.101)
(ffmpegsource 2.31.0.0)
built on Jan 2 2020, gcc: 9.2.0
x264 configuration: --chroma-format=all
libx264 configuration: --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat/ffmpegsource license: GPL version 2 or later
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 5th January 2020, 22:01   #1854  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 963
Quote:
Where do you see this?
In deco20's log
I checked the log on a default download version to compare, because it didn't look right
Quote:
[2020-01-04][15:39:31] x264 0.159.2991+49 524a90c t_mod_New [0-bit@all X86_64]
[2020-01-04][15:39:31] (libswscale 5.5.100)
[2020-01-04][15:39:31] (libavformat 58.29.100)
[2020-01-04][15:39:31] (ffmpegsource 2.31.0.0)
[2020-01-04][15:39:31] built on Dec 21 2019, gcc: 9.2.1 20191212
[2020-01-04][15:39:31] x264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] libx264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] x264 license: Non-Free
[2020-01-04][15:39:31] libswscale/libavformat/ffmpegsource license: nonfree and unredistributable
[2020-01-04][15:39:31] WARNING: This binary is unredistributable!
[2020-01-04][15:39:31]

Edit
I was commenting on deco20's problem

Last edited by gonca; 5th January 2020 at 22:05.
gonca is offline   Reply With Quote
Old 5th January 2020, 22:10   #1855  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,074
Quote:
Originally Posted by gonca View Post
In deco20's log
I checked the log on a default download version to compare, because it didn't look right

Edit
I was commenting on deco20's problem
So, apparently, deco20 has replaced the x264 binaries that ship with Simple x264/x265 Launcher. It looks like he is using the "t_mod_New" build instead.

I just downloaded the latest "t_mod" build from here and checked. Indeed, this build prints the "This binary is unredistributable!" warning – which means that whoever is distributing those binaries is probably violating the license!

Just to make it clear again: Simple x264/x265 Launcher does not ship with "t_mod" build, and never has. Also, this is probably not related to deco20's original problem.

[UPDATE]

New version of x264 "t_mod" build has resolved this issue.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 8th January 2020 at 19:40.
LoRd_MuldeR is offline   Reply With Quote
Old 19th January 2020, 11:21   #1856  |  Link
tormento
Acid fr0g
 
tormento's Avatar
 
Join Date: May 2002
Location: Italy
Posts: 1,047
Pssst.... I just noticed you forgot to update x264 & x265 download links
__________________
@turment on Telegram
tormento is offline   Reply With Quote
Old 21st January 2020, 08:17   #1857  |  Link
Forteen88
Herr
 
Join Date: Apr 2009
Location: North Europe
Posts: 418
Quote:
Originally Posted by LoRd_MuldeR View Post
Here is a new TEST build that has the latest x264 and Avs2YUV versions included:
x264_launcher-TEST.2020-01-03.exe
Thanks! Now I've tried it, and it works great, although I mostly used standard settings when I made my encode. Could you please release a portable version though, if that's not too much trouble?

Last edited by Forteen88; 21st January 2020 at 22:15.
Forteen88 is offline   Reply With Quote
Old 22nd January 2020, 20:07   #1858  |  Link
tormento
Acid fr0g
 
tormento's Avatar
 
Join Date: May 2002
Location: Italy
Posts: 1,047
Quote:
Originally Posted by Forteen88 View Post
Could you please release a portable version though, if that's not too much trouble?
Just rename to x264_launcher_portable.exe
__________________
@turment on Telegram
tormento is offline   Reply With Quote
Old 23rd January 2020, 21:08   #1859  |  Link
Forteen88
Herr
 
Join Date: Apr 2009
Location: North Europe
Posts: 418
Quote:
Originally Posted by tormento View Post
Just rename to x264_launcher_portable.exe
OK, thanks, but there is still stuff in the installation-register with this new Test-version.
Forteen88 is offline   Reply With Quote
Old 26th January 2020, 12:18   #1860  |  Link
tormento
Acid fr0g
 
tormento's Avatar
 
Join Date: May 2002
Location: Italy
Posts: 1,047
I'd like to give a try to HDR encoding and I am kinda newbie in that sector. Using DGIndexNV to decode video, there is something I need specifically to set on x265 to add metainfo and, above all, how is x264 launcher support about hdr?
__________________
@turment on Telegram
tormento is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 18:33.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.