[confirm] Anysee 30 Plus channel slow zapping (not MDAPI RELATED) (1 Viewer)

blackEyEz

Portal Pro
July 8, 2009
170
44
Netherlands
Home Country
Netherlands Netherlands
Hello, I have an Anysee E30TC Plus and the only way for us to make it work with MediaPortal is to use MDAPI and Splug.dll . I know its been stated many times that MP wont support MDAPI but this bug is not related to it. I have heard it seem to work fine in MP 1.0.2 and after 1.1 RC1 some users experienced slow zapping on non FTA SD channels (+15secs). Which makes this device unusable for us.

I made a log after zapping through these channels and this piece of log was asked for me to post and it shows allot of errors.

Code:
17-04-2010 17:25:13.222 [1bb0]New channel found (PAT/PMT/SDT changed)
17-04-2010 17:25:13.223 [1bb0] pcr      pid:   30 
17-04-2010 17:25:13.223 [1bb0] pmt      pid:   20 
17-04-2010 17:25:13.223 [1bb0] video    pid:   30 type: MPEG2
17-04-2010 17:25:13.224 [1bb0] audio    pid:   40 language: dut type: MPEG1 - audio
17-04-2010 17:25:13.224 [1bb0]Setting initial audio index to : 0
17-04-2010 17:25:13.225 [1bb0]DeMultiplexer: We detected a new media type change which has a video stream, so we let the mpegParser trigger the event
17-04-2010 17:25:13.225 [1bb0]demux:Wait for media format change:1
17-04-2010 17:25:13.225 [1bb0]OnRequestAudioChange()
17-04-2010 17:25:13.225 [1bb0]demux:Wait for Audio stream selection :1
17-04-2010 17:25:13.227 [1bb0]New Audio 4
17-04-2010 17:25:13.228 [1438]CTsReaderFilter::--SeekStart()-- No new seek 27.266000 ( Abs 27.266000 / 27.266417 ) - Stream compensated: 0, OnZap: 0, Force 0, Media changing: 1
17-04-2010 17:25:13.229 [1438]CTsReaderFilter::--SeekStart()-- No new seek 27.266000 ( Abs 27.266000 / 27.266417 ) - Stream compensated: 0, OnZap: 0, Force 0, Media changing: 1
17-04-2010 17:25:13.229 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:13.230 [1438]CTsReaderFilter::Run(2440.85) state 1 seeking 0
17-04-2010 17:25:13.228 [1bb4]vid:OnThreadStartPlay(27.266000) 1.00 0
done
17-04-2010 17:25:13.266 [1438]SetAudioStream : 0
17-04-2010 17:25:13.266 [1438]Old Audio 4, New Audio 3
17-04-2010 17:25:13.266 [1438]SetAudioStream : Media already changing
17-04-2010 17:25:13.266 [1438]demux:Wait for Audio stream selection :0
17-04-2010 17:25:13.273 [1bb0]Pes 0-0-1 fail
<Removed a BIG piece of repeating failures>
17-04-2010 17:25:15.652 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:15.797 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:15.836 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:15.937 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:16.024 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:16.626 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:16.648 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:16.814 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:16.850 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:17.014 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:17.090 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:17.311 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:17.459 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:17.484 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:17.609 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:17.717 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:17.751 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:17.989 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:18.266 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:18.298 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:18.450 [1bb0]demux: Alert: Wait for Media change cancelled on 5 secs timeout
17-04-2010 17:25:18.540 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:18.541 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:18.733 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:18.832 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:19.140 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:19.337 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:19.445 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:19.574 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:19.725 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:19.819 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:20.038 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:20.370 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:20.634 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:20.797 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:20.834 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:20.978 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:21.091 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:21.308 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:23.277 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:23.405 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:23.608 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:23.818 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:23.953 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:24.243 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:24.630 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:24.676 [1bb0]Pes 0-0-1 fail
17-04-2010 17:25:31.292 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:31.794 [1bb0]Pes header 0-0-1 fail
17-04-2010 17:25:31.862 [1bb0]  MPEG I-FRAME found 29.938000 
17-04-2010 17:25:31.863 [1bb0]DeMultiplexer: 30 video format changed: res=720x576 aspectRatio=16:9 fps=25 isInterlaced=1
17-04-2010 17:25:31.863 [1bb0]DeMultiplexer: OnMediaFormatChange triggered by mpeg2Parser
17-04-2010 17:25:31.863 [1bb0]demux:Wait for media format change:1
17-04-2010 17:25:31.863 [1bb0]DeMultiplexer: triggering OnVideoFormatChanged
17-04-2010 17:25:31.874 [1bb0]  MPEG First '0' frame found. 29.858000

Please can a dev help me, i asked many other forums. I mailed support of anysee. And heard nothing.

:D:D

