128 replies to this topic

[mamamia]

Hi, I wish this thread would also be available in the englisch section of this forum because in my opinion its an interesting thread that more people should be able to understand.

I tried to translate the last pages using google translate because I would like to understand what openlpli team thinks about the new vu+ drivers changes but the automated translation result is too pathetic to understand.

If the new driver update is flashed on vu+ solo2 clone, which one User over on vti forum baught from an amazon vendor, box returns hw error and has to be reflased with an older image/driver.

Thank you!

Edited by Frenske, 17 December 2013 - 15:37.
I moved the English part to the English end user section. In case there are new drivers you can continue the discussion overhere. ;)

[Erik Slagter]

If the new driver update is flashed on vu+ solo2 clone, which one User over on vti forum baught from an amazon vendor, box returns hw error and has to be reflased with an older driver. 

This can be quick over with, we don't support clones in any way.

[mamamia]

Hi Erik,

I know this but I would also like to know more about what openpli teams things about the changes in general and if openpli will also integrate new transcoding possibilties, gstreamer, & new additional vu plugins and new streaming file formats that are only supported by the new drivers .

 

I believe the last few pages give an insight about what openpli team thinks. I wish I could understand.

Thank you!

Edited by mamamia, 17 December 2013 - 13:36.

[Erik Slagter]

In short: we are not enthousiastic about certain changes that vuplus makes for new features. They require changes to the general code base (for all brands/receivers), just for vuplus, even though that's not necessary, from a technical point of view.

[Rob van der Does]

In short: we are not enthousiastic about certain changes that vuplus makes for new features. They require changes to the general code base (for all brands/receivers), just for vuplus, even though that's not necessary, from a technical point of view.

In short: meaning that transcoding & WMV-playback only work in OI-based images (VTi & BH).

[athoik]

Changing DVBMEDIASINK_CONFIG for VU is not required???

 

Vu only supports pcm? Strange...

 

 

./machine/include/vuxxo2.inc:DVBMEDIASINK_CONFIG = "--with-pcm"
./machine/include/vuxxo.inc:DVBMEDIASINK_CONFIG = "--with-pcm"
./machine/include/etxx00.inc:DVBMEDIASINK_CONFIG = "--with-wma --with-wmv --with-pcm --with-dts --with-eac3"
./machine/include/xp.inc:DVBMEDIASINK_CONFIG = "--with-wma --with-wmv --with-pcm --with-dts --with-eac3"

 

I  have mention this already here: http://openpli.org/f...id/#entry392437

 

And here https://github.com/o...18fd9eee316baa5 is the change by OE-Alliance on DVBMEDIASINK_CONFIG

Edited by athoik, 17 December 2013 - 14:19.

[mamamia]

I believe and hope they dont know better and that the language and cultural barrier is difficult to overcome. I hope you will help overcome barriers and make it work together. 

Edited by mamamia, 17 December 2013 - 15:27.

[athoik]

Hi,
 
Just more information regarding the dvbmediasink....
 
 
Vu uses the following dvbmediasink:
 

http://code.vuplus.com/gitweb/?p=vuplus_openvuplus;a=blob;f=meta-openvuplus/recipes-multimedia/gstreamer/gst-plugin-dvbmediasink_0.10.bb

SUMMARY = "Plugin for gstreamer: dvbmediasink"
SECTION = "multimedia"
LICENSE = "MIT | LGPLv2.1"
LIC_FILES_CHKSUM = "file://src/gstdvbaudiosink.c;beginline=1;endline=45;md5=023ebb8eaef9b8cce8591a9d96638392 \
                    file://src/gstdvbvideosink.c;beginline=1;endline=44;md5=b597d3f0a4e3b49db42d2b5140bd7004"

DEPENDS = "gstreamer gst-plugins-base"
BRANCH="master"
SRCREV="91738211ef106ae7d14c1ccc5c4dd26c0f2dbf58"
PR = "r10"

inherit autotools pkgconfig git-project
SRC_URI = "git://schwerkraft.elitedvb.net/dvbmediasink/dvbmediasink.git;protocol=git;branch=${BRANCH};tag=${SRCREV}"

