![]() ![]() Looking at the code in MinimServer, I can see a combination of circumstances that could possibly cause this. I confirm that this behaviour is incorrect. I've had a nightmare trying to post the above, with the server show a "Forbidden" error unless I take bits out, put them back in, etc. I thought of using a tool to change the modified dates on the recently re-tagged files back to a much older date, delete MinimServer's cache file while it's not running then re-scan? How can I fix this situation with my library? I have the MinimServer.log file for this and can supply the contents of the etc/recent folder as well if required. So why does that now appear in Recently Added? Looking at the log for the 2nd refresh above, it doesn't try to update the Bjork, Telegram album on the 2nd refresh as it's not changed. Recently Added now shows Bjork, Telegram as added today.Re-tagging another album (Various, The Ultimate System Set-Up Disc) from Sound Clip to Classical - that left no other audio files with the genre of "Sound Clip".The log shows it discarding the cache for each file and re-reading it - fine. ![]() Setting MinimServer logging level to Debug and triggering a re-scan.Re-tagging an album (Bjork, Telegram) from Electronica to Alternative - that still left other albums by other artists tagged as Electronica.I have tried to re-produce this as follows: Then I did the same with a 2nd artist and after a re-scan, all the albums from the 1st artist appeared under Recently Added. At first, the albums moved into the correct genre as expected (I didn't check Recently Added at this point). I re-tagged all albums by particular artists at once and then re-scanned. Today I wanted to tidy up the list of Genres, removing things like Indie and Britpop by re-tagging the items in those genres as Rock, Pop, Alternative, etc. PS - just tried installing the Kinsky Android app on my phone but it fails to start.I'm using MinimServer 2.1.2 update 218 for Synology NAS (DSM 6.x). Which brings me to a question: why run MinimServer on your moOde Player when moOde already can be a UPnP media server? The BubbleUPnP app shows "Moode UPNP" in its list of local renderers and shows "MinimServer", "Moode UPNP-mediaserver", and "Moode DLNA" among the local and cloud libraries it can access. I am running a copy of MinimServer on my laptop (hostname T520) and the BubbleUPnP app as the UPnP control point on my Android phone. I don't have an iPhone or any other Apple gear so won't try to advise. If you don't see it, then you need to do some troubleshooting. If you have enabled the UPnP Renderer function in your moOde player with the default name, it should show up as "Moode UPNP" in a list of available renderers in the Kinsky app. The fact that your MinimServer shows up in your Kinsky app shows you're half-way to your goal. moOde Player does not have a UPnP control point capability so neither the MinimServer nor the Plex DLNA server will "show up" in it. In turn, it will direct a UPnP renderer (here, your moOde player) to play the selections. ** Is target USB drive plugged in (y/n)? yĬlick to UPnP servers and selecting tracks is the function of the UPnP control point (here, your Kinsky app). ** Plug in target USB drive for the new OS ** Are all USB storage devices unplugged (y/n)? y ** Unplug all USB storage devices from the Pi ** Do you have a backup of your boot SDCard (y/n)? y STEP 1 - Download Raspbian Lite and create a new, base image ** Be sure to backup the SDCard used to boot your Pi ** a spare USB or USB-SDCard drive that the new OS will be ** enabled, at least 2.5GB free space on the boot SDCard and ** You will need a Raspberry Pi running Raspbian with SSH ** custom Linux OS that runs moOde audio player. ** Welcome to the automated process for creating the wonderful sd 0:0:0:0: Attached SCSI removable disk sd 0:0:0:2: Attached SCSI removable disk sd 0:0:0:3: Attached SCSI removable disk sd 0:0:0:1: Attached SCSI removable disk sd 0:0:0:0: Assuming drive cache: write through sd 0:0:0:3: Attached scsi generic sg3 type 0 scsi 0:0:0:3: Direct-Access SanDisk CF SDDR-289 1.00 PQ: 0 ANSI: 0 CCS sd 0:0:0:2: Attached scsi generic sg2 type 0 scsi 0:0:0:2: Direct-Access SanDisk SD SDDR-289 1.00 PQ: 0 ANSI: 0 CCS sd 0:0:0:1: Attached scsi generic sg1 type 0 scsi 0:0:0:1: Direct-Access SanDisk MS SDDR-289 1.00 PQ: 0 ANSI: 0 CCS sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 0:0:0:0: Direct-Access SanDisk uSD SDDR-289 1.00 PQ: 0 ANSI: 0 CCS usb-storage 1-1.4:1.0: USB Mass Storage device detected usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.4: New USB device found, idVendor=0781, idProduct=b6ba Usb 1-1.4: new high-speed USB device number 5 using dwc_otg ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |