lame benchmarks (pun intended)

[wawrzon]

@piru:
i knew it! what a mess! so, where is the file, clear instructions and finally g5 result? hurry up!

[wawrzon]

@kas1e: mufa might mix something up, although as another native polish speaker i must confirm that he explicitely claims that his version of lame is altivec enabled. time for him to confirm or contradict that, otherwise we must assume pirus graph is correct, besides...

@piru: ..has it now been confirmed that the same file has been used for the test??

[wawrzon]

@karlos, yeah, just thought the same, even if file was not placed in ram for conversion. my i7/2.93 needs 7s:

C:\Programme\Lame For Audacity>lame AKsack.wav AKsack.mp3
LAME 3.99.3 32bits (http://lame.sf.net)
Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz
Encoding AKsack.wav to AKsack.mp3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III (11x) 128 kbps qval=3
    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
 10529/10529 (100%)|    0:07/    0:07|    0:07/    0:07|   36.295x|    0:00
-------------------------------------------------------------------------------
   kbps        MS  %     long switch short %
  128.0      100.0        74.4  13.4  12.2
Writing LAME Tag...done
ReplayGain: +0.5dB

[wawrzon]

@kas1e: bad! now you are overreacting. in the end this practical benchmark in comparison with karlos and mine native x86 test shows, that x1k or mac mini for that matter, is almost as usable as middle range about up to date pc hardware. its surely not the whole truth, more to come, but i wouldnt call results devastating. the other question is as always if it is worth these investments but the question stands as it did, nothing changed for better or worse.

[wawrzon]

I realise it's a bit off topic

at least on blender test my i7 rig fits the expectations 00:39.26. so that might be a more dependable benchmark-

[wawrzon]

is there a way to influence it?

[wawrzon]

I seem to recall an option in the render settings somewhere for the number of threads, which seemed to be set to 4 on my quad core. Probably be 8 on yours if it is counting logical cores.

ah, didnt knoew one needs to set it manually within the app like on on lightwave. another thing amiga has introduced in advance. lol. so may previous result was with one thread since this is default, with 8 i get the picture done in 00:08.80