Help me track down the Psychovis problem!

[DigitAl56K]

Hi guys,

I'm trying to track down the problem that you're seeing with the Pyschovisual Enhancement options in the codec config window. So far I haven't been able to reproduce the issue on any of the boxes I've tested on, including some with AMD processors.

Can you tell me the CLI from the Settings screen immediately before the crash? (i.e. right before you try to change the Psy method)

Can you run an app like CPU-Z and tell me which instuctions your processor supports (e.g. MMX, SSE, SSE2, SSE3)?

Can you tell me the specific host application and version of the application that you are using?

Which language do you have the codec set to?

I'd like to fix this and post a patch up to DivX Labs, then roll it into the main DivX bundles at the next available oppertunity.

More info = better.

Thanks all :)

[cacepi]

Hi guys,

Can you tell me the CLI from the Settings screen immediately before the crash? (i.e. right before you try to change the Psy method)

Can you run an app like CPU-Z and tell me which instuctions your processor supports (e.g. MMX, SSE, SSE2, SSE3)?

Can you tell me the specific host application and version of the application that you are using?
All right, on a P4, 2.6GHZ with HT enabled, Windows XP SP2 (all updates installed) on US English locale, VirtualDub 1.6.11:

-bv1q 1 -vbv 4854000,3145728,2359296 -dir "C:\Program Files\DivX\DivX" -b 1 -nf -profile=3 -quantization=2

Psychovis: Shaping crashes
Psychovis: Masking does not crash

Same computer, switch to different user with Japanese locale: both shaping and masking crash.

On an AMD64 FX2 4400+ with VirtualDub 1.6.11, Windows XP SP2 (all updates installed), US English locale and same CLI:

Psychovis: Shaping crashes
Psychovis: Masking crashes

Switch to different user with Japanese locale: same result.

-HOWEVER-

Switching to H.263 quantization (not optimized) results in no crashing on either machine, regardless of locale.

Hope this helps,

cacepi

[DigitAl56K]

Thanks cacepi,

I still can't recreate it here :(

What language is the codec/DivX installed in, English or Japanese?

Does the crash happen when you begin encoding, or when you are configuring the encoder? If it's when you're configuring the encoder does the crash happen when you click 'OK', or when you change the psy drop-down option?

[Selur]

Tyan Tiger Board
1024MB ECC RAM
Dual Athlon 1800+ MP, supported Instructions: MMX(+), 3DNow!(+),SSE
codec is set to: germany
CLI: -bvn1 780000 -vbv 4854000,3145728,2359296 -dir C:\Programme\DivX\DivX -w -b 1 -nf -profile=3 -psychovisual=2

posted this also here: http://forums.divx.com/groupee/forums/a/tpc/f/401101651/m/914105262

Over here it crashes if you want to go back to the codec configuration after you closed it once.

Cu Selur

[george11]

AMD XP 2400+ MMX, 3DNow
Windows XP SP2, VirtualDub 1.6.11, VirtualDubMod 1.5.10.2

-bv1 780000 -vbv 4854000,3145728,2359296 -dir "C:\Program Files\DivX\DivX" -b 1 -nf -profile=3 -quantization=2

Psychovis: Shaping crashes
Psychovis: Masking does not crash

Crash with H.263 and H.263 optimized

Locale: Slovenian
DivX: English

Crash (lock) happen when changing drop-down option to Shaping

[mod]

AMD AthlonXP 1800 Palomino
512 mb DDR Pc2100
mobo Asus A7V880
video Asus 9600XTVivo
Lang: ITA

Same settings as george11

crash ONLY with dropdown menu over SHARP, with other settings np.

[Videostation]

AMD AthlonXP 3000+, MMX(+), 3DNow(+), SSE
512MB DDR400
mobo: MSI K7N2 Delta
DivX: german
VDMod 1.5.10.2

chrash as soon as i select the option "Formen" (shapes).

[cacepi]

All right, this is weird...


What language is the codec/DivX installed in, English or Japanese?

Does the crash happen when you begin encoding, or when you are configuring the encoder? If it's when you're configuring the encoder does the crash happen when you click 'OK', or when you change the psy drop-down option?Both are installed in English, and they crash when I select the psychovis option; CPU immediately jumps to 100%, and all memory gets eaten. I have to kill the VirtualDub process through Task Manager to return to normal.

But here's the fun part! I uninstalled on the AMD64 machine, immediately reinstalled, and now it doesn't crash, either on English or Japanese locale.

It's just... weird.

cacepi

Edit: just tried it once more, and it's crashing again now.

[Selur]

@DigitAl56K: Were you able to reproduce the problem?
(maybe SSE2/3 is used when it shouldn't be)

[cacepi]

@DigitAl56K: Were you able to reproduce the problem?
(maybe SSE2/3 is used when it shouldn't be)It's funny that it should crash on my machines, though, as AMD says that the X2 supports SSE2/SSE3...

<wildspeculation>Maybe the psychovis module isn't thread-safe?</wildspeculation>

cacepi

[Selur]

you are right, I totally overlooked that you got a X2 :)

[DigitAl56K]

OK, thanks to various pieces of information and especially from BLeST (who sent use CPU-Z screens and dumps using our Diagnostics tool) we've narrowed the problem down to what seems to be machines without SSE2/3, and we have a machine in the office we can reproduce on. I'm not sure about the X2 - we're currently debugging so I'm not sure what we'll find yet..

I'll try to get an update out to DivX Labs in the next day or two :)

[Sharktooth]

x2 has both SSE2 and SSE3.

[DigitAl56K]

Yes, it looks like we might be doing something that doesn't necessarily use SSE2/3, but is most likely to exhibit problems on older systems without these instructions. Either way we can reproduce it now so stay tuned for updates.. :)

Thanks everyone.

[Selur]

Either way we can reproduce it now so stay tuned for updates..
good to hear that reproduction of the problem is now possible :D