Jump to content

Jorgen

Members
  • Posts

    269
  • Joined

  • Last visited

Posts posted by Jorgen

  1. Thanks for looking over it, i just pulled the trigger [emoji4]

    I know this is too late, but I recommend a SFX PSU in that case. Nothing wrong with the seasonic, I have the exact same model. But it takes up more room than necessary and it doesn’t have a silent mode, the fan is always spinning. Space is at a premium in the node 304 especially when you have 4+ drives. You will discover this soon when trying to wrangle all the cables into submission... :)

    The standard case fans are pretty good too, I wasn’t able to justify the noctua cost when I was trying to make my server as silent as possible.

    Please post build logs!


    Sent from my iPhone using Tapatalk
  2. 9 minutes ago, cybrnook said:

    Would it be possible to revert to 1.1.0, for a test case? Or perhaps you still have it, and I can just change my docker source?

    You should be able to specify an older release by adding the correct tag to the Repository setting in the unRAID docker template. E.g. jlesage/handbrake:v1.13.5

    For available tags, see https://hub.docker.com/r/jlesage/handbrake/tags/

    I don't know which tag correspond to 1.1.0 though.

     

    Edit: if you specify a particular tag you will be stuck on that version forever and won't be notified of updates. Remove the tag to get back on the "latest" releases.

    • Like 1
  3. On 7/14/2018 at 10:58 AM, Jorgen said:


    Aha. I’ve got a Haswell, will do some quality comparisons.
     

     

    Ok, thanks for pointing this out. I had (wrongly) assumed that QSV only added hardware acceleration to the normal h264 encoder, but after somme googling I now realise it's a completely different implementation  of h264 encoding with different parameters and tradeoffs between quality/speed/file size.

     

    For other's benefit, QSV is really intended for real time streaming conversions where speed is more important than quality. If you care about quality, sacrifice raw speed and use the normal CPU powered encoders in Handbrake instead and you'll get better quality in smaller file sizes.

    Apparently, the best quality you can hope for using QSV is on par with the Veryfast preset for normal h264, but the file size will be larger.

     

    There are some tuning parameters you can add to QSV to improve things somewhat, but don't expect miracles: https://handbrake.fr/docs/en/latest/technical/video-qsv-options.html

     

  4. 8 hours ago, jowi said:

    how do i prevent TM from constantly spinning up the unraid disk every 10 minutes or so after the backup is finished?

     

    Go to the settings page for your TM share, and set AFP Security Settings/Volume dbpath to a directory that will persist on your cache drive (assuming you have a cache drive).

    TM constantly (well, every 10 minutes) checks info stored in some TM database files. If these are located on your array disk, the disk will spin up. By configuring the share as above, those files are actually stored on the cache drive. Not only does that prevent the array disk to spin up, the whole operation is also much faster.

    In fact, I recommend you do the same for ALL your AFP shares as it greatly improves general file browsing performance (ever waited 5 minutes for a share directory listing to be displayed in Finder?) 

     

    This is from the unRAID help for Volume dbpath:

    Quote

    Sets where to store netatalk database information. A directory with same name as the share will be created here.

    Leave this field blank to have the database created in the root of the share.

     

    • Like 2
  5. You are correct.  The quality of the produced video is poor if you want a reasonable file size.  However, I have a sandy bridge CPU, which is one of the first gen having quick sync support.  The quality has increased with new generations, so maybe it's less a problem now.

    Aha. I’ve got a Haswell, will do some quality comparisons.


    Sent from my iPhone using Tapatalk
  6. On 7/13/2018 at 7:10 AM, Djoss said:

     

    I've play with the feature a bit and I can say that the speed is there, but not the quality... At least on my sandy bridge.

     

    What do you mean about the quality not being there? Do you see a difference in actual output quality when using QS? Or am I misreading your comment?

  7. On 7/11/2018 at 10:46 PM, Jorgen said:

    I eventually fixed it by deleting the container and image, then re-installing via CA. Quick and painless, all settings retained, annoying error message gone. 

    Spoke too soon, problem has come back overnight. Deleting the Radarr container+image and re-installing fixed it again.

  8. 14 hours ago, Jorgen said:


    Thanks, good to know it’s working for you. I think I messed up the preset. I will start over and if It’s still happening I’ll post full logs.

     

    Sorry Djoss, need your help. I cannot get the watch folder to work with QSV encoder on my system.

    Logs attached from a successful conversion via WebUI and an unsuccessful via watch folder. Same preset, same movie file (just renamed for each test).

    The watch folder is still pretending the CPU doesn't support QSV.

     

    WebUI 2018-07-12 20-55-00.log

    conversion.log

    HQ 720p30 Surround QSV.json

  9.  
    It's working fine for me.  Can you provide the whole content of the conversion log for a failed video?

    Thanks, good to know it’s working for you. I think I messed up the preset. I will start over and if It’s still happening I’ll post full logs.


    Sent from my iPhone using Tapatalk
  10. On 7/10/2018 at 10:46 AM, Djoss said:

    Try the latest version, which have Quick Sync support.

    See https://github.com/jlesage/docker-handbrake#intel-quick-sync-video for more details on how to use it.

     

    Wow, this is so much faster! Thank you Djoss!

     

    Works great in UI mode, but I'm having problems getting this to work for the automatic watch folder.

    Has anyone else got that to work?

     

    Getting this in the docker log (from unRAID UI) when using watch folder:

    [autovideoconverter] Starting conversion of '/watch/Arrival.mkv' (16e292dbffc5c7745a3f5fcff335126b) using preset 'Mathias_MKV_720p30QS'...
    [autovideoconverter] 1 title(s) to process.
    [autovideoconverter] Encoding: 0.00 %
    [autovideoconverter] Conversion failed.

    In appdata/HandBrake/log/conversion.log I see this for the same job:

    ------- CONVERSION OUTPUT Wed Jul 11 23:39:07 AEST 2018 -------
    [23:39:07] hb_init: starting libhb thread
    [23:39:07] thread 152b319c2ae8 started ("libhb")
    HandBrake 1.1.0 (2018070900) - Linux x86_64 - https://handbrake.fr
    8 CPUs detected
    Opening /watch/Arrival.mkv...
    [23:39:07] CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
    [23:39:07]  - Intel microarchitecture Haswell
    [23:39:07]  - logical processor count: 8
    [23:39:07] Intel Quick Sync Video support: no
    [23:39:07] hb_scan: path=/watch/Arrival.mkv, title_index=1
    
    ...snip...
    
    x264 [error]: invalid preset 'quality'
    ERROR: Failure to initialise thread 'H.264/AVC encoder (libx264)'

    But for a successful job started from the UI, I see this in appdata/HandBrake/ghb/Encodelogs:

    Handbrake Version: 1.1.0 (2018070900)
    [23:24:20] gtkgui: Custom Preset: /My Presets/Mathias_MKV_720p30QS
    [23:24:20] 1 job(s) to process
    
    ...snip...
    
    [23:24:20] CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
    [23:24:20]  - Intel microarchitecture Haswell
    [23:24:20]  - logical processor count: 8
    [23:24:20] Intel Quick Sync Video support: yes
    [23:24:20]  - Intel Media SDK hardware: API 1.26 (minimum: 1.3)
    [23:24:20]  - H.264 encoder: yes
    [23:24:20]     - preferred implementation: hardware (any) via D3D11
    [23:24:20]     - capabilities (hardware):  breftype la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice
    [23:24:20]  - H.265 encoder: no
    
    


     

  11. On 7/9/2018 at 8:22 PM, livingonline8 said:

    So I have NzbGet, Radarr & Sonarr working perfectly for months but recently I noticed nothing is being downloaded so when I checked 

    I found out that Radarr cannot connect to NzbGet 

     

    When I tested the connection in Radarr I got the following error message "Test was aborted due to an error: Unable to connect to NZBGet. Error getting response stream (ReadDone2): ReceiveFailure"

     

    You post prompted me to check my radarr and I had the exact problem (same situation too, no config changes for months, only automatic container updates).

    - If I restart the container, the download client test works perfectly.

    - If I send a movie download request over to NZBGet, I get the error message (although the request gets to NZBGet and starts downloading)

    - If I try the download client test again, it now fails with the same error message. If I restart container I'm back to step one.

     

    I eventually fixed it by deleting the container and image, then re-installing via CA. Quick and painless, all settings retained, annoying error message gone. 

  12. 8 minutes ago, Luc1fer said:

    I made a new preset for h265, constant quality, 720p.  All of the video settings have saved to the profile as I wanted.  I also wanted no subtitles so I removed the subs.  I wanted audio transcoded to aac 5.1 but every time I add a new source file and choose the preset I created the video settings are fine but it has selected aac 2.0 audio transcoding and to burn in the subs.  I have tried to create a new preset with the same result.

     

    So at the moment I have to change the preset for every file I transcode as it won't save my audio and subtitle selections.

     

    Can you post a screenshot of the audio/subtitle changes you are making?  I have done similar changes and they stick for the preset for me.

  13. Slight but welcome performance boost for my VM on a Haswell CPU. Haven't noticed any .adverse side effects.
     
    M/B: ASUSTeK COMPUTER INC. - H87I-PLUS
    CPU: Intel® Core™ i7-4770 CPU @ 3.40GHz
    HVM: Enabled
    IOMMU: Enabled
    Cache: 256 kB, 1024 kB, 8192 kB
    Memory: 16 GB (max. installable capacity 16 GB)
     
    OSX VM, OVMF, Q35-2.10, 4 of 8 logical cores, 8GB RAM, GT710 passed through
     
    6.5.2

    To Clover boot screen: 18s
    To fully booted VM: 55s

    Geekbench results: single 4278, multi 8444

     

    6.5.3-rc1

    To Clover boot screen: 9s
    To fully booted VM: 37s

    Geekbench results: single 4325, multi 8494

     

    Geekbench compare before/after: https://browser.geekbench.com/v4/cpu/compare/8399440?baseline=8399110

  14. You can try connecting a physical keyboard and mouse to your unRAID server and then attaching them to the VM (via the edit menu). Then use VNC to view the screen (assuming you don’t have a GPU passed through) and use the physical mouse/kb to enter the details.
    This worked for me in a similar situation, but I guess it depends on where in the boot the devices becomes available.


    Sent from my iPhone using Tapatalk

×
×
  • Create New...