Jump to content


Photo

add in minidlna server dsd support

minidlna dsd iso

  • Please log in to reply
36 replies to this topic

Re: add in minidlna server dsd support #21 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 13 April 2019 - 19:41

It seems DSD is a audio codec. Never heard of it.


DSD is the format used by the "super audio CD", which fortunately never became very popular.

It's based on proper sampling theory and mathematics, but misrepresented to the public as if it were in some way superior to regular PCM. The truth is that all analog-to-digital and digital-to-analog converters in (and around) the audio domain use it as an intermediate format before the final analog stage. This is also known as "oversampling", for a while you'd commonly find things like "128x oversampling" on a CD player, while it's just a modern way of doing digital-to-analog conversion ("modern" means that it's cheaper and usually provides better quality than direct PCM would).

The "misrepresentation" is that it's implied that inaudible frequencies (for humans, above 20kHz, unless you're my age in which case it'll be more like 15kHz) somehow might contribute to the sound. Just like you cannot see ultraviolet light, you cannot "hear" or otherwise observe ultrasone frequencies, even up to the point that the energy of the emitted waves will actually physically harm you.
Real musicians never die - they just decompose

Re: add in minidlna server dsd support #22 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 19 April 2019 - 11:42

dlna is not only for video but also for pictures, this allows you to rescale the image on the server before sending it to remote device.

Yes, and I think this is wrong to transcode. Pictures used to be in lossy coding format (for example jpeg). These shouldn't be cascade coded (lossy coded more than once), because of artifacts (bad quality). I think it is bad to let the server rescale photos, because the device who best know how to do is the device with the display (i.e. client). The client might also want to zoom. ...well I hope transcoding will be keept out from readymedia, or be able to disable with build settings. I don't think it belong in OpenPLi.

I have begin to make changes to the DLNAServer plugin. Hopefully it comes out something useful.

Re: add in minidlna server dsd support #23 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 20 April 2019 - 17:11

Now I learn something new, GSOD = Green Screen Of Death !

I'm new to python and mixed some data types. However quick fixed and my changes seems to work.
Now it can look like the attached files. I have added "Use browser directory as root" and possible to have only one folder.

