oliver whittington wrote:
> Mark Clarkstone wrote:
>
> > The PlayTV is a dibcom device which has pid filtering & can only receive SD services which means smaller bandwidth, the DVB-T2 sticks all require much larger bandwidth.
> >
> > When I tried my Dibcoms (Hauppauge NOVA-T/TD) they worked fine with a VM, my PCTV T2 290e did not & I suffered with CC errors like you're getting now again this is because of the larger bandwidth use.
> >
> > If you can't stream the complete mux (see the mux tab in Tvheadend for a play link & stream two muxes) from both your PlayTV tuners at the same time (if you use VLC you should see the list of programmes under Playback -> Programmes) then I doubt you'll ever be able to receive one DVB-T2 mux.
> >
> > Also have you actually tried these sticks outside a VM? Do they work fine?
>
> I understand what your saying about the playtv... Not overly sure what PID filtering is but i'll have to read up. The way i see it is an SD stream is going tobe the same size regardless of the tuner being DVB-T or DVB-T2 tuner therefore the channels that worked on the PlayTV should work on the Geniatech T230, network dosnt seem to be an issue as everything from server to client is hardwired on 1gb ethernet ports. HD channels dont show any more or less continuity errors than SD broadcasts. If anything, when playing SD broadcasts, it's the playTV that has the potential to cause more bottleneck issues due to it being a dual-tuner and capable of two SD streams at the same time (increased bandwidth)- I never had a problem running 2 x SD streams on my playtv VM.
Not always, some tuners will use the full bandwidth regardless of the size of the mux.
If you can stream the complete mux then view the status -> stream tab you should see something like this.
!stream.png!
Notice how it's a perfect line, if yours is waving about then it's data starved. Be sure you're streaming the complete mux though & not just a single channel else it will fluctuate due to variable bitrates.
>
> My working Openelec system which i'd love to be able to create as a VM is not virtualised. It's simply an NUC running openelec with the T230 stuck in the front on a USB2.0 port. Works flawlessly.
>
> @JanSage - Thanks for confirming the firmware versions (my versions are idential) and the pass thru stuff. If you get a chance can you let me know what sort of signal strength your getting under status in TVH when running a channel to a client? Did you have to tinker with your profiles to force pass thru? I'd have expected to have seen a reference to pass-thru when a clint loads a channel in the logs? as whenever i look at the chevron log in TVH when a channel is loaded the log always references an HTSP:\\ connection. I'm assuming this is the normal transport protocol method for TVH regardless of selected profile?? (passthru, htsp)
>
> In regards to my previous post about virtualising my current openelec system, it seems it could be a tough call... openelec havn't supported their virtual image for some time so nothing is available from them. There downloads are .IMG format and ESX will only attach .ISO files during creation and P2V fails as the linux distro openelec is based on is quite custom built and dosn't mount /boot for the conversion to happen.
>
> I've got 4 of these damn T230 sticks! ... I've gotta make it work some how! :)