x264 & FFmpeg: "64-bit dictatorship"?

[LigH.de]

If there is only one thread running, it can run on only one core at a time (the OS may do some round-robin, though, except you set explicit core affinity in a task manager).

[bulgom]

Round-robin: that'd be 1 more thing to watch — &, left to learn: how to avoid it using a task mgr since, in my (quite critical) case, only a little overheat's able to ruin a 24-h (or so) reencoding 'session'.


But at the moment, still testing on single-core CPU & BTW, of the most ticklish kind! As jagabo reminded, the infamous "Pentium D" was terrible, unless run at North pole!

I now remember the critics of its time, and promised I'd never buy that frying pan. But I found this trashed PC few years ago (still contained a 200 GB SATA HD)

— with its CPU unit/radiator hanging out: obviously, the owner lost nerve after trying something. So I bought thermal paste, fixed it (tediously, due to missing special screws I had to make! = crazy, I know), & added 3 fans.

Blaming the bad frames issue: possibly on its HD, I even tried a 36 hours (!) "cluster (soft) regeneration"; w/no success: not 1 bad cluster...


The good side of all this, tough, is that I'm testing on the very worst piece of junk. Knowing that poisondeathray's advice just... WORKS,

— & after YEARS of hassle, THAT DESERVES a boogie-woogie dance! YeeeWooo!!/oops, excuse this —,

the 3 other PCs SHOULD follow!


Anyway, a 2nd — never ending* but expected &... don't care — test CONFIRMS the excellent news. ~One hour of video, processed by Avidemux, comes out: perfect again!

[ *'veryslow' setting on a slowed down 2006 CPU sure is... something! But I absolutely need to SHRINK a stack of vids. to the bone. ]


Thanx also to this "winThrottle" few kB Win. XP compatible thingy from http://www.oldskool.org/pc/throttle , which reads "Current CPU utilization e.g. 90%", sometimes hitting 97 or even 100% — but in all cases, the impeccable result's here.

——— SORRY (!) about my "32-bit OS's + AVC encoders" mistake, due to the "from-now-on zero 32-bit testing coverage" warning I read.


Once more, videohelp forum means: EFFICIENT help!


.

[jagabo]

XP can also be configured to use less than all cores in BOOT.INI with the /NUMPROC switch.
https://www.pantz.org/software/windows/bootinistartupswitches.html

[bulgom]

/NUMPROC=x and /ONECPU = cmd's I'm gonna test. Interesting page; didn't know that "boot.ini" supports such a number of options.

[jagabo]

I doubt /ONECPU will be useful for you. It's for multi CPU server motherboards. For example:

https://www.newegg.com/Product/Product.aspx?Item=9SIAE256CP4705

[bulgom]

Multi physical CPU MB: OK. Not my case.


Also, I can't wait to test software CPU cooling on another one, a "Dell Dimension 5100 (Pentium 4, 3 GHz, RAM 2 GB only)", single-core, that runs a 32-bit Win. 10 — although a 64-bit CPU is reported, but Win. 10 64 refused to install on (one more weirdo situation),

that spins its CPU fan like hell within the 1st mn of encoding + nonstop to the end, and known for that ever unsolved problem. In such a case, nobody would dare encoding using it (neither do I).

Not as aggressively as with "HP" boxes, I don't like "Dell" central units either (for several reasons). New stuggle to come...


.

[jagabo]

Stop using P4 CPUs. For Intel, don't use anything older than a Core 2 Duo.

[jagabo]

It looks like I was wrong about /ONECPU. On my single CPU quad core Q6600 system that boots 32 bit XP /ONECPU resulted in a single core running. So it appears to act just like /NUMPROC=1.

[bulgom]

Stop using P4 CPUs...

It's planned — but no time yet / (even) more urgent: to reduce the PILE of vids., incl. analog & even 8/Super-8... In a word: total mess!

"HP", now stable!, grinding 24/24 since yesterday; next: Dell "delight" (if possible).


.

[bulgom]

It looks like I was wrong about /ONECPU (...) appears to act just like /NUMPROC=1.

Good. Should act the same here; I'll have to test.


.