edit: here a bugreport of a similar problem: https://forum.team-mediaportal.com/...ing-between-2-channels-takes-long-time-78815/
 

te3hpurp

Retired Team Member
  • Premium Supporter
  • September 23, 2008
    910
    231
    Rovaniemi
    Home Country
    Finland Finland
    Hi.
    Line:

    17-04-2010 17:25:18.832 [1bb0]Pes header 0-0-1 fail

    Almost always is related to decryption problem.

    Remember and honor the forum rules about MDAPI discussion !

    Br,
     

    Mithrandir

    Portal Pro
    March 21, 2008
    53
    2
    Home Country
    Netherlands Netherlands
    I have the same issue (And yes also the same card).
    The user in the linked topic has a FloppyDTV and doesnt use MDAPI either.

    We didn't have this issue in any previous MP version ourselves.(We being me and many other Dutch viewers as the anysee is our only option since Digital eveywhere's demise). If your saying this is not a bug but related to MDAPI then i still don't understand why only a handful of channels show this issue. Decryption works the same on any channel so why only have the issue on a few.

    Probably blackeyez can confirm this issue is on a specific set of dutch channels. Other SD channels are fine.

    Edit: Just checked the logs some more but the delay takes place in the client not the server it seems.
    On server side time shift starts at 17:26:17.19(Which would be after decryption i would think?), on the client side video starts at 17:26:31.419.
     

    blackEyEz

    Portal Pro
    July 8, 2009
    170
    44
    Netherlands
    Home Country
    Netherlands Netherlands
    If there was a way MDAPI wouldnt be needed, i would be happy too. A SDK has been released and can be downloaded at: ::: anysee :::

    Could this issue be fixed by using this SDK and we can throw away MDAPI?
     

    fmulders

    MP Donator
  • Premium Supporter
  • June 3, 2009
    99
    14
    50
    Home Country
    Netherlands Netherlands
    Same problem here!

    Only with 1.1.0 RC2 Clean install on virgin W7 system. Please look at this issue MP team :(
    By saying "No" to this issue with the Anysee Tuner, in fact you are excluding a complete country to use MP.
    In the Netherlands we do not have any other solution...

    If extra logs are needed please let me know.
    Right now I am running RC1 again.

    Greatings Frank
     

    blackEyEz

    Portal Pro
    July 8, 2009
    170
    44
    Netherlands
    Home Country
    Netherlands Netherlands
    Yes true, we had one solution called digital everywhere's firedtv but that company got bankrupt so the anysee is our only solution to make it work with mediaportal. I dislike very much that we are labeled hackers by using MDAPI but thats our only solution to receive the dutch channels WE PAY FOR. :(
     

    Paranoid Delusion

    Moderation Manager
  • Premium Supporter
  • June 13, 2005
    13,062
    2,978
    Cheshire
    Home Country
    United Kingdom United Kingdom
    Hi Guys

    Not coming in here heavy handed, I can appreciate some of the problems you are facing, I know there have been a lot of changes to how cams are handled, could this feed back to the api you are using to interface with MP, might be worthwhile exploring within the relevant forum that deals with such things.

    Sorry there is no short answer, but good luck in your endeavours to get this sorted, but the chances are, it will be outside MP's control.
     

    te3hpurp

    Retired Team Member
  • Premium Supporter
  • September 23, 2008
    910
    231
    Rovaniemi
    Home Country
    Finland Finland
    Hi.

    I think some anysee owner with coding experience should try to implement patch
    using SDK so that CI interface could be used with MP. Team does not have manpower
    to do that.

    And of course I dunno if anyone has anysee and proper subscription(which costs)
    to begind development process.

    Regards,
     

    crackdown

    Portal Pro
    November 24, 2009
    100
    26
    Home Country
    Netherlands Netherlands
    I am a professional HTPC builder, and in The Netherlands the Anysee unit is the only possible solution to get it to work with DVB-C. Before the RC1 the anysee tuner worked marvellously in mediaportal. Now after RC2 zapping takes at least 12 seconds v/s 1 second in Windows media center.
    Now my humble opinion is that its too easy to say that the mdapi solution is not supported etc. The Anysee tuner itself worked great before, so why not now?
    I really do not want to advise people to use Microsofts Media Center, but in this case its a no go to use the anysee in Mediaportal. I really hope somebody with coding skills can look into this.
    We were left in the cold before bu digital everywhere, maybe Anysee can find a solution?
     

    tourettes

    Retired Team Member
  • Premium Supporter
  • January 7, 2005
    17,301
    4,800
    Just a quick note. When TsReader.log shows

    Pes header 0-0-1 fail

    it is 99% of problem with the decryption failure (first bytes of PES header aren't 001 like they should). In this case MDAPI is most likely just not able to decode the stream (don't ask me why... I wont bother myself with it).
     

    Users who are viewing this thread

    Top Bottom