(old)Puppy Linux Discussion Forum

Glad to hear that worked! Now if I could only find a way to do it programmatically.

nrpacks is part of the wizard already - it gets set when you choose to use the 'recommended' settings instead of Linux defaults. If you go into the tweaks section or choose the advanced wizard you can specify what nrpack number you wish to use.

ldolse wrote:Hi All, thanks for trying it out.

@grunter, Sounds like a rather strange problem - you used the wizard to test the sound output during the initial configuration, correct? Did the sound come out from the right place at that time? The only way I can see it changing is if the hardware did funny things where the internal and external cards swapped positions when the system initialized. Anyway glad you were able to resolve it. In the future you can always type 'mpdwizard' to get back to any options to make changes to the system.

Yes, it's very strange cause during te wiazrd I was able to hear the sound form my dac and, after rebooting even if everything remain the same, mpdpup doesn't use the dac but the internal soundcard.
Thank you for the suggestion of mpdwizard. You didd really a god job.

I'm chiming in!
Just ran the 0.9.3 install wizards - excellent job, so much better than 0.9.2.

Did find the WaveIO muted but running the recommended CLI commands above and rebooting did the trick for me [Atom based D510 mobo].

Jonathan

I have now run through the 0.9.3 install and found the following issues that prevented playback (with remote GMPC):

1. WaveIO muted - but that's to be expected and probably the WaveIO board's fault
2. In mpd.conf
a. in audio_output - the line device showed "" whereas it should read "hw:1,0" in my case. THe WaveIO had been recognised and configured so that is strange.
b. buffer_before_play I had set to be 100% in the wizard, but the line in mpd.conf read "100%%"

Hope the above were not caused by my finger trouble, but I try to be careful with these things.

Anyone else had the same?

Jonathan

Idolse
Would be grateful for guidance on how to set SOX as the upsampler in mpdPup.

I see there is a section in mpd.conf for SOX output at the end with "enable=no" and my wizard entry for "176,400" correctly shown. Is it just a matter of "enable=yes"? Does one leave the main audio_output as is?

Many thanks
Jonathan

ldolse wrote:Glad to hear that worked! Now if I could only find a way to do it programmatically.

nrpacks is part of the wizard already - it gets set when you choose to use the 'recommended' settings instead of Linux defaults. If you go into the tweaks section or choose the advanced wizard you can specify what nrpack number you wish to use.

For integrating i'm of no help, too noob
Did not find them in the wizard because for some reason it hangs and returns to the initial page when i try to select the recommended setting, so only choice was the default. Not a big problem now that i've done them manually.

jrling wrote:Idolse
Would be grateful for guidance on how to set SOX as the upsampler in mpdPup.

I see there is a section in mpd.conf for SOX output at the end with "enable=no" and my wizard entry for "176,400" correctly shown. Is it just a matter of "enable=yes"? Does one leave the main audio_output as is?

Many thanks
Jonathan

When you use the wizard you just choose advanced instead of basic. If you've already done the initial configuration then you just type 'mpdwizard', select 'sound' and you'll find the configuration in one of those sub-menus.

Sorry Idolse,
I don't understand where and how I must change "tunes.local" with my IP static to view cover art... Can you explain me step by step? Thanks

I did choose the Advanced Wizard (great BTW) and gave my settings for SOX, and I got a new section at the end of mpd.conf for SOX.
However, I had assumed the "enable=no" in the SOX audio_output section meant that it was was not turned on?

SQ seems quite significantly better in my 0.9.3 set-up and apart from SOX which I am not sure is working, I chose the later version of MPD. Otherwise everything else was the same settings as 0.9.2.

I am certainly happy with that, but was curious as to why SQ improved!

Jonathan

PS Did you see my two reported wizard issues in an earlier posting? Don't know if they are of interest?

ldolse wrote:

jrling wrote:Idolse
Would be grateful for guidance on how to set SOX as the upsampler in mpdPup.

I see there is a section in mpd.conf for SOX output at the end with "enable=no" and my wizard entry for "176,400" correctly shown. Is it just a matter of "enable=yes"? Does one leave the main audio_output as is?

Many thanks
Jonathan

When you use the wizard you just choose advanced instead of basic. If you've already done the initial configuration then you just type 'mpdwizard', select 'sound' and you'll find the configuration in one of those sub-menus.

When you enable Sox a virtual sound device is created for each sample rate you choose. You need to use an MPD client which supports configuring the Audio Output (most do). You go into that section of the client, disable the primary audio output and enable one fo the Sox outputs.

Changing mpd.conf to enabled=yes is not really recommended - with that you'd probably be simultaneously enabling the default output + sox, and that could result in some weird behavior since both are trying to do different things on the same hardware interface. I wish MPD had a feature where you could tell it the underlying hardware for a sound card was the same across a set of cards so that it only allowed you to enable one, but it doesn't.

Hi Jonathan,

I did miss your post regarding the wizard behavior, thanks for pointing it out.

Just use 100 in the wizard instead of 100%. There is supposed to be logic which detects that, but apparently I need to fix it.

For audio_output, how many different audio_output sections/devices did you see in mpd.conf? What was the name of the one that had device set incorrectly? It would help immensely if you could tell me exactly what path you took through the wizard to create the settings - this has always worked fine for me, so you problably chose a route through the configuration that I didn't think to test.

kocozze wrote:Sorry Idolse,
I don't understand where and how I must change "tunes.local" with my IP static to view cover art... Can you explain me step by step? Thanks

Hi Kocozze, Sorry I missed this before - Looks to me like MPDroid works a bit differently than other MPD clients according to their Github page:
https://github.com/abarisain/dmix/wiki/Album-Art-on-your-LAN

