Josh.5

This wouldn't touch your subtitles. This only removes the PNG thumbnail image in the video container.

So the cause of the failure is the PNG video stream. I will see if I can come up with an improvement to the video encoder plugin, but if you want a quick fix I would suggest installing the "Strip all image streams from file" Plugin and putting that first in the worker flow. This will remove the png stream from your file.

Can you post just the FFmpeg command log of the failed task

Do you have a dl link? And do you have UST the failed FFmpeg command log (that's all that is required)

For people posting issues with failed FFmpeg commands, I want to point out that there is more to it than the last few lines containing the error. I would suggest posting complete logs. Posting partial logs is your way of self diagnosis. If you intend on solving your own problems, then that's fine. But if you want help from someone else, this is counter productive. Post full logs and you will get a faster resolution to your problem.

Sorry to hear that you are finding that a bit difficult. Unfortunately there was no simple way to make that happen. Patreon is one of the best services available that I could find that allows me to hook into it's website for authenticating people and linking that with donations. All their competition were pretty trash at that and required that I be the one who writes a lot of code to make it happen. Perhaps someone here could walk you through the process?

Looks cooked to me! Do you mind raising an issue on the unmanic-plugins GitHub repo. I'll get that fixed when I get some time

Sounds like a good idea TBH. Instantly I can think of a big issue tho. What if you kill the container. You now have some "ignore" flags lying around in your library that are preventing any Unmanic installation from processing those files

Actually, I have it on my TODO list to create a plugin for that: https://github.com/Unmanic/unmanic-plugins/issues/34 Watch that issue on GitHub for updates on progress. Hopefully wont be far away. When it is ready, it will be able to go back over your already processed files and add the stereo track. The issue will be ignoring files that have been processed by the old version of Unmanic... If you have any ideas on that, I'm well open to suggestions.

IMO, pausing containers is FAR better than pausing processes. There is no overhead at all for pausing a container. You have full flexibility and it does not affect the processes running inside that container at all (they have no knowledge that they have been paused). Pausing a process inside the Unmanic container is a request to that process to pause itself. It knows that it is paused and then has to also manage all the things that go with it being paused. In Unmanic's case this is things like accounting for pause time when calculating ETC. Also, you have the issue that pausing a worker only pauses that one sub-process. You still have a small amount of overhead. Whereas pausing a container pauses absolutely everything within that container. However, with that said... demonstrate-unmanic-api-pausing-a-container.mp4 You can pause/resume workers with the Unmanic API. See this video for location of API spec.

Exactly. Everyone uses the app differently. And the requests for features coming in then affected everyone. This way it's possible to give someone a feature that does not affect anyone else. It also gives Unmanic the ability to carry out functions that are not related to FFmpeg or video files.

In the description are some time stamps. Watch the one about data panels

Awesome. Take a look at that video for the section about data panels

Yup. Defaults in the previous version were: Preset "medium" Profile "main" These are the defaults for the encoder from NVIDIA.

Check the first post

Tonight I have pushed a new release of Unmanic. Version 0.1.0 (because Unmanic will forever be a ZeroVer). If you have any questions I encourage you to join the discord chat and ask there for help. You will likely get responses quicker on things like what Plugin is best used for a specific situation, etc. This release is about 3-4 months in the making. I'm really glad to finally get it out. Thanks to everyone who jumped onto the staging release over the past 3 weeks and provided me with bug reports and suggestions for improvements. There is still plenty that I want to do, this release now allows me to move onto the next feature set....

I've made a video to help people migrate from the current Unmanic version to the upcoming release (hopefully before this weekend)

Both options are available in the upcoming release. If you want to switch over to the staging docker tag you can access it early...

I also just want to use this to reiterate what I posted last week. We are getting very close to releasing Unmanic v0.1.0 (what is currently in staging) This is a big change to how Unmanic works. If you want to stay where you are, backup your config or lock in your version to tag 0.0.9 as there is no downgrade path supported. Glad to see you have it working Jammy. Feel free to message us in the discord channel if you need assistance.

Does anyone in this forum have an 11th Gen Intel CPU that can test this Docker tag: josh5/unmanic:dev-intel_gen11

I was just about to say that the fix was actually really simple and I've already updated the plugin. To fix it, just update the plugin and remove the following from the main options: -init_hw_device vaapi=vaapi0:/dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device vaapi0 I will look into the CRF slider. At this point I am not sure what FFmpeg options work with the VAAPI and NVENC encoders and what don't. This is why I have left them out. The libx264/5 encoder is really well documented and it was really easy for me to put it all together.

In the plugin settings, unselect the "Write your own FFmpeg params" option. I'll update the plugin either tonight or tomorrow to fix the issue.

Can you show me the config for the plugin. This doesn't look right

I have the almost ready to go. Just holding off while other stuff is tested. You could try them out by adding my Dev plugin repo. https://raw.githubusercontent.com/Josh5/unmanic-plugins/repo/repo.json

Nothing really has changed with how the event monitor works. If you suspect there is an issue, try enabling debugging first. Then manually drop a file into the directory that should be monitored and check the logs to see if it is picked up. Let me know how you get on