Jump to content

enmesh-parisian-latest

Members
  • Content Count

    90
  • Joined

  • Last visited

Community Reputation

4 Neutral

About enmesh-parisian-latest

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Having same issue, set mover tuning to "very low / idle" I'm assuming the settings aren't applied to an existing mover session as plex is still inoperable. Thanks for the fast update to mover tuning, I noticed the "help" info for the two new settings hasn't been added yet.
  2. Any idea when v1.48 will be available?
  3. Thanks for the response, I'll quit panicking. Any benchmark tools you'd recommend to track drive performance over time?
  4. On reboot today I was alerted by FCP that three of my disks have "Write Cache is disabled" errors: Write Cache is disabled on disk4 You may experience slow read/writes to disk4. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise. NOTE: If this drive is connected to your server via USB, then this test and the fix may or may not work / be accurate as USB support for smartctl and hdparm is hit and miss Write Cache is disabled on disk5 You may experience slow read/writes to disk5. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise. NOTE: If this drive is connected to your server via USB, then this test and the fix may or may not work / be accurate as USB support for smartctl and hdparm is hit and miss Write Cache is disabled on disk6 You may experience slow read/writes to disk6. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise. NOTE: If this drive is connected to your server via USB, then this test and the fix may or may not work / be accurate as USB support for smartctl and hdparm is hit and miss I ran a check on disk4: hdparm -W /dev/sdl /dev/sdl: write-caching = 0 (off) then: sudo hdparm -W1 /dev/sdl /dev/sdl: setting drive write-caching to 1 (on) write-caching = 0 (off) Seems like I can't set it to "on". Should I be concerned about the drives? server-diagnostics-20190528-0256.zip
  5. More than likely it's the chroma plugin, disable it (it does nothing) and try again. 90% sure it'll fix it.
  6. Regarding the multiple library thing, there are a few ways of doing it. You could run two seperate beets containers and just call them like beet1 & beet2. The neater way would be just to have two seperate config files and use the -c flag to specify the config files: docker exec beets beet -c /config/config-v1.yaml import /downloads docker exec beets beet -c /config/config-v2.yaml import /downloads Inside the config files you can specify different musiclibrary.blb databases. I'm not sure how the state.pickle file would be affected by the two libraries, although you may be able to specify the state.pickle inside the config.
  7. You're on your own with this one, I don't use a local MB server. If beets is being run as users:nobody and you've run DSNP, then there's no way it can be changing permissions outside its own user group. Check your container actually has the PUID and PGID set correctly. I suggest due to the volume random questions which you can find answers to already, I suggest you consult the documents. I had many similar questions when I was starting out with beets and received the RTFM suggestion many times. Every time I'd overlooked the clearly written answers already available to me. Really, the beets docs are very well written although you may need to read a few times for it to sink in. Due to the breadth of the possibilities we could be here for days.
  8. Oh right sure, you can point beets at any folder you've mapped to it. so in this case you could set: copy: no move: no then you can run: beet import /libraryfolder/Abba-Album2 to specify the album you want included. Ok sure, I had my own MB server running at one point. I ended up removing it as I could never be sure if it was causing problems or not. Once the initial library scan is complete the scan times aren't that bad. Besides, I find discogs provides me with better matching anyway. I'd suggest putting the local MB server on the backburner until you have everything else working smoothly. You should only run DSNP if a container (or user) has been editing files as a user other than users:nobody, if beets is set correctly then check the app which is creating the files in the first place (downloader or file browser) As mentioned in the documents, beets has its limitations when it comes to perfect matching of releases. You can increase or lower the threshold before beets requires user input, I have mine set at 82% of a confident match, anything below will require me to manually match. Too many or too few tracks always triggers a manual import where I look up the id on discogs or MB then input manually. Look up the documentation on the fetchart plugin, you can be very specific about artwork sourcing. I don't use it myself rather relying on existing artwork in the folder. Not wanting to pass you off onto someone else, but I generally find the beets google groups to be very helpful technically when it comes to beets support. That's where I go for assistance.
  9. Any data in the files id3 tags, folder names or any matched data from discogs, musicbrainz (or any other source via plugin) can be sent anywhere you like, be it a tag or a file/foldername. Just find the ID3 tag and apply it to the folder name Check out the docs, "The -L (--library) flag is also useful for retagging. Instead of listing paths you want to import on the command line, specify a query string that matches items from your library. In this case, the -s (singleton) flag controls whether the query matches individual items or full albums. If you want to retag your whole library, just supply a null query, which matches everything: beet import -L" I think that's what you mean? MBZ mirror? Make sure you're running beets as users:nobody, usually PUID/PGID of 99:100 in your beets container settings. Then make sure your data permissions are correct, the easiest way to do this is install the Fix Common Problems plugin then run Tools > Docker Safe New Perms. YW
  10. Chroma is a pretty dodgy and unnecessary plugin in my opinion. Switch it off by deleting or commenting out the 'chroma' line under plugins in your config file
  11. Was a while ago, but HBA was my choice I believe. Good card, but it squeals when it gets too hot
  12. Try dumping your docker.img and starting fresh. 6 Months later my docker still isn't perfect and nginx is a bitch but everything mostly works.
  13. Again, I'm really no expert on the plugin, however common sense would suggest you isolate what the problem is by making sure you can convert to other formats, then work out why only m4a doesn't work (if that's the case).
  14. I'm no expert in using the convert plugin, however I'd recommend trying different formats other than m4a. If others work but m4a doesn't then you may want to look at ffmpeg.
  15. Hey Zozat, I suggest you experiment with trial and error. The config.yaml file can become very complicated, so I'd recommend starting with no plugins or any modfications. Make sure you can get a simple import from a source to destination before adding the convert plugin. Once you're happy with the way the data is being handled with a VERY simple config file, then add the plugin and fiddle with the settings. Please read the manual several times, there's always something to miss on first read: https://beets.readthedocs.io/en/v1.4.7/plugins/convert.html . Keep in mind that by default, the plugin depends on FFmpeg to transcode the audio, so you might want to install it. Here's a simple example for convert plugins: convert convert: auto: no dest: C:/Transcodes never_convert_lossy_files: yes quiet: false formats: flac: command: ffmpeg -i $source -y -vn -aq 2 $dest extension: mp3