digitalFAQ.com Forums [Archives] - Nice CCE Prediction finally on the first view

Page 2 of 3

Show 40 post(s) from this thread on one page

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Avisynth Scripting (http://www.digitalfaq.com/archives/avisynth/)

- - Nice CCE Prediction finally on the first view (http://www.digitalfaq.com/archives/avisynth/7760-nice-cce-prediction.html)

incredible

01-22-2004 09:11 AM

Just for information I use:

- Win 2000
- Latest Avisynth 2.54
- And the Downloads mentioned above (latest ECLcce of the Doom9 Thread posted there by the board admin.

... and as you see above it works, but your problem could be elsewhere, so I don't know

jonny

01-22-2004 09:53 AM

@Inc.
Amd or Intel proc.?

On my side:
I'm running under an XP2000+, Win2000 SP4, Radeon 9500, Directx 9, AviSynth2.53

Racer99

01-22-2004 09:57 AM

First of all Thanks for the help jonny!

Quote:

Originally Posted by jonny

Ok, the crash happen when i read informations from the AviSynth file (the same function is called hitting the test button or when you start the joblist).

Correct.

Quote:

Can you give me the specs of the machine where the is no crash?

Asus P4S8X motherboard with Intel P4-2.53 GHz and 1GB RAM (Geil PC3200 DDR), Nvidia FX5700 video, 2-60GB Drives, DVD-R, CD-RW.

Both systems are running identical software versions. Windows XP Pro w/SP1, Avisynth 2.54 (development build, but I have uninstalled and tried 2.53 with no success), Xvid codec, CCE v2.67.00.23, QCCE and ECLCCE from the links above.

As well as TMPGEnc, PowerDVD, DVD2AVI 1.77.4 (I've tried v1.76 also). Again this was a fresh install of XP (full HD format).

Quote:

There is a couple of things you can try, before i go to send you some testing versions (if you have the time to test, of course)

I'll be glad to, I'll find the time somehow.

Quote:

- Try with a minimal script:
version()
bilinearresize(720,576)
converttoyuy2()

Will do

Quote:

(if the above fails)
- Try to use different AviSynth versions (2.52 or the latest cvs: http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html), using the script above.

As I mentioned above. I have tried 2.53 and 2.54 rc2. I think I have 2.52 somewhere. Will test it.

Quote:

(if the above fails)
- Try to encode the same script in XviD or DivX, using my app "Enc" (http://jonny.leffe.dnsalias.com)
("Enc" shares the same code of "qcce", but runs over a different version of Perl)

I'll give it a shot when I get home.

Again Thanks for the help :D

Racer99

incredible

01-22-2004 10:15 AM

ok. Jonny, maybe a bit too much but just to be shure...

- Epox 8rda+ Mainboard / Nforce2 chipset.
- AMD XP 1800+ CPU running at 2530 mhz real
- 2x TwinMos Winbond DDR á 256mb PC 3200 Rams running at 221 FSB
- GeForce MX 440
- Win2000 SP4
- DirectX 9
- Avisynth 2.54

kwag	01-22-2004 10:20 AM

Quote:

Originally Posted by jonny

@kwag:
Perl is not needed (actually i pack all the files nedded with a program called Perl2Exe)

Ok :imstupid:

-kwag

Racer99

01-22-2004 10:22 AM

I'm standing right there beside you Karl :D

jonny

01-22-2004 10:41 AM

LOL :D (sorry for my crude answer... i write fast when i'm at work! ^^).

***OT***
Karl, check PMs at doom9 (you'll find the end of a story...)
***OT***

kwag	01-22-2004 10:55 AM

Quote:

Originally Posted by jonny

***OT***
Karl, check PMs at doom9 (you'll find the end of a story...)
***OT***

PM answered ;) ( Finito :!: :lol: )
-kwag

Racer99

01-22-2004 10:43 PM

Hey jonny,

Well I did another complete re-install, this time I installed even less stuff. I'm still not sure where the problem is. At first I thought it was with QCCE, then Avisynth, now who knows.

Let me tell you what I have "discovered". When I use you minimalist script,

Code:

version() 

bilinearresize(720,480)

converttoyuy2()

Virtualdub handles it fine. QCCE bombs. So I tried Enc. Same results. This time instead of reporting a fatal problem, the programs just disappear. I check my task manager and I see them under the process tab at about 50% usage for about 10 seconds, and then poof they are gone.

Along the way I started adding things to the script and "discovered" something strange. Once I added a line with "LoadPlugin". Virtualdub would report a fatal error. If I load this script up in qcce, same thing...Crash.

Code:

LoadPlugin("F:\DVD to CD\decodefix100\MPEG2Dec3dg.dll")

Mpeg2Source("E:\SEX_CITY_SEASON5_D1\test.d2v")

version() 

bilinearresize(720,480)

converttoyuy2()

I again check the encoders. They handle the scripts fine, so if you got anymore clues, let me know.

Suggestions welcome :!:

Racer 99

jonny

01-23-2004 04:41 AM

So, with this script, now VDub *always* crash?
It's a really strange thing anyway.
The only difference between your 2 pcs that could have some influence is the gfx card (imo), maybe some driver issue combined with avisynth?

EDIT:

Quote:

I again check the encoders. They handle the scripts fine, so if you got anymore clues, let me know.

I don't understand, after the first crashes, the script is now working in VDub and qcce?

Racer99

01-23-2004 06:28 AM

Thanks jonny,

I tried the video card thing. I actually swapped them back to their current configuration when I found out it wasn't the problem.

Let me explain my "vdub' crash. The script loads and runs fine. Vdub only reports an error when I close down the program (exiting). I am able to execute and create videos from any script (one that is valid anyway). It is only when I exit vdub do I get that annoying pop up error box telling me it crashed.

The only reason I found this was I was testing to make sure it's not a script issue. No clue as to why. I've e-mailed Avery at virtualdub about this issue too.

Thanks again.

Racer99

incredible

01-23-2004 06:33 AM

Quote:

The script loads and runs fine. Vdub only reports an error when I close down the program (exiting)

:!:

My friend, where did you put the "LoadPlugInEx.dll" to get AVS 2.0x filters to work with Avisynth 2.5x ???? (In case if you installed that .dll).

So if you use that .dll be shure that it's NOT in the PlugIn Folder of Avisynth 2.5x !!
Just put it in the top folder of avisynth 2.5x and do point on that .dll manually in generated scripts if needed!

Maybe that could be the reason of your "Vdub crash" problem, as its many times mentioned in the Web.

Inc.

Racer99

01-23-2004 07:05 AM

Thanks incredible for your reply.

I did have them in that directory. I moved them and the problem still persists. :(

Racer99

jonny

01-23-2004 07:45 AM

Quote:

It is only when I exit vdub do I get that annoying pop up error box telling me it crashed.

When i read infos from the AviSynth script, actually i do:
-Open the script via vfw
-Read the infos
-Close the script << i think both VDub and qcce crashes here! (you could verify this opening/closing the script in VDub)

I suppose this cos it's not the first time i see *something similar* ( http://forum.doom9.org/showthread.php?s=&threadid=63269 )

Quote:

I've e-mailed Avery at virtualdub about this issue too.

Perhaps sh0dan could help you too on tracking this strange behavior.

Quote:

tried the video card thing. I actually swapped them back to their current configuration when I found out it wasn't the problem.

I had no courage to ask you this... let me tell you: you do more than 10 betatesters together!!! WOW thanks :D

Racer99

01-23-2004 08:38 AM

I'll keep trying.

jonny

01-23-2004 12:03 PM

If i'm not wrong:
P4 2.53 GHz doesn't have Hyper-Threading
P4 3.0 Ghz have Hyper-Threading

You could also try to disable HT from the bios.

Racer99

01-23-2004 12:22 PM

You are correct. The only problem is I tried that, and my system would not boot up. There is also an environment variable that says the number of processors is two. Maybe I need to change it there?

Racer99

jonny

01-23-2004 05:48 PM

No experience in this field :(
You can try to see if there are bios updates for your mobo (it's strange that the sys doesn't boot disabling ht)

Jellygoose

02-09-2004 08:27 AM

Ok, I tried qcce today (newest version) and went to sleep. Now I woke up, and qcce seems to be done, but: where do I see what the final Q value was that the program used?? :roll:

jonny

02-09-2004 09:11 AM

You can check this opening the main log file with the menu: "Job list > View log file" (or you can open the file manually, it's located in: "jobs\jobs.log").
It's not 100% user friendly, i know ^^
The next version already have this info directly in the joblist (i think this week i'll release it)

EDIT:
Ops.. 1.02 should already have this info in the joblist (it's the first number after [Ok])
(iirc, can't check cos i'm at work)

Page 2 of 3

Show 40 post(s) from this thread on one page