do we have DDP in PLi's OE ?
http://code.vuplus.c...62d271710cec38d
merge requests for PLi's git
Started by Persian Prince, 16 Apr 2013 12:12
1748 replies to this topic
Re: merge requests for PLi's git #261
-
- Senior Member
- 1,982 posts
+247
Excellent
Re: merge requests for PLi's git #262
-
- Senior Member
- 27 posts
+1
Neutral
Posted 3 September 2013 - 22:09
do we have DDP in PLi's OE ?
I think it is supposed to work, but since I haven't been able to passthrough/downmix e-ac3 on my solo2 (except in some very rare cases where I can get passthrough to work if I start timeshifting) I was suspecting buggy drivers from vu+.
The strange thing is that I believe it actually worked for a while a couple of months ago, but haven't had the time to verify if I was just hallucinating.
Regards,
n0dder
Edited by n0dder, 3 September 2013 - 22:10.
vu+ solo2, Pioneer SC-LX88, Pioneer KRP-500A
1W, 5E, 13E via 4:1 DiSEqC in Tuner A; 19.2E in Tuner B; DVB-T2 via PCTV Nanostick T2 (290e)
Re: merge requests for PLi's git #263
-
- PLi® Core member
- 46,969 posts
+541
Excellent
Posted 5 September 2013 - 16:24
DDP = Dolby Digital Plus aka ac3+?
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: merge requests for PLi's git #264
-
- PLi® Core member
- 8,458 posts
+327
Excellent
Posted 5 September 2013 - 19:16
Yes its AC3+
+ else if (!strcmp(type, "audio/x-eac3")) {
+ GST_INFO_OBJECT (self, "MIMETYPE %s",type);
+ bypass = 0x22;
+ }
I think we are using OpenPLi Xtrend dvbmediasink for VU+ right? But VU+ is using Dreambox dvbmediasink with patches!
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: merge requests for PLi's git #265
-
- Senior Member
- 1,982 posts
+247
Excellent
Re: merge requests for PLi's git #266
-
- Senior Member
- 1,982 posts
+247
Excellent
Re: merge requests for PLi's git #267
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 12 September 2013 - 10:52
please merge https://sourceforge....rge-requests/1/ and above patch for less png size
tested and they're ok
good luck
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #268
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 12 October 2013 - 21:43
"use simple Makefiles" for openpli's enigma2
tested and works ok (faster and more simple)
next patches will be for openpli's oe
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #269
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 12 October 2013 - 22:37
dreambox patch for openpli's oe (master branch = 3.0)
new kernel changes
new flash changes
dm500hdv2/dm800sev2 support
some other dreambox stuff
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #270
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 12 October 2013 - 22:58
enable ipv6 for python and add some extra python modules
(master branch = 3.0)
this is the last patch for now
also i sent merge requests on sourceforge
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #271
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 13 October 2013 - 17:04
did you take a look at the patches ?
you can apply Makefile.patch without take a look because it's just about Makefiles and works without problems
but i think you need some time for other 2 patches
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #272
-
- PLi® Core member
- 14,052 posts
+298
Excellent
Posted 13 October 2013 - 17:23
For openPLi3, don't send any more patches, all new development is done on OpenPLi 4 now (where Python already supports ipv6).
As for the makefiles, I'd prefer to only change them when needed, e.g. next time when something needs to be added. I have seen problems with this kind of wildacrd usage in Makefiles in the past, and adding a file to the makefile list might just help remember the authore to add it to version control as wel...
As for the dreambox patches, split them up into functional units please. It's way to much to sift out. For one thing, we're not planning on adding DMM "v2" support anytime soon.
As for the makefiles, I'd prefer to only change them when needed, e.g. next time when something needs to be added. I have seen problems with this kind of wildacrd usage in Makefiles in the past, and adding a file to the makefile list might just help remember the authore to add it to version control as wel...
As for the dreambox patches, split them up into functional units please. It's way to much to sift out. For one thing, we're not planning on adding DMM "v2" support anytime soon.
Real musicians never die - they just decompose
Re: merge requests for PLi's git #273
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 16 October 2013 - 15:54
so i guess it's not about contribution anymore it's about wishes
sorry i won't do it again
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #274
-
- Senior Member
- 51 posts
+5
Neutral
Posted 16 October 2013 - 16:01
Please take a look at my merge request too https://sourceforge....ge-requests/16/
it looks like it does not cause any trouble now, but the original approach there looks wrong
Re: merge requests for PLi's git #275
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 16 October 2013 - 16:04
Indeed, the string object will be destroyed as it goes out of the scope.
Re: merge requests for PLi's git #276
-
- Senior Member
- 51 posts
+5
Neutral
Posted 16 October 2013 - 16:13
and it is a bit silly to use std::string for a static string, we do not need any dynamic memory allocation there
Re: merge requests for PLi's git #277
-
- PLi® Core member
- 46,969 posts
+541
Excellent
Posted 16 October 2013 - 17:14
so i guess it's not about contribution anymore it's about wishes
sorry i won't do it again
Here we go again. GPL requires forkers to submit their patches, but it doesn't require the one being forked from to apply them.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: merge requests for PLi's git #278
-
- Senior Member
- 51 posts
+5
Neutral
Posted 16 October 2013 - 20:32
I think there is a possible bug in the hearingimpaired logic and here is the fix https://sourceforge....ge-requests/17/
Re: merge requests for PLi's git #279
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 16 October 2013 - 21:16
yes, hard to follow the logic, but looking at the symmetrics with the !defaultdvb counterpart, it must be a typo indeed.
Re: merge requests for PLi's git #280
-
- Senior Member
- 51 posts
+5
Neutral
Posted 16 October 2013 - 21:32
would be good to close merge requests if the code is merged
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
