Jump to content

Search the Community

Showing results for tags 'EXTEND'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. FordGT90Concept

    HDHomeRun EXTEND log behavior

    Public Service Announcement Since I've lost two EXTENDs already to "reset reason = application watchdog" I've been paying closer attention to what my EXTENDs do. Here is what they sit at now (number is the last segment of the IP address): 100, new as of a month or so ago. 19700101-00:00:20 System: reset reason = application watchdog 19700101-00:00:20 System: E5592573 0000000E 004E2D68 0042D3A0 00432724 0040D9D0 004DDCEC 004DDCC0 19700101-00:00:20 System: 00506E0C FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:20 System: network link 100f 19700101-00:00:21 System: ip address obtained: 192.168.0.100 / 255.255.255.0 20180415-06:00:50 System: time changed from Thu Jan 1 00:00:37 1970 to Sun Apr 15 06:00:50 2018101, about 19 months old and the most used of the three. 19700101-00:00:17 System: reset reason = application watchdog 19700101-00:00:17 System: E5592573 0000000E 004E2D68 0042D3A0 00432724 0040D9D0 004DDCEC 004DDCC0 19700101-00:00:17 System: 00506E0C FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:17 System: network link 100f 19700101-00:00:18 System: ip address obtained: 192.168.0.101 / 255.255.255.0 20180401-06:00:53 System: time changed from Thu Jan 1 00:00:34 1970 to Sun Apr 1 06:00:53 2018102, about 19 months old and rarely used. System Log 19700101-00:00:17 System: reset reason = firmware upgrade 19700101-00:00:17 System: network link 100f 19700101-00:00:18 System: ip address obtained: 192.168.0.102 / 255.255.255.0 20180328-21:18:07 System: time changed from Thu Jan 1 00:00:34 1970 to Wed Mar 28 21:18:07 2018102 is perfectly fine so not much to talk about there. 100 and 101 both have the application watchdog message; however, note the time it occurred. It's almost like they deliberately rebooted themselves at 6am. The question is why? Did the log get so full it had to purge it? I don't think this behavior is in error because nothing was recording at the time. Still strange and something to be aware of.
  2. FordGT90Concept

    HDHomeRun EXTEND transcoding profiles

    I have three general classes of devices I run Emby on: ​-Windows PCs, they would prefer MPEG2 -Amlogic S905/X, they would prefer MPEG4 "heavy" "mobile" -Surface 2 & smartphones, they would prefer MPEG4 "mobile" There's two situations: 1) Live TV: I assume Emby can request a specific profile from the HDHomeRun EXTEND and I also assume this isn't being done. If it is being done, then I get the impression it is broken because the default profile set in each EXTEND impacts the streams that are played from it. If it isn't automatically figuring this out, I'd like to be able to set it in Emby Server where Emby Theater requests MPEG2 and everything else gets MPEG4 "mobile." Is this possible now? It is possible to add? Is it something that will be added? 2) Recordings: This is where things get iffy because Emby Server itself isn't the destination where the video will be consumed. I think the best solution is to be able to select a transcoding profile on a per recording or series basis. For example, I know some series only get watched on the Windows computers so it would recorded as MPEG2. I know series may be watched on tablets or Amlogic boxes so it would be recorded as MPEG2 "mobile." Then there is sports events of all kinds need to be recorded as MPEG2 or MPEG4 "heavy" because MPEG4 "mobile" looks like crap. Is this possible now? It is possible to add? Is it something that will be added? HDHomeRun EXTEND are powerful little devices but options in Emby appear to prevent them from being used optimally. Edit: Apparently MPEG4 "heavy" is too much for the Amlogic 905/X devices. Here is what MPC-HC got off the recording: Video: MPEG4 Video (H264) 1920x1080 29.97fps [V: h264 high L4.0, yuv420p, 1920x1080] Audio: Dolby AC3 48000Hz stereo 384kbps [A: English [eng] (ac3, 48000 Hz, stereo, 384 kb/s)] Here's an MPEG4 "mobile": Video: MPEG4 Video (H264) 1280x720 29.97fps [V: h264 high L4.0, yuv420p, 1280x720] Audio: Dolby AC3 48000Hz 6ch 448kbps [A: English [eng] (ac3, 48000 Hz, 5.1, 448 kb/s)] That is of a football game which would definitely be at least 1080i. It appears "heavy" doesn't change resolution where "mobile" does.
×
×
  • Create New...