The way I've been using the T2 is to modify the HB format to include the following: About the only thing that can be set that effects the encoding speed and/or quality is the video bit rate "-vb n" (where n is implicitly kb.) When one uses the hardware encoders in the T2 chips there are not many tuning options available. After reviewing my old notes and playing around a little with the latest HB 1.3.2 I have at the least some recommendations: I finally got around to looking at this again. I’ll be on vacation for 3 weeks, so no experiments from my end for a bit. In general it seems like you need a higher bitrate using T2 hardware than software to get closer to similar quality. In general it’s very sparsely documented, and seems more trial and error with the VideoToolBox API. Found a few hints about knobs not available on FFmpeg that could help. My 2 x264 channels seem to be better when using FFmpeg, but I haven’t tried going down the route of selecting a different encoder by channel. FFmpeg glitches the audio and typically the audio sync multiple times per hour on my Cox channels. Waiting for Handbrake guys to pull support for T2 machines. My plan is to just use T2 hardware for my typical 2-4 shows per night. CPU load for the hardware is low, maybe 20% or less, so a lot of time is left for software. Maybe on machines with more cores the software would close the gap. On my MacMini, the T2 hardware seems to be 3-4x faster than software. On T2 Mac’s, it seems like allow_sw defaults to on. Its a year old so might not mean anything anymore. Only other interesting thing I found was a way to resolve some ugly artifacts by increasing bufsize & maxrate to 9M. On another note, using no audio codec or just using “-acodec aac” gives QuickTime error -50 on playback.Įither adding "-ac 2" or "-ac 6” after "-acodec aac" seems to make it playable. Its much slower but will allow you to move forward. If you add “-allow_sw true” after the hevc_videotoolbox you can play around using the software only implementation. It appears that ffmpeg_edl_ac3.sh does some magic with the parameters that can’t seem to be corrected by putting the video options in a different field (or editing formats has some magic about using an old setting.) The "-vcodec hvec_videotoolbox -vtag hvc1” options have to come after the "-i ” otherwise you get a "Unknown decoder ‘hevc_videotoolbox’”. I think you might need some bash-foo on ffmpeg_edl_ac3.sh. Set file sharing appropriately for the Channels folders for other accounts.I was already starting to play with ffmpeg directly on some TiVo downloads using some Googled tips. You can then logon to your own separate account. If security/auto logon is a problem for you, set up a separate account just for Channels to run as a Service, it will start automatically. The next (and probably my last) computer is likely to be a Mac with an Apple Silicon processor when I have given up Windows completely. I also keep 2 rotated Bombich Carbon Copy Clones of the HDD. Everything, including 200GB of iCloud is backed up on 3 rotated TimeMachine drives. I wrote a lot of software for Windows, including shrink-wrap, but now only run it occasionally inside Parallels VMs.Ĭhannels is very stable on an external 2TB LaCie USB-C drive. At one time we had five PCs, but now the only computer in the house is an Intel iMac running 24/7 with an UPS. That may pose a security issue for you and auto-login will not be available if you use FileVault2.īTW, to manage headless servers, I use Splashtop, which is free for home use. On MacOS, AFAIK, you can only set an app to run at startup by setting it to run at login, which means you have to set auto-login. On Win, you can set an app to run at startup, without having to set auto-log in to your account (see windows - Start an application at system start without login - Stack Overflow and Windows preload software before login - Super User) The one advantage I can think of of always running on the Win side is (I think - not totally sure about this - others, please correct me if I'm wrong): So the question is whether to run Win or MacOS as the always-on side on which Plex and Channels servers are running. Your use case seems to require dual-boot for the flexibiilty it gives. FWIW, I have Channels DVR running on a Synology DS 220+ and Plex running on a headless Win 10 Intel NUC. But I do have a fair amount of experience with running always-on headless servers (Mac Mini running MacOS, Intel NUC running a lightweight Linux, and Intel NUC running Win10. I'm very new to Channels DVR (and liking very much so far).
0 Comments
Leave a Reply. |