[Boblight SupportThread] Update: 11-02-2014, Boblight 0.8R6

Wir haben aktuell ein Problem mit dem Board und arbeiten an der Lösung...

    Hi speedyisfast, thanks for your support and your answer

    Zitat

    Original von speedyisfast
    boblightd -f
    now look in top, is there one boblightd or 2


    two, and for such with different PIDs. killing one, kills both

    Zitat

    Original von speedyisfast
    stop boblightd: killall boblightd
    Ok now start with script.
    /etc/init.d/boblight-control start
    now look in top, are there one or more processes.


    two, and as writen before it results in "ERROR: 127.0.0.1:19333 Write timed out" after some time

    Zitat

    Original von speedyisfast
    I have no dm800 here so i can not test it here sorry.
    I'am working on 0.6r8 with a new liveupdate and a check if there are more processes of boblight.


    Hope this helps, but I expect there is a problem with DM800HD with sedu.

    Zitat

    Original von speedyisfast
    Update 0.6R8


    [Boblight Test-Thread] Update: 06-03-2013, Boblight 0.6R8


    How to force boblightd to use ONLY sockets? It seems it still start up with port 19333. In this case is now runs with two boblightd and two boblight-enigma2.

    Code
    ps | grep bob
 1347 root     13808 R    /usr/bin/boblightd -f
 1348 root     13808 R    /usr/bin/boblightd -f
 1350 root     16044 S    /usr/bin/boblight-enigma2 -f
 1353 root     16044 S    /usr/bin/boblight-enigma2 -f


netstat -a 
tcp        0      0 0.0.0.0:19333           0.0.0.0:*               LISTEN
unix  2      [ ACC ]     STREAM     LISTENING       8276 /tmp/boblight.socket
    Zitat

    Originally posted by testo22


    How to force boblightd to use ONLY sockets? It seems it still start up with port 19333. In this case is now runs with two boblightd and two boblight-enigma2.

    Code
    ps | grep bob
 1347 root     13808 R    /usr/bin/boblightd -f
 1348 root     13808 R    /usr/bin/boblightd -f
 1350 root     16044 S    /usr/bin/boblight-enigma2 -f
 1353 root     16044 S    /usr/bin/boblight-enigma2 -f


