INTERACT FORUM

Devices => PC's and Other Hardware => Topic started by: Zoltrix on June 08, 2024, 10:53:17 pm

Title: These benchmarks too low to run JRiver?
Post by: Zoltrix on June 08, 2024, 10:53:17 pm: Hi all,

I'm currently running latest version of JRiver on a Windows 10 PC, specs are:

AMD A8 7600
32GB RAM
Nvidia GeForce 1050

Screenshots of benchmarks are attached.

For Video settings I've enabled "Red October JRVR" and "Hardware accelerate video decoding". For Audio I've turned on bitstreaming.

Overall runs pretty well, but during playback of a movie (4k Remux) I'll get 2-3 short audio dropouts. Checking task manager (screenshot attached), GPU usage seems ok, but sometimes CPU will spike to 100%.

Is the CPU just too old to be trying to play this type of content?

Cheers,
Zolt
Title: Re: These benchmarks too low to run JRiver?
Post by: JimH on June 09, 2024, 04:32:30 am: Try turning off hardware acceleration.

JRVR has settings for low powered machines.
Title: Re: These benchmarks too low to run JRiver?
Post by: Zoltrix on June 09, 2024, 04:37:32 am: Thanks for the tip JimH. Would turning off hardware acceleration result in less quality in terms of picture?
Title: Re: These benchmarks too low to run JRiver?
Post by: Zoltrix on June 11, 2024, 07:39:02 am: Perhaps should have purchased the Mac license, but I already have the Windows one now.
Title: Re: These benchmarks too low to run JRiver?
Post by: Zoltrix on July 21, 2024, 08:39:15 am: After many weeks, and trying three different computers and Win10 and Win11, found the solution here: https://yabb.jriver.com/interact/index.php?topic=137521.0

Man what a waste of time.

I think has others have said, might be a good idea to remove (or provide a warning) for those people trying to use DirectSound.
Title: Re: These benchmarks too low to run JRiver?
Post by: JimH on July 21, 2024, 08:55:16 am: Quote from: Zoltrix on July 21, 2024, 08:39:15 am
After many weeks, and trying three different computers and Win10 and Win11, found the solution here: https://yabb.jriver.com/interact/index.php?topic=137521.0

Man what a waste of time.

I think has others have said, might be a good idea to remove (or provide a warning) for those people trying to use DirectSound.
Were you also bitstreaming? What did you change?

More details, please.
Title: Re: These benchmarks too low to run JRiver?
Post by: craigmcg on July 22, 2024, 03:25:04 pm: Based on Zoltrix's comment "I think has others have said, might be a good idea to remove (or provide a warning) for those people trying to use DirectSound." I'm wondering if there would be value in MC 32 or 33 now changing the default audio output from the legacy DirectSound to WASAPI.

I believe that DirectSound has been the default for several years before the introduction of WASAPI and, as the old versions of Windows which didn't have/support WASAPI are no longer supported by MS, I suspect that changing the default from WASAPI would not cause much confusion.

My two cents.
Title: Re: These benchmarks too low to run JRiver?
Post by: Awesome Donkey on July 22, 2024, 04:45:46 pm: Making WASAPI the default? Interesting idea, though if such a thing is considered exclusive mode should be disabled by default otherwise people are going to complain about system sounds, browser audio, etc. isn't working during playback or pausing playback.

Honestly it might be worth splitting WASAPI into two audio output options (without having a exclusive mode checkbox in device settings, just straight split it in two); WASAPI (which would be shared and the default) and WASAPI Exclusive. That would likely be a bit more clear to most users and it would make it easier to enable exclusive mode to achieve bit-perfect playback with one setting change (instead of having to go into the device settings and enable it there).
Title: Re: These benchmarks too low to run JRiver?
Post by: craigmcg on July 22, 2024, 05:23:24 pm: Quote from: Awesome Donkey on July 22, 2024, 04:45:46 pm
Making WASAPI the default? Interesting idea, though if such a thing is considered exclusive mode should be disabled by default otherwise people are going to complain about system sounds, browser audio, etc. isn't working during playback or pausing playback.

Honestly it might be worth splitting WASAPI into two audio output options (without having a exclusive mode checkbox in device settings, just straight split it in two); WASAPI (which would be shared and the default) and WASAPI Exclusive. That would likely be a bit more clear to most users and it would make it easier to enable exclusive mode to achieve bit-perfect playback with one setting change (instead of having to go into the device settings and enable it there).

I totally agree with your suggestion of splitting WASAPI Shared (being the default) with WASAPI Exclusive as an option; I was thinking about the exclusive related complaints while sitting by my big green egg grilling supper after posting and your suggestion definitely provides a clearer choice for new users.
Title: Re: These benchmarks too low to run JRiver?
Post by: JimH on July 22, 2024, 08:35:18 pm: I believe that our default WASAPI is not exclusive and that a user must explicitly set exclusive. That seems safe.
Title: Re: These benchmarks too low to run JRiver?
Post by: Zoltrix on July 23, 2024, 05:50:11 am: Quote from: JimH on July 21, 2024, 08:55:16 am
Were you also bitstreaming? What did you change?

More details, please.
Good suggestions regarding WASAPI being default.

And to confirm, yes I was using bitstreaming as well, and the issue seems to carry across multiple Windows versions and hardware types.

The issues occurred on:
Intel Core i750 950 / GTX 1050 (Windows 10)
AMD A8 7600 / GTX 1050 (Windows 10)
Intel Core i5-13600T / UHD Graphics 770 (Windows 11)
Intel Core i7-9750H / GTX 1650 (Windows 11)