[Support] Josh5 - Unmanic - Library Optimiser


Recommended Posts

5 hours ago, JPDom1 said:

I have updated to the latest version and just 2 things to report.

 

1. I do my conversions folder by folder at the moment (/Mnt/usr/series/Show to convert) and then "edit" the container to the next show when it is done (/Mnt/usr/series/Show to convert). Each time the container starts up it goes back to the default settings it is not persistent.

2. When changing something in the settings and then clicking "Submit" my browser goes to http://192.168.0.4:8899/settings/?step=general with the page below. I then manually need to remove the "/?step=general" to get back to the settings GUI

 

image.thumb.png.5a0535ae5f3a39f504451fb57379d285.png

 

Apart from that my poor Threadripper has been crying for a week while my disk free disk space keeps going up 🙂 

I am experiencing the same thing with settings.

Link to comment

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...
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

  • Haha 1
Link to comment

Q: What is the benefit of cloning multichannel audio into a separate stereo audio track?

 

My understanding is creating maximum compatibility, but if I am using Plex, isn't this redundant? The only advantage I can see is using less system resources when playing back an AAC stereo track VS an AC3 passthrough or AAC 5.1 > AC3 transcode on the fly via Plex.

 

Unless I can be convinced otherwise, I'm disabling the clone function for now.

 

I searched in this thread and couldn't find an answer.

Link to comment
Q: What is the benefit of cloning multichannel audio into a separate stereo audio track?
 
My understanding is creating maximum compatibility, but if I am using Plex, isn't this redundant? The only advantage I can see is using less system resources when playing back an AAC stereo track VS an AC3 passthrough or AAC 5.1 > AC3 transcode on the fly via Plex.
 
Unless I can be convinced otherwise, I'm disabling the clone function for now.
 
I searched in this thread and couldn't find an answer.
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

  • Thanks 1
Link to comment

After nearly a couple thousand conversions, my history is not working any more. I tried to reset things by renaming the history.json and completed jobs folders, but that just made unmanic upset, and no current history showed up. Is there a way to start things over properly without blowing it away and setting up from scratch?

 

Or should I just wait for the next beta where history is rolled into the database?

  • Like 1
Link to comment
9 hours ago, Zer0Nin3r said:

a separate stereo audio track?

So, with the Create a stereo clone of streams turned off, does Unmanic still passthrough stereo AAC tracks? I would not be opposed to that.

 

BTW. After completing the upgrade to the latest release and re-saving my settings, I was noticing some issues still with enabling subtitles even though I am converting to MKV. I've disabled subtitles (again) for now to resolve the encoding issues surrounding subtitles.

Edited by Zer0Nin3r
Info about Unmanic + subtitles
Link to comment

Been experiencing random Kernal panics not knowing what is causing it. Finally tailed my syslog to get a capture when it crashed and got it.

I think this might be related to this container not 100% sure as i have also recently switched to a new system.

 

Crash attached below and it is the "FFMPEG" that gets my attention.

Although this crash is different to my others currently running a memtest will let it run over night.

System was up for 10 minutes before it crashed and my unmatic container is configured to scan every 5 minutes so this happened just after the scan.

 

TR4 1950X

64GB DDR4 Kingston 3000MHZ

Asus X399 Aorus Pro

P2000

Dell H310 x2 It mode

Lots of disks

 

