Posts by s3n0

    EN:

    Hi. The Insight UHD channel at position 19.2E is broadcasting in the h265 format. Does your set-top box support also the h265 format ?

    If the Insight HD channel works for you, then the Insight UHD must also work.

    Furthermore, this channel is broadcast in Irdeto encoding mode and not in Cryptoworks mode. Is your satellite card + Oscam set to Irdeto mode ?


    SK:

    Ahoj. Insight UHD kanál na 19.2E pozícii je vysielaný vo formáte h265. Podporuje tvoj satelitný príjmač tiež h265 formát ?

    Pokiaľ ti funguje kanál Insight HD, tak musí fungovať aj Insight UHD.

    Ďalej platí, že tento kanál je vysielaný v režime kodovania Irdeto a nie v Cryptoworks režime. Je tvoja satelitná karta + Oscam nastavený na režim Irdeto ?

    It looks like drive.google has limited continuous downloads of multiple files without interrupting for 4 - 5 minutes or limited after about 35 - 40 downloaded archive files. Then this problem occurs and for some time (10 min. cca) it is not possible to download anything from drive.google. If the plugin downloads files continuously for 4 minutes, then it will start downloading only messages in the form of HTML answers (approx. 1 kB large html file), with this information:


    "We're sorry ... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now."


    fa72fce.png


    Then it is necessary to wait about 10 minutes (I do not know exactly, I did not test it) to reset this limit and then it is possible to download again from a specific IP address these files from the drive.google profile from Chocholousek.


    I've already written about this problem with Chocholoušek, maybe something can be solved with another mirror server for picon archives. Google Drive is a disastrous file-hosting server with lots of limitations. It is also very slow (in response to requests).

    Look for the debug mode in the OpenATV settings and also Enable the logging of the debug-log file. Fortunately, OpenATV creates a detailed debug-log file.


    MENU > Settings > System > Logs settings > Enable debug log - Yes


    Then save the changed setting and restart the Enigma. The debug-log file in the "/home/root/logs" folder will be created immediately. After reporting the error, just send the debug-log file to me in a private message (only as prevention, if the debug-log also contains some private information, which never happens).

    Hi.


    Thanks for the bug report.


    However, I would also need to see the debug log. Unfortunately, the screenshot is not enough.


    Which Enigma is installed there ?


    /// EDIT :

    Also, the displayed run time (time track) is incorrect. Hm ... Or is it correct ? Why do you have up to 53 satellites there ? :-) So much ... um ... :-).


    Does it always happen after unpacking a certain number of archives ? Are downloaded files deleted from the "/tmp" folder in your case ? They should be deleted automatically (by the plugin algorithm).


    Which update method do you use ?


    It would really be a suitable debug-log, to solve the problems + then some more possible additional questions then from me. :scratch_one-s_head:

    2.1.200427

    A directory browser has been added - for the purpose of selecting a user-defined picon folder.

    - !!! please be careful when deleting and creating folders in the directory browser !

    - !!! you are responsible for any loss of important data, after accidentally deleting the directory !

    Minor changes in the source code.

    Hi.


    In my opinion, there is no "best" guide, because each card coding is very different and also different Oscam settings are needed. There are completely different dependencies, depending on the type of card encoding or even according to a specific DVB provider. There are also various compatibility issues, for example with the CCCAM communication protocols (if you want to share cards). So it's not that obvious.


    It is best to search the internet for the settings that your decoder card needs. And then you study everything about a specific coding and specific "troubles" with the Oscam settings, designed for a specific DVB provider.


    All the main information about the configuration files can be found on the website here:

    http://www.streamboard.tv/wiki/OSCam/en


    The most important or basic and most necessary is to set up three Oscam configuration files:

    oscam.conf

    oscam.server

    oscam.user

    And everyone else is not so important to the running of Oscam. Of course, in some cases, other Oscam configuration files can be very important!

    Hi. Thanks for bug report. It was known error "UnboundLocalError: local variable 'new_file' referenced before assignment". This was an incorrect filename on the drive.google server and was fixed 2-3 hours later ;-) . When you open the plugin configuration, a new online version is tested. Just reopen the ChocholousekPicons plugin configuration and the file will be downloaded correctly from the internet.

    I'm sorry, but I still don't understand ... what does the ATV have to do with it and what about the VIX ? What settings ? I do not understand. Did you move the configuration from VIX to ATV ? Or what ? Hmm...

    :scratch_one-s_head:

    Does your terminal connection (SSH or Telnet) work ? It will help a lot if you write that yes or no. The problem can be further diagnosed via Shell. You can also try reinstalling OpenWebif from the Enigma feed + restarting Enigma.

    2.0.200424

    Minor fixes for some SKINs (in NewNigma2 / OE2.0):

    - thanks to alexbore, for renting a set-top box for remote debugging of the source code (DM800HDse with NewNigma2 / OE2.0)

    - determining the position of the nested widget via "center,center" does not work, therefore it's necessary to use the relative determination of the position "x,y"

    - removed the ability to scroll the list in the satellite configuration window, via the left / right buttons on the RCU, as the .pageUp() and .pageDown() methods for the ConfigList does not work in some OE cores (SKINs)

    - fixed error "FATAL!: addTimer must be called from thread 3261 but is called from thread 3680" (probably a bug in some C-libraries in some Enigma distributions)

    Added "Cancel" button in the satellite configuration window (including improved control of changes made by the user).

    knislinge2000 :


    You need to write more details. What web-browser are you using ? Is you web-browser updated ? What kind of the computer network is it (home LAN, remote VPN, access via port forwariding, etc.)? Are you sure you have the correct IP address ? Try inserting the text http:// before the IP address (if you haven't done so, try it, in some web browsers, under certain circumstances, it is unfortunately necessary to add this text as well). Try to open the OpenWebif interface in another web browser, if you have another one installed on your PC.

    Contact the developers at the URL which I post before. There you will find support for OscamEmu. I do neither development nor support for OscamEmu, sorry. I also don't use OscamEmu and I don't know him very well. I don't see shell-scripts that cause this error. I don't know what might be missing in your system (some libraries are missing ? bad versions of libraries ? incorrect POSIX syntax in the script ?). I have no idea sorry.

    I still don't solve it quite easily. The problem with calling Enigma functions from a separate background thread that want to use a timer, is related to the OE core of your NewEnigma2 firmware. You can found a many similar problems on the internet ... for example here:

    [1] https://dreambox.de/board/inde…led-from-thread/&pageNo=1

    [2] https://board.newnigma2.to/wbb…-HD-se-Newnigma2-v4-0-12/

    However, in the case of OE2.0 this works and in the case of OE2.5 and newer this is solved by a special timer method. But in your OE core it does not work.


    Your debug-LOG file only shows that there is an error that I am describing. I don't see anything there by pressing left / right on the "Picon folder" configuration item. Immediately after opening the plugin configuration, you pressed the blue button on the RCU. CrashLog jumped out. But you've already sent me 3 times. :-(


    As I say ... I need physical access to the device and playing with it for at least 2-5 hours cca. It is not possible to solve complex things with someone who is not a programmer. Sorry. :-(