(old)Puppy Linux Discussion Forum

Posted: **Thu 17 Jan 2013, 00:15**

I'm not sure exactly what you mean by this statement:

bonalux wrote:if i try to run the wizard, it cannot recognise the server folder

Specific descriptions of exactly what you're seeing help immensely.

Can you ping your fileserver from the command line?

If you can't figure it out at all you could try starting from scratch by deleting your savefile from another system - it's the .2fs file on the flash device. This will put things back in a virgin state and you can start over.

Posted: **Thu 17 Jan 2013, 00:36**

@Bonalux

Sounds like a hardware issue.

If MPDPup works fine from another computer 'untouched' but does not on another then it should not be the software.

run mpdpup in the machine that is having the problem, then from another machine check the router to see if the machine actually has network connection and an IP address. Confirm that IP address in the client too.

BTW, are you using any tweaks?

Posted: **Thu 17 Jan 2013, 15:58**

ldolse wrote:I'm not sure exactly what you mean by this statement:
bonalux wrote:if i try to run the wizard, it cannot recognise the server folder
Specific descriptions of exactly what you're seeing help immensely.

Can you ping your fileserver from the command line?

I wasn't clear, when i run the wizard, the first step asks for IP, share name and folder, i fill the fields and go ahead, i leave blank password and user fields because there is not a pwd and OK, then after some passages it asks to verify if it can mount the shared folder, i say yes but it cannot find it (unable to mount the smb share). Parameters checked trice and the same parameters are working with the other installation (that is on a different usb key and pc).

This evening when home i try to ping the nas to see what happens. i don't think it's a hardware problem because i can acces the alix for configuration etc... so the net it's ok.

Thanx a lot to all.

Posted: **Fri 18 Jan 2013, 08:44**

Don't ask me why but today i've tried reinstalling all and now it's working again

Only difference from last effort was that after every mod at config (first auto wizard, changing mpd version, unmuting waveio in alsa and doing usbnrpack mod) i've rebooted and waited a little before continuing (the first reboot i've waited till the database rebuild was done).

Don't have the time and patience to retry again and see if it works because of this procedure or not

sorry.

Thanks to all for the support.

Posted: **Fri 18 Jan 2013, 14:20**

Is there a way (command line or other) to tell what version of MPD I'm currently running? When I go back to mpdwizard it always defaults to 0.16 and I want to be sure I'm using 0.17.

Posted: **Fri 18 Jan 2013, 19:53**

Dynobot wrote:Open question.

From what I understand 64bit operating systems are more efficient and able to process more data per CPU cycle or something like that....

Is it possible or even worth the effort to build a 64bit version of MPDPup?

Even though MPD itself is not 64bit there is a 64bit version of alsa [which actually does the handling of data]....

I also think that going forward it might be a good idea that for those like myself who want tweaks to get incorporated into MPDPup to provide a link and data/explaination, source etc to back up or quantify the tweak.

Going forward I will make sure I do just that...

Good idea about providing source/explanation for suggested tweaks.

Have to say that if ldolse is prepared to do so, an ARM version of mpdPup would I guess be quite a lot in demand. There are a number of excellent ARM-based SOC boards out there at very reasonable prices.

Posted: **Fri 18 Jan 2013, 19:54**

clar2391 wrote:Is there a way (command line or other) to tell what version of MPD I'm currently running? When I go back to mpdwizard it always defaults to 0.16 and I want to be sure I'm using 0.17.

try

mpd --version

from the command line.

Posted: **Fri 18 Jan 2013, 20:53**

ldolse wrote:
Regarding processes renicing - the extra info on discovering which processes to renice is perfect - better setting of nice values is something I've wanted to get working properly for a long time.

ldolse

I wondered if you had any suggestions for other processes that directly contribute to audio output, that would benefit from higher priority setting?

Conversely, I noted in my set-up that the following are all set to 'nice -20' being the highest priority setting, and wondered whether any need to be for highest music quality, or could be downgraded in priority?

