@Kévin Chalet Tested briefly your program. It does quickly exactly what's supposed to do, and that's amazing It's perfect for the average WMC user, which traditionally understand almost nothing about what's under the hood. But for a bit more complex scenario it can be problematic. It writes the HdhrProxy file in the current directory, which is unharmful, but also overwrites the WMC configuration W/O asking any confirmation, which potentially means it destroys hours of days of work/refinement. So, for sure would be very welcome a prompt after the .ini is generated, but before the WMC setting is injected. Also would be nice to have an option to feed it (alternatively) with an already made .ini, instead of just the TVH address. That would be very handy if you have an already working .ini, or if you had to fix/mod something in the ini generated from a previous run A way could be, just look in the current directory. If no ini is present ask for TVheadend address (then ask if you want to inject the data in WMC) If the .ini is already there, ask if you want to use it or if you want to generate a new one, then proceed like above.
Ok, first real channel HEVC ever for my country. Finally the first in clear transmissions are starting to be aired. Obviously you imagine what happens cooperating with @Kévin Chalet.... You get the Tour de France This is obviously not transcoded, to show the stream info, now let see how it works in WMC
Hahaha, I love it Interestingly, it's not a 4K channel, which matches what we see in many other countries (even in the US with ATSC 3.0). Do you know whether HEVC+4K channels are planned in Italy?
To say the best it's complicate. In theory they told for months that everything was supposed to switch to DVB-T2 and HEVC in January, it's July and we have one "experimental" channel in HEVC, everything else was just moved to H264 (and there are still few minor/local MPEG2 channels that survived). Perhaps I think everything is still in DVB-T1 (I have no idea how to check the difference and if does it matter for quality or whatever else) Then we have already few channels in HBBTV, that standard that I never heard before, that you tune from the air but you actually receive from the net. I tried it, I have enough bandwith but no 4K screen and no HW capable of managing it w/o dropping frames and with reasonable CPU usage. So back to your question I think that 4K on DVB-T will come after the scenario will stabilize further, and all the current channels will be migrated to to h265 leaving room to 4K channels.
HI, I'm a new user, I would like to try the acer-5100 configuration but if possible on the same pc... Thank you
Thanks for the reply, what i'm looking for is to reuse wmc again for tv, since in italy we are switching to dvb-t2 i had stopped with wmc and switched to jriver but "first love is never forgotten". I have a pc that I use exclusively as an htpc, a hauppauge dual card... Is it possible to configure windows mc on the same pc? If the answer is yes, I need your help because I've never used linux and I don't know where to start... Thank you
First read my previous messages here in this thread. We aren't moving yet, basically the whole thing, for now, proved to be a giant lie aimed more to help to sell new TVs than anything else. As today practically any HD device sold after 2012 or so is capable of managing all current TV channels, except the test channel 200 and the experimental RAI sport HD on channel 558. So, currently, WMC is perfectly usable AS is and likely will be a viable option for the foreseeable future so no need to hurry Back to your question using WMC + TVHeadend on the same machine is possible. To be more precise is possible in a number of ways. The tricky part is to decide which is the best one, and I experimented a lot until I narrowed what IMO is the best one. I'm going to summarize advantages and disadvantages below: #1 Linux machine running a Windows VM. It works but I don't suggest running a virtualized WMC for picture quality reasons (usually you loose at least the deinterlaced video. I think this is mostly a VMware VGA limit, not a Linux problem itself, anything other than VMware usually is even worse, unless you use the PCI passtrough, which introduces another share of practical troubles. #2 Use a windows physical machine, and run a linux VM running TVheadend. The tuner will be connected to the VM using the native functionality of VMware or Virtualbox. Likely the easiest option setup, but it's a no go because the huge traffic the USB tuner generates, which usually hangs after a while. #3 Use a windows physical machine, and run a linux VM running TVheadend using Hyper-V. Same as #2 with the added complication that Hyper-V requires a costly USB to IP redirector (that hangs anyway), with the addition that setting UP a Linux VM inside Hyper-V is more complicate than doing the same in VMware or VBOX #4 Use a windows physical machine and run TVheadend inside WSL2. In short it's a nightmare. Looks like I'm the only one in the world that was stubborn enough to fully setup the thing, that at the end shares the same problem as options #2 #3. I learned a lot doing that, but for the specific use it was basically wasted time. #5 Use a windows physical machine and run TVheadend inside WSL1, relatively easy to setup, but the Linux inside WSL1 has no access to the tuner. So you need to feed it with an IP TV stream. Hence you need a Windows program that manages the tuning. NextPVR is what I use. It's robust, it's currently supported easy to setup and free for personal use. In short what proved to be the best solution works this way Tuner---->nextPVR---->tvheadend---->HDHrproxy---->HDHomerundrivers----->WMC Seem more complicate than actually is (but for sure isn't deadly simple). Perhaps the nice tool that @Kévin Chalet shared few messages ago simplified greatly the generation tuning process for people who start from scratch. My original solution using DVBlink instead of HDHrproxy+HDHR drivers, is still easier to setup for newbies, but kévin's variation is worth the added complications for a number of reasons. So, in short, start installing WMC as is (so you can start using it in minutes), start installing Ubuntu 16.04 or 18.05 inside WSL1, so you can start practicing with it, then you'll have all the time needed to setup TVH and the other bits, and you can ask more precise questions about the problems you eventually face. P.S. I must add that considerations about the possible ways are intended valid for USB tuners. Likely using PCI/PCIe ones leads to a very different scenario, given the PCI pass-trough possibilities included in many virtualization SW. Obviously a network tuner like a real HDhomerun device will be the easiest option but involves a different amount of money