What does "fix demuxer" (refers to stream relay) setting does in DVB-api configuration
Posts by Marcus1305
-
-
Display More
I must only confirm than is perfect working on my device !
QuoteDisplay MoreUnix starttime: 1710865714
Starttime: 19.03.2024 17:28:34
Version: oscam-1.20_svn-r11734-799
Compiler: arm_cak7-icam-l2b_(samur)
Box type: pulse4k (generic)
PID: 2812
TempDir: /tmp/.oscam
ConfigDir: /etc/tuxbox/config/OSCam/
WebifPort: xxxx
In my case it finds the cw too but the image is lagging for some reason only on that channel. With Ncam and the same config it is working without any issues for some reason. Tfrc sent me config and the only difference is pmt mode = 0 ( I use 6 ) , and extended cw api = 1 ( I use 2) . I doubt that could cause the issue but will try.
-
Can someone test Dazn 1 De and confirm it works without any issues on samur's oscam
It's ok with Samur's 734-799 version.
I wanted to send you pm but you have disabled it, could you send me your oscam conf in pm? For some reason that channels lags with samur's oscam
-
Can someone test Dazn 1 De and confirm it works without any issues on samur's oscam
-
Everything the same, you can try it and confirm.
-
Why does Dazn 1 work on Fairbird's Ncam and doesn't work/heavy lag on Samur's Oscam, it seems like Ncam is more stable for slyde.
-
Max Sport 1 HD and Diema Sport 3 HD on 1.9e changed their transponders, so picons are missing.
-
France 2 and 3 UHD on 5w picons missing
-
what is your architecture for the packages?
armv7
-
Why is the option to clear whole search history replaced with option to delete only one by one, is it possible to have both?
-
Display More
ncam config 16.09.2023
O.E 2.0- OE 2.5
thanks fairbirdI always wondered should I change or disable these emu readers in ncam because all of them had multiple labels and devices with # in front, is it supposed to be like that? Second one and third one are yellow in ncam because they have # in front of device.
[reader]
label = github:AbuHaya3/Keys/main/SoftCam.Key
[reader]
#label = github:"and path"
label = github:JetCamFastCam/JetFastCamRza/main/SoftCam.Key
#label = github:fairbird/MyImagesFeeds/master/SoftCam-Files/SoftCam.Key
#label = github:smcam/s/main/SoftCam.Key
#label = github:MOHAMED19OS/SoftCam_Emu/main/Enigma2/SoftCam.Key
[reader]
label = Internet_SoftCam
protocol = emu
#device = https://raw.githubusercontent.…SoftCam-Files/SoftCam.Key
#device = https://raw.githubusercontent.…/main/Enigma2/SoftCam.Key
-
Hello everyone, I am testing the latest Openpli 9 image in Python 3 which is working well, pleasantly surprised, however I cannot find a Multistalker pro version that works, the one from the Levi45 plugin does not work, thank you for your assistance.....
OpenPli 9 is python 3.9 and this plugin requires older python 3 version
I am on openatv 7.4 which is python 3.11.2 so that does not ring true to me
I don't know maybe only the specific openpli version of this plugin is affected by this problem. Multiple users on this thread wrote this already
Edit: Apparently plugin works only on 3.11 and 2.7 versions of python
-
Hello everyone, I am testing the latest Openpli 9 image in Python 3 which is working well, pleasantly surprised, however I cannot find a Multistalker pro version that works, the one from the Levi45 plugin does not work, thank you for your assistance.....
OpenPli 9 is python 3.9 and this plugin requires older python 3 version
-
Display More
I don't really want to get involved 'in your discussion' ;) - I compared also v1.0.13 with v1.0.15 on my pure2 (6.5) image.
v1.0.13 - history zap nearly opens immediately
v1.0.15 - history zap opens noticeably slower - I wouldn't say it take >2 sec but about 1 sec
(without any accusations or claims... I can live with ~1s)
Finally someone to confirm, why would you live with that second if you don't have to in the older version.
-
Does the plugin work in Openpli 9.0 py3?
-
it's not about number of channels because it doesn't affect the start up speed of plugin. Even when I have 1-2 channels in zap history new version will take 2 seconds more than older version just to o p e n not to perform similar epg search. You don't need miliseconds or calculations, difference is huge you can see it by eye.
-
My friend I don't know if you are using google translate or something else is the problem. You are missing my point for some reason I don't know if it's intentional because I explained my problem 5-6 times and you keep talking about different thing. Forget about similar epg search I don't even use that feature it's probably same speed in both versions.
Similar epg search is performed by pressing green button when you open the plugin it's not the same thing I am having problem with.
-
I am not talking about similar search algorithm at all I don't even need that.
Most simplified explanation:
1. I watch random channel
2. I press the button "back" on the remote (hotkey(shortcut) for your plugin)
3. It loads the history of the zapped channels
on 1.0.13 it shows instantly on 1.0.15 there is very annoying 2 second delay
I hope you understand, no similar searches, translations and other features, just simple press of the button to show the history of the zapped channels, that's slower.
-
Just tested 1.0.15, new features are cool but 1.0.13 much quicker responsiveness
-
It is not time spent for similar epg search that is the problem but the fact that when I press my hotkey for the plugin it isn't nearly as snappy as previous version, just feels heavier sluggish.
