Home of the Squeezebox™ & Transporter® network music players.
Page 572 of 748 FirstFirst ... 72472522562570571572573574582622672 ... LastLast
Results 5,711 to 5,720 of 7479
  1. #5711
    Senior Member Apesbrain's Avatar
    Join Date
    Jun 2005
    Location
    East Coast, USA
    Posts
    1,697
    Is it possible using a custom CSS (prefs/material-skin/css/desktop.css) to fix the size of artwork shown in "Now playing" view to 600px by 600px? If yes, how would I do it? Thanks.

  2. #5712
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by Apesbrain View Post
    1. In "Now playing" view, when you click "off" the "Track information" icon it should return to the "Now playing" view.
    No. I canse why you'd want that, but the view is closed.

    Quote Originally Posted by Apesbrain View Post
    2. Again in "Now playing" view, the "Toggle queue" icon serves no purpose.
    I could make the button appear disabled, but I will not remove it as it'd change the position of the others.
    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.

  3. #5713
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by Shozzer View Post
    With regard to the Toggle Queue button, would it be possible to also toggle so that the Playlist is shown full screen? It would be very useful to be able to see the full names of certain tracks (usually classical tracks) which are otherwise cut off. I know that on the PC you can adjust the amount of space given to the playlist but that isn't available on a tablet. In any case, even with the PC, you can't adjust the screen to show just the playlist.
    You can adjust the size on a tablet, its just trickier.
    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.

  4. #5714
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by afriend View Post
    #2 So all I need now is Material to translate keywords in a track's comment tag (if present, else rating = 0) and set this as the rating value (= as if the 'R' tag had returned this value).
    Using comment field for this is a hack, and I have no intention of supporting that. Material will only read tags via LMS with its 'R' tag nothing else. If you are stating this does not work, then I may as well only support tags with TrackStat - as per existing releases.
    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.

  5. #5715
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by Apesbrain View Post
    Is it possible using a custom CSS (prefs/material-skin/css/desktop.css) to fix the size of artwork shown in "Now playing" view to 600px by 600px? If yes, how would I do it? Thanks.
    Yes. Use your browser's developer tools to determine the CSS path/selector to use.
    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.

  6. #5716
    Senior Member
    Join Date
    May 2006
    Location
    Silicon Valley
    Posts
    644

    Sliding finger on artwork to adjust volume

    Mobile layout: I often use a finger sliding on the "Now playing" artwork display to adjust volume. I like this, but I find that the steadiness of my hands is so bad, that when I lift my finger from my phone's screen, that the volume gets adjusted again at that last instant. Would it be possible to ignore/undo any volume change that occurs in the 50 msecs or so, before this activity stops?


    Needles to say, I was not a brain surgeon.
    Living Room: SB Touch + DIY PSU > CI Audio VDA.2 DAC + VAC.1 PSU > VRX.1 cables > Emotiva XSP-1 Gen 2 preamp + XPA-DR2 amp > Blue Jeans cables > B&W 804 speakers
    Laptop: System76 Galago + Ubuntu 16.04 + Squeezelite + Vivaldi/Material Skin > Emotiva Little Ego DAC > Grado PS500 headphones
    Bedroom: RPi Zero W + Squeezelite > miniBOSS DAC HAT > Bose SoundLink Revolve
    Phone: Pixel 3a + SB Player + Material APK > Senn IE80 earbuds
    Server: Puget Systems Serenity + Ubuntu 18.04 + LMS 8.2

  7. #5717
    Senior Member
    Join Date
    Jul 2010
    Posts
    260
    Quote Originally Posted by cpd73 View Post
    Using comment field for this is a hack, and I have no intention of supporting that. Material will only read tags via LMS with its 'R' tag nothing else. If you are stating this does not work, then I may as well only support tags with TrackStat - as per existing releases.
    If by hack you mean a less common way of storing rarely changed rating values so they can be accessed across different OS and applications, then yes, correct.

    And you clearly misunderstood: I wasn't asking you to add this "hack" to Material. I've forked your repo and I was only asking for advice on how to achieve step 2 of what I explained because I don't know JS like you do. It will remain in my fork only and have no effect on any of the Material branches.
    If you don't want to help with that, ok, understood.

  8. #5718
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by afriend View Post
    If by hack you mean a less common way of storing rarely changed rating values so they can be accessed across different OS and applications, then yes, correct.
    But there is a rating tag that can be used for most (all?) file formats - and an LMS client should get its ratings from LMS.

    Again, do your ratings get returned by LMS if the 'tags:R' parameter is used?
    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.

  9. #5719
    Senior Member
    Join Date
    Jul 2010
    Posts
    260
    Quote Originally Posted by cpd73 View Post
    But there is a rating tag that can be used for most (all?) file formats - and an LMS client should get its ratings from LMS.

    Again, do your ratings get returned by LMS if the 'tags:R' parameter is used?
    I suppose you mean the LMS rating tag. Yes, I know, the rating value stored in the tracks_persistent database. But that's LMS's own rating tag. The metadata containers of my m4a/alac, mp3, flac and APE files don't share one common rating tag (if at all) where I could store the rating so it could travel with the file across different OS and applications.

    And the LMS rating value exists only if you have rated a track in LMS or imported a rating using a plugin like the (no longer maintained) CustomScan - which required a second scan of all of your files. BTW even CustomScan would ask you to specify the tag where you'd stored your rating (like grouping or comment...). And Trackstat was - among other things - basically a means to store your ratings (imported with CustomScan or rated in LMS) separate from the LMS database so it could survive a clean wipe and be rebuilt afterwards. And I've always done a clean wipe before rescanning for the last 10(?) years.

    So if you use your tracks across different OS with different applications - which like LMS all have their own metadata databases and ways of dealing with ratings - it's proven to be a lot easier to use some tag like comment to store the rating and display it everywhere. That's why I don't use Erland's deprecated plugins anymore and that's why my tracks_persistent database has no entries.

    All I want to do is display that rating. I've never supposed this would be part of the standard Material release. That's why I forked your repo. I just need some help with the missing JavaScript link between the returned comment tag value and the display of the rating (as explained in #5712).
    I hope I could explain why and how I do it that way.

  10. #5720
    Senior Member
    Join Date
    Mar 2017
    Posts
    2,874
    Quote Originally Posted by afriend View Post
    I suppose you mean the LMS rating tag. Yes, I know, the rating value stored in the tracks_persistent database. But that's LMS's own rating tag. The metadata containers of my m4a/alac, mp3, flac and APE files don't share one common rating tag (if at all) where I could store the rating so it could travel with the file across different OS and applications.
    No I meant tags within the files. FMPS_RATING can be used for MP3, APE, Vorbis, iTunes::FMPS_rating for MP4, FMPS/Rating for ASF

    However, I didn't mean to get into an argument - you can store you ratings wherever. But, if LMS does not return your rating when 'tags:R' is used there is no use in this setting within Material unless TrackStat is installed. That was my main point. And you still have not answered this - perhaps because you don't know?

    As to how to modify Material to obtain your ratings via the comments tag - I suggest you try and use Material's custom JS loading. Create 'material-skin/custom.js' in your LMS's prefs folder. Material will load this at start-up. You could use this to overwrite some Material functions, etc. This would save you having to maintain a fork. See https://github.com/CDrummond/lms-mat...ed-Information for more details.

    Alternatively, have LMS read your ratings and store in its DB - this would then work for all clients. It's probably as simple as writing a plugin to be run after each scan to extract the tags.
    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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •