displaying bitrate, codec etc in iPeng and Squeezepad?

[aubuti]

Sometimes when listening to tracks from music services like MOG or Rhapsody I like to take a look at the reported bitrate. In the LMS web interface this is shown in the right-side panel, but I can't figure out where -- or if -- that information is available on iPeng or Squeezepad. Any pointers?

And if that info is currently not available on one or both of those great apps, please consider this a feature request. Thanks.

[bluegaspode]

Long press on the cover of the playing song should reveal the context menu with all available information in both Apps.

If you don't find what you are searching there, then it's unfortunately in the responsibility of Logitech to provide it.

[pippin]

It's as bluegaspode writes. You'll find it in the "More Info" menu.

[aubuti]

Thanks guys. All looks well on Rhapsody in both apps, including bitrate and encoding info. But on MOG the results are a lot more mixed.

On one MOG album I was trying the long press on the Now Playing cover image doesn't provide any context menu info in either app. It would seem that on this one that MOG isn't sending info for this album. In Squeezepad the context menu shows only track title. In iPeng it shows various Lookup... , Search For Album, Search For Song Title, etc options, but none of the album or track info.

BUT, for that same album (The Tel Aviv Session) if I go to the track listing (not the Now Playing cover image) in either app I get the usual info on the context menu (genre, duration, artist, On Amazon, etc), although not bitrate or codec.

On a different MOG album, long pressing the NP cover image in either iPeng and Squeezepad shows a context menu with most of the normal info most normal context info, though no bitrate or encoding type on either. On the LMS web ui it is showing 320k CBR MP3 for both this album and the previous example with no metadata, but I wonder if that is just a blanket (and potentially misleading) placeholder in LMS.

EDIT: sorry, forgot to mention that I'm not getting a "More Info" sub-menu for any context menus with MOG and Rhapsody. (Rhapsody's bitrate/codec in the main context menu in both apps.)

[pippin]

As bluegaspode already stated: if MOG (or the MOG App on MySB in this case) doesn't deliver any info, the Apps can't show it...
Doesn't MOG always use the same bitrate (320 Kbps mp3) anyway?

[garym]

As bluegaspode already stated: if MOG (or the MOG App on MySB in this case) doesn't deliver any info, the Apps can't show it...
Doesn't MOG always use the same bitrate (320 Kbps mp3) anyway?

no, sometimes 320, sometimes 256. Where is LMS WebGUI getting the bitrate info on MOG?

[aubuti]

I thought that some MOG was 320 and some was less, but I could be getting that confused with Spotify. Maybe MOG doesn't send the bitrate, although as garym says, where does the LMS web ui get it then.

But aside from the bitrate/codec question, I am puzzled why -- for that one album at least -- the apps show the other metadata in a context menu from the track listing, but not from the NP cover image's context menu. In other words, MOG is delivering the other metadata for that album, and whether the apps display it depends on which context menu is called. Is that clearer?

[bluegaspode]

But aside from the bitrate/codec question, I am puzzled why -- for that one album at least -- the apps show the other metadata in a context menu from the track listing, but not from the NP cover image's context menu.

Because Logitech decided (?!), that context menus in the tracks menu should have different content compared to context menus for playlist items
It's one of the many inconsistencies we learned to like

[pippin]

Well, there's a reason but usually it's the other way around and there is _more_ info for playlist entries than for track items. I suspect there is an error in this case keeping this menu from being processed correctly somewhere within MySB. And I believe it's only the menu generation and the info itself would be there which explains why the Web Interface gets it. Probably another case of a misprocessed special character or a leftover '"'

A lot of the metadata only gets processed and some cross-reference menus only generated when a track is being added to the current playlist, that's why the menus are different.

[aubuti]

Thanks for the info and explanations. And it seems to be an additional level of metadata garbling with this one particular album. But it sounds really good :-)