Closed scramatte closed 2 years ago
I've got the same problem using mumudvb_2.0.0-dmo2+bp1_amd64.deb with oscam-svn_1.20.10176+svn202005241631~ubuntu19.10.1_amd64.deb & oscam-1.20_svn11581 built by myself.
mumudvb_2.1.0-dmo1_amd64.deb works fine with both OSCAMs.
So, I guess it is MuMuDVB issue.
So it's more an issue of package as you say it works with the latest MuMuDVB
On Sat, Jul 18, 2020 at 2:34 AM Ro-Den notifications@github.com wrote:
I've got the same problem using mumudvb_2.0.0-dmo2+bp1_amd64.deb with oscam-svn_1.20.10176+svn202005241631~ubuntu19.10.1_amd64.deb & oscam-1.20_svn11581 built by myself.
mumudvb_2.1.0-dmo1_amd64.deb works fine with both OSCAMs.
So, I guess it is MuMuDVB issue.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/258#issuecomment-660393361, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRIDZ7HQVKX5LYQYPQ673R4DUZFANCNFSM4KKZY3WA .
Same problem.
MuMuDVB Version 2.1.0_20181020_mumudvb2
--- Build information ---
Built with CAM support.
Built with SCAM support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.11.
Built with support for DVB-T2.
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.net/
Project from the cr@ns (http://www.crans.org)
by Brice DUBOST (mumudvb@braice.net)
MuMuDVB Version 2.1.0_20181020_mumudvb2
--- Build information ---
Built with CAM support.
Built with SCAM support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.10.
Built with support for DVB-T2.
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.net/
Project from the cr@ns (http://www.crans.org)
by Brice DUBOST (mumudvb@braice.net)
Hello
I think it is worth a shot to ask on the mailing list, the people who developed the oscam support are there
Brice
On Sat, Jan 23, 2021 at 9:37 PM marian34-git notifications@github.com wrote:
Same problem. `MuMuDVB Version 2.1.0_20181020_mumudvb2 --- Build information --- Built with CAM support. Built with SCAM support. Built with ATSC support. Built with ATSC long channel names support. Built with support for DVB API Version 5.11. Built with support for DVB-T2. Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://mumudvb.net/ Project from the cr@ns (http://www.crans.org) by Brice DUBOST (mumudvb@braice.net) version work:MuMuDVB Version 2.1.0_20181020_mumudvb2 --- Build information --- Built with CAM support. Built with SCAM support. Built with ATSC support. Built with ATSC long channel names support. Built with support for DVB API Version 5.10. Built with support for DVB-T2.
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://mumudvb.net/ Project from the cr@ns (http://www.crans.org) by Brice DUBOST (mumudvb@braice.net)`
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/258#issuecomment-766175290, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRID4TXY74ASM2E7OYTPLS3MXOZANCNFSM4KKZY3WA .
Just tested MuMuDVB with OSCam-Emu, both built from the latest sources. Same issue. MuMuDVB built with support for DVB API Version 5.11 doesn't work with OSCam-Emu. There are also a lot of strange warnings in VLC log:
ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1)
MPV doesn't play the stream either.
MuMuDVB built with support for DVB API Version 5.10 works fine.
How did you choose the specific build version of the DVB API
This is very strange and as I don't understand the OScam internals it's hard to me to help further besides having in this issue how to build with the 5.10
On Tue, May 25, 2021 at 3:46 PM Ro-Den @.***> wrote:
Just tested MuMuDVB with OSCam-Emu, both built from the latest sources. Same issue. MuMuDVB built with support for DVB API Version 5.11 doesn't work with OSCam-Emu. There are also a lot of strange warnings in VLC log:
ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1) ts warning: scrambled state changed on pid 100 (1->0) ts warning: scrambled state changed on pid 100 (0->1)
MPV doesn't play the stream either.
MuMuDVB built with support for DVB API Version 5.10 works fine.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/258#issuecomment-847884389, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRID7BGTSL7B7VTORKOJTTPOS4BANCNFSM4KKZY3WA .
Is in settings in oscam on DVBAPI page have writenn port number?
Hi,
I'm trying to unscramble channels using oscam 1.20 r11572-798 build from following git repository https://github.com/oscam-emu/oscam-patched
Everything looks ok, I see ECM requests into oscam log but channels still scrambled :
Channel "Chan1" is now highly scrambled (97% of scrambled packets). Card 2
Note I'm running debian 10, with TBS tuner cards and MumuDVB build from Github repository too.
I suspect that is might due to dvbapi version that is different between MumuDVB and Oscam
(dvbapi) Using /tmp/camd.socket listen socket, API forced to DVBAPIv3 (0), userconfig boxtype: 11
And looks that MumuDVB use version 5.11 ...Regards