Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    Senior Member
    Join Date
    May 2012
    Posts
    139

    Testing Revised Plugin on PicorePlayer - how best to proceed

    I have been playing around with the old Inguz DSP plugin and re-wrote the UI a couple of years ago. I have now rebuilt the executables using .Net 5 which means I can build as a standalone exe for pretty much any platform.

    I managed to get it all running on picoreplayer this weekend, but it has all disappeared now I have done a reboot, I understand the reasons for that, but really looking for some advice as to the best strategy for installing on a pi

    The exe is quite chunky at about 20 MB as it contains all the .Net libraries required.
    and currently installs here
    /usr/local/slimserver/Bin/armhf-linux

    The plugin, with all the perl and web pages currently installs to a Plugins directory here
    /usr/local/slimserver/Plugins.

    logging/settings and temp folder are here
    /usr/share/InguzEQ

    1) I could package the whole lot up as a fresh plugin - would that persist beyond a reboot and can you point me in the direction of the current docs.
    2) I could just create symlinks for the folders and the additional couple of files - is that advisable.

    Ultimately I want to re-name the plugin and maybe replace the core engine as Pi performance is a bit limiting (dropouts at 96 K and higher and gaps between tracks)

  2. #2
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    If you make an extension, your files will end up in the required locations after boot. Instructions here: https://docs.picoreplayer.org/inform...re_extensions/

  3. #3
    Senior Member
    Join Date
    May 2012
    Posts
    139
    Thanks, just had a read...

    So presumably I would need to make an extension for the 3 folders that I want to persist and script up this part as install script for other people to use.

  4. #4
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    It seems like there are three parts to your installation.

    Maybe it makes sense to have only the large executable included in the extension.
    I'm not sure about the pros and cons of including the plugin as part of a pCP extension - maybe it would be better to make the plugin available as a separate download via the normal LMS plugin method.
    The settings and temp folder presumably contains files that change whenever the user makes a change, so it doesn't sound like they should be part of the extension, as they would be overwritten by the extension after every boot. It's maybe better to put them in a place that's backed up whenever the user does a backup (e.g. /home/tc) or if you put them in another location, make sure that location is added to the list of files and folders that get backed up (/opt/.filetool.lst).

  5. #5
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,776

    Testing Revised Plugin on PicorePlayer - how bestto proceed

    > So presumably I would need to make an extension for the 3 folders that I
    > want to persist and script up this part as install script for other
    > people to use.


    For other people to user your plugin you should simply create a plugin
    package (.zip file). Plugins installed normally will be backed up
    automatically.

  6. #6
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    Quote Originally Posted by mherger View Post
    For other people to user your plugin you should simply create a plugin
    package (.zip file). Plugins installed normally will be backed up
    automatically.
    Is that correct, or are they installed in a location (outside of the pCP file structure) that is persistent? Assuming that's the case, then a 20MB executable isn't an issue. It only becomes an issue if it's included as a file in the normal pCP backup, because a file that size will slow down the backup process and pCP will warn you about the size of the backup.

  7. #7
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,776

    Testing Revised Plugin on PicorePlayer - how bestto proceed

    >> For other people to user your plugin you should simply create a plugin
    >> package (.zip file). Plugins installed normally will be backed up
    >> automatically.

    >
    > Is that correct, or are they installed in a location (outside of the pCP
    > file structure) that is persistent? Assuming that's the case, then a


    Oh, it might be in the persistent part, yes. It's the LMS cache folder.


  8. #8
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,776

    Testing Revised Plugin on PicorePlayer - how bestto proceed

    > The settings and temp folder presumably contains files that change
    > whenever the user makes a change, so it doesn't sound like they should
    > be part of the extension, as they would be overwritten by the extension
    > after every boot. It's maybe better to put them in a place that's


    Simplest would be to just use LMS' cache and prefs folder.

  9. #9
    Senior Member
    Join Date
    May 2012
    Posts
    139
    I have been trying to create the tar structure and I suspect that I have permissions wrong somewhere. I will look at the cache option too.

  10. #10
    Senior Member
    Join Date
    May 2012
    Posts
    139
    I am going to follow the approach that chill suggested in #4.

    The extension works for the executable (when I install the correct binary P )

    So will now experiment with doing a proper plugin install.

    Will take me a while though as I don't have much free time.

Posting Permissions

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