Print

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

[Hugo]

Editor's note: subject formerly: "perhaps a stupid question about my internal browser"

Hello,
My first post, so please be gentil  
I'm using JRiver19 on W7. My internal (chrome) browser after updating W7 went into an external one. JRiver was killed by the update process.
I cannot easily reverse this.
Can anyone help?
Kind regards, Hugo

[MrC]

So you had your Options > Tree & View > Web Browser > Engine set to Chromium?  And now you can't run MC anymore (it crashes)?

If so, I wonder if just changing the registry key:

   HKEY_CURRENT_USER\Software\JRiver\Media Center 19\Properties\Web Browser - Engine  to the default value of IE will be sufficient?

You might try it - quit MC, open regedit, and find that key and examine / change the value.

Was that gentle enough?  :-)

Welcome.

[Hugo]

Was that gentle enough?  :-)

Welcome.

Yes that's not too scary, now I can tune up the question  , thanks for the welcome  .

So you had your Options > Tree & View > Web Browser > Engine set to Chromium?  And now you can't run MC anymore (it crashes)?

No the killing was only temporary, and as I just found out, not the real issue. I can still use JRiver properly, only my browser keeps popping up externally whenever I download external screens (like with help or performer store). I'd better start from scratch explaining this...
I just bought a fanless ITX to run JRiver on. However, as it's only 1Ghz fast, it has problems with iso-files from sacd's. It will use 100% cpu and start to stutter. So I quit a lot of processes, including all (!) windows components. Now I find out that some are needed to show websites internal in JRiver. Do you know which ones that are?
And best of all: could you help me speed up either W7 or JRiver? Are there any settings that could reduce JRiver's usage of CPU with SACD sampled to 192/24?

[MrC]

...So I quit a lot of processes, including all (!) windows components. Now I find out that some are needed to show websites internal in JRiver. Do you know which ones that are?

Great, now that you're an old timer and are feeling comfortable... You're pretty much on your own once you start killing Windows procs, esp those that are required by the IE (or Chromium) browser control.

SACD at 192/24 will place a load on the system - I don't know the minimum requirements for this.  But I don't think you're going to squeeze out more speed by killing (generally already optimized) Windows processes.

[Hugo]

Great, now that you're an old timer and are feeling comfortable... You're pretty much on your own once you start killing Windows procs, esp those that are required by the IE (or Chromium) browser control.

hmmm  I can understand that, have to put them all on again I guess

SACD at 192/24 will place a load on the system - I don't know the minimum requirements for this.  But I don't think you're going to squeeze out more speed by killing (generally already optimized) Windows processes.

Is this the place to also make a note about the system requirements for SACD to 192/24?

I already had to shut down automatic w7-update, firewall and scanning to make listening without resampling work properly.
So in general, JRiver on W7 requires (much) more CPU than my AMD 1Ghz, is my current finding.

Is there anyone else with some advise (except from speeding up the motherboard)?

[MrC]

I'm sure some others will chime in regarding the min. requirements for SACD 192/24.  I've changed your Subject so that others are more likely to notice what you're after.

Edit: I've pinged an expert on this...  Hold tight.

[Hugo]

ok thanks for the help; I have the internal browser working again.

[6233638]

Is this the place to also make a note about the system requirements for SACD to 192/24?
So in general, JRiver on W7 requires (much) more CPU than my AMD 1Ghz, is my current finding.
Is there anyone else with some advise (except from speeding up the motherboard)?

Unfortunately, it sounds like your system is going to be underpowered for playing back DSD/SACD.
Try running the JRMark benchmark (Help → Benchmark) and post your overall score here.
I think a score of around 2000 is the minimum requirement for stereo DSD conversion to PCM - but this only applies to files which are not using DST compression. (DSF files, or uncompressed SACDs)
 
Converting to 176.4kHz, 88.2kHz, or 44.1kHz rather than 192kHz may lessen the CPU requirements, but that is a complete guess based on the fact that DSD's sample rate is 44100x64.
If you are currently using Memory Playback (Tools → Options → Audio → Settings → Play files from memory…) try disabling it - or try enabling it if you are not.
 
 
If your DAC supports DSD natively, enabling bitstreaming should considerably reduce the system requirements for DSD playback, but prevents you using other DSP options in Media Center.
This is found under: Tools → Options → Audio → Settings → Bitstreaming
 
 
Failing that, you could always use Media Center's offline conversion tools (Tools → Advanced Tools → Convert Format…) to convert from DSD/SACD to 192kHz FLAC files or another format of your choosing.
 
This would not be a lossless conversion as you are converting from DSD to PCM - so you may wish to keep the original files - but assuming your system can play high-res PCM files without any trouble, it should be able to play these.

[InflatableMouse]

What I'm missing is how your SACD's are stored. Are you playing native SACD (ie, DSD) or are they already converted to flac (but sourced from SACD)?

This makes a huge difference, as a low powered pc might not be able to convert DSD to PCM on the fly, while it could happily resample PCM sources to anything you wish.

[Hugo]

Hi, first of all thanks for your suggestions. 

Try running the JRMark benchmark (Help → Benchmark) and post your overall score here.

The JRMark is 714. I am a bit surprised; could I have known this up front?

Converting to 176.4kHz, 88.2kHz, or 44.1kHz rather than 192kHz may lessen the CPU requirements, but that is a complete guess based on the fact that DSD's sample rate is 44100x64.
If you are currently using Memory Playback (Tools → Options → Audio → Settings → Play files from memory…) try disabling it - or try enabling it if you are not.

I tried both but to little avail; apparently the internal conversion to PCM is the most cpu-consuming; playing from memory gives an extra hickup at the start of iso-playback, further on it levels out.

If your DAC supports DSD natively, enabling bitstreaming should considerably reduce the system requirements for DSD playback, but prevents you using other DSP options in Media Center.
This is found under: Tools → Options → Audio → Settings → Bitstreaming
 
 
Failing that, you could always use Media Center's offline conversion tools (Tools → Advanced Tools → Convert Format…) to convert from DSD/SACD to 192kHz FLAC files or another format of your choosing.

Unfortunately my dac doesn't support DSD.
Your other suggestion is one to go forward on; in the end it gives the proper result I guess, although other formats do leave my pc a bit stressed too and sometimes (for example when I open a browser or at the start of playback) hickuping a bit. But it is a big different stretch from stottering (and I really mean: stottering) to hickuping. 

What I'm missing is how your SACD's are stored. Are you playing native SACD (ie, DSD) or are they already converted to flac (but sourced from SACD)?

This makes a huge difference, as a low powered pc might not be able to convert DSD to PCM on the fly, while it could happily resample PCM sources to anything you wish.

My sacd's are stored natively as dsd in .iso-format.
I will follow your suggestions reformatting them in advance, although I remain open to additional suggestions!
Thanks again.

[InflatableMouse]

If you're going to convert them in advance, backup the original ISO's, don't delete them .

Converting them to 24/88.2 will probably help in playback. My dad's Atom can't play SACD's, but it plays 24/88.2 just fine.