Josh.5

If I create a test build today, would you be able to test it for me?

What CPU do you have? This is not entirely unexpected as one of the big changes was an update to FFmpeg and some of its dependencies. I tested this on my i7-6770 and a i3-6100. So I wonder if you have a newer CPU??

With no settings in the advanced tab?

Can you please remove any settings you have in advanced settings and try again.

Unmanic 0.0.8 released. See here for a condensed changelog: https://github.com/Unmanic/unmanic/releases/tag/0.0.8

This is possible. It's on my to-do list to create a plugin to convert ass to srt streams using something like https://pypi.org/project/asstosrt/

Yea. I think it's worth making a backup of your Unmanic config folder and start fresh to see if that helps. If you like, I can give you more help over a chat on Discord. We could probably solve the issue there in a short voice call.

Unfortunately I think I will not be able to solve this through forum posts. I'm happy to help out over a chat on discord. Join the discord server and message me.

Can you try setting the docker config of the tmp/unmanic volume to another location on your array. Just so we can test if it does the same thing.

So I got thinking today. There is not really any point in creating a whole new screen just to handle blacklisting paths when the current plugin system can handle it with 10-20 mins of development time. So with that in mind I created a plugin for you to do this. I also then thought it may be worth creating another video to show how simple it is to create a plugin for Unmanic. Feel free not to watch it as it's pretty dry and long. But you should now be able to download the new "Path Ignore" plugin.

Could you please explain this part further? Are you using a symlink to connect 2 "tmp" directories?

Can't see any issue in the unmanic log. Could you please pull the latest "staging" docker image and test it again. If it still does not work, could you also try deleting your appdata/unmanic/.unmanic directory and trying again.

Not at the moment. But the next item on my to-do list is to create a "blacklist" tab where you could do this

Could you please provide some screenshots of your setup? Specifically the docker template config and the settings in the Unmanic webui. Thanks

Great to hear you have found a solution! I believe it is possibly a permissions issue that was causing Unmanic to not start. Unfortunately, without logs to accompany your other posts, I cannot say for sure. All the best 🖖

@Sebastiaan99 In your log I see it is failing on the first video. I cannot see what is causing the whole application to crash.. Could you still please send the Docker logs for that. However I have just pushed a fix to the "staging" branch to fix a bug shown in your files FFMPEG logs in the database that you sent me. After you have those Docker logs for me, could you please switch over to the "staging" branch and test it again? Let me know how you get on.

Could you send me some docker logs or anything like that?

You have uploaded an empty zip file there my friend...

Are you able to get the docker logs also? I had a quick look and it looks like Unmanic has encountered some exception that it could not handle. I'll take a closer look tonight since you sent me the DB also, I may be able to reproduce the issue...

Awesome! I want to say that I really appreciate these videos that you have made. I know that they will be helpful to a lot of users of Unmanic. Thanks!

I'm not able to help you with the long lines you have provided. If you have logs with errors in them, feel free to open an issue ticket on GitHub with ALL the logs attached. As I mentioned earlier, if you are wanting help personally with regard to configuring Unmanic or issues with your files, please contact me on discord as a patron. I am unable to provide assistance to everyone who has issues with the configuration of unmanic or issues specific to their files. I would much rather spend my time further developing the application.

Message me on discord and I'll be able to help you out

There was indeed. Unfortunately, to properly fix this you will need to wipe your settings dB file. I found 2 issues. The first issue that you are having here I've fixed and you can keep using your Unmanic installation with current settings simply by updating to the staging branch again. But the second issue is more of a pain. You will not be able to install plugins down the line if you don't reset the database... I recommend that anyone running the staging branch who updated within the last 48 hours, delete your unmanic.db and fetch the latest version of the staging branch. I need to come up with a better way to mutate dB structure for switching between Unmanic versions in the future.

I'm sorry, I'm unable to reproduce this. I am running Unraid 6.9.2 and Unmanic on the latest build of the staging branch. I would like to make the suggestion. If anyone wants personal support from myself in setting up Unmanic, I have setup a discord channel. I am able jump on a voice call if required (However, I'm only willing to do voice calls to supporters of the top tier on Patreon). http://unmanic.app/discord

Did this just start happening today?