Jump to content

Channel sources/tuners


garyan2

Recommended Posts

garyan2

I made an interesting discovery today. A little background...

 

I just found out one of my local broadcast stations added a new station Bounce (channel 9.4). Since Schedules Direct does not yet have guide information for Bounce in my lineup, I added a lineup from a neighboring city which does have Bounce (channel 33.4). I then assigned that station listing to my local channel to complete the guide.

 

The problem occurs when I try to have emby tune to Bounce on 9.4, it tries to tune 33.4 and I get an invalid stream error. The only place it can get this information is from the channel information in the WMC database which really has nothing to do with the actual tuners. How does serverWMC handle multiple devices with multiple channels for the same station? Does in not pay attention to the devices (sources) assigned to a station and only uses the channel information?

Link to comment
Share on other sites

krustyreturns

Hi Gary,

 

Not sure I understand but... If in wmc you added the station/device for this to its setup (and assuming it works in wmc), then the info is in wmc's database for this device.  In wmc, look at 'edit sources' for the channel in question and make sure that the only sources for this channel are the device you want.  

 

PS, I became a epg123 user a few months ago.  Great program!

Link to comment
Share on other sites

garyan2

Hi Gary,

 

Not sure I understand but... If in wmc you added the station/device for this to its setup (and assuming it works in wmc), then the info is in wmc's database for this device.  In wmc, look at 'edit sources' for the channel in question and make sure that the only sources for this channel are the device you want.  

 

Yah, I know I probably did a poor job in describing the problem, but here goes ...

 

In WMC, I manually added the new channel to be logical 9.4 and physical 9 which is what it is. It is tunable and viewable.

 

5a92f1b1bc301_WMC94.png

 

 

The listings I attached to it are from another city which is logical channel 33.4. What was surprising was when I tried to tune to this new channel in emby, it was failing because it was trying to tune to 33.4.

C:\Users\Administrator\AppData\Roaming\Emby-Server\system\ffmpeg.exe -analyzeduration 3000000 -fflags +igndts -i "http://192.168.1.155:5004/auto/v33.4" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 libx264 -pix_fmt yuv420p -preset veryfast -crf 23 -maxrate 139808000 -bufsize 279616000 -profile:v high -level 4.1 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames "expr:gte(t,n_forced*3)" -vf "yadif=0:-1:0" -flags -global_header -vsync -1 -codec:a:0 libmp3lame -ac 2 -ab 192000 -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3 -individual_header_trailer 0 -segment_format mpegts -segment_list_entry_prefix "hls/da220c3a311ed009220c89f70c88a705/" -segment_list_type m3u8 -segment_start_number 0 -segment_list "D:\Emby-Server\transcoding-temp\da220c3a311ed009220c89f70c88a705.m3u8" -y "D:\Emby-Server\transcoding-temp\da220c3a311ed009220c89f70c88a705%d.ts"
...
http://192.168.1.155:5004/auto/v33.4: Server returned 404 Not Found

The only place it could have gotten that information was from the WMC database for the channel which I add in the .MXF file.

    <Lineups>
      <Lineup id="l1" uid="!MCLineup!USA-OTA-85342" name="EPG123 Local Over the Air Broadcast (85342)" primaryProvider="!MCLineup!MainLineup">
        <channels>
          <Channel uid="!Channel!USA-OTA-85342!96786_33_4" lineup="l1" service="s1" number="33" subNumber="4" />
        </channels>
      </Lineup>
      <Lineup id="l2" uid="!MCLineup!USA-OTA-85747" name="EPG123 Local Over the Air Broadcast (85747)">
        <channels>
          <Channel uid="!Channel!USA-OTA-85747!42676_4_1" lineup="l2" service="s2" number="4" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!81351_4_2" lineup="l2" service="s3" number="4" subNumber="2" />
          <Channel uid="!Channel!USA-OTA-85747!100105_4_3" lineup="l2" service="s4" number="4" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!35688_6_1" lineup="l2" service="s5" number="6" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!36183_6_2" lineup="l2" service="s6" number="6" subNumber="2" />
          <Channel uid="!Channel!USA-OTA-85747!36187_6_3" lineup="l2" service="s7" number="6" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!36184_9_1" lineup="l2" service="s8" number="9" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!63024_9_2" lineup="l2" service="s9" number="9" subNumber="2" />
          <Channel uid="!Channel!USA-OTA-85747!64906_9_3" lineup="l2" service="s10" number="9" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!33914_11_1" lineup="l2" service="s11" number="11" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!66662_11_2" lineup="l2" service="s12" number="11" subNumber="2" />
          <Channel uid="!Channel!USA-OTA-85747!91574_11_3" lineup="l2" service="s13" number="11" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!106966_11_4" lineup="l2" service="s14" number="11" subNumber="4" />
          <Channel uid="!Channel!USA-OTA-85747!32484_13_1" lineup="l2" service="s15" number="13" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!54806_13_2" lineup="l2" service="s16" number="13" subNumber="2" />
          <Channel uid="!Channel!USA-OTA-85747!46789_13_3" lineup="l2" service="s17" number="13" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!106045_14_4" lineup="l2" service="s18" number="14" subNumber="4" />
          <Channel uid="!Channel!USA-OTA-85747!33917_18_1" lineup="l2" service="s19" number="18" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!99600_18_3" lineup="l2" service="s20" number="18" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!76896_40_3" lineup="l2" service="s21" number="40" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!87135_46_3" lineup="l2" service="s22" number="46" subNumber="3" />
          <Channel uid="!Channel!USA-OTA-85747!34926_58_1" lineup="l2" service="s23" number="58" subNumber="1" />
          <Channel uid="!Channel!USA-OTA-85747!95698_58_3" lineup="l2" service="s24" number="58" subNumber="3" />
        </channels>
      </Lineup>
    </Lineups>

