Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 01 Apr 2020, 04:56
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
OLD: mpdPup - Simplified MPD Music Server/Jukebox - v0.9.2
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 31 of 31 [464 Posts]   Goto page: Previous 1, 2, 3, ..., 29, 30, 31
Author Message

Joined: 23 Oct 2009
Posts: 365

PostPosted: Sun 28 Oct 2012, 10:25    Post subject:  

Yeah, Puppy can be built from the binaries of a variety of distros. mpdPup specifically is built from Debian Squeeze, and in general Squeeze packages should work from a binary perspective, although on rare occasions the various config files and extras may wind up in the wrong place.

I'm not sure if you're running on hardware that's capable of running X, Puppy has a graphical package manager built in, no CLI options though. The package manager is configured to use the Squeeze repositories by default, but in it's stock state nothing is populated and it's not particularly intuitive about how to get it working. At some point I'll write up a proper article on using it, but here are the basics:
  • launch the Puppy Package Manager (right-click menu or 'ppm' from rxvt/terminal)
  • Click 'configure package manager'
  • Click 'Update Now'
  • Follow the various prompts at the terminal(s) that pop up and let it download the databases/do it's thing (this will take a little while)
  • Click 'OK' to close that window once it's done, then close and re-start the Package Manager
  • When it comes back up it will still be empty, but now there will be multiple 'repo' options across the top of the Window. Choose the various Debian options to browse those repositories.
  • Use the radios on the left to browse categories, or just use the search box on the lower left to find your package.
  • Single click on the package name to bring up an install window, follow the instructions

I'm pretty sure it doesn't take care of dependencies automatically, you may need to install multiple packages, you can find the dependencies through trial and error or by using the Squeeze package reference site.
Back to top
View user's profile Send private message 

Joined: 27 Oct 2012
Posts: 3

PostPosted: Sun 28 Oct 2012, 11:09    Post subject:  

Thanks for the package manager information, that will be helpful.

By the way, I had installed the wrong jack package. When I installed the package with the dev libraries, Brutefir compiled without problems.

Regarding running MPD -> Brutefir with pipe instead of Jack, it is much more difficult to get pipe output to work with Brutefir than using a Jack output to Brutefir. Also, the pipe output to Brutefir will strip off the ending of the last song in the playlist equivalent to whatever delay Brutefir has to run with (which depends on the size of your filters).

I also noted the following post by an MPD developer regarding why the pipe output is not enabled by default in MPD builds: "It is off by default because it is a hack, which does not match our quality standards. If users think that it should be turned on by default, then why not, but I'm not comfortable with supporting this plugin." So I guess Jack output is still preferable for Brutefir.

One more question... It seems most puppy builds do not support Firewire output. Do you have any plans to include Firewire in MPDPup?

Back to top
View user's profile Send private message 

Joined: 23 Oct 2009
Posts: 365

PostPosted: Sun 28 Oct 2012, 13:01    Post subject:  

Thanks for the info regarding Pipe, I hadn't personally tried it, just saw it mentioned on a number of boards - I might disable it in future mpd builds if it's basically broken. Does using Brutefir as an ALSA plugin have similar issues (assuming it's an option)? That's the method a few users have tried with Sox, more info several pages back in the thread.

Regarding Firewire, I've been supporting whatever is in the kernel, if there is a specific kernel module for Firewire Audio that is maintained outside the main kernel just point me to the source code and I'll look into adding it. I don't have any Firewire DACs so I wasn't aware.
Back to top
View user's profile Send private message 

Joined: 25 May 2012
Posts: 11

PostPosted: Wed 31 Oct 2012, 06:20    Post subject:
Subject description: WaveIO detection solved

Previously I had a problem with mpdpup not detecting my WaveIO usb interface on mpdpup power up.
This is now solved , it turned out to be very easy . The problem was solved by a bit of trial and error and almost no understanding – after looking on the waveIO forum a clue was seen, there was talk of using lsusb command to look at the usb bus.

This resulted in a list with the waveIO shown as ID 20a0 listed last as seen by testing with and without it connected . Simply re- locating the WaveIO with respect to the USB boot stick moved the waveIO to second last in the list and mpdpup auto detects it every time on start-up. The result of lsusb is now as below
There are only two items using the 3 USB ports on the PC. The last listed below is the USB boot stick. I have no idea what the others are with the same ID. Does this mean other items are sharing the usb bus ?

# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 20a0:4143
Bus 001 Device 003: ID 0204:6025

Happy that problem is solved, if it happens to others, just try re-positioning the waveIO on the USB ports . I tried too long before this was found .
Back to top
View user's profile Send private message 

Joined: 03 Nov 2012
Posts: 5

PostPosted: Sat 03 Nov 2012, 14:32    Post subject:  

Hi, really glad that someone as created such an easy linux hifi dstribution, many compliments.

I've just installed mpdPup on virtualbox, but I've found some problems.
I've configured a static IP, but MPDroid, on my smartphone, cannot connect to it and secondly, Puppy hasn't recognized the hdds connectd via sata port.

Do you think that these problems are caused by virtualbox?

Normally I use a dedicated music pc with a pci soundcard and an hdd connected via usb. Do you think this setup could have any problem?

Thanks, and many compliments again.
Back to top
View user's profile Send private message 

Joined: 23 Oct 2009
Posts: 365

PostPosted: Sat 03 Nov 2012, 14:48    Post subject:  

I've never tried using Virtualbox. I use VMWare fusion for most of my development, but I use real hardware for normal use. If Virtualbox is anything like VMWare you need to make sure you're in bridged mode vs. NAT'd mode, otherwise all your virtual machines will be hidden from the rest of the network - that would explain the Android problem.

No idea on the SATA problem, but since that's such a basic thing I would think it also relates to Virtualbox.

Lastly audio is quality is degredated pretty heavily by the numbers of abstractions the VM environment puts between mpd and the actual hardware.

A dedicated PC with a PCI soundcard should be ok, the only thing is if your music is on a USB drive then I don't recommend using a USB stick for booting from the same bus, as the drive enumeration can vary each time the system reboots. Better to boot from SATA for the OS and keep USB just for the audio library.

Last edited by ldolse on Wed 07 Nov 2012, 07:45; edited 2 times in total
Back to top
View user's profile Send private message 

Joined: 23 Oct 2009
Posts: 365

PostPosted: Tue 06 Nov 2012, 15:05    Post subject:  

I'm pleased to announce that I've finally wrapped up a new release. Posted on the Puppy Linux boards here. A lot of the changes are based on the trials and tribulations of the many users who have taken mpdPup for a spin, thanks for all your testing and feedback!

Some highlights:
  • Lots of newbie proofing, enhanced wizards, new drivers
  • easy access to advanced mpd/alsa/driver tweaks for audiophiles
  • Optional inclusion of GMPC and various Web GUIs for users who want a built in user interface and are less concerned with minimal functions. These are disabled by default to keep the hardcore people happy.
  • Updated versions of MPD and many clients/codecs

And a lot more - check the new thread below for a more complete changelog; this thread has gotten a little long in the tooth, time for a fresh start.

Go here:
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 31 of 31 [464 Posts]   Goto page: Previous 1, 2, 3, ..., 29, 30, 31
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1103s ][ Queries: 12 (0.0725s) ][ GZIP on ]