Is offline listening coming to the PC player?

 BillG wrote: 
I believe the problems I was having in Chrome may have had nothing to do with Beta Player but some sort of more general memory leak since it began happening with other sites.  Now that I've solved that issue I will have to re-test it.

Testing the beta web player against foobar2000 + 320 aac link and ASIO on my big sound system. Well, Foobar win the test, much better sound and the memory usage went down 800 megs...    Just saying !  
testing 1-2. :-)   On a small sound system ( computer's speakers)  or a Bluetooth speaker, I doubt that people would see such a big difference.  

Thanks again for your hard work,  both of you...

 BillG wrote: 
thanks for answering...  Good to know, I'll keep using Chrome.  It sound very good .  I never thought I would be using a Html 5 plugin instead of foobar 2000 and the 320 aac...  When I'll have a chance i'll listen to both at higher volume on my large speakers and test.  The only problem is the amount of memory it use in chrome, almost 1 gigs . I lowered the slide show to 720P and audio buffer to 5 minutes...no Ken Burns and it use 960 megs right now..  maximum audio quality.

It must be costly to have so many streams formats ?    I'll explain this to my friends and on my Facebook page about music.  It's time for a donation.. 

 siriuss wrote: 
The beta player uses Vorbis in Chrome & Firefox, MP3 in Edge & IE, and AAC in Safari.

The audio dynamics processing is completely different in the beta player — though both the beta & main stream are very lightly processed, so the difference probably isn't glaring. The main stream is processed via an FM-style Optimod multiband compressor-limiter & the beta player uses individual song files that are processed via a mastering plugin called Ozone 6.

In both cases, 90% of the 'processing' involves adjusting the overall track level to account for differences in density — turning the old stuff up & the new stuff down, in the simplest terms.

 The Edge browser finally work fine with the beta player.  Very cold day in Canada so everybody is on the internet, hiccups can happen.  And my kid is hugging the bandwidth . Good sound . Sound like Vorbis to me.   At 63 I don't have the hearing to tell so much, but AAC has less bass than Vorbis.  If you need more testing just ask.
Thanks for your hard work.

 BillG wrote: 

The beta player is working well in chrome + win 10 .  6 gigs of ram.  Asus essence stx audio.

I am quite surprised by the quality of the sound ( very good)   usually I use foobar and the 320 aac link + ASIO. The beta player is almost as good. What codec do you use in the web player ?  vorbis ?

With the PSD tool, it's almost better to use the web player than the  AAC link in Foobar2000. Only if I raise the volume to "somewhat loud" I can hear the difference.   Going to test it more right now .

I went to test it again with chrome + win 10 and i only hear the welcome speech 15 seconds and the circle start turning  and turning...    Going to test with edge.  :  Edge not playing nothing, turning dots only.   Going back to foobar 2000  :-)  and will test more after a reboot.

Would be nice to have a Ogg Vorbis 320 and I would pay $8 canadian a month for Flac 500-600kbs. I wish I had more money, you guys worth more than I can give.

But I push on my rich friends to make their donations  :-)  and a LOT of advertising.

 Mwrwellcom wrote: 
It's so frustrating that all the iOS devices and ATV only stream to one site, whereas the iTunes on OSX streams simultaneously to multiple locations. Can't they at least pretend that Steve is watching them so they do things right?

 BillG wrote: 
Ah. I knew I wasn't tracking something...

 ScottFromWyoming wrote: 
That's a web app?  Meaning, it runs in Safari?

 BillG wrote: 
MLB At Bat lets me choose the airport express from my iPad2. 

 Mwrwellcom wrote: 
Apple doesn't provide a way to add that function to a web app.  However, you can use Airfoil to route audio from any app (including whatever web browser you're using for RP) to Airport Express.

You should also be able to route system audio (everything from your Mac) to Airport Express by option-clicking on the audio icon in the menu bar. Works with AppleTV, anyway.

I ALWAYS stream RP through my Airport network to at least 2 different Airport Express-connected stereos. Is there a way to put that functionality into the web app? I use the iTunes Internet Radio stream, with some success, but usually end up running one of the mobile apps from my iOS devices. Oddly, the most robust, and the most often used, is a gen 1.0 iPod touch, which runs a very old version of the app.... Everything else seems to drop, or skip or freeze at random.
I guess I would love a robust Web app that I could stream to my remote devices.
Oh, and we LOVE RP! 

 BillG wrote: 
Yep looks like a resource issue.  You think with a sizeable amount of memory and such it would be but it is an old system.  Thanks for the response.

 xtalman wrote: 
Sounds like a CPU-resource issue rather than a network issue.  What does Activity Monitor tell you about what's going on? 

Been using this a while now and while mostly good it does have a tendency to sound like some of the tunes are skipping.  Not sure why.  Other stream fine.  Using Firefox on OSX at work mostly with a gigabit connection.

New release out. Still some interface issues, but the underlying player code is greatly improved. Under most circumstances, it should be crash-free & solid.

Of course now that I've said that out loud...

 elshagon wrote: 
Still haven't had a chance to check out Chrome + Win10.  I only have one Windows system here (we're Macs & Linux normally) and I'm currently running an extended test in Edge — coming up on 2 days with no crashes.

I tried it with 3 different pc's all x64 with Windows 10 and Chrome.  They all have the same extensions running in Chrome, but with two of the 3 pc's the beta crashes quickly.  The pc's have 6, 6 and 8 gb memory.  The one that doesn't crash is the pc with the least amount of computing power, the two which crash are high end.

 I looked at the more tools - task manager in Chrome as you suggested and see it do the following:
1.  On pc with no crashes memory hovers around a constant 800kb
2.  On 2 pc's with almost instant memory crash the memory quickly rises to near 3 GB and then the page crashes.

With the 2 pc's where the beta crashes it plays fine in the Microsoft Edge browser.  One pc has an ATI video card and the other an Nvidia.

edit:  I kept trying to figure what was causing the memory leak but just started it up again and it's playing without problems now at a steady 1.4 GB memory usage without crashing.  I will keep testing it on Chrome to see if it continues to play correctly.  Thanks again for running one of my favorite pleasures!
 

 BillG wrote: 
A little over 1 GB like you, between 1.1 and 1.2, I'm going to try it on Microsoft Edge browser

edit:  It's been playing fine on Microsoft Edge for a half hour, so it must be a Chrome thing.