If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The change you made to browse-functions.js did not fix the first problem. The artist_id is still undefined.
Whilst I cannot be 100% certain, as I do not use Qobuz, but if the selection from the "(...)" menu works then the selection from this list should now too - as I added the artist_id parameter there.
Please ensure you fully re-load the page. Especially with dev versions the browser likes to load from cache. With Chrome you just need to open the dev tools, press and hold the refresh button, and select "Empty cache and hard reload"
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
IThe bottom bar, like in the other devices and orientations, is even more problematic when the page controls are hidden.
Again, your screenshot shows an unusable (for most) layout (the queue is way too thin). Yes it may be fine for you (and that's fine, your device your choice) but it is not a layout that I am going to explicitly cater for.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Not sure how that is relevant. Just use "auto" layout and the most suitable layout should be chosen.
The auto layout gives me the non-Desktop version on an iPad in portrait mode, but the desktop mode when in landscape mode. It is exactly this switching that I don’t want. There is plenty of space for the Desktop mode on a Retina display in portrait mode, so I force desktop layout so that the controls are in the same location on all devices regardless of orientation or resolution. This has value, esp. for my wife on our home system iPad (used for home automation and kitchen use).
Again, your screenshot shows an unusable (for most) layout (the queue is way too thin). Yes it may be fine for you (and that's fine, your device your choice) but it is not a layout that I am going to explicitly cater for.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
What about the following (ignore alignment, colours, etc - only mockups):
Local files (cover on left, artist image on right):
Online services (cover art on left, logo on right):
Other streams (cover art on left, generic icon on right):
...also I think these images should be hidden when insufficient space (the exact amount to be decided)
I think this is a terrific solution. The balancing of the cover art and the artist image/spotty logo looks elegant and the solution of hiding them if there is a space issue is perfect.
Nicholas
RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
also use a Gramofon off platform
One question - if you are listening to a radio stream like BBC Sounds there is often quite a large radio text displayed where the album name is. This is often truncated at the moment. Will that continue to be the case? Should or could it be scrolled?
Nicholas
RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
also use a Gramofon off platform
One question - if you are listening to a radio stream like BBC Sounds there is often quite a large radio text displayed where the album name is. This is often truncated at the moment. Will that continue to be the case? Should or could it be scrolled?
No, scrolling text will not be implemented, sorry.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
One question - if you are listening to a radio stream like BBC Sounds there is often quite a large radio text displayed where the album name is. This is often truncated at the moment. Will that continue to be the case? Should or could it be scrolled?
[ATTACH]38523[/ATTACH]
It isn't truncated in the mobile layout [emoji2]
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
No, scrolling text will not be implemented, sorry.
Fair enough; scrolling makes everything look like we're stuck in the last century
Nicholas
RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
also use a Gramofon off platform
I've made some changes in git/master to help with this, would be great if you could test. If you do not know how, then don't worry - I'll make a release soon.
Sorry for late response - yes this is now a lot better - thanks for the effort.
Oh so it is. Thanks! I'm about 80% mobile : 20% desktop on the laptop. Should have noticed that myself.
Nicholas
RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
also use a Gramofon off platform
...actually it only looks nice in those screenshots. The following (IMHO) looks awful:
...think I might just go back to left aligned text. As center aligned there is no nice place to put the cover art.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
There is no explicit mini player - just shrink the window.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment