INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: 'Compression' field gone wrong?  (Read 1569 times)

pluto

  • World Citizen
  • ***
  • Posts: 175
'Compression' field gone wrong?
« on: April 17, 2013, 04:50:04 am »

I think something has gone wrong with the 'compression' field in or around build 169... I use it as part of my custom display in the main header.

Usually, "MP3", "FLAC" or whatever. Following installation of 169 - nix!
Logged

pluto

  • World Citizen
  • ***
  • Posts: 175
Re: 'Compression' field gone wrong?
« Reply #1 on: April 18, 2013, 03:53:06 am »

I think something has gone wrong with the 'compression' field in or around build 169

For the avoidance of doubt here, I am referring to Media Center's internal field, not some arbitrary field within an arbitrary tagging arrangement. I have hitherto used this as part of a my customized display on the main header to show the format of the material playing. This stopped working and now displays a blank space where it used to show MP3, FLAC or whatever.

Would someone be kind enough to cross check this please, or am I the only one?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72536
  • Where did I put my teeth?
Re: 'Compression' field gone wrong?
« Reply #2 on: April 18, 2013, 06:36:46 am »

For the avoidance of doubt here, I am referring to Media Center's internal field, not some arbitrary field within an arbitrary tagging arrangement. I have hitherto used this as part of a my customized display on the main header to show the format of the material playing. This stopped working and now displays a blank space where it used to show MP3, FLAC or whatever.

Would someone be kind enough to cross check this please, or am I the only one?
For an APE file, I see Normal 3.80.

Make sure that you don't have extra spaces in your expression.
Logged

pluto

  • World Citizen
  • ***
  • Posts: 175
Re: 'Compression' field gone wrong?
« Reply #3 on: April 18, 2013, 11:25:33 am »

Don't know why, but a reinstall fixed this, so job done.

A little mystery.
Logged
Pages: [1]   Go Up