Posts by dniestre

  • FootOnsat

    Quote from fairbird

    Test ..

    If still the same ... give this in telnet and send output and the log also

    Code
    killall -9 gst-launch-1.0

    It worked with 3-4 videos in a row, but after trying one from Twitter, it stopped working on YouTube.


    Code
    >>> DONE <<<
root@dreambox:~# 
c
lear
[H[Jroot@dreambox:~# 
killall -9 gst-launch-1.0


gst-launch-1.0: no process found
root@dreambox:~#

  • FootOnsat

    I just tried opening it with the AIO image installed again, and it is now displaying the image and sound in high-quality resolution. The log is writing... I haven't left the video yet. Should I do something?


    I used the interface.py file here.

  • FootOnsat

    It only worked the first time! After that, there was no sound. When I reinstalled everything, I forgot to enable debugging. I'll test it again.

  • FootOnsat

    Now I have tested with a new image GP 4.2 (not AIO) and the sound worked only one time with your latest interface.py file!


    In subsequent attempts, it no longer worked.


    I didn't have the log enabled.

  • FootOnsat

    Another message from GEmini


    Quote

    "Final update: I've flashed a clean DreamOS 2.6 stable image and re-installed all codecs. Even with a fresh system, gst-launch returns 'Device Busy' for both dreamhdmi and default ALSA devices.

    This confirms that on Dreambox Two, Enigma2 holds an exclusive lock on the audio hardware. To make your plugin compatible, you must use the internal Enigma2 playback engine:

    self.session.nav.playService(eServiceReference(4097, 0, path))

    Using alsasink via GStreamer directly will never work on this hardware while Enigma2 is running."

  • FootOnsat

    Tests:


  • FootOnsat

    Subject: Technical Debugging Report - Audio Sink Conflict on DreamOS (AIO/Gemini)


    Hi,

    I have completed extensive debugging on my Dreambox (DreamOS 2.6 / Gemini AIO) regarding the audio output issue in your plugin. Here is the technical breakdown of the findings:

    1. The Conflict (ALSA Exclusive Access)

    The plugin currently attempts to use alsasink (specifically device=dreamhdmi). On modern DreamOS images, the Enigma2 process maintains exclusive control over the ALSA driver.

    • Observation: When running gst-launch-1.0 with alsasink, the system returns: Error: Device 'dreamhdmi' is busy.
    • Verification: The audio only works if I manually stop Enigma2 via init 4. This is not a viable solution for a plugin.

    2. Missing Sinks

    The standard workaround of using dvbaudiosink is not applicable here, as the element dvbaudiosink is not present in the GStreamer environment of these newer images.

    3. Installed Dependencies

    I have verified that all necessary GStreamer codecs and parsers are installed and working:

    • gstreamer1.0-plugins-good-audioparsers
    • gstreamer1.0-plugins-bad-faad
    • gstreamer1.0-libav The pipeline is technically sound, but the Sink is the bottleneck.

    4. Recommended Solution

    To ensure compatibility with DreamOS and allow audio to play alongside Enigma2, the plugin should avoid direct GStreamer sink calls and instead utilize the native eServiceReference (4097). This allows Enigma2 to manage the audio routing and hardware arbitration.

    Suggested implementation change: Instead of a manual GStreamer pipeline with alsasink, please use:

    Python

    Python
    from enigma import eServiceReference@@@WCF_PRE_LINEBREAK@@@# Use Service 4097 to let Enigma2 handle the GStreamer output@@@WCF_PRE_LINEBREAK@@@ref = eServiceReference(4097, 0, "/tmp/your_audio_file.mp4")@@@WCF_PRE_LINEBREAK@@@self.session.nav.playService(ref)@@@WCF_PRE_LINEBREAK@@@

    By using the native service handler, the audio will play correctly without requiring the user to kill the Enigma2 process.

  • FootOnsat

    I can't find a solution, even with the help of AI.


    Gemini says:

  • FootOnsat

    This morning, the plugin is having trouble obtaining information about yesterday's games, making it difficult to test the videos (status: wait).


    I managed to do the test: first, the sound played without the image. Then, I stopped the sound and the image started playing, but without sound.

  • FootOnsat

    Quote from fairbird

    The problem is you found these command to run audio only with stop E2 .. and this does not correctly wen need command run audio with E2 working

    Code
    gst-launch-1.0 playbin uri=file:///tmp/a.mp4 video-sink="dreamvideosink" audio-sink="alsasink"
gst-launch-1.0 filesrc location=/tmp/a.mp4 ! qtdemux ! aacparse ! avdec_aac ! audioconvert ! alsasink


    Anyway try this from attach ..

    if does not work send the log and also try to find correct command work with E2 working not stop

    It doesn't work. The device is always busy, which is why it is necessary to stop enigma2. However, with this command, the sound works without stopping enigma2 (init 4):


    Code
    wget -qO - "http://localhost/web/mediaplayerplay?file=/tmp/a.mp4"

  • FootOnsat

    According to Google Gemini:

  • FootOnsat

    The sound plays with these commands, but only if the system is stopped (init 4) - thanks to Gemini and you of course:


    Code
    gst-launch-1.0 playbin uri=file:///tmp/a.mp4 video-sink="dreamvideosink" audio-sink="alsasink"
gst-launch-1.0 filesrc location=/tmp/a.mp4 ! qtdemux ! aacparse ! avdec_aac ! audioconvert ! alsasink

  • FootOnsat

    After running the commands, the box lost sound and the videos still have no sound.



    I'll try AI for help.


    Thank you for your effort!

  • FootOnsat

    Don't work.


  • FootOnsat

    here it is...



    pasted-from-clipboard.png


  • FootOnsat

    none work.


    Code
    root@dreambox:~# 
c
lear
[H[Jroot@dreambox:~# 
a
play -L


-bash: aplay: command not found
root@dreambox:~#