More > JRiver Media Center 23 for Windows

Problem with JRiver 23 and ASIO

<< < (3/7) > >>

Hung:
Hi,

Please check for benchmark:

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
    Single-threaded integer math... 4,544 seconds
    Single-threaded floating point math... 3,097 seconds
    Multi-threaded integer math... 2,289 seconds
    Multi-threaded mixed math... 1,575 seconds
Score: 1651

Running 'Image' benchmark...
    Image creation / destruction... 0,230 seconds
    Flood filling... 0,242 seconds
    Direct copying... 0,778 seconds
    Small renders... 1,040 seconds
    Bilinear rendering... 1,435 seconds
    Bicubic rendering... 0,912 seconds
Score: 4745

Running 'Database' benchmark...
    Create database... 0,152 seconds
    Populate database... 0,855 seconds
    Save database... 0,169 seconds
    Reload database... 0,092 seconds
    Search database... 1,104 seconds
    Sort database... 0,679 seconds
    Group database... 0,637 seconds
Score: 5830

JRMark (version 23.0.72 x64): 4076

JimH:
A good machine, not a great one.  Maybe not enough for heavy DSD conversion.

Hung:
It is NUC 7i5BNH, 8G Ram, 128 SSD. So can you let me know what is enough configuration for output coding with lowest level (1xDSD, Asio native) on MC 64x ?

JimH:
You probably know more than we do at this point.  Just keep testing to see what works.  When you do find out, please post here again.

Awesome Donkey:
Unless I'm mistaken, that NUC only has a Core i5-7260U which is a dual core, four thread CPU. If so, that's where your bottleneck is when forcing the DSD output formatting. It's simply not powerful enough to handle on-the-fly conversion to 8xDSD, for example. It *might* be able to do 1xDSD, but don't be surprised if it can't handle even that.

Navigation

[0] Message Index

[#] Next page

[*] Previous page