Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[AndreaT]

Dear All,

I am evaluating the actual MC 23 player. I am comparing it to my usual Foobar 1.3.16 solution.
I configured both exactly in the same way, using the same VST plug-in (Thuneau Allocator and Voxegon PristineSpace).
The DAC I use is the MOTU 896, USB 2 interfaced via its own Windows ASIO drivers.

My PC is a Dell D-830, 4GB RAM, 2.2 GHz dual core processor,  running Windows 7 32bit with all the available updates installed.
Windows Defender and Windows Firewall are operating with default setting.

MC 23 is reported to use less than 300MB RAM, while it consumes over 80% of the CPU power.

When playing MC 23 I suffer from continuous audio stream micro interruptions.

To be noted that the MOTU DAC is configured at 96kHz having 2048 samples buffers set.

The PC is dedicated to the job and this problem doesn't occur when playing with Foobar.

Is there any task prioritizing setting or anything and I can try to solve this annoying problem?

Thanks and regards
Andrea

[JimH]

Try turning off auto import and thumbnailing. 

[blgentry]

I think your computer is rather low powered.  How about running JRiver's benchmark and posting the end result.

Help > Benchmark > Run Benchmark

If, as I suspect, your machine has limited CPU power, I would suggest you start by turning off all of your VSTs.  Then see if it plays OK.  This might take some experimentation to find a configuration that works well and meets your needs.

Brian.

[JimH]

A VST bug was found and fixed today.  A new build should be available in a day or two.

[AndreaT]

Dear JimH, thanks for your correctness and prompt notification of a found bug. I will wait for the fixing and I will retest all again.

Dear blgentry, herein the results of the Benchmarks execution:

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

Running 'Math' benchmark...
    Single-threaded integer math... 4,927 seconds
    Single-threaded floating point math... 3,085 seconds
    Multi-threaded integer math... 5,129 seconds
    Multi-threaded mixed math... 3,233 seconds
Score: 1160

Running 'Image' benchmark...
    Image creation / destruction... 0,326 seconds
    Flood filling... 1,965 seconds
    Direct copying... 2,944 seconds
    Small renders... 3,167 seconds
    Bilinear rendering... 4,855 seconds
    Bicubic rendering... 2,839 seconds
Score: 1367

Running 'Database' benchmark...
    Create database... 0,480 seconds
    Populate database... 5,462 seconds
    Save database... 1,877 seconds
    Reload database... 0,334 seconds
    Search database... 2,510 seconds
    Sort database... 2,046 seconds
    Group database... 1,208 seconds
Score: 1545

JRMark (version 23.0.30): 1357

Thank you all for the support
Kind regards,
Andrea

[Awesome Donkey]

Yeah, that's a pretty low score.

Have you tried increasing the buffer of the driver (ASIO) you're using?

[JohnT]

I see you're running build 23.0.30.  Since the VST bug wasn't introduced until build 23.0.32 and causes an immediate crash, I don't think that's the source of the problem.

[ssands]

You might also want to check if there are any background tasks that might impact performance, such as anti-virus scan, automatic backup.

[pompon]

You might also want to check if there are any background tasks that might impact performance, such as anti-virus scan, automatic backup.

Same problem with motu 1248.
I have the most powerfull gaming laptop here.mchange the pc will not do the tricks.
Motu driver are bad.

It's not possible to tell windows to stop antivirus scan at my knoledge. Cant kill the process.

When the next song is loaded in momory, its create a click pop in the soung currencly playing.

My exasound dac dont have this problem at all.

[mojave]

I have the MOTU 1248 and Ultralite AVB. No issues here. By the way, MOTU just released new drivers on August 14. 

The Allocator manual recommends setting your ASIO buffer size to 8192 samples to eliminate stutter since Allocator process audio in 8192 samples.

[AndreaT]

Dear All,

the new 23.0.36 is OK: no more micro interruptions audible.

Compared to the 23.0.30 the new 23.0.36 (on my PC) uses only 60% of CPU resources and the RAM allocation is stable around 311MB (ver 23.0.30 had peak up to 450MB).

Also MC Benchmarks give bit better numbers:

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

Running 'Math' benchmark...
    Single-threaded integer math... 4,888 seconds
    Single-threaded floating point math... 3,042 seconds
    Multi-threaded integer math... 5,153 seconds
    Multi-threaded mixed math... 3,302 seconds
Score: 1160

Running 'Image' benchmark...
    Image creation / destruction... 0,282 seconds
    Flood filling... 1,992 seconds
    Direct copying... 2,908 seconds
    Small renders... 3,165 seconds
    Bilinear rendering... 4,849 seconds
    Bicubic rendering... 2,868 seconds
Score: 1370

Running 'Database' benchmark...
    Create database... 0,527 seconds
    Populate database... 3,931 seconds
    Save database... 1,446 seconds
    Reload database... 0,294 seconds
    Search database... 2,631 seconds
    Sort database... 2,045 seconds
    Group database... 1,197 seconds
Score: 1781

JRMark (version 23.0.36): 1437

Thanks to MC Team for the optimization of the new build.
Kind regards
Andrea