Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Josh.5 last won the day on October 3

Josh.5 had the most liked content!

Community Reputation

54 Good


About Josh.5

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Feature requests are welcome. You should raise an issue for it on GitHub. Issues posted here in the forum are easy to lose track of and forget about. Sent from my ONEPLUS A6000 using Tapatalk
  2. I have merged and published the next release. See here for a change log: https://github.com/Josh5/unmanic/releases/tag/v0.0.1-beta7 If you are having issues with conversions, you will now have the ability to flick on debugging in your settings which will also enable saving of the whole FFMPEG command STDOUT log. This does log a fair amount, so do not just leave debugging on unnecessarily. By doing this, you will then have visibility of the issue that is preventing FFMPEG from succeeding via the history screen's Conversion Details section (See screenshot below). Note: If you have errors with the application not starting after this update (as I imagine that some of you will) it is because you have jobs in your history that are too old to migrate to the new database. That is unfortunately too bad as I did not wish to spend too much effort making sure everyone's history was migrated (as that would require quite a bit of testing). If you see an error like in the screenshot below, then run these commands: cd /mnt/user/appdata/unmanic/.unmanic/config/ mkdir tmp mv history.json ./tmp/ mv completed_job_details ./tmp/ or just delete it if you do not wish any sort of backup of your history.... cd /mnt/user/appdata/unmanic/.unmanic/config/ mkdir tmp rm ./history.json ./completed_job_details Once you have done this, restarting Unmainc will work fine. All your settings will be intact with a fresh history log. Sorry for the inconvenience on this. I really am trying to push forward with finishing all these breaking feature adds prior to a full release hopefully before the end of this month.
  3. Feature requests are welcome. You should raise an issue for it on GitHub. Issues posted here in the forum are easy to lose track of and forget about. Sent from my ONEPLUS A6000 using Tapatalk
  4. Yes. Unmanic will just copy the stereo AAC streams from the source file to the destination file without re-encoding. Your subtitle issue is likely due to the subtitle codec of the source being image based. Unmanic can only handle text based subtitles at this time. Image based ones will cause an error with the FFMPEG command. I have created a feature request on GitHub for modifying the application's behaviour in dealing with these image based subtitle codecs: https://github.com/Josh5/unmanic/issues/74
  5. I would just wait for the history feature to be complete. Should be done soonish
  6. I use this as I had issues with Plex transcoding audio to Chromecast (or the lack thereof). I found that I had a bunch of videos that would not play or would play rediculously slow because the Chromecast could not handle them. They were either DD or DTS surround sound audio tracks. Plex was not transcoding the audio as the Chromecast was "compatible". I found that re-encoding the audio tracks fix 100% of the issues. I also found that there were heaps of occasions where I did not need the surround sound audio. I'm pretty sure Plex does not modify the audio streams when you select quality unless the player cannot support it. I personally just found it easier to have the stereo stream available. Also, keep in mind, not everyone can afford to have Plex setup to do on-the-fly transcoding. Sent from my ONEPLUS A6000 using Tapatalk
  7. The issue with the settings pages not redirecting is known. It works fine in Firefox for anyone willing to switch from chrome to a superior web browser... [emoji14] I'll fix it after the next release. For now just click back or something (or switch to Firefox). Sent from my ONEPLUS A6000 using Tapatalk
  8. Awesome. I appreciate the gesture, but I won't be taking donations for this application any time soon. I would prefer that if you feel a need to contribute, you do so by reporting bugs (as you have) and by helping others here in the forums. And of course, if you can code, pull requests on GitHub are also welcome. Cheers. Sent from my ONEPLUS A6000 using Tapatalk
  9. A fix for the 0% issue that everyone is having is being built and pushed now. ETA 10 mins. @Squid I've logged your issue on Github https://github.com/Josh5/unmanic/issues/73. Cheers.
  10. Ah, so this is 100% my fault. I should have posted something here before moving onto the next feature... Last night I merged in the applications settings changes that I've been working on for the past wee while. These new changes moves all the settings to an SQLite database. There were also changes made to how Unmanic loads data pertaining to containers/audio codecs/video codecs/subtitles. These changes will allow things like employing HW encoders in the future (slowly getting there...). For now, the big takeaway is that anyone who updates Unmanic with last nights changes will need to go and save their settings again. The error you have posted is that 'mkv' container (how it was configured) is now 'matroska' as that is the correct name of the FFMPEG. So the container settings need to be saved again. TL;DR Everyone who updates Unmanic needs to save their settings again or it will stop working for them. EDIT: If anyone is interested in what the update changed: https://github.com/Josh5/unmanic/releases/tag/0.0.1-beta6
  11. It's all good. Unmanic is getting close to an out of beta release. I think dev-settings is the last big project before a full release. The rest will be pretty simple upgrades. Sent from my ONEPLUS A6000 using Tapatalk
  12. Well that sucks Sent from my ONEPLUS A6000 using Tapatalk
  13. Yea. It's gonna suck for average people when I merge the dev-settings branch and they have to go and save their settings again because it has changed. The application is still in beta as it is still at a point where it could change and an update could mean a fresh install. Untill that is not the case, I was holding out on it being put in CA. But if they have published the template, then they can provide support to the people using it right. Sent from my ONEPLUS A6000 using Tapatalk
  14. Subtitles are a little tricky. At the moment unmanic has real shitty support for the subtitle streams in your video files. The problem is that different containers have different implementations on how subtitles are stored and therefore ffmpeg requires different arguments depending on your combination of subtitles, src container and destination container. Removing embedded subtitle streams will fix a lot of errors when converting between containers until I expand on the settings capabilities of unmanic and how it generates tasks for ffmpeg. Sent from my ONEPLUS A6000 using Tapatalk
  15. Actually that output is enough as far as unmanic goes. It looks like ffmpeg did not like the arguments it was passed or the file needed some kind of special configuration. Can you please try running that command manually from a terminal inside the docker container. Ffmpeg will give you some output that will show what is wrong. Then can you give me that output? Sent from my ONEPLUS A6000 using Tapatalk