What is very interesting is when I tried to recreate just now, emby is now tuning to the proper channel. So now I'm a bit confused on what happened and how it corrected itself. :huh:

C:\Users\Administrator\AppData\Roaming\Emby-Server\system\ffmpeg.exe -analyzeduration 3000000 -fflags +igndts -f mpegts -i "http://192.168.1.155:5004/auto/v9.4" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 libx264 -pix_fmt yuv420p -preset veryfast -crf 23 -maxrate 5000000 -bufsize 10000000 -profile:v high -level 4.1 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames "expr:gte(t,n_forced*3)" -vf "yadif=0:-1:0,scale=trunc(min(max(iw\,ih*dar)\,1920)/2)*2:trunc(ow/dar/2)*2" -flags -global_header -vsync cfr -codec:a:0 libmp3lame -ac 2 -ab 192000  -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3  -individual_header_trailer 0 -segment_format mpegts -segment_list_entry_prefix "hls/c478e4fc927e748785f1a4e0207f1cee/" -segment_list_type m3u8 -segment_start_number 0 -segment_list "D:\Emby-Server\transcoding-temp\c478e4fc927e748785f1a4e0207f1cee.m3u8" -y "D:\Emby-Server\transcoding-temp\c478e4fc927e748785f1a4e0207f1cee%d.ts"

PS, I became a epg123 user a few months ago.  Great program!

Thanks! What took you so long?

  • Like 1
Link to comment
Share on other sites

krustyreturns

Ah, I see.  I assume what is different today is emby updated with the new channel info. I have never been clear on when this actually happens.

 

What took me so long? laziness.  What got me to do it? my family complaining.

Link to comment
Share on other sites

garyan2

I was just really surprised emby even knew about 33.4. I would have thought that would be behind-the-scenes/transparent.

 

Thanks for the look and the feedback.

Link to comment
Share on other sites

  • 2 weeks later...
garyan2

I'm going to revive this thread. Emby is once again trying to tune 33.4 when it should be 9.4. I guess we'll see what it looks like tomorrow but I would really like to know why emby even thinks 33.4 exists. ??

 

From the log...

2018/03/05 20:33:03.481 OpenLiveStream> -----------------start------------------------
2018/03/05 20:33:03.481 OpenLiveStream> transcode profile will be set to: none
2018/03/05 20:33:03.481 OpenLiveStream> client: Emby^THEBLACKBOX requesting live stream on channel KTVWDT4/9.4
2018/03/05 20:33:03.491 LiveDlnaStream> live-tv dlna started
2018/03/05 20:33:03.541 LiveDlnaStream> DLNA device: 192.168.1.155 / 10414B48, has a tuner available, stopping search
2018/03/05 20:33:03.541 LiveDlnaStream> DLNA address set: http://192.168.1.155:5004/auto/v33.4
2018/03/05 20:33:03.541 LiveDlnaStream> total time: 0.05 sec
2018/03/05 20:33:03.551 OpenLiveStream> stream path returned to client: http://192.168.1.155:5004/auto/v33.4
2018/03/05 20:33:03.551 OpenLiveStream> -----------------done-------------------------
Edited by garyan2
Link to comment
Share on other sites

krustyreturns

Sorry, I didn't notice that you were running in dlna mode previously.  This was an issue for another emby/dlna user some time ago and I can't recall what we found the cause to be, so instead I just punted and added a workaround.  In serverwmc settings look for RemapChannelNumberDLNA and set it to:

 

<RemapChannelNumberDLNA>33.4--9.4</RemapChannelNumberDLNA>

 

then save settings and restart serverwmc.

Edited by krustyreturns
Link to comment
Share on other sites

garyan2

I was just about to post that there was no change. Will do with the remap ... Thanks.

 

So what happens if say I have cable and OTA and have merged them together. When it looks for a free tuner, what channel does it try?

Link to comment
Share on other sites

krustyreturns

Glad it worked, sorry about the double dashes, not sure what I was thinking there.  

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...