1 S 0 11 2 0 61 -20 - 0 - ? 00:00:00 cpuset
1 S 0 12 2 0 61 -20 - 0 - ? 00:00:00 khelper
1 S 0 15 2 0 61 -20 - 0 - ? 00:00:00 kblockd
1 S 0 16 2 0 61 -20 - 0 - ? 00:00:00 ata_sff
1 S 0 23 2 0 61 -20 - 0 - ? 00:00:00 xfs_mru_cache
1 S 0 24 2 0 61 -20 - 0 - ? 00:00:00 xfslogd
1 S 0 25 2 0 61 -20 - 0 - ? 00:00:00 xfsdatad
1 S 0 26 2 0 61 -20 - 0 - ? 00:00:00 xfsconvertd
1 S 0 35 2 0 61 -20 - 0 - ? 00:00:00 kpsmoused
1 S 0 727 2 0 61 -20 - 0 - ? 00:00:00 loop1
1 S 0 826 2 0 61 -20 - 0 - ? 00:00:00 loop0

Many thanks

Posted: **Sat 19 Jan 2013, 10:48**

I also note that MPD's process is running at Nice setting 0 (Zero). Would it benefit from moving to say -19 or -20?

Posted: **Sun 20 Jan 2013, 05:04**

I really don't know any more about which proceses do audio than what's been contributed to this thread thus far. MPD's nice value is currently the default. I had previously launched it using nice -15, but that was causing a problem on some person's hardware so I reverted that. I'll use renice in the next release. Not sure what the best value is, but -20 seems like overkill - need to make sure other processes get what they need when they need it - not that there aren't plenty of CPU resources.

@bonalux, glad you got it working

@clar2391 - the wizard always highlights 0.16, didn't add extra logic to check the current version, will do that to avoid confusion in the future.

Posted: **Sun 20 Jan 2013, 15:23**

ldolse - I am happy to do some experimental on my system. Of course, we are getting into system-specific territory and the preferable solution no doubt for those with dual-core processors like me is to have MPD running on its own separate core - as suggested by Dynobot but requiring some utilities to be included in the build to achieve.

A couple of questions if I may -

1. Is there a config file that can be edited to change the default Nice setting of MPD at boot time?
2. If not, can you let me have the command line that will search for the MPD PID No, return the value and then apply that value to a 'renice PID xx -19' in the script file I am using to apply different Nice values to processes, as per my previous postings.

Many thanks

Posted: **Mon 21 Jan 2013, 16:43**

jrling wrote:1. Is there a config file that can be edited to change the default Nice setting of MPD at boot time?

No - not today. This is how I plan to implement the function though.

jrling wrote:2. If not, can you let me have the command line that will search for the MPD PID No, return the value and then apply that value to a 'renice PID xx -19' in the script file I am using to apply different Nice values to processes, as per my previous postings.

You could try something like this

Code: Select all

ps -ef | grep XYZ | grep -v grep |  awk '{ print $2 }'

- replace XYZ with the process name you want.

Posted: **Mon 21 Jan 2013, 21:04**

Thanks ldolse

I found this command to renice by name rather than PID No. -

renice XX -p $(pidof <name>)

and it seems to work!

Posted: **Sat 26 Jan 2013, 22:13**

Can you share with us some of your plans for the next version of mpdpup...the last one was already absultely stunning...I am looking forward to the next one very much....

Posted: **Sun 27 Jan 2013, 07:23**

multiblitz wrote:Can you share with us some of your plans for the next version of mpdpup...the last one was already absultely stunning...I am looking forward to the next one very much....

The next one will primarily just be about further refinement of the last one. It will still use the same kernel and base os as the last version. Jumping to a new kernel is going to be a big project and I'd like to get some of the current requests/problems resolved first.

Here are the things I've been thinking about:

final fix for unmute, nrpacks
0.17 by default, remove 0.16 (my personal issue was finally isolated to a bad power supply)
Renicing/priority tweaks discussed over the last few pages, enable mmap
fix albumbler so that it can finally be used from remote control on bootup
update mpd, mpdlcd, hiface drivers
CIFS credential handling suggestion
add playlist/radio hotkey programming to empcd (this might be a stretch, I need to learn a bit more C to do this right)
Add libexiftool and start working on scripts to extract album artwork from metadata as well as automatically fixing filenames based on metadata

Posted: **Mon 28 Jan 2013, 23:26**

HI Idolse, Hi all

* suggested evolution (for the dumbs possibly

)
- at boot, error message if ethernet unavailable
- at boot, error message if remote file server unavailable
- option to display the cover art on the device (eg I use a NetBoot as my server with Mpod remote control but would find it great to have a permanent display with a large size)
- use a rating for titles/album in the mpd database

* more general question : i use Mpod and Mpad on Apple devices but find these clients very limited, specifically the display of long titles or album names. What are good alternatives ?

I have not upgraded until now but already very happy !

Jean-Louis

