title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Windows Home Server 2016 Batchripper Autostart does not work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • anne-nh
    • Feb 2020
    • 4

    Windows Home Server 2016 Batchripper Autostart does not work

    Hello community!


    This is Anne from Germany and this is my first question here in the forum.

    I have problems configuring Windows Homeserver 2016 to meet my needs. Since about 2013 I have been using a NAS as my music streaming platform. Previous operating system Windows Homeserver 2011. Only the software dbpoweramp CD Ripper and dbpoweramp Batchripper were installed. It should stay that way.

    Windows Homeserver 2016 is now the new operating system. When restarting, dbpoweramp Batchripper should start automatically. I have inserted the program in the Startup folder. But it doesn't start automatically.

    Exactly the same version works for my new Windows 10 computer. I also correctly inserted it for the autostart. After starting up, dbpoweramp Batchripper starts automatically.

    It is important to me that dbpoweramp Batchripper starts automatically after starting up. What can I do? My favorite solution is the autostart solution.
    Is it possible to turn dbpoweramp into a Windows service and how does it work with Powershell?

    I look forward to your support.

    Anne
  • Spoon
    Administrator
    • Apr 2002
    • 43888

    #2
    Re: Windows Home Server 2016 Batchripper Autostart does not work

    I am sorry we do not have a solution for auto ripping on Homeserver 2016.
    Spoon
    www.dbpoweramp.com

    Comment

    • anne-nh
      • Feb 2020
      • 4

      #3
      Re: Windows Home Server 2016 Batchripper Autostart does not work

      Thanks Spoon,

      I have a solution. Automatically start dbpoweramp Batchripper is now a task - Deutsch Aufgabenplaner - and it is running

      Now weeks without my NAS music streaming the list "Top Artists" ans "Top Album" (Asset UPnP) are lost. Where are this files saved? Direct in dbpoweramp? I hope I can use my backup.

      Thanks
      Anne

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 43888

        #4
        Re: Windows Home Server 2016 Batchripper Autostart does not work

        They are in Assets database, you cannot potentially restore that.
        Spoon
        www.dbpoweramp.com

        Comment

        • anne-nh
          • Feb 2020
          • 4

          #5
          Re: Windows Home Server 2016 Batchripper Autostart does not work

          Thank you spoon

          The program is still on the old hard drive.
          Where do I have to look?
          Saving the configuration as an additional option is certainly also worth considering.

          Thanks
          Anne

          Comment

          • Spoon
            Administrator
            • Apr 2002
            • 43888

            #6
            Re: Windows Home Server 2016 Batchripper Autostart does not work

            You mean the items in the root of the tree are missing?
            Spoon
            www.dbpoweramp.com

            Comment

            • anne-nh
              • Feb 2020
              • 4

              #7
              Re: Windows Home Server 2016 Batchripper Autostart does not work

              Right.

              The "Top Albums" and "Top Artists" list is empty.

              How can I restore them from the previous installation?

              Or differently, where is the list saved?

              Thanks
              Anne

              Comment

              • Spoon
                Administrator
                • Apr 2002
                • 43888

                #8
                Re: Windows Home Server 2016 Batchripper Autostart does not work

                It is saved into the database, you can not most likely copy the database from one machine to another because the paths for the files are different.
                Spoon
                www.dbpoweramp.com

                Comment

                Working...

                ]]>