Oct  3 21:34:04 Mufasa kernel: traps: ffmpeg[31800] general protection ip:152919c2051e sp:1529128aba60 err                                                                                                          or:0 in libx265.so.169[1529196fd000+533000]
Oct  3 21:34:04 Mufasa kernel: BUG: unable to handle kernel paging request at 0000000000003bc0
Oct  3 21:34:04 Mufasa kernel: PGD 0 P4D 0
Oct  3 21:34:04 Mufasa kernel: Oops: 0000 [#1] SMP NOPTI
Oct  3 21:34:04 Mufasa kernel: CPU: 8 PID: 31779 Comm: ffmpeg Tainted: P           O      4.18.20-unRAID #                                                                                                          1
Oct  3 21:34:04 Mufasa kernel: Hardware name: Gigabyte Technology Co., Ltd. X399 AORUS PRO/X399 AORUS PRO-                                                                                                          CF, BIOS F1 10/01/2018
Oct  3 21:34:04 Mufasa kernel: RIP: 0010:__dec_node_state+0x0/0x53
Oct  3 21:34:04 Mufasa kernel: Code: 84 e0 81 65 44 88 01 c3 48 8b 3f 48 89 f8 48 c1 ef 38 83 e7 03 48 c1                                                                                                           e8 3a 48 69 ff 80 06 00 00 48 03 3c c5 00 65 ea 81 eb 8d <48> 8b 97 c0 3b 00 00 89 f6 b0 ff 48 8d 4c 32 01                                                                                                           65 0f c0 01 65 44
Oct  3 21:34:04 Mufasa kernel: RSP: 0018:ffffc900273e7b70 EFLAGS: 00010213
Oct  3 21:34:04 Mufasa kernel: RAX: 0000000000000037 RBX: ffffea001aa1f940 RCX: 000000001aa1f940
Oct  3 21:34:04 Mufasa kernel: RDX: 22ffea001aa1f908 RSI: 000000000000000c RDI: 0000000000000000
Oct  3 21:34:04 Mufasa kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8806f6fb9380
Oct  3 21:34:04 Mufasa kernel: R10: ffff88107f2fc000 R11: ffff88103568afee R12: ffff8806f5492518
Oct  3 21:34:04 Mufasa kernel: R13: 80000006a87e5067 R14: ffffc900273e7c98 R15: ffffea001aa1f940
Oct  3 21:34:04 Mufasa kernel: FS:  0000152912b8bb20(0000) GS:ffff88103ca00000(0000) knlGS:000000000000000                                                                                                          0
Oct  3 21:34:04 Mufasa kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  3 21:34:04 Mufasa kernel: CR2: 0000000000003bc0 CR3: 0000000001e0a000 CR4: 00000000003406e0
Oct  3 21:34:04 Mufasa kernel: Call Trace:
Oct  3 21:34:04 Mufasa kernel: page_remove_rmap+0x24d/0x29c
Oct  3 21:34:04 Mufasa kernel: unmap_page_range+0x5da/0x88a
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x34/0x70
Oct  3 21:34:04 Mufasa kernel: unmap_vmas+0x4b/0x7f
Oct  3 21:34:04 Mufasa kernel: exit_mmap+0xc8/0x16a
Oct  3 21:34:04 Mufasa kernel: mmput+0x4d/0xe5
Oct  3 21:34:04 Mufasa kernel: traps: ffmpeg[32284] general protection ip:14e28c68b73e sp:14e28575a4c0 err                                                                                                          or:0
Oct  3 21:34:04 Mufasa kernel: traps: ffmpeg[31226] trap invalid opcode ip:147bd24c0d55 sp:147bcb790428 er                                                                                                          ror:0 in libx265.so.169[147bd236d000+533000]
Oct  3 21:34:04 Mufasa kernel: do_exit+0x3b0/0x8b0
Oct  3 21:34:04 Mufasa kernel: do_group_exit+0x9a/0x9a
Oct  3 21:34:04 Mufasa kernel: get_signal+0x417/0x44c
Oct  3 21:34:04 Mufasa kernel: in libx265.so.169[14e28c637000+533000]
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70
Oct  3 21:34:04 Mufasa kernel: do_signal+0x31/0x59d
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x34/0x70
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70
Oct  3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70
Oct  3 21:34:04 Mufasa kernel: exit_to_usermode_loop+0x25/0x96
Oct  3 21:34:04 Mufasa kernel: prepare_exit_to_usermode+0x66/0x6d
Oct  3 21:34:04 Mufasa kernel: retint_user+0x8/0x8
Oct  3 21:34:04 Mufasa kernel: RIP: 0033:0x1529197cfa64
Oct  3 21:34:04 Mufasa kernel: Code: Bad RIP value.
Oct  3 21:34:04 Mufasa kernel: RSP: 002b:0000152912b86cc8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff02
Oct  3 21:34:04 Mufasa kernel: RAX: 0000000000000008 RBX: 0000152912b86e80 RCX: 0000000000000480
Oct  3 21:34:04 Mufasa kernel: RDX: 00001528ff35ff78 RSI: 0000000000000008 RDI: 0000152912b86e80
Oct  3 21:34:04 Mufasa kernel: RBP: 0000152912b86f10 R08: 0000152907d23f78 R09: 0000000000000480
Oct  3 21:34:04 Mufasa kernel: R10: 0000000000000020 R11: 0000000000000001 R12: 0000000000000008
Oct  3 21:34:04 Mufasa kernel: R13: 000055ac0aeb6b98 R14: 0000152912b87100 R15: 000055ac0b5a0048
Oct  3 21:34:04 Mufasa kernel: Modules linked in: macvlan nvidia_uvm(O) xt_CHECKSUM iptable_mangle ipt_REJ                                                                                                          ECT ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE                                                                                                           iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 h                                                                                                          wmon_vid bonding edac_mce_amd nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper kvm crct10dif_pc                                                                                                          lmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm pcbc aesni_intel mpt3sas aes_x86_64 crypto_simd cry                                                                                                          ptd agpgart atlantic raid_class scsi_transport_sas syscopyarea nvme ahci i2c_piix4 k10temp sysfillrect glu                                                                                                          e_helper i2c_core sysimgblt ccp fb_sys_fops libahci wmi_bmof mxm_wmi nvme_core wmi button pcc_cpufreq acpi                                                                                                          _cpufreq
Oct  3 21:34:04 Mufasa kernel: CR2: 0000000000003bc0
Oct  3 21:34:04 Mufasa kernel: ---[ end trace 186181c9c6d6be3d ]---
Oct  3 21:34:04 Mufasa kernel: RIP: 0010:__dec_node_state+0x0/0x53
Oct  3 21:34:04 Mufasa kernel: Code: 84 e0 81 65 44 88 01 c3 48 8b 3f 48 89 f8 48 c1 ef 38 83 e7 03 48 c1                                                                                                           e8 3a 48 69 ff 80 06 00 00 48 03 3c c5 00 65 ea 81 eb 8d <48> 8b 97 c0 3b 00 00 89 f6 b0 ff 48 8d 4c 32 01                                                                                                           65 0f c0 01 65 44
Oct  3 21:34:04 Mufasa kernel: RSP: 0018:ffffc900273e7b70 EFLAGS: 00010213
Oct  3 21:34:04 Mufasa kernel: RAX: 0000000000000037 RBX: ffffea001aa1f940 RCX: 000000001aa1f940
Oct  3 21:34:04 Mufasa kernel: RDX: 22ffea001aa1f908 RSI: 000000000000000c RDI: 0000000000000000
Oct  3 21:34:04 Mufasa kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8806f6fb9380
Oct  3 21:34:04 Mufasa kernel: R10: ffff88107f2fc000 R11: ffff88103568afee R12: ffff8806f5492518
Oct  3 21:34:04 Mufasa kernel: R13: 80000006a87e5067 R14: ffffc900273e7c98 R15: ffffea001aa1f940
Oct  3 21:34:04 Mufasa kernel: FS:  0000152912b8bb20(0000) GS:ffff88103ca00000(0000) knlGS:000000000000000                                                                                                          0
Oct  3 21:34:04 Mufasa kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  3 21:34:04 Mufasa kernel: CR2: 00001529197cfa3a CR3: 0000000001e0a000 CR4: 00000000003406e0
Oct  3 21:34:04 Mufasa kernel: Fixing recursive fault but reboot is needed!

 

TIA,

Link to comment

Hi,

 

I just installed this and pointed unmanic at my library, but nothing at all happens.  Is there, like, a start button that I'm missing?

 

In the unmanic settings I have:

/library/movies -> /mnt/user/plex/movies

/library/tv -> /mnt/user/plex/series

/tmp/unmanic -> /tmp/unmanic

 

In unmanic settings:

/library/movies

/tmp/unmanic

Run Scan on Start is selected

 

EDIT: For some reason, about an hour later, it started running.

Edited by Whiskeyjack
Link to comment
1 hour ago, Whiskeyjack said:

Hi,

 

I just installed this and pointed unmanic at my library, but nothing at all happens.  Is there, like, a start button that I'm missing?

 

In the unmanic settings I have:

/library/movies -> /mnt/user/plex/movies

/library/tv -> /mnt/user/plex/series

/tmp/unmanic -> /tmp/unmanic

 

In unmanic settings:

/library/movies

/tmp/unmanic

Run Scan on Start is selected

 

EDIT: For some reason, about an hour later, it started running.

Probably had the library scan set for 60 mins and that’s what kicked it off. Restarting the container also triggers a library scan after you select the “run scan on start” option in the UI settings. 
 

A start/pause button might be useful in the UI, but I supplement that with the start/pause feature for the docker in the unraid UI instead. (Useful if you have unmanic with hi cpu pins and you need to temporarily run some other heavy processes)

Link to comment
8 minutes ago, Cpt. Chaz said:

A start/pause button might be useful in the UI, but I supplement that with the start/pause feature for the docker in the unraid UI instead. (Useful if you have unmanic with hi cpu pins and you need to temporarily run some other heavy processes)

+1

I use the docker commands to automate this. Super easy to script. My home theater VM is scripted so when it's in use, this container is shut down.

Link to comment
24 minutes ago, jonathanm said:

+1

I use the docker commands to automate this. Super easy to script. My home theater VM is scripted so when it's in use, this container is shut down.

i keep plex on a dedicated machine separate from unraid, but that's a brilliant alternative!

Edited by Cpt. Chaz
typo
Link to comment
15 hours ago, jonathanm said:

After nearly a couple thousand conversions, my history is not working any more. I tried to reset things by renaming the history.json and completed jobs folders, but that just made unmanic upset, and no current history showed up. Is there a way to start things over properly without blowing it away and setting up from scratch?

 

Or should I just wait for the next beta where history is rolled into the database?

I would just wait for the history feature to be complete. Should be done soonish

Link to comment
9 hours ago, Zer0Nin3r said:

So, with the Create a stereo clone of streams turned off, does Unmanic still passthrough stereo AAC tracks? I would not be opposed to that.

 

BTW. After completing the upgrade to the latest release and re-saving my settings, I was noticing some issues still with enabling subtitles even though I am converting to MKV. I've disabled subtitles (again) for now to resolve the encoding issues surrounding subtitles.

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

 

  • Thanks 1
Link to comment
Taking requests?  While I don't want to convert anything in the library I would like an option to normalize volume across all the media.  If it requires rencoding the media to another format so be it.  Volume normalization is the main thing I'm looking for.
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

Link to comment
On 10/6/2019 at 3:22 AM, Mantene said:

Yeah, I did that at first, but it takes so long with fewer cores. If it could use the nvidia driver it would be much more efficient. Plus the quality of nvenc is actually quite good.

i don't think that makes a lick of a difference in quality

Link to comment

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). 

 