Posted: **Thu 31 Jan 2013, 11:23**

Hi!
I have been using MPD puppy for some time, and I am very happy for the labor that has been put into this software. Thank you.

I have a question. I don´t know but maybe the information about this are to be find in the forum somewhere, but there is a lot of posts to read through.
Anyway. My question is simple. If I play a - say 24 bit 96 kHz file. Do MPD pup any resampling to 16 bit 44,1? Or is the file sent to the DAC in it´s original bit and samplerate? I am asking, because when running my DAC under Windows it only accepts maximum 16 bits and 48 kHz. Running under MPD puppy there is no problem playing 24 bits 96 kHz, but is this due to resampling taking place?

Best Regards

Posted: **Thu 31 Jan 2013, 11:33**

@ Jean-louis - I'll try to implement some of those suggestions - some straightforward, others are easier said than done.

Regarding MPoD/MPaD, I'm not aware of any good alternatives for iOS. Best option might be to try some of the PHP clients in the iOS Safari browser.

Magellan wrote:I have a question. I don´t know but maybe the information about this are to be find in the forum somewhere, but there is a lot of posts to read through.
Anyway. My question is simple. If I play a - say 24 bit 96 kHz file. Do MPD pup any resampling to 16 bit 44,1? Or is the file sent to the DAC in it´s original bit and samplerate? I am asking, because when running my DAC under Windows it only accepts maximum 16 bits and 48 kHz. Running under MPD puppy there is no problem playing 24 bits 96 kHz, but is this due to resampling taking place?

Hi, glad to hear it's been working for you. The behavior depends on your Sound device/DAC. When it's initialized it tells ALSA what bitrates it supports. If you play a bitrate that the DAC doesn't support then it will be resampled to a bitrate that your DAC does support. This behavior can be disabled, but if you do that it means you won't be able to play back content at bitrates your DAC doesn't support.

Posted: **Thu 31 Jan 2013, 11:55**

ldolse wrote:
Magellan wrote:I have a question. I don´t know but maybe the information about this are to be find in the forum somewhere, but there is a lot of posts to read through.
Anyway. My question is simple. If I play a - say 24 bit 96 kHz file. Do MPD pup any resampling to 16 bit 44,1? Or is the file sent to the DAC in it´s original bit and samplerate? I am asking, because when running my DAC under Windows it only accepts maximum 16 bits and 48 kHz. Running under MPD puppy there is no problem playing 24 bits 96 kHz, but is this due to resampling taking place?

Best Regards
Hi, glad to hear it's been working for you. The behavior depends on your Sound device/DAC. When it's initialized it tells ALSA what bitrates it supports. If you play a bitrate that the DAC doesn't support then it will be resampled to a bitrate that your DAC does support. This behavior can be disabled, but if you do that it means you won't be able to play back content at bitrates your DAC doesn't support.

My USB DAC also accepts SPDIF. I know it accepts 24 bit 192 kHz over SPDIF. I am not sure however, if it also accepts the same bit- and samplerate over USB. I guess the most simple way to test this is to disable the resampling function in ALSA. Is this covered in the graphic configuration tool, or do I have to perform some command line exercise?

Posted: **Thu 31 Jan 2013, 12:02**

Magellan wrote:My USB DAC also accepts SPDIF. I know it accepts 24 bit 192 kHz over SPDIF. I am not sure however, if it also accepts the same bit- and samplerate over USB. I guess the most simple way to test this is to disable the resampling function in ALSA. Is this covered in the graphic configuration tool, or do I have to perform some command line exercise?

16/48 over USB is a strange limitation if the SPDIF supports up to 24/192. Usually the limitations are based on what class of USB audio the DAC supports - Class 1 is limited to 24/96, Class 2 can go up to 24/192. 16/48 is generally only seen for really inexpensive/old sound devices which were designed for computer only usage (as 16/48 has historically been the default computer bitrate)

Disabling auto-resampling isn't covered in the Wizard, as it's not something a user would typically do. It would probably require editing some ALSA files as well as mpd.conf, I'm not 100% sure on what the steps would be. It would probably be easier to just Google the model of your DAC and see what the USB interface supports.

Info on mpd.conf edits here: http://mpd.wikia.com/wiki/Tuning

(old)Puppy Linux Discussion Forum

mpdPup - Simplified MPD Music Server/Jukebox - v0.9.3

MPD Version

Re: MPD Version

Evolutions

Resampling

Re: Resampling

Re: Resampling

Re: Resampling