Search the Community

Showing results for tags 'dvb-t2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements and Promotions
    • EyeTV News and Announcements
    • Promotion, Events, Giveaways and Contests
    • Industry News
    • EyeTV User Video Conference FAQ
  • General Feedback, Comments and Reviews Topics Posts
    • EyeTV Product Reviews
    • EyeTV Labs
    • EyeTV Wishlist
    • EyeTV Support Page FAQ
  • EyeTV Portfolio Software
    • EyeTV User Conference (Jitsi) Software Meeting
    • EyeTV 4 (MacOSX APP)
    • EyeTV 3 (Mac OSX APP)
    • EyeTV Plus
    • THC (Windows APPs)
    • Toat@l TV (Windows APP)
    • EyeTV iOS APPs
    • EyeTV tvOS APP
    • EyeTV Android APK smart phone / table
    • EyeTV Android APK Fire TV / Nexus Player / MyGica
  • EyeTV Portfolio Hardware
    • EyeTV User Conference (Jitsi) Hardware Meeting
    • EyeTV Mobile
    • EyeTV Micro
    • EyeTV W
    • EyeTV Netstream 4sat
    • EyeTV Netstream 4c
    • EyeTV Netstream 4a
    • EyeTV Go
    • EyeTV Hybrid
    • EyeTV Diversity
    • EyeTV T2 Hybrid
    • EyeTV T2 Lite
  • EPG Subscriptions
    • EyeTV User Conference (Jitsi) EPG Meeting
    • EPG – TV Guide
    • EPG – Gracenote
    • North America Products (discontinued)
  • North America Products
    • EyeTV Netstream 4a
    • EyeTV Hybrid A (ATSC (OTA) – ATSC Clear QAM)
    • EyeTV U6
  • EyeTV Legacy Products
    • EyeTV DTT
    • EyeTV Netstream Sat / DTT
    • EyeTV Netstream Sat / DTT
  • EyeTV Off Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 9 results

  1. I just purchased an EyeTV Hybrid last week with the understanding that the new software EyeTV 3 now supported HD signals from the Hybrid. However, when I do an exhaustive scan I only find SD DVB-T channels. Is there some special setting required to get the HD channels?
  2. In March 2017 Germany has started to rollout DVB-T2 with h265 codec and DVB-T1 is not longer supported. Devices with DVB-T2 and h264 codec are not working in Germany. Is there any plan to get this h265 codec supported in the nearest future on EyeTV W device? Thanks for your response.
  3. Hi, I have an EyeTV T2 tuner capable of receiving DVB-T2 (Freeview HD) channels in the UK. It is currently connected to a late 2013 iMac. Watching HD channels with EyeTV 3 works fine. Also, if I record a program from one of these channels, the recording plays fine in the EyeTV software, on both the 2013 iMac with NVIDIA GeForce GT 750M graphics card, and on my relatively low powered 2009 MacBook. However, when I export one of these recordings, without re-encoding it, to an .mp4 file, the resulting file does not play very well on either Mac using Quicktime or VLC. The video frame rate is very choppy and the sound stutters. Also, skipping through the exported video is impossible and the video just turns to a grey screen. I have tried to play the exported mp4 files on multiple devices aside from the two Macs including a Samsung Smart TV, a PS3 and a Blu-Ray player and they all have the same problem. I was wondering why the recordings play fine in EyeTV but not when exported? The actual contents of the file, the video codec etc. should not change. Inspecting the exported .mp4 files show that they are 1080p H.264 encoded files with a Mbps of around 4 and with AAC encoded audio. I am sure these files are not too high a bit rate for my equipment to handle. Strangely, if I go to the .eyetv file of the recording and right-click>Show Package Contents, there is a .mpg file inside containing the recording that opens and plays fine in VLC. I was wondering what happens during the export process to inhibit the resulting .mp4 files from playing well? Do these recordings have some kind of digital rights management on them? Another thing I thought it could be is that the exported .mp4 files are somehow lacking a "header"? I remember this used to be a problem with the old .avi container format in that even relatively low bitrate files that should play fine would stutter and play badly if the header was absent. I'd be grateful if anyone could advise me on what I need to do with these files to allow them to play properly, ideally without re-encoding the video as I do not want to lose quality. Many thanks for your help
  4. In March 2017 Germany has started to rollout DVB-T2 with h265 codec and DVB-T1 is not longer supported. Devices with DVB-T2 and h264 codec are not working in Germany. Is there any plan to get this h265 codec supported in the nearest future on EyeTV W device? Thanks for your response.
  5. Guten Tag, hab heute schon update 3.6.9 (7517) gemacht, aber mein Hybrid findet keine DVB-T2 Sender. Ort: Berlin, Info zur hardware: Ist wohl kein Hybrid mehr, sondern nur noch Kabel-Adapter? Danke und Gruß Ulrich
  6. Hi, some days ago most regions in Germany switched to DVB-T2 (H.265 HEVC). EyeTV does support the nice HDHomerun Network Tuner: https://www.silicondust.com/product/hdhomerun-connect/ With firmware 20161117 this tuner is able to receive DVB-T2 broadcasts. Unfortunately there is a bug in EyeTV 3.6.9 (7416): EyeTV is able to find the channels, but lists them as "audio only" Is there a new (beta?) version which fixes this problem?
  7. What is the difference between T2 lite und T2 Hybrid?
  8. Just recently my trustworthy EyeTV Tivizen stopped working. Not because the hardware broke, but because Austria switched from DVB-T to DVB-T2 h.264 with basic encryption. A decryption module (CI+ slot) is available for small price from www.simplitv.at - but which device working with EyeTV has such a slot?
  9. My recently purchased Eye-Tv Hybrid DVB-T/T2 tuner is not able to correctly process any of the DK DVB-T MUX2 channels. The picture frames freezes, no picture are shown only audio. MUX1 channels are shown correctly. Also DVB-T2 encoded (Boxer payTV) channels (H.264) works very well with EyeTv Hybrid. MUX2 works well on the EyeTv Diversity tuner. Could this be solved via a firmware update? MUX1og2_2016.pdf