However selecting folder behave strange (I haven't changed any in that code). Let me see if I can fix it. It is also not possible to change the name.

If call "print" in the python code, where comes the text?

Attached Files



Re: add in minidlna server dsd support #24 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 20 April 2019 - 18:03

Start Enigma in foreground and debug mode:

init 4
ENIGMA_DEBUG_LVL=4 enigma2

you can stop it via any restart menu option, or by pressing Ctrl-C. You can go back to daemon mode with

init 3

Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: add in minidlna server dsd support #25 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 20 April 2019 - 19:20

You could use our mirror: https://github.com/O...sionE2/minidlna

 

which is with dsd support and soon I will add some other patches too.


Open Vision sources: https://github.com/OpenVisionE2


Re: add in minidlna server dsd support #26 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 21 April 2019 - 22:02

To change directory have two problems. First it is unclear for the user what is happen. Entering the dialog, the directory will change. This is confusing. The reason is that the filelist will enter the current directory and select the top most item. In many times this is the parent directory. So the parent directory will be default at open the dialog. This is unclear for the user. It took me a while to realize this. However maybe not a big thing. But maybe the name of the current directory (which contents is visible in the file list) should be written in the dialog. Only the selected directory is written.

The second problem is that the FileList component doing wrong if the directory passed to it isn't ending with "/". It will jump up one directory level. So I made a change so the directory config strings are always ending with /. The readymedia process can handle this.

Have also make it possible to change the server name, by help of VirtualKeyBoard.

While running the DLNAServer dialog it appears some messages...

[ActionMap] Keymap 'DirectionActions' -> Unknown action 'upUp'! (Typo in keymap?)
[ActionMap] Keymap 'DirectionActions' -> Unknown action 'downUp'! (Typo in keymap?)
[ActionMap] Keymap 'WizardActions' -> Unknown action 'up'! (Typo in keymap?)
[ActionMap] Keymap 'WizardActions' -> Unknown action 'down'! (Typo in keymap?)
[ActionMap] Keymap 'WizardActions' -> Unknown action 'right'! (Typo in keymap?)
[ActionMap] Keymap 'SetupActions' -> Unknown action 'right'! (Typo in keymap?)

[Skin] Error: {PLi-FullNightHD/skin.xml}: color 'window-fg' must be #aarrggbb or valid named color. Please contact the skin's author!

(this last message comes because of VirtualKeyBoard, I think)

Is this normal, or something wrong?



Re: add in minidlna server dsd support #27 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 5 May 2019 - 11:39

Hello again! Time to finish this, sorry but I do other stuff in life also.

 

The DLNAServer plugin is today taken from git://code.vuplus.com/git/dvbapp.git and have two patches applied. Now I have fixed some things and add more settings. I think it is strange to keep connection with this dvbapp repo,since the source haven't been changed for 7 years. If someone change it, our patches will propably not work. So would it be okay to take a copy of this source (it is only one small file) and have it in OpenPLi repo?

 

However in the current place in the openpli-oe-core repo it is only recipes that take sources from other places, so maybe the DLNAServer in such case should be placed elsewhere. Maybe in OpenPLi enigma2-plugins repo?

 

 

We also need to decide about default configs of directories in readymedia service and DLNAServer plugin. I was thinking about /media/hdd/movie, however not all boxes have hdd. So maybe only /media, but how about the log file? Warnings can be good to see, however several TVs will create warnings - so default need to be error. Maybe that should be off by default, then no risk for big log file. If the user have problem, they need to switch on log and troubleshoot.

 

Please tell me your thoughts about this.



Re: add in minidlna server dsd support #28 Pr2

  • PLi® Contributor
  • 6,074 posts

+257
Excellent

Posted 6 May 2019 - 10:03

The right place to place settings is:  /etc/enigma2/  and since it is a plugin integrated with E2 you can use the same mecanism as other plugin does that insert configuration parameters into /etc/enigma2/settings file.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: add in minidlna server dsd support #29 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 6 May 2019 - 15:55

The plugin have one own setting and that is already located in the E2 settings file.

The readymedia daemon have a configuration file (minidlna.conf). It is located in /etc.

I have no plan to change these.

 

The question is for the database file och log file. Suggestions from me...

 

Database file: /var/lib/readymedia

This is actually where it is today. I now looked around and found that other modules put files below /var/lib, so maybe a good place.

 

Log file: /var/volatile/tmp

This is the same as /tmp and here is some other log files. This place is in ram disk. I also propose that the log is switched off by default.



Re: add in minidlna server dsd support #30 rantanplan

  • PLi® Contributor
  • 1,806 posts

+83
Good

Posted 6 May 2019 - 16:56

This is all very simple, but is unnecessarily complicated here.
That you do not like any database, which is also used otherwise is ??

Take the current minidlna version from the OE  and copy it into your own multimedia or connectivity directory.

https://github.com/o...imedia/minidlna

Then you just change the path towards minidlna.bb instead of the already misleading readymedia.bb

https://github.com/k...294b600ccec4890



Re: add in minidlna server dsd support #31 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 6 May 2019 - 19:49

Of course the database is wanted. The thing was that I earlier propose to put it on the harddisc. However not all boxes have harddisc. I now also think it isn't good to have it on harddisc, since it can take time to wake it up and this will delay the responce for the user browsing DLNA. So sorry, forget about the discussion on where the db file should be.

 

You refer to minidlna. That is the old name. The name is now readymedia. So we already using newer.

 

The purpose of what I do is to add functionality.

 

PS. I don't do it for me. I have it already running and for me I actually don't care about the DLNAServer plugin. I can handle it at the command prompt with nano directly towards readymedia conf file. However others might want it also. The thread creator wanted dsd support (I don't), so that's why I update readymedia. ...however I might want to put in new functionality into readymedia and so it would be good it is up to date.



Re: add in minidlna server dsd support #32 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 6 May 2019 - 22:35

I now realize that the new source (for ReadyMedia) don't use the name readymedia anywhere. It is still called minidlna (and minidlnad). The name readymedia in any file is introduced in OpenPLi.

 

Now both minidlna and readymedia exist. The readymedia is the one that is used by DLNAServer and is the one that works. However, both are old. As written before in this thread, it seems like the readymedia is the new one and should be used. But should we really do so? Maybe we should remove readymedia and update minidlna. If we go for minidlna, I think we should keep what was introduced with readymedia (i.e. DLNAServer plugin).

 

I'm new here, so I need advice. Is this something that OpenPLi team can discuss and decide, or how do we continue.



Re: add in minidlna server dsd support #33 Pr2

  • PLi® Contributor
  • 6,074 posts

+257
Excellent

Posted 7 May 2019 - 11:13

You can propose a default location for the DB but then let people be able to configure where they want to have it really set.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: add in minidlna server dsd support #34 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 12 May 2019 - 00:11

The DB location is not possible to configure in the plugin and I have no plan to include that. However possible to change in the conf file (the plugin doesn't change it).

About the plugin. When I testing I realize how Reset works. It set back to the previous value, before user right now change. However this is easy done by Exit instead and open the plugin again. I think this is more normal todo. If begin do changes and regret, just Exit without saving. I think the Reset should instead set decent values (hardcoded default values). Because when if the user have tested around a lot, it would be possible to get back the default values. Today this is impossible (after a Save).

I was thinking about to skip readymedia and instead update minidlna. However it is located in meta-openembedded and I don't think I can nor should change in that repo.
So now I thinking about to keep readymedia where it is.

About the plugin. I would like to take a copy of the source and have the source in one of our repo. First I thought about enigma2-plugins. However I notice it is a different structure there. No bb files for each plugin, instead Makefile.am files. It also seems like these plugin doesn't have runtime dependency to other module. The DLNAServer plugin have a runtime dependency. So if it is build/installed another ipk package needs to be built/installed. So now I hope it will be okay to keep it where it is, but create new files and change recipe.

How about quote of strings in python, double " or single ' ? It is a mix in this plugin. First I thought it might be a logical explanation, but not. So I thinking about to change to double quote all over, except at a one char comparison.

I will summarize my changes and package them nice. We will see if you like it.



Re: add in minidlna server dsd support #35 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 13 May 2019 - 14:32

Aren't there any other sources? We hate to use sourceforge, its availability is very flaky, and when the repo can't be reached, it breaks our automatic build process.


This seems to be the origin place of the source, with development.


Yes, it is. But the problem is that bitbake bails out when it can't fetch a source. Even if it has a local copy in it's source cache it can use.

We run hundereds of builds daily, automated and unattended. Monitoring, checking, and manual restarting when fetch issues happen is a full time job we can do without... ;)

If there is no other option, we'll have to setup a mirror ourselfs, to avoid build issues...


How is it if the recipe will take a specific commit (or tag) and PV and PR will be constant. Will this give less access to sourceforge? If so, can we accept it as a solution?



or should we take from here:
 

You could use our mirror: https://github.com/O...sionE2/minidlna
 
which is with dsd support and soon I will add some other patches too.


I don't know if this is a copy or a mirror (i.e. updated with new things from originate source at sourceforge).

Re: add in minidlna server dsd support #36 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 13 May 2019 - 14:54

How is it if the recipe will take a specific commit (or tag) and PV and PR will be constant. Will this give less access to sourceforge? If so, can we accept it as a solution?

 

No, bitbake will always access the source repository, if only to check the version. Even if you already have that version in your local source cache. And bitbake will bail out with a build error if that repo is unreachable. 

This is why it is such a pain, especially if you have a build run with 70-odd machines that runs for 14-16 hours, which aborts because of this.

 

I don't know if this is a copy or a mirror (i.e. updated with new things from originate source at sourceforge).

 

I have less problems with a github mirror, as long as it is actively maintained. 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: add in minidlna server dsd support #37 -M-

  • Senior Member
  • 128 posts

+4
Neutral

Posted 13 May 2019 - 20:20

I don't know the purpose of OpenVisionE2/minidlna repo. If it always will be a mirror, or if they will go their own way in the future. Maybe @Persian Prince can tell us?

 

Should we take the latest version (last commit at build time), or select the latest commit that exist now?

If we select a specific commit, we will be protected against big changes that we might not want. However we don't get fixes and new functionality automatically. However OpenVisionE2 is also STB software, so I think what they make we can use also. However right now I actually apply a patch. If future changes, the patch might fail.


Edited by -M-, 13 May 2019 - 20:21.



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users