image.thumb.png.3f824d236435d8a255be1058df0d4ca1.png

 

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 

 

image.thumb.png.60e1fd4a227b899b102ec79de488c17b.png

 

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.

Edited by Josh.5
Added notice about issues with new release
  • Thanks 1
Link to comment

I started using this about two weeks ago and its great! I eats the shit out of my CPU though. I'd love to see a utilization limiter or, better yet, a scheduler that auto pauses jobs outside the window. right now I run this during the week by turning the app on and off. I also have the app pinned to 4 of my 8 cores and that seems to work OK, but it would run much faster if I could let it use them all when everyone is asleep through a scheduler.

 

Otherwise it's a really great tool! I'd also like to see it save the scan job from files to be converted so it doesn't have to scan the entire library every time I bring it online.

Link to comment
I started using this about two weeks ago and its great! I eats the shit out of my CPU though. I'd love to see a utilization limiter or, better yet, a scheduler that auto pauses jobs outside the window. right now I run this during the week by turning the app on and off. I also have the app pinned to 4 of my 8 cores and that seems to work OK, but it would run much faster if I could let it use them all when everyone is asleep through a scheduler.
 
Otherwise it's a really great tool! I'd also like to see it save the scan job from files to be converted so it doesn't have to scan the entire library every time I bring it online.
You can always do CPU pinning that's what I do and I think most people do but the time or is a good idea

Sent from my SM-N960U using Tapatalk

  • Like 1
Link to comment
18 minutes ago, eagle470 said:

I started using this about two weeks ago and its great! I eats the shit out of my CPU though. I'd love to see a utilization limiter or, better yet, a scheduler that auto pauses jobs outside the window. right now I run this during the week by turning the app on and off. I also have the app pinned to 4 of my 8 cores and that seems to work OK, but it would run much faster if I could let it use them all when everyone is asleep through a scheduler.

 

Otherwise it's a really great tool! I'd also like to see it save the scan job from files to be converted so it doesn't have to scan the entire library every time I bring it online.

You can create a little script to turn the docker on and off. 
I'm not good with scripting so, I made 2 scripts. The first one is to tell it when to turn it on. Then the second when to turn it off. 
I know there is a far more eloquent way of doing this, but I am okay with this for now sense it works.

My script is simply docker start unmanic for the first one. Then docker stop unmanic in the second then custom cron jobs on both to make them run at the times I desire.  
 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.