Yes, but I am talking about oscam-emu. Perhaps it stayed at 11391 although it seems to be built without clockfix, which is something you promised, so at least this is OK.
oscam-emu startup
Started by Robinson, 25 Jan 2018 23:23
58 replies to this topic
Re: oscam-emu startup #41
-
- Senior Member
- 2,621 posts
+30
Good
Posted 16 February 2018 - 19:32
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #42
-
- Senior Member
- 2,621 posts
+30
Good
Posted 16 February 2018 - 20:32
Have to see what is going on, because I've bumped it 8 days ago: https://github.com/O...b6ea310fdbbff1d
I don't know much about github but perhaps this is the reason:
-SRCREV_pn-enigma2-plugin-softcams-oscam ?= "11391"
+SRCREV_pn-enigma2-plugin-softcams-oscam ?= "11398"
SRCREV_pn-enigma2-plugin-softcams-oscam-emu ?= "11391"
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #43
-
- PLi® Core member
- 70,891 posts
+1,833
Excellent
Posted 16 February 2018 - 21:12
Yes, but I am talking about oscam-emu. Perhaps it stayed at 11391 although it seems to be built without clockfix, which is something you promised, so at least this is OK.
Ah, then don't write
Are you going to update oscam build used in HD51?
when you mean oscam-emu. 
I don't update the emu unless someone tells me to, as the emu is a patch on oscam, it needs to be pinned to the version the patch is for.
I've updated both earlier today: https://github.com/O...6f5d839d6f49cff
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: oscam-emu startup #44
-
- Senior Member
- 2,621 posts
+30
Good
Posted 16 February 2018 - 21:55
Thanks 
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #45
-
- Senior Member
- 229 posts
+6
Neutral
Posted 17 February 2018 - 00:05
@ developers,
There is a new oscam-emu repo on github. Check it out, you might find it useful.
It is oscam already patched with emu, so you don't have to worry about patching, or having to check whether the patch has been updated to work with latest oscam svn. There will also be a new release available when new features (that worth updating) are added to oscam or to emu.
Edited by nautilus7, 17 February 2018 - 00:07.
Re: oscam-emu startup #46
-
- PLi® Core member
- 70,891 posts
+1,833
Excellent
Posted 17 February 2018 - 15:05
If someone can update the recipe? I don't have much time this weekend...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: oscam-emu startup #47
-
- Senior Member
- 44 posts
+2
Neutral
Posted 10 March 2018 - 01:26
Well I've been doing some extensive testing of this flakey startup of oscam-emu and have finally determined the problem. I've tried compiling without "clockfix" and using "--wait 0" in the start cmd. These perhaps help a little but do not eliminate the problem.
The issue is if there are two instances of emulator in the oscam.server file eg. if you have added another emu reader for AFN.
Only one emulator gives a a reliable start-up. If you have two, it then becomes flakey. The work-around is to disable the extra emulator entry until it is needed.
A proper solution will require a study and amendment of the oscam code.
Re: oscam-emu startup #48
-
- Senior Member
- 229 posts
+6
Neutral
Posted 10 March 2018 - 16:09
I actually have the same issue, as I discussed earlier. I also use systemtime to get time from ntp server. I have an oscam-emu compiled without clockfix and I start it with --wait 0. I also use a 2nd emu reader!
For me the issue only happens when doing a reboot. Not a simple gui restart.
What you say about the 2nd emu reader is interesting. I will try to see if disabling the 2nd reader helps in my case too. And I''ll have to find what is causing this in the first place and how I can address it in the emu...
Thanks.
Re: oscam-emu startup #49
-
- Senior Member
- 2,621 posts
+30
Good
Posted 10 March 2018 - 18:05
007.4, you may be on the right track.
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #50
-
- Senior Member
- 2,621 posts
+30
Good
Posted 6 September 2018 - 13:04
Well I've been doing some extensive testing of this flakey startup of oscam-emu and have finally determined the problem. I've tried compiling without "clockfix" and using "--wait 0" in the start cmd. These perhaps help a little but do not eliminate the problem.
The issue is if there are two instances of emulator in the oscam.server file eg. if you have added another emu reader for AFN.
Only one emulator gives a a reliable start-up. If you have two, it then becomes flakey. The work-around is to disable the extra emulator entry until it is needed.
A proper solution will require a study and amendment of the oscam code.
I don't expect anyone is trying to dig into this?
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #51
-
- PLi® Core member
- 70,891 posts
+1,833
Excellent
Posted 6 September 2018 - 13:19
Not me, I don't use emu's.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: oscam-emu startup #52
-
- Senior Member
- 2,621 posts
+30
Good
Posted 7 September 2018 - 07:18
I meant oscam emu developers.
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: oscam-emu startup #53
-
- PLi® Core member
- 70,891 posts
+1,833
Excellent
Posted 7 September 2018 - 12:49
I doubt they read this forum...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: oscam-emu startup #54
-
- PLi® Contributor
- 6,197 posts
+261
Excellent
Posted 7 September 2018 - 13:38
streamboard is the place to discuss this but setting the --wait 0 option is a bad idea since OScam need to have the STB having the right time to start since decoding is timebased.
The --wait option is there to specify the amount of time OScam should wait for the box to get the proper time by default from the TP (or via NTP if you install systemtime plugin).
So with --wait 0 OScam will stop immediately if your box is not already at the right time.
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
Re: oscam-emu startup #55
-
- PLi® Core member
- 46,969 posts
+542
Excellent
Posted 14 September 2018 - 10:14
And BTW there is a myriad of options to check a delay or time span without the need for having a correct wall clock time. This should be fixed in Oscam.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: oscam-emu startup #56
-
- PLi® Core member
- 70,891 posts
+1,833
Excellent
Posted 14 September 2018 - 10:43
I've tried to discuss this in the past, but got nowhere and gave up...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: oscam-emu startup #58
-
- PLi® Core member
- 57,456 posts
+708
Excellent
Posted 14 September 2018 - 10:46
Probably the OSCAM authors need a good example how this can be made...
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: oscam-emu startup #59
-
- PLi® Core member
- 46,969 posts
+542
Excellent
Posted 14 September 2018 - 11:31
Are you serious?
From the top of my head:
- alarm() timer
- clock_gettime, clock types CLOCK_MONOTONIC, CLOCK_MONOTONIC_COARSE (may not work on STB), CLOCK_MONOTONIC_RAW (may not work on STB) and CLOCK_BOOTTIME
- poll() / select() on e.g. /dev/null
- times()
- usleep()
These are all independent of the wall clock.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