SRC_URI_append_vuplus = " \
                file://fix_dvbaudiosink_async_opt.patch;patch=1;pnum=1 \
                file://fix_dvbvideosink_dm8000_padtemplate.patch;patch=1;pnum=1 \
                file://fix_dvbaudiosink_support_ddp.patch \
                "

FILES_${PN} = "${libdir}/gstreamer-0.10/*.so"
FILES_${PN}-dev += "${libdir}/gstreamer-0.10/*.la"
FILES_${PN}-staticdev += "${libdir}/gstreamer-0.10/*.a"
FILES_${PN}-dbg += "${libdir}/gstreamer-0.10/.debug"

It's obvious that Vu uses the same dvbmediasink as Dreambox.

Bypass on dreambox/vu for wma audio is 0xd or 0xe (13 or 14)
https://schwerkraft....6c0f2dbf58#l861

Bypass on openpli/xtrend for wma audio is 0x21 or 0x20 (33 or 32)
http://sourceforge.n...udiosink.c#l533

Streamtype on dreambox/vu for wmv video is 16 or 17
https://schwerkraft....c0f2dbf58#l1502

Streamtype on openpli/xtrend for wmv is 3 or 5
http://sourceforge.n...deosink.c#l1304

So i guess we need to create gst-plugin-vu-dvbmediasink_0.10.bb and start using it for vu boxes.

@OpenPLi, what do you think?

[littlesat]

Jammer dat vu hier dmm na gaat ipv et die deze functionaliteit al jaren geleden al jaren had....
Het is misschien geen officieele standaard, maar het was wel zo makkelijk en logisch geweest....

Edited by littlesat, 17 December 2013 - 22:15.

[dAF2000]

Jammer dat vu hier dmm na gaat ipv et die deze functionaliteit al jaren geleden al jaren had....
Het is misschien geen officieele standaard, maar het was wel zo makkelijk en logisch geweest....

 

English please, littlesat.

[dAF2000]

Translation:

 

Too bad VU is copying DMM now. DMM had this functionality already for years.

It may not be an official standard, but it would be logical if it was.

[littlesat]

Daf.. Sorry for the switch into Dutch... But not dmm but xtrend had it for years...

Edited by littlesat, 17 December 2013 - 22:26.

[athoik]

Hi,

Here is the patch required from Vu boxes. It creates gst-plugin-vuplus-dvbmediasink for Vu boxes.

vuplus: Use same dvbmediasink as in code.vuplus.com

The new drivers with wmv/wma support are not working with OpenPLi images
because OpenPLi uses an implementation of dvbmediasink compartible with
Xtrend and XP drivers.

Vu is using dreambox dvbmediasink witch is incompartible with OpenPLi.

This patch creates a new dvbmediasink, same as in code.vuplus.com

 0001-vuplus-Use-same-dvbmediasink-as-in-code.vuplus.com.patch.txt   7.68KB   45 downloads

I haven't/cannot test it (since i don't have a Vu).

[JanHJ]

Will this patch be applied to the OpenPli image?

[athoik]

I don't know if it is working.


Either we need to change sink or at least starting by changing DVBMEDIASINK_CONFIG

Changing

[athoik]

Changing DVBMEDIASINK_CONFIG won't hurt.

./machine/include/vuxxo2.inc:DVBMEDIASINK_CONFIG = "--with-pcm"

./machine/include/vuxxo.inc:DVBMEDIASINK_CONFIG = "--with-pcm"



+DVBMEDIASINK_CONFIG = "--with-wmv --with-wma --with-pcm --with-eac3"

OE-Alliance did that, but again since i dont have such a receiver i cannot confirm if it is working or not.
 

[athoik]

@OpenPLi, can you change DVBMEDIASINK_CONFIG for vu boxes. It wont hurt right?

[pieterg]

Won't help either.
Ioctl values and codecdata will be incompatible

[athoik]

Then someone must confirm that patch on http://openpli.org/f...vu/#entry392787 is working.

 

I asked a strace from BH from a friend with vuduo2, but wmv video didn't work when running enigma with strace, so i cannot find ioctl (in order to confirm what BH is using).

[macnuts]

I can test it on duo2.

After applying that patch and building image, is flash required or replacing some modules would suffice?

Edited by macnuts, 23 December 2013 - 10:54.