netstat -a 
tcp        0      0 0.0.0.0:19333           0.0.0.0:*               LISTEN
unix  2      [ ACC ]     STREAM     LISTENING       8276 /tmp/boblight.socket


    MM very strange, you have pm.


    for all sedulight members:


    THANKS!!! for the donations :winking_face:
    I have buyd a sedulight controller from a store here.
    I'am now testing sedulight.

    Hi,


    I have tested here with my sedulight.


    Config:


    Is the jumper for 50000 on the board. ?
    So it's here ok.


    PLease test this prefix and postfix.


    Kind regards Speedy

    Hi Speedy,


    thanks so much for getting a SEDU! You're the best!


    Yes, the jumper has to be in to make it 500K. If you remove the Jumper, it would have 250K for PC-usage.


    I always used prefix 5A B0, so you say 5A A1 should be correct? I will try this and tell you what it changes.

    What exactly is the issue with Sedu? I have been running Sedu with Boblight some months ago with no problems at all. I haven't checked it with the recent versions, but there should technically be no real issue as the boblightd covers the writing of data onto the Sedu.

    checking for long long... yes
    checking for long double... yes
    +++ Divide By Cucumber Error. Stopping. +++

    2 Mal editiert, zuletzt von mamba0815 ()

    Zitat

    Originally posted by Schnarchzappen
    ...
    So I used your donate-accout and sent a small money for buying a Sedu-Lights Controller some minutes ago.
    I hope, other users will do the same. We all have payed much more money, mostly für the leds, to get a new kind of TV-Lightning.
    ...


    I also sent some money to support Speedy. Amazing how much time he's spending for this!

    I had done my test on Sedu with these configs:


    256 Channels:
    [device]
    name ambilight
    output /dev/ttyUSB0
    channels 768
    type momo
    interval 10000
    prefix 5A B0
    postfix A5
    rate 500000


    170 Channels:
    [device]
    name ambilight
    output /dev/ttyUSB0
    channels 510
    type momo
    interval 10000
    prefix 5A A2
    postfix A5
    rate 500000


    I do not recollect any issues back in May 2012 ...

    checking for long long... yes
    checking for long double... yes
    +++ Divide By Cucumber Error. Stopping. +++

    Mal eine Frage an die Allgemeinheit.


    Ist es aktuell normal, dass es bei 1920x1080i Sendern eine Verzögerung von ca. 0,5 bis 1 Sekunde gibt?


    Bei SD-Sender, sowie 1280x720 Sendern kann ich fast keine Verzögerung feststellen.


    Ist das nur bei mir so, oder kann das jemand bestätigen?



    Ansonsten eine wirklich super Leistung von speedy. Danke für dieses wunderbare Plugin.


    Yes the delay at 1080i is "normal" so far :) 720p and SD is fine. Hopefully Speedy will find a fix for it :)

    SD is fine? Dann hast Du wahrscheinlich kein Sedu - oder?
    Bei mir schaltete sich mit den alten Versionen Sedu automatisch aus, mit der aktuellen Version (und Speedys config) bleibt es zwar an, friert bei SD aber für längere Zeit ein und die Farben passen dann gar nicht. Auch nicht mehr, wenn man dann wieder auf HD-Sender zurückschaltet.
    Delay ist übrigens mit beiden Configs (Prefix 5A A1 / 5A B0; jeweils mit Typ momo) gleich.

    Also bei SD Sendern konnte ich bis jetzt keine Freezer feststellen, wie lange dauert das denn bei dir circa?


    Bin mir da aber nicht 100% sicher, da ich kaum SD Sender schaue.
    Außerdem lass ich das ganze zur Zeit über 'nen Raspberry Pi laufen, da mein Sedu irgendwie nicht mehr wollte, und ich dann keine nerven mehr hatte :face_with_rolling_eyes:

    Bei SD passen die Farben von Anfang an nicht, "frieren ein" und ändern sich dann nur noch sporadisch zwischendurch.
    Das scheint aber nur Sedu zu betreffen!

    Hi,


    For all members who have a delay at some resolutions.


    Open a terminal and start boblight with:


    boblight-enigma2 -t 5 -k -d (change 5 in your number)


    -t means the delaynumber, with this we can test what number we need for the resolution.
    -k is the grab info, this gives also the ofs and ofs2.
    -h is help :p


    If you have found a resolution with a good delay, please post it.


    To built in this, i need this info:
    - The tv channel, ofs+ofs2 (-k), resolution (-d), VideoFPS (-d), and the delaynr :)



    You can test one thing more:


    Enabled the lights with the GUI.
    open terminal


    type: ps | grep bob
    now you see the boblight processes.


    give them another priority with, renice 19 pidnr (change pidnr to the processnumber, you see it whit the (ps | grep bob) first numbers.
    Now look if the delay is gone.


    Thanks for testing..


    Kind regards Speedy.

    Hi Speedy,


    box is a solo².


    Sender: ZDF HD with 720p. A delay of 3 seems to be good for me
    [Boblight::debug] grabFPS 10.0 :tired_face: videoFPS:50 :tired_face: Shift,Skip,Ival:3,16,0.10 :tired_face: Res:80x45 (Source 1280
    x720)
    Adr: 207A8000 Adr2: 208AC000 OFS: 832 448 C-offset:1064960
    Stride: 1280 Y-Res: 720


    Sender: Kabel1 HD with 1080i. A delay of 5 seems to be a little behind the picture, delay of 4 is to fast.
    [Boblight::debug] grabFPS 10.0 :tired_face: videoFPS:25 :tired_face: Shift,Skip,Ival:5,32,0.10 :tired_face: Res:60x33 (Source 1920
    x1080)
    Adr: 21E78000 Adr2: 22076000 OFS: 1088 576 C-offset:2088960
    Stride: 1920 Y-Res: 1080


    Hope that helps :)


    ftobi

    From my experience with the dealy-function in the Atmolight-Plugin I can tell the delay is NOT fixed by the parameters you have listed above. The TV itself has a rather signiciant influence on the delay. In other words: knowing the delay parameters i.e. for Samung TVs doesn't mean they work for Panasonce (etc). It is -more or less- required to find a delay value that works for all resolutions as a general rule of thumb with internal adjustments depending on the resolution and mode (progressive, interlaced).


    Just my $ 0.02 ... :winking_face:


    Mamba

    checking for long long... yes
    checking for long double... yes
    +++ Divide By Cucumber Error. Stopping. +++