If that page is correct you just need to find the settings in MPDroid and set the following two items:
Path to music: Should be 'musiclibrary' - no quotes, when using mpdPup
Cover filename: Whatever you name your Album art file - e.g. 'folder.jpg'

Hi, I'm encountering several problems with the installation of mpdPup on my music-pc and it's strange since I had no problem on a virtualmachine.

I cannot get internet connection, even if it says that the DHCP connection has been established, I cannot configure a static IP and at the startup it says "making the filsystem usable...depomd failed".

acvtre wrote:Hi, I'm encountering several problems with the installation of mpdPup on my music-pc and it's strange since I had no problem on a virtualmachine.

I cannot get internet connection, even if it says that the DHCP connection has been established, I cannot configure a static IP and at the startup it says "making the filsystem usable...depomd failed".

Sounds like the hardware may have some compatibility issues. What sort of hardware are you using?

A mobo intel d945gsejt, with d-link dwa140 for wifi connection, external usb hdd and a soundcard onkyo se-200.

Puppy installed on a transcend 4gb CF linked via 44pin cable to the mobo.

acvtre wrote:A mobo intel d945gsejt, with d-link dwa140 for wifi connection, external usb hdd and a soundcard onkyo se-200.

Puppy installed on a transcend 4gb CF linked via 44pin cable to the mobo.

Well the good news is it shouldn't be the motherboard, since I use the same board. That said none of the other components are common between us.

• You probably need to do some research on each of the other components you chose and see if there are any Linux compatibility issues. Google is your friend.
• Your Wifi card may have some conflicts with other drivers and somewhat poor linux compatibility - follow the blacklisting instructions here: http://www.murga-linux.com/puppy/viewtopic.php?t=6362, and/or here: http://ubuntuforums.org/showthread.php?t=1638334.
• I haven't done any work around supporting Wifi from the MPD Wizards. Puppy Linux does have Wifi support, but you'll need to launch the Puppy Linux Network Wizard before you run the MPD wizards to set an IP and wireless settings. If you got DHCP to work you can stick with that and access the sytem by it's hostname - tunes.local. You just need bonjour/avahi/zeroconf/mdns (all words for the same thing) on your client system.
• The Onkyo uses the same Chipset as the ESI Juli@, so it's probably ok, but it doesn't look like there are a lot of users out there using it with Linux

idolse,

Long time lurker enjoying ur MPD a lot.....with my 30$ small PC from ebay .Just wanted to thank you for this new release i just want to thank you for this release.

Thanks
V

ldolse wrote:Well the good news is it shouldn't be the motherboard, since I use the same board. That said none of the other components are common between us.

• You probably need to do some research on each of the other components you chose and see if there are any Linux compatibility issues. Google is your friend.
• Your Wifi card may have some conflicts with other drivers and somewhat poor linux compatibility - follow the blacklisting instructions here: http://www.murga-linux.com/puppy/viewtopic.php?t=6362, and/or here: http://ubuntuforums.org/showthread.php?t=1638334.
• I haven't done any work around supporting Wifi from the MPD Wizards. Puppy Linux does have Wifi support, but you'll need to launch the Puppy Linux Network Wizard before you run the MPD wizards to set an IP and wireless settings. If you got DHCP to work you can stick with that and access the sytem by it's hostname - tunes.local. You just need bonjour/avahi/zeroconf/mdns (all words for the same thing) on your client system.
• The Onkyo uses the same Chipset as the ESI Juli@, so it's probably ok, but it doesn't look like there are a lot of users out there using it with Linux

I was using this same configuration on voyage and I had no problem, except that configuring voyage is a pain in the ass.

My client is a android phone, what do you suggest for it?
Is it possible that the problem is the CF? I had to reinstall puppy with unetbootin at least 10 times before having it working.

What other wifi card would you suggest? On voyage I simply had to install its drivers.

ldolse wrote:

kocozze wrote:Sorry Idolse,
I don't understand where and how I must change "tunes.local" with my IP static to view cover art... Can you explain me step by step? Thanks

Hi Kocozze, Sorry I missed this before - Looks to me like MPDroid works a bit differently than other MPD clients according to their Github page:
https://github.com/abarisain/dmix/wiki/Album-Art-on-your-LAN

If that page is correct you just need to find the settings in MPDroid and set the following two items:
Path to music: Should be 'musiclibrary' - no quotes, when using mpdPup
Cover filename: Whatever you name your Album art file - e.g. 'folder.jpg'

Hi idolse, thank you very much...now it's work very fine!!!

acvtre wrote:I was using this same configuration on voyage and I had no problem, except that configuring voyage is a pain in the ass.

My client is a android phone, what do you suggest for it?
Is it possible that the problem is the CF? I had to reinstall puppy with unetbootin at least 10 times before having it working.

What other wifi card would you suggest? On voyage I simply had to install its drivers.

I doubt it's the CF card - Unetbootin has occasionally been problematic for me as well, but as it generally works it's been low on my priority list to investigate - there are some alternatives to it, not sure if one of the other projects is any better.

For Android I think MPDroid is the best game in town, though that's just based on what I've read/heard, not first-hand experience.

The depmod errors specifically relate to some sort of driver issue, so I would guess based on those links I gave you that the Wifi card is the most likely culprit. If you had it working on Voyage then you can definitely get it working on Puppy Linux as well, it's just that the two distributions get built in very different ways.

What drivers did you have to install on Voyage? If they're in the Debian package repo (which is what Voyage uses), then you should be able to install them on mpdPup with the Puppy Package Manager. What I'm distributing is generally the stock Linux kernel drivers - if the hardware vendor or some other team maintains their drivers outside of the kernel tree then I only fix those as people point them out to me.

I don't really have any recommendations regarding other Wifi hardware, I never use it with Linux, so can't comment.