Announcement

Collapse
No announcement yet.

Correct way to handle an updated custom.conf file

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Correct way to handle an updated custom.conf file

    > - Is there a mechanism for telling LMS that a new custom.conf should
    > be used/loaded?


    I think you could call
    Slim::Player::TranscodingHelper::loadConversionTab les().


    #2
    Correct way to handle an updated custom.conf file

    The Inguz EQ plugin, will dynamically add a new player to the custom.conf file, and also will re-write the custom.conf file when a new version of the plugin is deployed.

    Currently this involves manually re-starting lms, and if it is not re-started the player will suddenly start spewing loud white-noise - . Obvs I would like to do something about this.
    • Is there a mechanism for telling LMS that a new custom.conf should be used/loaded?
    • Is there a better way of handling this scenario that I have not thought of?
    • Failing that, is there an issue with restarting LMS?



    Whatever the answer, it would be great if you were able to supply a code snippet.

    Thanks in advance.

    Comment


      #3
      Originally posted by mherger View Post
      > - Is there a mechanism for telling LMS that a new custom.conf should
      > be used/loaded?


      I think you could call
      Slim::Player::TranscodingHelper::loadConversionTab les().
      Works a treat - thanks. I also needed to disable some code in the plugin which throws up a restart-required message.

      I have tested it by
      1. incrementing the script version
      2. adding a new player


      Both of which will cause the custom.conf to be re-written. White noise would appear when a new player was added, but doesn't now.

      Comment

      Working...
      X