[RonCH]

Hi James and Chris, 

Have you thought about providing something like a RESTful API to the BDP functionality?  This would allow developers to write applications ( a rich client )  that could control  ( and display the state of ) the BDP.  I'm not a huge fan of the mobile apps for the BDP around at the moment ( MPD clients )

This could of course work along side of the BDP being able to render the web pages itself.

What are your thoughts here?

regards
Ron

[tatcom]

+1 on that!

[dznutz]

I agree, the BDP is fantastic, all it needs is a nicer and more modern interface much like what sony and lumin have going on

[Phil A]

I've mentioned before that JRiver has a linux version.  Never seen it in action but the one thing that has kept me from seriously looking at the BDP-2 is the interface.  Almost was ready to seriously look at it about a year back and asked some questions of a friend who is a big Bryston fan and a reviewer and that's what held me back.  I'm hoping that they will do a BDP-3 next year and think about it.

[abuhannibal]

I have used the JRiver Linux version. It's fine - basically the same as the windows version minus a few things which Linux handles differently, such as updates. Works fine and I have found it to be stable, however, while I would not say that the UI is maddening (I know it well at this point and have kinda grown to love it) there is no doubt that their documentation lags seriously behind the code base. And they are also a little behind the curve in things like Tidal integration, though time will tell how important that proves to be.  So far though, still what I use on a daily basis.

[Phil A]

I have used the JRiver Linux version. It's fine - basically the same as the windows version minus a few things which Linux handles differently, such as updates. Works fine and I have found it to be stable, however, while I would not say that the UI is maddening (I know it well at this point and have kinda grown to love it) there is no doubt that their documentation lags seriously behind the code base. And they are also a little behind the curve in things like Tidal integration, though time will tell how important that proves to be.  So far though, still what I use on a daily basis.

I'm just used to the interface.  I have (Windows 10) music servers with it, my main PC and back-up PC as well.  In three other back-up systems I use the Oppo Media Control App. I can use JRiver but don't use them enough to be motivated to change.  One of these systems is used primarily for HT (and daytime TV) where I have an Oppo 203 (along with a preamp with HT Bypass and a 2-channel amp), another is the upstairs bonus room and that gets used literally a couple of times a year and the one I use the most is the master bedroom system where I have an Oppo 103D and the system feeds the outdoor speakers.  So several times a year I use it but not often enough to worry about the interface.

[unincognito]

In regards to your title, it is, the firmware is stored in a squashfs filesystem, used by many live and embedded environments.  All our code is written in python, php, perl and node; for those not in the know the code is there and compiled each time the program or library is called/executed.  MPD is available externally and it's commands for managing and playback are well documented.

But we'll consider it

[RonCH]

In regards to your title, it is, the firmware is stored in a squashfs filesystem, used by many live and embedded environments.  All our code is written in python, php, perl and node; for those not in the know the code is there and compiled each time the program or library is called/executed.  MPD is available externally and it's commands for managing and playback are well documented.

But we'll consider it

Hi Chris,

Thanks for your reply.

I'm just interested in having a public API to BDP functionally.   And it's not good practice to put hooks into your code - when you update or refactor your code mine would break.  I would prefer a more decoupled solution.  That's why I suggested something like a REST API.  The BDP is already a web server, so a RESTful API could sit nicely along side that. 

You're correct that I could just implement another MPD client, but the BDP is much more than just a MPD server ( it provides Tidal, CD Backup and other services ).   

regards
Ron