Posts by joeuser

There is no need to patch MuMuDVB anymore, he has incorporated my changes into the latest versions on his git. It is best if you build your own to make sure all the dependencies are ok...
Oscam-emu/OSEmu needs to be patched, or you can download the already patched bin I posted in #24.
The sample config for MuMuDVB is posted.
Probably easiest is to first try with osemu and the command line I posted...

If you do not have a serial cable connected (the really preferred way to debug these boxes...) then you can try to telnet to the box and run:

killall rcS
killall enigma2
/usr/local/bin/enigma2

That should stop the script that automatically restarts enigma2 if/when it stops and stop enigma2, then restart enigma2 so the output will be printed to the telnet session. From there you can maybe see what is going on.

Possibly it is a plugin (autobouquet??? I dont use...) which is trying to run?

I have been thinking about it (and chatted with a few others about it.) Problem is that oscam-emu/osemu needs to work with all different systems, not just powervu. We need to find a way to change it, yet keep it compatible with all other systems. I have not had much time to work on it, but I think in the end, there will have to be a whole new UpdateKeys function just for powervu. Even then it will be a little difficult to deal with multiple channels using the same sid and multiple channels using the same key.

Give me a few minutes and I will post a repacked image which should load better...

Thanks, first was a typo, unfortunate I cannot edit the post anymore. I will ask an admin to fix it or let me fix it.
Second is a typo from the origial oscam-emu/oscam, but I will change it if I make any other changes...

EDIT:
Typo in post #3 VLC Playlist fixed..

how about "ls -al /usr/bin/oscam-svn11203-openpli40-webif-oscam-emu-patched"
And with changing permissions?

Quote from juvik

Hi
Easiest way is to setup a incoming VPN on the home network, then connect to that with the outside PC and everything acts like you're inside the home network.... ��

While that may be easiest to use, it is certainly not the easiest to setup and you are quite likely to have performance issues trying to stream through a VPN...
(But it does add more security if your system/internet connection can handle it.)

Looks like the script is designed to have other scripts:

...
...
oscamstart="/usr/emuscript/Oscam_em.sh start" # ruta script de inicio oscam 
oscamstop="/usr/emuscript/Oscam_em.sh stop" # ruta script de inicio oscam 
...
...

BTW - while it was probably useful in the past, I would not automatically update oscam these days. It seems quite often, one fix ends up breaking something else and has to be reversed or fixed again. Which is normal for development, but not good for a stable system. Also, most often the fixes probably don't even affect your usage and are not needed.

To use another transponder at the same time, you need another tuner, another instance of MuMuDVB (using a different listening port) and another instance of OSEmu (using a different listening port.)

Or better yet, use TVHeadend and just one oscam-emu/osemu instance to access all tuners.

I do not know what "rk" is???
You should not need to change permissions.
Try running it from where you extract it without the "-b" option.

I am not sure of a solution, but just wondering how you use VLC to constantly stream the current channel being watched when the channel changes?

My server has been running for more than 1 year without being restarted, so I never bothered with any auto start. :)
If you install MuMuDVB from your distribution, it should include init scripts. For oscam, I think you can probably find here (in the oscam section) some scripts to start on boot.

Quote from linoobs

I may have missed it, but wich url must stream tvheadend?

see this post:http://linuxsat-support.com/showthread.php?t=98100&p=316865&viewfull=1#post316865

Quote from benwiddowson

Looks like it's a usb hub then as I hate stuff in the front socket.

FYI - depending on which and how many USB devices, it is usually best to use a powered USB hub...

You can try this fix for MuMuDVB ( for TVHeadend, Astra use from other thread...)

Here are updated files for TVHeadend. The stream emm processing is now enabled/disabled via config. (Default is disabled.)

For OSEmu, use the "-e" option.

For oscam-emu add the following line to the oscam.conf file:

[streamrelay]
stream_emm_enabled            = 1

Or it can be configured via the webif...

- - - Updated - - -

BTW - to get debug output, for osemu use the "-v" option and for oscam use the debug option "-d68" (4 = cardreader - prints pids found , 64 = emm - prints UA keys found in stream).
Warning, for some channels with lots of UA keys in the stream, it will spew a lot of "key not found/missing" messages...

- - - Updated - - -

Sorry, I forgot to upload the oscam-emu patch...

- - - Updated - - -

Added fix for detection of ac3 tracks on some channels.

A few builds with my latest patch.

I, and at least a few other people, are using OSEmu/oscam-emu as a standalone application using just it's stream relay. The stream source can be any DVB streaming application (DVBlast, MuMuDVB, TVHeadend, Astra, etc ) and the client can be any player on a PC, phone/tablet or set top box. In this configuration, there is no dvbapi connection and no emm processing is done (no AU.) So, I have added the function of AU to the stream relay. For it to work, the CAT pid and EMM pid need to be included in the received stream.

Other changes:
1. In module-emulator-stream.c added connection id to client data so the connection id can be printed in log messages. Now it is not so confusing when there are multiple concurrent clients connected. Also, the change makes it unnecessary to have separate functions/calls for ParseTSPackets with oscam-emu and osemu.
2. In module-emulator-osemu.c changed from cs_log to cs_log_dbg for missing keys so it does not spew lots of messages in normal operation when a channel has many, many unknown UAs.
3. Updated module-emulator-osemu.h in OSEmu to be aligned with version from oscam-emu.
4. In module-emulator-stream.c add the logging of the found emm pid.
5. Added a configuration option to oscam-emu to enable the stream realy emm processing (disabled by deafult) and added it to webif.

[streamrelay]
stream_emm_enabled            = 1

In OSEmu, the emm processing is enabled when using the already existing "-e" option.

6. Also made small fix to oscam-config-global.c:

-DEF_OPT_UINT32("stream_relay_enabled"     , OFS(emu_stream_relay_enabled),        1),
+DEF_OPT_UINT8("stream_relay_enabled"     , OFS(emu_stream_relay_enabled),        1),

7. add detection of audio stream types 0x05 and 0x06 (should fix ac3 track detection)

TODO:
Make a real CAT parser, the included code was just a quick hack...
In oscam-emu, make the stream_emm_enabled changeable on-the-fly through the webif. Now a restart is required.

Attached is the oscam-emu patch and the OSEmu source is available on github:https://github.com/joeusercz/OSEmu

BTW - I only did limited testing, so any feedback would be helpful - especially for improving the CAT parsing...

V 1.9
- Added TS Demuxer (PID extractor). You can use this tool to extract EMM or other PIDs from the given .TS-188 files.
- During the indexing of EMM files, .min text files will be created too. min text files contain unique packets (with smaller sizes, suitable for uploads).
- Added displaying expired UA's count per each indexed file.

Well, luck has nothing to do with it. And neither does magic and my crystal ball doesn't show me what you are doing wrong. ;) You need to post what you are doing and maybe some logs, configs, etc...