Ncam Emu by RAED

There are 1,955 replies in this Thread which was already clicked 709,445 times. The last Post () by joaoccbernardo.

  • Actually I was thinking about this suggestion before, why have separate files contain almost same data.....


    So I asked about the benefits of it, I don't want to push in spacific direction but it just idea to discuss


    **Proposal for File Unification Between OSCam and NCam**


    After examining both codebases, it appears there's significant redundancy in many core files (readers, servers, etc.) that could benefit from unification. Key observations:


    1. **Code Duplication**: Approximately 70-80% of reader/server implementation files contain identical or nearly identical code between projects


    2. **Maintenance Burden**: Currently, bug fixes/enhancements often need to be manually ported between projects


    3. **Divergence Points**: Where NCam requires unique functionality (e.g., specific protocol support), these could remain as separate extensions


    **Suggested Approach**:


    - Create a shared core module for common components (readers, servers, etc.)

    - Maintain project-specific extensions where needed

    - Implement a build system that can compile against either codebase


    **Benefits**:

    - Reduced maintenance overhead

    - Synchronized bug fixes

    - Clearer distinction between shared and unique functionality

    - Smaller codebase footprint


    The unification would particularly help with:

    - Reader protocol implementations

    - Server connection handling

    - Common utility functions

    - Basic ECM/EMM processing


    Would appreciate thoughts from both developer communities on this proposal.


    ---

  • Of course, it's not possible to unify oscam and ncam...

    And it's not possible to separate the codes and put them in separate files...

    We're talking about C++, not Python ...


    On the contrary, when we think about separating the features found in ncam separately, it will become more complicated during the update and maintenance phase...


    As for me, I don't support oscam at all. As you know, my support is only for ncam... You can discuss this matter in a separate thread covering all emojis...


    Here, I only support ncam, and I have no future intention of creating a new, separate project... Because ncam is essentially an independent project from oscam. It's built on the oscam source code, but it has become independent. Why would I go back and rewrite it just to ensure compatibility between the oscam and ncam config files? I have nothing to do with supporting oscam...


    So, I apologize...

  • fairbird


    Hello dear, is it possible for you to find us a solution for the Pure2 image?


    Activating the emulator from the panel and restarting Enigma2 twice in a row causes the front display information to disappear, showing only a yellow bar.


    7.jpg


    2025-06-27_135231.jpg


    However, when activating the emulator via Telnet and restarting Enigma2 twice, this issue does not occur and everything works fine


    2025.jpg


    Code
    root@dm920:~# /usr/bin/cam/ncam -c /etc/tuxbox/config/

    lcdshot_20250628203206.png



    The test was done on both the internal flash and the external flash.



  • fairbird

    Changed the title of the thread from “Ncam Emu compiled and patched by RAED” to “Ncam Emu by RAED”.
  • Update ...


    Ncam V15.4


    Download link in first post

  • The emulator takes a very long time to activate on the Dream Elite image — almost a minute and a half.


    Code
    {
        "name": "NCam 15.4",
        "binary": "ncam",
        "config": "-r0"
    }

    With this modification, it activates very quickly and performs even better.


    Code
    {
        "name": "NCam 15.4",
        "binary": "ncam",
        "config": "-b -B -r 2 -w 1 -c /var/tuxbox/config/ &"
    }
  • Update ...


    Ncam V15.5


    Download link in first post

  • If you have access to 19.2°E, you could reproduce the error. If you stay on a Sky DE channel for several hours, the classic “hammering sound” error occurs, as was the case at the beginning of the development of OSCAM ICAM. The box freezes. The only thing that helps is to pull the power plug.

    DM One & DM Two AIO+GP4.2

  • What is your device ?!And approximately how long before your box freezes?!

    Please after freezes the device take the ncam.log from tmp and upload it here.


    Because no one sent to me this issue before.


    Another important thing to keep in mind is that the channels are streamed, not broadcasted via regular satellite. This means they consume the processor and RAM, and if you continue to play these channels, your device will almost certainly freeze.

    This also depends on the type of device and the power of your RAM and processor.

  • Probably no one reported this because most Dreambox One&Two user - see my signature - use OSCAM.


    Roughly speaking, a few hours... I usually leave it on one channel when the Bundesliga is on from 3 p.m. to 8 p.m.


    As I already wrote, this phenomenon occurred in the early days of OSCAM ICAM development. It was then resolved with a patch and no longer occurs.


    I will test ncam on Monday at the earliest and provide the log.

    DM One & DM Two AIO+GP4.2

  • hi. im trying to add my second server information to ncam.server file. but it doesnt work. it connects only to the first server. all the server informations are correct. checked many times. whats wrong and what can i do? i have ncam 15.4. both server lines are working with oscam.

  • 2025-11-02_225347.jpg

Your resource for Ncam softcam.

Find configs, tools, downloads, and community support for setup, optimization, and card/server management. Master modern card sharing with Ncam. Access configurations, tools, downloads, and dedicated support for efficient Enigma2 server/client setup.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!