OraStream Posted December 4, 2017 Share Posted December 4, 2017 On 11/30/2017 at 11:33 PM, The Computer Audiophile said: One thing I struggle with is the sentence, "Audio streaming will be directly from the original record masters to web browsers." Using a web browser for high end playback is the worst. Audio is usually routed through the OS mixer and there are little to no options. Plus, there is no remote control for sitting and listening, you must be at your computer. Web browser listening is great for the times while I'm working at my computer, but the need for high resolution is usually diminished during these times. Anyway, just a thought. At its current state of development, Web Audio don't have sample rate matching; hence the output audio is determined by the OS (as Chris has pointed out) and DAC support. Development, however, is progressing so sample rate matching in Web Audio protocols won't be too long away. There are other matters relating to web audio, e.g. stuttering on initiating some PC apps. On the other hand, it has made native resolution audio more broadly accessible to music consumers, e.g., casting 96.24 audio to speakers with the $35 Chromecast Audio. Both OraStream and BRIO desktop apps implement sample rate matching. Both apps also interface to networked players, such as, DLNA/UPnP renderers, SONOS, Chromecast and BluOS player devices. They would be available when the service requires them. asdf1000 1 Link to comment
OraStream Posted December 5, 2017 Share Posted December 5, 2017 10 minutes ago, Em2016 said: Hi, when you say 'when the service requires them' do you mean when NYA approves support with these desktop apps? We provide adaptive audio streaming and web/native audio player implementations (OraStream's tech) for desktop and mobile platforms. While we also develop front-end client apps, services don't necessarily need to use them as is with the Neil Young Archives. Link to comment
OraStream Posted December 5, 2017 Share Posted December 5, 2017 39 minutes ago, Em2016 said: Thanks for clarifying. For bit perfect playback (with sample rate matching) perhaps it should be looked at for NYA? Soon? Thanks - please provide via customer feedback to the Archives. Kind regards. Link to comment
OraStream Posted December 8, 2017 Share Posted December 8, 2017 On 05/12/2017 at 8:01 PM, mansr said: It doesn't matter how much CPU power you throw at it. The problem is the way Firefox schedules its activities. By default, all tabs share a single process, so rendering a large page in another tab easily makes audio stutter. The number of processes can be increased by opening the about:config page and increasing the value of the dom.ipc.processCount setting. It seems to help with the stuttering here. Bear in mind that each process adds at least few hundred MB of memory usage, so don't go too crazy. A new player build has been deployed to the NY Archives. It uses multi source nodes to schedule audio buffering - helps reduce audio stutter. Also enables HTTP fetch to benefit users on supported browser (Chrome, Safari, Opera) with streaming delivery via CDN and higher audio (bitrate) quality. LDF 1 Link to comment
OraStream Posted December 9, 2017 Share Posted December 9, 2017 OraStream server backend support http and https requests. Link to comment
OraStream Posted December 9, 2017 Share Posted December 9, 2017 2 minutes ago, mansr said: Ok, then it's an issue with NYA. Think https is available on NYA. Link to comment
OraStream Posted December 26, 2018 Share Posted December 26, 2018 Hi Chris In case CA readers missed this, the Neil Young Archives mobile app is available on the App Store. Users' reviews have been good!. Seasons' greetings! The Computer Audiophile 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now