Jump to content

Josh.5

Members
  • Content Count

    80
  • Joined

  • Last visited

  • Days Won

    4

Josh.5 last won the day on October 3 2019

Josh.5 had the most liked content!

Community Reputation

56 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. Yea. Pgs subs are images, not text. They cannot be converted to txt. Your problem is you are trying to remux it into another container (mkv) which does not support pgs subs codec for subtles. You can select the option in settings to remove subtle streams. That should resolve your problem. But you will then need to also download your subtitles separately after the conversion if you still want them. Sent from my ONEPLUS A5010 using Tapatalk
  2. FFMPEG log recording is only enabled if you turn on debugging. Sent from my ONEPLUS A5010 using Tapatalk
  3. Just thought I'd write a quick update. I was expecting to have HW encoding sorted by end of October, but now that we are getting into the warmer months I'm using all my free time to carry out some much needed maintenance on my house. I probably will not get back to working on Unmanic until February/March. If you find issues, feel free to put them on GitHub, I will get around to it eventually. Hope everyone has a Merry Christmas (or whatever other holidays you celebrate at this time of year) and thanks for using Unmanic. Sent from my ONEPLUS A6000 using Tapatalk
  4. There will be an FFMPEG command also in your unmanic logs. That would be the best place to start. After that it would be a case of finding out what FFMPEG limitations exist for h265 and the command that Unmanic generated. How big is the file? Sent from my ONEPLUS A6000 using Tapatalk
  5. FFMPEG logs are not saved unless debugging is enabled. They add an unnecessary weight to the database for everyday use. It is possible that in the future when history is able to be cleared etc, the FFMPEG logging will be on all the time. But for now as there is no simple way to reduce the history log, this is a debugging only feature. If you are seeing issues with files failing to convert, I'd recommend that the first course of action is to enable debugging. This will then show you the FFMPEG logs and also other key logs from Unmanic and will greatly help with determining the cause of the failure. I'd be willing to bet you have an issue with subtitles as that is the common problem most people have with Unmanic at this stage. Flick on debugging and take a look... Sent from my ONEPLUS A6000 using Tapatalk
  6. 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
  7. 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.
  8. 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
  9. 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
  10. I would just wait for the history feature to be complete. Should be done soonish
  11. 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
  12. 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
  13. 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
  14. 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.
  15. 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