DVB-IP Mediaportal IPTV Source Filter doesn't work correctly (1 Viewer)

Status
Not open for further replies.

solvit

MP Donator
  • Premium Supporter
  • January 18, 2006
    15
    2
    Bonn
    Home Country
    Germany Germany
    In MP1 the IPTV-Tuner works smoothly after installing "MediaPortalUrlSourceSplitter2.2.10.5911.mpe1".

    But using the IPTV-Tuner in MP2 no channel is detected correctly and I get the log file error "CMPIPTV_HTTP: parseURL (): unsupported protocol 'udp' ". I suppose that UDP is not well integrated in the DVB-IP tuner of MP2.
    I don't know, perhaps there is a MP2 TV plugin for streaming protocols to solve this problem?
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    Please collect the MP2 logfiles and add them here, otherwise we have no way to check this.
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    Thanks for the logs.

    In the MediaPortal TV Server\MPIPTVSource.log you can see that the UDP protocol handler is available:
    Code:
    13-04-2016 10:58:17.487 [1654] [{A2B4C8BC-CCA4-4DE2-B93A-9E6FEC2551F4}] [Info]  MPIPTVSourceStream: LoadPlugins(): loading configuration file: C:\ProgramData\Team MediaPortal\MediaPortal TV Server\MPIPTVSource.ini, section: UDP
    13-04-2016 10:58:17.487 [1654] [{A2B4C8BC-CCA4-4DE2-B93A-9E6FEC2551F4}] [Info]  MPIPTVSourceStream: LoadPlugins(): protocol 'UDP' successfully instanced, id: {FCDD1B60-0559-41DE-8A1A-F61BDFA1DBC5}

    But then the given url is not (considered to be) valid:
    Code:
    13-04-2016 10:58:17.503 [1654] [{6ACC2F57-0B89-43B8-A71B-12864502B86D}] [Info]  MPIPTVSource: SetConnectInfo(): Start
    13-04-2016 10:58:17.518 [1654] [{6ACC2F57-0B89-43B8-A71B-12864502B86D}] [Info]  MPIPTVSource: SetConnectInfo(): additional data: udp://@0.0.0.0:1234
    13-04-2016 10:58:17.518 [1654] [{6ACC2F57-0B89-43B8-A71B-12864502B86D}] [Info]  MPIPTVSource: SetConnectInfo(): count of parameters: 0
    13-04-2016 10:58:17.518 [1654] [{6ACC2F57-0B89-43B8-A71B-12864502B86D}] [Info]  MPIPTVSource: SetConnectInfo(): End
    13-04-2016 10:58:17.518 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ParseUrl(): Start
    13-04-2016 10:58:17.534 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ClearSession(): Start
    13-04-2016 10:58:17.534 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ClearSession(): End
    13-04-2016 10:58:17.534 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ParseUrl(): url: udp://@0.0.0.0:1234
    13-04-2016 10:58:17.550 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ParseUrl(): unsupported protocol 'udp'
    13-04-2016 10:58:17.550 [1654] [{CD920478-B8FE-4815-ACED-CFE5F2A86507}] [Info]  CMPIPTV_FILE: ParseUrl(): End, Fail

    The "udp://@0.0.0.0:1234" looks strange, where do you get the channels / tuning details from?

    In MP1 the IPTV-Tuner works smoothly after installing "MediaPortalUrlSourceSplitter2.2.10.5911.mpe1".
    @georgius this MP1 package, is it for TvServer or MP1-Client?

    The MP2 TVE version is on same level as MP1.14, I guess the linked mpe1 contains alternative binaries? If so, could we simply copy the files into the existing MP2 folders?
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    I have checked the contents of your linked mpe1 file. The contained filters are copied to TvServer on installation.

    There is one change in MP2: it loads the filters by filename and doesn't require a registration.

    So I made a quick test and placed all .dll into the attached archive.

    @solvit can you:
    1. Stop MP2-Server (i.e. via rightclick on statusmonitor symbol in try)
    2. Take a backup of folder: C:\Program Files (x86)\Team MediaPortal\MP2-Server\Plugins\SlimTv.Service3
    3. Extract contents of archive into this folder, it will replace the MPIPTVSource.ax and add all the required new files
    4. Start MP2-Server
    5. Test DVB-IP
    6. Collect logfiles again and post your results
     

    Attachments

    • EXP_MP2_TVE3_MpUrlSourceSplitter.7z
      3.6 MB

    solvit

    MP Donator
  • Premium Supporter
  • January 18, 2006
    15
    2
    Bonn
    Home Country
    Germany Germany
    I did as you told. But it doesn't work, no channel was created. Attached you find the new log file.

    It seems that the IPTV source stream based on the protocols is created and after creation it is destroyed.
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    Ok, so I first need some more information from @Developers . I hoped the MediaPortalUrlSourceSplitter2 could be interface compatible with MPIPTvSource (because I couldn't see changes in MP1 code for it and installer exchanges registrations on un-/install).

    Are there any other requirements for replacing the filter? Note: because MP2 loads the filter by filename I also renamed the MediaPortalUrlSourceSplitter2 to "MPIPTVSource.ax".
     

    georgius

    Retired Team Member
  • Premium Supporter
  • October 31, 2010
    1,376
    654
    Bratislava
    Home Country
    Slovakia Slovakia
    In MP1 the IPTV-Tuner works smoothly after installing "MediaPortalUrlSourceSplitter2.2.10.5911.mpe1".
    @georgius this MP1 package, is it for TvServer or MP1-Client?
    For both. If installed on MP1 client, it's for OnlineVideos. If installed on TV server, it should replace TV server IPTV filter (if registration of filter succeeded). If TV server and MP client are on same machine, than filter is placed under TV server installation directory, but it is registered as IPTV filter and also as source splitter for OnlineVideos.
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    @georgius, thanks for your answer.

    For the MPIPTvSource there were changes to allow loading filters from the location of the actual .ax file (see here). Can you tell me how the filter load its the other dlls with protocol support? Does this require specific locations (i.e. relative to process executable)? If so, the OP might be able to get the filter working by copy the files into another location?

    Could you consider a change in the new filter like done for MPIPTvSource as well? This would make it more interoperable :)
     

    georgius

    Retired Team Member
  • Premium Supporter
  • October 31, 2010
    1,376
    654
    Bratislava
    Home Country
    Slovakia Slovakia
    @georgius, thanks for your answer.

    For the MPIPTvSource there were changes to allow loading filters from the location of the actual .ax file (see here). Can you tell me how the filter load its the other dlls with protocol support? Does this require specific locations (i.e. relative to process executable)? If so, the OP might be able to get the filter working by copy the files into another location?

    Could you consider a change in the new filter like done for MPIPTvSource as well? This would make it more interoperable :)
    It seems that filter is loading other dlls (protocols, parsers, decryption, ...) similar as MPIPTvSource.
    C++:
    CHECK_CONDITION_HRESULT(result, GetModuleFileName(GetModuleHandle(MODULE_FILE_NAME), pluginPath, MAX_PATH) != 0, result, E_CANNOT_GET_MODULE_FILE_NAME);
    First it gets module handle, then it gets module path, MODULE_FILE_NAME is "MPUrlSourceSplitter.ax". Filter does not need specific location, it only depends on MODULE_FILE_NAME - this can't be changed (in current state). Also search patterns for plugins (protocols, parsers, decryption, ...) are hard-coded, e.g. "mpurlsourcesplitter_protocol_*.dll".
     
    Status
    Not open for further replies.

    Users who are viewing this thread

    Top Bottom