Some series/episode data formats not recognised within description

[sub]

That's what tscapture produced, and I definitely had the "whole mux, not single channel" option selected... I'll try again and see if I get the same.

What capture device are you using?

[sjabaker]

Well - I treble checked it was recording "full transport stream", and ran until the 60-sec unlicensed evaluation limit was reached ... same result, file sizes in the 7-13MB range.
I also tried with the "single channel" only option selected, as a test - and got sizes broadly similar (15 vs 7, 7 vs 9, and 7 vs 13), so it seems that tscapture is failing to read the whole mux.

I also used the "dump transport stream" function in EPG Collector to collect separate 60-sec streams, and it explicitly warned that "No PID's have been entered so the complete transport stream will be dumped" ... they come out a bit bigger but not that much (~15, 22 & 42MB).
Link to the shared folder this time, with all the files in, just in case they're useful: https://1drv.ms/u/s!AtsVBvATpsLhgYmKS1Rb...c?e=YsaEof - the EPG Collector dumps are '482 MHz.ts', '506 MHz.ts' & '746 MHz.ts'.

That doesn't appear to be limited to just 60 secs of collection, so I could do longer dumps from there if duration can compensate for the seeming inability for the full mux stream to be obtained?
Alternatively, if you can work from just a full textual representation I can share an xmltv file created from the same DVB source (from EPG Collector, with as much "manipulation" as possible turned off, and certainly nothing that changes the description fields)?

Otherwise, I'm not sure!?
Do I need to fiddle with settings for the tuners in the HDHomeRun Software for Windows, perhaps? I vaguely remember some obscure reference relating to modifying the Windows registry to enable something to do with HDHomeRun tuners in the EPG Collector user guide - I'll dig that out and see if it looks relevant.

Sorry this is turning into a bit of a pain!,
Steve

[sjabaker]

That's what tscapture produced, and I definitely had the "whole mux, not single channel" option selected... I'll try again and see if I get the same.

What capture device are you using?

Sorry - just saw this as I posted my reply... as implied in what I wrote, I'm using HD HomeRun devices, specifically the 'Quattro' DVB-T/T2 quad-tuners.

[sub]

Do I need to fiddle with settings for the tuners in the HDHomeRun Software for Windows

Try going into the HDHomeRun Setup utility, and check the BDA Compatibility Mode. Maybe set it to MediaPortal to see if it makes a difference.

A 1 minute full transport should be something like 250MB.

[mvallevand]

Make sure the HDHR Windows software is current and you are using the NextPVR BDA driver setting. If the software is old don't use NextPVR use Default or MediaPortal.

Martin

[sjabaker]

I dug up that reference I half-remembered, and it *does* look like it's the HDHR's that're the issue - it says that by default they filter the stream and while it doesn't stop the entire EPG being read it does prevent the entire mux stream being dumped. (It's apparently also supposed to prevent the 'Find EPG' function in that app, which I ran seemingly successfully anyway, hence why it was only a fuzzy recollection.)

Apparently I need to edit these two registry keys (where 'xxxxxxxx' is the HDHomeRun ID #):
[HKEY_LOCAL_MACHINE\SOFTWARE\Silicondust\HDHomeRun\Tuners\xxxxxxxx-0]
"BDAPIDFilter"="Disabled"
[HKEY_LOCAL_MACHINE\SOFTWARE\Silicondust\HDHomeRun\Tuners\xxxxxxxx-1]
"BDAPIDFilter"="Disabled"
...and then set them back to 'Enabled' afterwards.

I'll give that a try and then let you know (if probably needs a logout/reboot, in which case it may take a little time to find a convenient moment...)

[mvallevand]

No you don't want PID filtering.

Martin

[sjabaker]

OK, success I think... changing the registry entry didn't work by itself, but also changing the BDA compatibility to 'NextPVR' gave me sensibly-sized dump files (c. 180-250MB each) - now available in the same shared folder as "482 MHz full mux.ts", "506 MHz full mux.ts" & "746 MHz full mux.ts".

Thanks,
Steve

PS: for reference in case this thread is useful for anyone else in future, the manual registry change noted above doesn't seem to be required - just changing the BDA compatibility mode via the HDHomeRun Setup software is enough. (It may well do essentially the same thing in the background, but it avoids having to muck around in the registry.)

[mvallevand]

That's better, yes there are lots in there without brackets or with a / instead of a space.

Martin

[sjabaker]

Just checking - was that enough to replicate the issue, or is it still a case of "working on your machine but not mine" (per sub's initial response)?