Josh.5

Thanks for the report. I think I see the issue. I'll get a fix pushed shortly. Lookout for an update to that Plugin

No, you were not missing anything. I had not yet tested or pushed the VAAPI plugins. I am assuming that you are wanting H265/HEVC VAAPI. I have pushed a plugin for that (you will find it in the repo if you refresh it.

There is an option in these Plugins to set the container. Open the Plugin infor by clicking on the icon. At the top you will see 2 tabs, "Info" and "Settings". There is also a plugin specifically for remuxing video files. Search for "remux" or "container" in the plugin installer. Hope that helps

I have whipped up a plugin as requested for your needs. Called "Ignore files recently modified", you will find it in the plugin installer on the new "staging" build of Unmanic. This Plugin can be configured to ignore files that were last modified x time ago (can be seconds, mins, hours, etc.). Add it as one of the first items in your Plugin Flow. It will fail if a file was last modified more recent than the time configured, and no other tests will be carried out against the file - it will be ignored and not added to the task list.

So there is a little trick that you will want to do with Docker to achieve what you are asking here. Basically, map the external directory, eg '/mnt/user/Media/videos/movies' to '/library/watch/movies' inside the container. The problem is that everyone will have a different use case with different folder structure. So the only way to handle this is to include the full path right back to the root '/' directory. Then it is up to the user to create their directories accordingly. Docker makes this easy obviously with the little trick I just mentioned above. But this will be more of a problem for people who install and run this native on their host. Also, appreciate the support on patreon. Thanks! Actually... as I am thinking about it further, I realise there is a way to do what you are asking... I could add a fourth config option to that Plugin where you can remove the library path from the recreated directory structure. That would remove '/watch' - which is exactly what you were wanting. It would also be versatile and work on anyone's installation, native or docker

Also, those are some fancy looking screenshots! Rounded windows popping out with shadows applied behind them. Damn Apple.

Great. Thanks for the images. The problem is your '/library/watch' directory does not exist. It is not mounted into your Docker container. You have '/library/tv' and '/library/movies' mounted in, but no '/library/watch'

Ok. And how is the move2 plugin configured? I assume /library/watch is the out directory. Can you also confirm that /library/watch is indeed a mount into your docker container (perhaps post us a screenshot)?

What are the permissions on the directory '/library/watch'?

Highly unlikely that there will be anything in-depth created. That sounds like a lot of time-consuming work on my end. I will do my best to get the documentation updated to reflect the new configuration before pushing the staging branch. But I would recommend to people that they treat this like a fresh install and set it up on a small portion of their library first in order to get it all working. If you want to lock your setup to the old version of Unmanic, I would suggest chaining the docker image tag from "latest" to "0.0.9" or something. That will prevent the update from happening on your machine. It is my intent to keep this in staging for as long as I am getting feedback on critical things that need to be changed. Once that is done, a release will be made. From where I sit, I need to push this out before I can develop any other features, and the other features list is growing. I also need to push this out before my real job takes a big priority again, and that will start happening by they end of this week. Documentation aside, the system is pretty feature complete and free of major bugs. It is well worth people switching over to the staging branch now (after making a backup of their appdata directory) and starting to test it out prior to me pushing it to the master branch for a release. If people leave the switchover 'till the release date and then find that a feature they relied on is missing, that is on them. This week is their window to report back what is needed or they may find themselves waiting a month or 2.

Do the files have a suffix appended when they are still being written to (before the .ts)? If so you can use the path ignore plugin with some regex to ignore those files. I can make a plugin to ignore files under a configured age. Eg. Ignore files newer than 1 hour. That will prevent your ones being picked up while still being written to. The last option is to not use the library scanner with these files. Use the event monitor. That will only pickup files on completion of writing.

No need to be signed in to anything to use Plugins. At this point, I've allowed up to 5 Plugins when not a patron supporter. That should allow anyone the ability to do anything with Unmanic. It's just the additional nice to haves that would require more than 5. There is a plugin that only remuxes if that is all you want to do. Otherwise there is an option in the video encoder plugins also to select the out container

This afternoon I am pushing the upcoming feature development to the staging branch. This is a very big change to how Unmanic works. If you do want to try it, which I encourage that you do, please backup your config before moving to it. The new version should be able to handle migrating some bits of data from your current install, however you WILL need to reconfigure the application (not that it is a difficult process). The way Unmanic works has changed. Unmanic is no longer a tool for running FFmpeg commands against your library. Rather it runs "Plugins" against your library. This change will give us the ability to expand Unmanic into other areas of managing our libraries of other file types (not just videos). The first thing that you may notice when you run it is that the layout has changed a bit. The main dashboard should still be familiar, but it is now completely re-written with VueJS. When you look at the settings they are also similar, but there is no longer any section for configuring FFMpeg. The only settings options available are for configuring the library management, workers and Plugins. Over the next few days I will be uploading a bunch of new Plugins. If anyone is using the old version of Unmanic with Plugins, please do not update them. This release will break Plugins for the old version of Unmanic. If you want to keep using those Plugins with the old version of Unmanic, then you will want to back them up now as they will be gone by the end of this weekend. The new Plugins do not rely on FFmpeg. You can now create a Plugin that can run any command in Unmanic's workers. It is my intent that I will be writing some new Plugins for managing images and music files over the next few weeks and then hopefully you guys will have ideas for things that you would want for me to write (or you could try your hand at writing them yourself).

Awesome. Thanks for the detailed report and logs. @SuberSeb, @harriedr I believe @rbourassa44 just identified your problem. I'll add a fix for this in the next release.

Thanks for bringing this up. I'll work on an improvement so that this is possible in a future release. If you open a GitHub issue for this, I will close it once a solution is available and you will be notified.

I'm currently undertaking a complete rewrite of the frontend which includes a small overhaul of how plugins work and the opening of them up in limited quantities to everyone. This development still has around 20-30 hours remaining. The first phase is already in staging and I will be pushing the past 3 weeks work into staging again sometime this week. None of these changes will make their way into a new release until they are completed. This may be a few weeks away yet. Once that release comes, I will be doing nothing but writing plugins like the one you have just mentioned. The whole point of this re-write is to make Unmanic more modular to better suite everyone's unique use-cases. I would suggest that over the next few weeks, if people are wanting to try out the updated plugin system, they switch over to the staging branch and provide me with some feedback on the development progression. A big note of change... Once the next release does become available, you will likely notice that all FFmpeg related settings will be completely removed from Unmanic. Unmanic is migrating away from an "FFmpeg" tool and will have new capabilities for managing libraries of any file type. That being said, you will still be able to use FFmpeg plugins on your files very similarly to how you can now with Unmanic's settings. I believe I will be setting up Unmanic to limit only a single plugin enabled at a time for people who do not wish to sponsor the project (which is absolutely fine!). That still gives everyone the ability to use the plugins on their library, and the ability to try out plugins before deciding if they want to sponsor the project at all. It also gives me the ability to monetise the development effort that I put into the project over the next few years - something that will greatly help me to keep the project going. I would be curious to know if anyone believes the sponsorship requirements that I setup through Patreon are too high? No offence taken here if you speak your mind. At the end of the day, Unmanic is free for anyone to use how they want. I have not restricted the source in any way and have given this to you freely without wanting anything in return. I have no intention of ever making the Unmanic project anything other than open source - so no proprietary v2 re-writes on the horizon. All I am trying to do now is provide my creation as a service to those who are asking for me to continue to develop new features for them (like a plugin to remove various audio streams) and requesting support for that continued development in the form of optional monthly donations. This is absolutely a hobby project of mine and I do not get offended when people use it for free and message me with feedback or ask for assistance. I'm absolutely here to help everyone in this community as much as I can.

First of all thanks for taking Unmanic for a spin. Patreon does not charge until the first of the month. So you hav til then to decide if the additional stuff is worth it for you. That being said, the next major release will enable a limited number of plugins for everyone to use without signing into anything. Also, it is worth saying that the way that I have written the plugins, they will reprocess files that have already been converted. Eg, if you convert them to hevc now and in a few months time you want to run the plugin that reorders subtitles, it will do that to your library without reencoding the video streams. So you absolutely can process your library while waiting for a plugin to fix that other need of yours.

I can make you a plugin to do that this week. No problem. Did you find the plugin for removing images from the video files?

Have you got access to the plugins? There is one in there that will strip out the PNG stream that is causing the error with Unmanic

Sounds really cool. Perhaps it would be better if we work on merging this feature into the main source?

Yes, that should then be mapped to a share

Sounds like you have not set a mapped volume for your cache

Can you please test tag "dev-intel_compute_runtime"

Would you be free at some point to walk through this with me on discord? Possibly over a voice chat an a screen share?

That message is displayed when the browser loses connection with the backend server. It could be because you locked the computer for a time. Refreshing the browser should make it work again. But the browser should also attempt to reconnect after a few seconds and you should see it refresh automatically. If it's not doing that, then something may be wrong.