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 February 2007, 20:55 | #421 | Link |
Fighting spam with a fish
Join Date: Sep 2005
Posts: 2,699
|
Okay, well a short little preliminary test of the blank clip script on the single core led to nothing. I aborted it after 12.1%. Mostly because it crashed @ 12% on my dual core.
I will complete a full test on the single core, it will just take a long time. I have access to another dual core that I will test eventually, and see if I can isolate it further. @TSP Is there anything I can do to help you diagnose this better? Like send you the error report created by windows when it crashes? I don't know if I mentioned this or not, but it crashes on Xvid as well. The weired thing about it is that the blank clip script doesn't crash (atleast, not that I remember), but it does crash on the Step Up script, so I am sure that it is not just x264's problem. |
6th February 2007, 02:53 | #423 | Link |
Fighting spam with a fish
Join Date: Sep 2005
Posts: 2,699
|
Nope, its not the overclock for two reasons.
1) I just updated by bios and my clocks are now back to normal, so I tested to be sure, and it still crashed. 2) I just tested on a new core 2 duo build of mine, actually I built it for my mom, but it also crashes using the same exact filters/MeGUI setup/Avisynth setup. Edit: I think that I found the problem!!!!!!!! TSP, try running the blankclip encode using the new colormatrix 2.1. If I removed Colormatrix() from the script, it worked! So, I think that the new multithreaded version of Colormatrix is having issues with you multithreaded Avisynth. Last edited by Adub; 6th February 2007 at 04:12. |
6th February 2007, 10:52 | #424 | Link |
Registered User
Join Date: Aug 2004
Location: Denmark
Posts: 807
|
merlin7777: Yes colormatrix 2.1 does crash very fast on my machine. setting threads to 1 in colormatrix seems to be more stable
__________________
Get my avisynth filters @ http://www.avisynth.org/tsp/ Last edited by tsp; 6th February 2007 at 11:17. |
7th February 2007, 21:19 | #427 | Link |
Fighting spam with a fish
Join Date: Sep 2005
Posts: 2,699
|
What kind of processor are you using?
Besides MT doesn't like resizing, and that is the one that you will want for realtime watching. SetMTmode is better for encoding, unfortunately for you, it supports resizing but it wont usually speed up realtime watching significantly, at least it doesn't for me. That is why I use MT for realtime viewing. |
7th February 2007, 21:32 | #428 | Link |
Registered User
Join Date: Aug 2004
Location: Denmark
Posts: 807
|
webzeb: The problem is that ffdshow insert a source filter before the avisynth script so SetMtmode is never the first filter in the script. You can see it by removing the selection in "add ffdshow video source" checkbox in the avisynth option in ffdshow.
Merlin7777: Yes the bug is official. I don't know if it is triticals code or mine that are wrong (probably mine ). Also if threads is not specified the default value is the number of cores available according to the manual.
__________________
Get my avisynth filters @ http://www.avisynth.org/tsp/ |
7th February 2007, 21:47 | #429 | Link | |
Registered User
Join Date: Jun 2002
Location: France
Posts: 21
|
Quote:
I play HD (720p/1080p) stuff, resized to 1024*768px. (I watch it on a 1024*768px plasma TV. ) Thank you for your answer, Fred
__________________
Create More ! |
|
7th February 2007, 23:09 | #430 | Link |
Registered User
Join Date: Aug 2004
Location: Denmark
Posts: 807
|
It is possible to use a resizer with mt() (at least after I fixed a bug in mt.dll see first post) by first doing the vertical resize and afterwards the horizontal resize. Something like this:
Code:
src=avisource("c:\test.avi") s.mt("spline36resize(1280,last.height())",splitvertical=false) mt("spline36resize(last.width(),704)",splitvertical=true)
__________________
Get my avisynth filters @ http://www.avisynth.org/tsp/ |
7th February 2007, 23:46 | #432 | Link |
Actually in reserve
Join Date: Oct 2004
Posts: 1,605
|
Hi,
@TSP, many thanks from a young dualcore owner (still in test). Continue the good work. Regarding speed some test results here http://forum.doom9.org/showthread.ph...439#post948439 or here http://forum.doom9.org/showthread.ph...322#post949322 Did
__________________
Having a problem with AutoGK? Read & use the FAQ & MORE FAQ first Want to exchange on AutoGK? try doom10.org In reserve (inactive) for an undefined period of time. |
8th February 2007, 00:08 | #433 | Link | |
Registered User
Join Date: Jun 2002
Location: France
Posts: 21
|
Quote:
__________________
Create More ! |
|
8th February 2007, 02:29 | #434 | Link | |
Fighting spam with a fish
Join Date: Sep 2005
Posts: 2,699
|
Actually TSP you are wrong, the default is one thread at least it is supposed to be:
Quote:
Last edited by Adub; 8th February 2007 at 02:31. |
|
8th February 2007, 09:37 | #435 | Link |
Registered User
Join Date: Aug 2004
Location: Denmark
Posts: 807
|
Merlin7777: yes threads=1 are the default must have seen the default value for thrdmthd. Can you reproduce the crash with version 2.0?
__________________
Get my avisynth filters @ http://www.avisynth.org/tsp/ |
8th February 2007, 15:08 | #436 | Link |
Fighting spam with a fish
Join Date: Sep 2005
Posts: 2,699
|
if you mean colormatrix 2.0, then no. On my preliminary tests with colormatrix 2.0 and the blankclip script, I couldn't get it to crash. It appears that the new multithreading in colormatrix is very skittish when pared with MT Avisynth.
|
8th February 2007, 18:25 | #438 | Link |
Registered User
Join Date: Aug 2004
Location: Denmark
Posts: 807
|
Jeremy Duncan: MT 0.6 contains a new mt.dll (that fixes the bug with vertical resizing) and avisynth.dll(same the one from post #407)
__________________
Get my avisynth filters @ http://www.avisynth.org/tsp/ |
Thread Tools | Search this Thread |
Display Modes | |
|
|