[mythtv-users] MuMuDVB and MythTV

[Mark]

>> -----Original Message-----
>> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
>> Of Charles Bovy
>> Sent: Wednesday, 11 November 2015 5:37 AM
>> To: Discussion about MythTV
>> Subject: Re: [mythtv-users] MuMuDVB and MythTV
>> 
>> 	Hi all,
>> 
>> 	I'm using mythtv-0.27.5 to record from TS streams over HTTP.
>> 	I'm not sure if your data are also TS stream over HTTP?
>> 	I've patched my 0.27-fixes with a few patches from ticket #12168
>> (which are all applied in master).
>> 	Those patches are now in devel/027-candidates. Maybe worth a try
>> to check with that branch?
>> 
>> 	Regards, Charles
>> 
>> 	_______________________________________________
> 
> -----Original Message-----
> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
> Of Mark Perkins
> Sent: Wednesday, 11 November 2015 6:55 AM
> To: Discussion about MythTV
> Subject: Re: [mythtv-users] MuMuDVB and MythTV
> 
> My tests were all with udp or rtp ts streams on Master/0.28. There is a note
> on the Mumudvb page that http didn't work with MythTV so I never thought
> twice and didn't try. But the note could be years old, I'll give it a try - thanks!

Ok yes switching to http unicast mode worked for me (more or less, further info to follow in new thread). Using master/0.28 with a pull from a couple of days ago.

Snippet of a MuMuDVB config file:
$ cat card0.conf
freq=177500
modulation=QAM64
delivery_system=DVBT
card=0
tuner=0
tuning_timeout=30
timeout_no_diff=60
check_status=1

bandwidth=7MHz
trans_mode=8k
guardinterval=1/16

rewrite_pat=1
rewrite_sdt=1
rewrite_eit=1
sort_eit=1
rtp_header=0
dvr_thread=1
dvr_thread_buffer_size=5000
sap=1
multicast=0
multicast_ipv4=0
multicast_ipv6=0
unicast=1
ip_http=192.168.1.101

new_channel
#ip=192.168.1.101
unicast_port=4071
name=78 - RACING.COM
pids=1408 1409 1410
service_id=1368

new_channel
#ip=192.168.1.101
unicast_port=4072
name=7 - 7 Digital
pids=1280 1281 1282 1284
service_id=1360

new_channel
#ip=192.168.1.101
unicast_port=4073
name=71 - 7 Digital 1
pids=1296 1281 1282 1284
service_id=1361

new_channel
#ip=192.168.1.101
unicast_port=4074
name=72 - 7TWO
pids=1312 1313 1314 1316
service_id=1362

new_channel
#ip=192.168.1.101
unicast_port=4075
name=73 - 7mate
pids=1328 1329 1331 1333
service_id=1363

new_channel
#ip=192.168.1.101
unicast_port=4076
name=70 - 7 Digital
pids=1344 1281 1282 1284
service_id=1364

new_channel
#ip=192.168.1.101
unicast_port=4077
name=74 - TV4ME
pids=1392 1393 1394
service_id=1367


And snippet from playlist file:
$ cat playlist.m3u
#EXTM3U
#EXTINF:0,78 - RACING.COM
http://192.168.1.101:4071
#EXTINF:0,7 - 7 Digital
http://192.168.1.101:4072
#EXTINF:0,71 - 7 Digital 1
http://192.168.1.101:4073
#EXTINF:0,72 - 7TWO
http://192.168.1.101:4074
#EXTINF:0,73 - 7mate
http://192.168.1.101:4075
#EXTINF:0,70 - 7 Digital
http://192.168.1.101:4076
#EXTINF:0,74 - TV4ME
http://192.168.1.101:4077

> -----Original Message-----
> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
> Of Hika van den Hoven
> Sent: Tuesday, 10 November 2015 9:05 AM
> To: Discussion about MythTV
> Subject: Re: [mythtv-users] MuMuDVB and MythTV
> 
> Hoi Mark,
> 
> 
> If I look at the IPTV recorder examples on the wiki, the m3u file
> looks something like:
> 
> #EXTM3U
> #EXTINF:0,300 - NASA TV
> #EXTMYTHTV:xmltvid=hls.nasatv
> http://public.infozen.cshls.lldns.net/infozen/public/public.m3u8
> #EXTINF:0,304 - BBC News
> #EXTMYTHTV:xmltvid=hls.bbcnews
> http://akamedia2.lsops.net/live/bbcworld1_en.smil/playlist.m3u8
> 
> So they point all to a m3u8 file and have an xmltvid added.
> 
> 
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com

I omitted (rightly or wrongly) the #EXTMYTHTV:xmltv lines because I am concurrently testing using the Shepherd xmltv programme guide which has functionality to auto populate the xmltv id's as part of the setup process.