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 |
2nd September 2006, 08:07 | #1 | Link |
Registered User
Join Date: Jan 2006
Posts: 101
|
running x264.exe without running avisynth in it's own thread
I've been trying to encode this movie for about a week now. The source is 1080i and I'm converting it over to 1080p. Now I found that it's been crashing alot it seems.
I've seemed to nail it down to the option, Run AviSynth in its own thread. It always does this when I'm trying to do something else on my computer. The command line for it is --thread-input. Unfortunately it's not an option in the megui program. I've also noticed that it seems to speed things up if I don't enable it. I'm running build 558 and are using the MT plugin version of avisynth 2.5.6a. Which greatly helps to speed up encoding I find. I never came across this when encoding to XViD before. It probably doesn't have that option anyways, which might explain why it didn't crash. I also know x264 is alpha software. So it could be a bug I just found too. Has anyone else come across this? |
2nd September 2006, 14:23 | #3 | Link |
Mr. Sandman
Join Date: Sep 2003
Location: Haddonfield, IL
Posts: 11,768
|
MeGUI automatically enables --thread-input if threads are set (or autodetected) to 2 or more.
Crashing means your system is not stable, so before doing any other thing, test your hardware for possible problems.
__________________
MPEG-4 ASP Custom Matrices: EQM V1(old), EQM AutoGK Sharpmatrix (aka EQM V2), EQM V3HR (updated 01/10/2004), EQM V3LR, EQM V3ULR (updated 04/02/2005), EQM V3UHR (updated 17/12/2004) and EQM V3EHR (updated 05/10/2004) Info about my ASP matrices. MPEG-4 AVC Custom Matrices: EQM AVC-HR Info about my AVC matrices My x264 builds. Mooo!!! |
2nd September 2006, 20:10 | #4 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
|
|
3rd September 2006, 02:30 | #5 | Link |
Pain and suffering
Join Date: Jul 2002
Posts: 1,337
|
Infact Pengvado told me: When you run --threads 2 --thread-input is also used by x264.
--threads 1: 1 thread doing encoding and avs --threads 1 --thread-input: 1st thread doing encoding and 2nd thread doing avs --threads 2: 1st and 2nd thread doing encoding, 3rd thread doing avs --threads 2 --thread-input: same --threads 3: 3 threads doing encoding, 4th thread doing avs |
3rd September 2006, 03:11 | #6 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
Oh and how many threads can I put? I have a dual core cpu. Am I only supposed to put 2 then? I'm assuming so. |
|
3rd September 2006, 07:51 | #8 | Link |
Angel of Night
Join Date: Nov 2004
Location: Tangled in the silks
Posts: 9,559
|
Sounds like an undesirable interaction between MT avisynth and MT x264, more than anything. Odd, not something I've experienced, but it might have something to do with certain filters' bad behavior under multithreading.
|
3rd September 2006, 09:51 | #9 | Link | ||
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
Quote:
|
||
3rd September 2006, 10:06 | #10 | Link |
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
Before anything else, simplify the avs script to a bare minimum ( i.e, mpeg2source only ), and try again.
MT isn't the most stable thing. HybridFuPP relies on MaskTools 1.5 which aren't that stable eithers, and on MVTools which I definitely wouldn't call stable, especially when used with MT. BTW, answering on the question you asked on the HybridFuPP thread, you can save the script with a lossless encoding, that way the script is only processed once.
__________________
|
3rd September 2006, 10:29 | #11 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
|
|
3rd September 2006, 10:41 | #12 | Link |
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
Yes, it would ( 1 MB / frame, i'd say, for 1080p, so 1 hour @ 25 fps would give 90 GB ). But the only other thing that can be speeded up by saving a stat file between both passes in HybrippFupp would be the result of MVAnalysis, and that definitely not accounts for much in the slowliness of HybridFupp
__________________
|
3rd September 2006, 11:00 | #13 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
|
|
3rd September 2006, 11:09 | #14 | Link |
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
You can't. I tried to make the MVTools output a stat file if asked too, but I soon realised the file would be quite big ( ~700 MB ), so I dropped the idea. Anyway, as I said, it doesn't help that much ( you'd win something like 2-3% of the overall encoding time )
@mods : sorry to have somehow hijacked the thread, I should have answered the HybridFuPP part on the dedicated thread.
__________________
|
3rd September 2006, 11:12 | #15 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
|
|
3rd September 2006, 11:21 | #16 | Link |
Registered User
Join Date: Jan 2002
Location: France
Posts: 2,856
|
I contributed to the MVTools and the MaskTools, so I added the needed code. I deemed the results useless, so I dropped it. Believe me when I say you greatly overestimate the gain you'd have by not computing twice the motion vectors.
__________________
|
3rd September 2006, 11:33 | #17 | Link | |
Registered User
Join Date: Jan 2006
Posts: 101
|
Quote:
Oh and 2-3% time saved when an encoding takes 27 hours does help. Thanks for all your help though. Oh and the results are in. It didn't crash at all for once for me. Putting it in an avi container now. So now I know to not use the option --thread-input from now on. The next encode shouldn't take a week now. |
|
|
|