Josh.5

For now disable that plugin. I have opened an issue to resolve this: https://github.com/Unmanic/unmanic-plugins/issues/154

Can you send me the full command log. This looks like the extract subs to srt plugin, not the nvidia plugin that you said you were using. I cannot see your screen so you need to provide me with all the details you can, Give me screenshots of everything and dont assume that I know what is happening on your PC

Bugger

@Jurak can you also post the ffmpeg command that it ran for that error above?

But some are succeeding?

Are all the plugins up to date?

Did the issue start after you updated the the latest release?

Has this just started?

The limit has been increased to 10 or 20. The metrics data can be reset by deleting the history.db file in . unmanic/userdata/file_size_metrics/

In your appdata, delete the Unmanic settings.json file and then start the container

This sounds good in theory. But in practice you will regret that approach when you end up with files with no audio tracks in them because the language was unknown. Unmanic can be run multiple times against your library. If you run it and then find that some of your files had languages that you didn't want, just update the plugin settings and run the library scan again.

@ReflexReaction Try looking at the logs (also enable debugging) when you execute a library scan. There will be lines in there explaining why the files are not being added to the queue. Feel free to join the discord channel. You would be more likely to get assistance there than in this forum.

Well the reason for the error in the log is because you are running too many transcodes at a time. What GPU do you have? As for the 25GB files... I don't think anyone can help you on hearsay. Without logs being posted, your on your own.

By default they end up back in the same directory as the source. Have you installed a data panel plugin? (This has been asked a number of times now. I am working on adding a notice to this page to suggest installing a plugin if the page is empty)

I've been working with @GonjaT today to help them setup the FileBot configuration as well as document a bit about how it is done. I've added a section to the Unmanic Docs page called "Guides". Please feel free to write up and submit any setup guides that you think other members of the community may find useful as I have done here. It helps us all out and is a great way for you to show your appreciation towards the project. Link: https://docs.unmanic.app/docs/

Do you have a data panel plugin installed?

Are all your plugins up-to-date? You can clear the write lock by deleting the unmanic.db-shm and unmanic.db-wal files in the config directory

Look for the exec custom Post-Processor script plugin. There is an example on how to setup for filebot in the description after you install it.

Not all h265 encoders are equal. You will also need to specify bitrate etc. I personally do not believe that you will get the results you are looking for. But if you are keen to do as you say, I suggest you fork the h265 plugin from the official repo and modify it to force the encode when the file is already in h265

Well if you can give me a detailed run-down on a collection of FFmpeg commands for transcoding to AV1 with various bitrates (VBR or CBR), etc. Then I can do the python work for you... I looked at the docs for AV1 the other day and after about an hour I gave up.

I've added a note to it. They did not look very far for the API docs... The API schema is OpenAPI v3 compliant and is in the project and can be imported into any API development tool they want - Postman, Insomnia, swagger, etc. The API is hosted in the application web UI. I do need to better document how to find these things. I think that is what I am going to spend my December doing. Not sure if you can re-open that ticket now that I've added the direction to the API docs...

Can you post a link to that request you made with Sonarr. I'll keep an eye on it if anything is required on my end. Since you brought it up.. An upcoming release should contain in it a massive improvement to library scanning times. You also have the ability to enable the event watcher, which is pretty good at listening out for file movements within your library. Even with millions of files, that event watcher works well.

I'm a little sus that your GitHub does not exist anymore... Where did it go?

You are quite right. I should update the instructions removing that warning as I highly doubt anyone is still running the older version of Unraid and so there is no need to keep those instructions. Just follow the instructions in the template adding the --runtime=nvidia option and the other things that it says to.

I'll need all the logs. There are items in your Post-Processor queue that are either taking a long time or are throwing exceptions and staying in cache.