What is Nero Score?
Nero Score measures your processor’s (CPU) multi-core power and is pushing your graphics card (GPU) to it’s maximum limit with real world multimedia use cases.
Nero Score is used by journalists to review hardware, hardware manufacturers to optimize their latest products, as well as computer owners to evaluate their individual system to make purchase decisions.
What kind of benchmarks are included in Nero Score?
The initial version of Nero Score includes an CPU AI benchmark and measures how many pictures per second can be processed with artificial intelligence on the given CPU. So this in not about training an model, but actually applying a trained model on data (called inference). The outcome of this test will let you compare how different CPUs score in this domain. The result can be 1:1 matched with CPU-based AI inference solution, like e.g. Nero AI Photo Tagger. The data set for this test includes 50 pictures that will be inferred 3 times each. The format and size of the pictures doesn’t matter for this test as the AI inference only needs an input of 299×299 pixels in size anyway.
What kind of tests will be next in Nero Score?
The roadmap for Nero Score foresees an extension into further multi-media related use cases utilizing CPU and multiple GPUs e.g. video encoding, streaming, applying video/audio/photo effects.
How is the score calculated?
Nero is fully transparency on the calculation of the actual score. Each of the tests executed within Nero Score will generate a score of it’s own. For example: The CPU AI benchmark measures how many pictures are processed per second. This number is multiplied by a factor of 25 to generate the score for this specific test. So there is a 1:1 relation between the score and the performance of the CPU for the given task. A PC with twice the score will be twice as fast.
As soon as there are more tests a total score will be calculated from the single results and the simple formula for this calculation will be made transparent, too. Over time there might be changes on how the score is calculated, those will be called out and documented with revisions to ensure that results are always reproducible and comparable.
What should be considered before/While running a test?
- Laptops should be connected to a power supply.
- The high performance power plan should be selected on any device.
- All open applications should be closed.
- No user activity should be done in the foreground.
- Background activity should be avoided e.g. no virus scans, software update downloads, cloud uploads.
Which kind of platforms are supported by Nero Score?
At the moment Nero Score is supporting Windows 10 64-Bit exclusively.
How can I get Nero Score?
Nero Score is only available to selected partners at the moment. A public release is planned for March 2021.
Which languages are supported by Nero Score?
English (en-US), Russian (ru-RU), French (fr-FR), Spanish-Espania (es-ES), German (de-DE), Turkish (tr-TR), Dutch (nl-NL), Portuguese-Brazil (pt-BR), Polish (pl-PL), Italian (it-IT), Chinese-Traditional (zh-TW), Portuguese (pt-pt), Korean (ko-KR), Chinese-Simplified (zh-CN), Czech (cs-CZ), Danish (da-DK), Finnish (fi-FI), Japanese (ja-JP), Swedish (sv), Hungarian (hu-HU), Greek (el-GR), Norwegian (nb-NO), Portuguese-Portugal (pt-PT), Swedish (sv-SE), Romanian (ro-RO), Slovak (sk-SK), Ukrainian (uk-UA), Vietnamese (vi-VN), Indonesian (id-ID)
Technically not supported at the moment: Thai, Hebrew, Arabic, Spanish-Mexico.
IS Nero Score run FIT for running at the PoinT-of-Sale (POS)?
Absolutely, there is an offline versions available that allows unattended operation on POS hardware.
Are there command line options available?
Yes, for example “C:\Program Files (x86)\Nero\Nero Apps\Nero Score\NeroScore.exe” runtimes:50 stoptime:3 logfile:1 will executed the current test 50 times with a pause of 3 seconds in between and create a log file in %temp%\NeroScore (so inside he current users system temp folder).
- runtimes: number of times the test should be run
- stoptime: time between the runs in seconds
- logfile: defines if a log file should be generated 1 = yes / 0 = no
- logfilepath: alternative path for the log file e.g. “E:” or “D:\Score”
- autoexit: defines if the application should exit after all tests are done 1 =yes / 0 = no
- language: use any of the above 4 letter codes to define the application language manually (e.g. es-ES)
- exepath: runs a specific application on exit (e.g. “C:\WINDOWS\system32\notepad.exe”)