Please put some debug messages and show us a case where those variables have different value, also provide the patch and the steps to reproduce it.
Well very nice.
But actually about the whole sequencing You have had extremely detailed logs already more then a year ago. With proves step by step. With pinpointed higliths where it wen't wrong and so ......
This exact for the start non start problem.
Sorry But if you really do insist I will restart again but it's more then a full day task. And this for logs you have had more then A year ago and in detail reworked to highlight and pinpoint the differences.
If You have an archive and kept them there perhaps look for them.
But if you still have you're dm800se i suggest to make a, ok we are looking forward a brandnew image based on pli gst-1 branch and adapt the meta to you're needs.
But use for the sink :
well here the conf for dm
dreambox.inc
MACHINE_EXTRA_RRECOMMENDS = " \
gstreamer1.0-plugin-multibox-dvbmediasink \
ntfs-3g \
kernel-module-cifs \
dm800se.conf
#@TYPE: Machine
#@NAME: Dreambox DM800se
#@DESCRIPTION: Machine configuration for the Dreambox DM800se
OPENPLI_FEATURES = "fan usbconsole"
MACHINE_FEATURES += "modem wlan kernelwifi externalwifi dvb-c blindscan-dvbc colorlcd hdmicec"
require conf/machine/include/dreambox-brcmnand.inc
require conf/machine/include/dreambox-nand-64mb.inc
require conf/machine/include/dreambox-part-64mb.inc
require conf/machine/include/dreambox-jffs2.inc
require conf/machine/include/dreambox-mips32el.inc
DVBMEDIASINK_CONFIG = "--with-dreambox --with-pcm --with-wma --with-wmv --with-dtsdownmix --with-eac3"
CHIPSET = "bcm7405"
# Image fails to boot if kernel exceeds some unknown limit, so make that
# explicit here. I don't know what the actual limit is, but 6416679 boots
# and 6604470 didn't.
KERNEL_IMAGE_MAXSIZE = "6500000"
Then You will be able to test all media You're self.
I did add a lot off extra debug stuff in the mediasink just cause we are still in development state . That's why I used for example a lot off INFO instead off DEBUG
after You did in you're box by just run:
GST_DEBUG=dtsdownmix:4,dvbaudiosink:4,dvbvideosink:4 enigma2.sh
for example.
but for all media you will be able to see what is happening concerning pause unpause.
apart from the fact that just the dts downmix is just a imminent prove about the previous wrong working in servicemp3.cpp it does cause at own will regularly weird facts. such as jumps missing a couple of seconds off audio at media start this for every box.
The cause can really be followed in my mediasink which is made for that .You can follow state, event, changes and follow them up in function off e2 servicemp3.cpp.
Off course if You are convinced that gstreamer should be launched at wild and that the video is running on it's own disregarding any audio ,.... that's the case now after you're commit :
https://github.com/O...9ffaa6af62c377d
You went so what a year back in time ???
So You have the choice take what I really find out and my severe error actually the use of :
if(m_paused && !m_user_paused)
Was indeed a severe error and could cause the deadlock . In rather exceptional conditions but yes it is possible.
The correct code is simply.
if(!m_user_paused)
Whatever log I give you You will always need more. I suggest to use my media sink or you can adapts you're own to have a bit more detailed sequencing info , just do what you wan't.
)
