Getting behind on my replies here...
@Denis, Sorry I can't provide tons of help on this remote support - I'll need to pick up some cheap USB sensors/remotes to see if I can figure out what's going on. You were on the right track with the udev rules though. Maybe it's showing up as a slightly different device during the boot process and missing those rules you created - try checking dmesg and lsmod to see what has been loaded after a clean boot. The XWindows bit is mystifying to me - not sure what it's doing to the inputs to 'fix' the system.
@kocozze, Spotify can be listened to but you need to use the command line to do it, it's far from intuitive. It also needs spotify premium to work. I don't believe Grooveshark is supported at all. Generic streaming radio is much easier to deal with.
@thisvv, I'm not sure what's going on, and it's a bit difficult to tell from your description what the problem is. Maybe try making changes from the CLI instead of the command line? What exactly are you trying to change?
mpdPup - Simplified MPD Music Server/Jukebox - v0.9.3
No Hd sound
Hi Idolse
Thank You or big work and helping .... just a question please:
Mpdpup is working fine on Hiface Two usb soundcard playing 16/44 audio files only. But No Hd audio file (24/88,96,192) is possible to play on MpdPup!
Soundcard and Dac support 24/192 but hd flac files not start. Something went wrong in configuration? Help me please. Regards
Thank You or big work and helping .... just a question please:
Mpdpup is working fine on Hiface Two usb soundcard playing 16/44 audio files only. But No Hd audio file (24/88,96,192) is possible to play on MpdPup!
Soundcard and Dac support 24/192 but hd flac files not start. Something went wrong in configuration? Help me please. Regards
I think I found out what's wrong. Seems like empcd can't (re)start automatically - my event is called "irremote0", and it seems that the path is too long (as it says in the empcd.conf). Once I (re)start empcd manually, everything works.ldolse wrote: @Denis, Sorry I can't provide tons of help on this remote support - I'll need to pick up some cheap USB sensors/remotes to see if I can figure out what's going on. You were on the right track with the udev rules though. Maybe it's showing up as a slightly different device during the boot process and missing those rules you created - try checking dmesg and lsmod to see what has been loaded after a clean boot. The XWindows bit is mystifying to me - not sure what it's doing to the inputs to 'fix' the system.
I'll see what I can do to start empcd manually, by invoking "/usr/sbin/empcd" when the machine is started. What would be the best way? I've tried adding it to "profile", but it seems like it's not a good way
Any other idea about starting empcd automatically (and properly)? I'll try changing the name of my event , or just leaving it as "event4"...
Thanks,
Denis
BTW, Idolse, can you contact me at denple@gmail.com ?
I think I might have a hardware donation for you
Also, I can offer help in documenting the mpdPup project, like writing a manual, etc. (I've already written a manual in Croatian....)
THX,
Denis
I think I might have a hardware donation for you
Also, I can offer help in documenting the mpdPup project, like writing a manual, etc. (I've already written a manual in Croatian....)
THX,
Denis
OK, looks like I sorted out the problem with the remote.
First, I had to add another command to /etc/rc.d/rc.local:
Namely, the default command for starting empcd (file "30.empcd" in /etc/init.d) doesn't seem to work - I'm not sure why...
First command (sleep 10) seems to be necessary - the remote has to wait for MPD to start cleanly, otherwise it won't start properly - this could be even "sleep 15" or "sleep 20", just to be on the safe side.
After finding out which "event" in /dev/input belongs to remote sensor, I was able to see which button does what by using command "empcd -y 9 -f" (prior to that I edited "/etc/empcd.conf" by selecting the proper "event" - in my case it was the line:
After that, I noted the button codes, and edited the "empcf.conf" appropriately, using the key codes I got in the step above.
THEN came the real pain in the behind:
I wanted to make sure the remote sensor is always mapped to appropriate symlinked "event", which I called "ir0".
If I use the default "eventX", it sometimes happens (particularly if I remove or add another USB device, e.g. USB DAC) that the event numbers get shuffled around - so, it's not a good idea to use e.g. "event4" - because it can sometimes be "event5"
After a LOT of reading, and a lot of trial and error, I managed to write a proper udev rule, which now always maps the USB remote sensor to "/dev/input/ir0", regardless whether it is attached to "event4" or "event5" - or whatever. Well, at least it seems to work - most of the time
Took me quite a while to find out the unique string to use as identifier for the udev rule - I finally used "Phys" key, which I got by using command "cat /proc/bus/input/devices"....
To cut the long story short, it was an arduous journey
But, I think I got the USB remotes sorted out now.... mostly... So, if anyone needs help with any particular remote control problem, perhas I could be of help...
It bugs me that it still happens now and then that the remote isn't recognized, and the key presses do nothing: it happens mostly after shuffling the usb devices around, plugging them into different USB sockets... But, it now works relatively reliably - the most important thing is that the remote sensor is recognized and properly mapped to symlink "/dev/input/ir0" - and I edited "empcd.conf" to use "/dev/input/ir0" as the eventdevice...
Also, the remote starts working only after a slight delay (about a minute AFTER the mpd is started....). No big deal... as long as it works OK afterwards
Next I'll also try to use that "power off" button on the remote using the "exec" command in the empcd.conf in order to shut down the system from the remote.
It would also be nice if I could start (power on) the computer using the remote, but that won't be that easy, I guess (from what I managed to deduce so far...).
First, I had to add another command to /etc/rc.d/rc.local:
Code: Select all
sleep 10
/usr/sbin/empcd &First command (sleep 10) seems to be necessary - the remote has to wait for MPD to start cleanly, otherwise it won't start properly - this could be even "sleep 15" or "sleep 20", just to be on the safe side.
After finding out which "event" in /dev/input belongs to remote sensor, I was able to see which button does what by using command "empcd -y 9 -f" (prior to that I edited "/etc/empcd.conf" by selecting the proper "event" - in my case it was the line:
Code: Select all
eventdevice /dev/input/event4THEN came the real pain in the behind:
I wanted to make sure the remote sensor is always mapped to appropriate symlinked "event", which I called "ir0".
If I use the default "eventX", it sometimes happens (particularly if I remove or add another USB device, e.g. USB DAC) that the event numbers get shuffled around - so, it's not a good idea to use e.g. "event4" - because it can sometimes be "event5"
After a LOT of reading, and a lot of trial and error, I managed to write a proper udev rule, which now always maps the USB remote sensor to "/dev/input/ir0", regardless whether it is attached to "event4" or "event5" - or whatever. Well, at least it seems to work - most of the time
Took me quite a while to find out the unique string to use as identifier for the udev rule - I finally used "Phys" key, which I got by using command "cat /proc/bus/input/devices"....
To cut the long story short, it was an arduous journey
But, I think I got the USB remotes sorted out now.... mostly... So, if anyone needs help with any particular remote control problem, perhas I could be of help...
It bugs me that it still happens now and then that the remote isn't recognized, and the key presses do nothing: it happens mostly after shuffling the usb devices around, plugging them into different USB sockets... But, it now works relatively reliably - the most important thing is that the remote sensor is recognized and properly mapped to symlink "/dev/input/ir0" - and I edited "empcd.conf" to use "/dev/input/ir0" as the eventdevice...
Also, the remote starts working only after a slight delay (about a minute AFTER the mpd is started....). No big deal... as long as it works OK afterwards
Next I'll also try to use that "power off" button on the remote using the "exec" command in the empcd.conf in order to shut down the system from the remote.
It would also be nice if I could start (power on) the computer using the remote, but that won't be that easy, I guess (from what I managed to deduce so far...).
-
Mark van de Pas
- Posts: 5
- Joined: Thu 14 Feb 2013, 13:08
sound quality mpd + Puppy <-> mpd + Tiny Core
Hi Idolse,
Through your mpdPup-project I learned how good puppy-linux can sound compared too regular mainstream Linux distro’s like Ubuntu Studio etc.
Info on my setup: mpdPup -> ESI-juli@ digital part (separately linear powered) -> Van den Hull optocoupler -> Lavry Black DA10 -> Vovox Direct S -> Klein & Hummel O300.
The very good sound quality coming from mpdPup made me curious what sound quality other puppy’s would deliver.
So I tried various other puppy’s, finally stumbling upon Tiny Core Linux.
Quite too my surprise: Tiny Core Linux + cifs- utils + alsa-dev + DeadBeef (with GAIN + re-& alsa up-sampling disabled) is another significant step-up in sound quality from mpdPup.
Audacity2 sounds equally superb on Tiny Core.
So may be better sound quality might be there because Tiny Core is used.
I know I should compare: mpdPup <-> Tiny Core + mpd.
But being a linux newbie I cant’t manage too setup a working mpd in Tiny Core.
There is a mpd.tcz, but configuring mpd in Tiny core is way too complicated for me.
So here’s my question:
* Have you (or any other inmates) ever tried mpd on Tiny Core?
Just too compare sound quality coming from: mpd + tiny core <-> mpd + puppy ?
Mark
NB I used the words “significant step-up in sound quality
Through your mpdPup-project I learned how good puppy-linux can sound compared too regular mainstream Linux distro’s like Ubuntu Studio etc.
Info on my setup: mpdPup -> ESI-juli@ digital part (separately linear powered) -> Van den Hull optocoupler -> Lavry Black DA10 -> Vovox Direct S -> Klein & Hummel O300.
The very good sound quality coming from mpdPup made me curious what sound quality other puppy’s would deliver.
So I tried various other puppy’s, finally stumbling upon Tiny Core Linux.
Quite too my surprise: Tiny Core Linux + cifs- utils + alsa-dev + DeadBeef (with GAIN + re-& alsa up-sampling disabled) is another significant step-up in sound quality from mpdPup.
Audacity2 sounds equally superb on Tiny Core.
So may be better sound quality might be there because Tiny Core is used.
I know I should compare: mpdPup <-> Tiny Core + mpd.
But being a linux newbie I cant’t manage too setup a working mpd in Tiny Core.
There is a mpd.tcz, but configuring mpd in Tiny core is way too complicated for me.
So here’s my question:
* Have you (or any other inmates) ever tried mpd on Tiny Core?
Just too compare sound quality coming from: mpd + tiny core <-> mpd + puppy ?
Mark
NB I used the words “significant step-up in sound quality
-
Supersurfer
- Posts: 13
- Joined: Sat 02 Mar 2013, 12:10
empty folders in mpad
Dear Idolse,
in Mpad I have a lot of empty albums showing in album mode. I can not get rid of them in Mpad, they seem to be in the mpdpup database.
These empty albums were left after I had moved music files to other folders (there are no empty folders on the NAS)
Is there an elegant way of deleting/removing the database or removing these empty folders one by one?
Kind regards,
in Mpad I have a lot of empty albums showing in album mode. I can not get rid of them in Mpad, they seem to be in the mpdpup database.
These empty albums were left after I had moved music files to other folders (there are no empty folders on the NAS)
Is there an elegant way of deleting/removing the database or removing these empty folders one by one?
Kind regards,
Tiny Core
Hi Mark,
Great post!!
unfortunately , the coming period will be very busy and i doubt if i can find the time to try your suggestions and to fiddle with Tiny Core and mpd.
If i get somewhere i will let you know.
If possible, coud you post a small manual of how to create your setup?
Many thanks!
Douwe
ps since i use mpdpup (in stead of cmp2) i spend a lot more time listening to music (in stead of tweaking and repairing the very unstable cmp2)
Great post!!
unfortunately , the coming period will be very busy and i doubt if i can find the time to try your suggestions and to fiddle with Tiny Core and mpd.
If i get somewhere i will let you know.
If possible, coud you post a small manual of how to create your setup?
Many thanks!
Douwe
ps since i use mpdpup (in stead of cmp2) i spend a lot more time listening to music (in stead of tweaking and repairing the very unstable cmp2)
Well I spent some time playing with TinyCore Linux. Got Deadbeef to work, sounds great, did not do any critical listening/comparison between mpdpup though.
Also MPD does not work with TInyCore at the moment with the current rev and mpd. The packages are out of sync. Furthermore I can not compile mpd on TinyCore from scratch.
I also tried to install the Real-time Kernel on TinyCore per instructions dated 2011. That too is out of date with the current rev.
I went back to mpdpup and poked around looking at various process and discovered that about 10 processes not audio related are 'reniced' to the highest priority. These processes like kpsmoused might be great for a standard install because it speeds things up like responsiveness of the mouse etc. but for mpdpup having the highest priority is a waist. So I promptly reduced the processes of everything to 0 except audio related processes.
I really really REALLY do hope that mpdpup will not become your standard abandoned Linux project.
On another note, for anyone interested and has a Nexus 7 or 10 or probably anything with the Android OS that can run JB 4.2.x. There is a new ROM out that enables USB audio and it works with just about every Dac I have tried and have on hand which includes XMOS, VIA [Audiogd], Tenor and a few iBrasso headphone usb-dac-amps. This means that any of the above can be turned into a Squeezebox Touch. I currently have my Nexus 7 assigned to such duties right now. This means for about $140 bucks anyone can go to their nearest Walmart and buy any tablet that runs Android, install the ROM and instantly have a Squeezebox Touch.
Enjoy!
Also MPD does not work with TInyCore at the moment with the current rev and mpd. The packages are out of sync. Furthermore I can not compile mpd on TinyCore from scratch.
I also tried to install the Real-time Kernel on TinyCore per instructions dated 2011. That too is out of date with the current rev.
I went back to mpdpup and poked around looking at various process and discovered that about 10 processes not audio related are 'reniced' to the highest priority. These processes like kpsmoused might be great for a standard install because it speeds things up like responsiveness of the mouse etc. but for mpdpup having the highest priority is a waist. So I promptly reduced the processes of everything to 0 except audio related processes.
I really really REALLY do hope that mpdpup will not become your standard abandoned Linux project.
On another note, for anyone interested and has a Nexus 7 or 10 or probably anything with the Android OS that can run JB 4.2.x. There is a new ROM out that enables USB audio and it works with just about every Dac I have tried and have on hand which includes XMOS, VIA [Audiogd], Tenor and a few iBrasso headphone usb-dac-amps. This means that any of the above can be turned into a Squeezebox Touch. I currently have my Nexus 7 assigned to such duties right now. This means for about $140 bucks anyone can go to their nearest Walmart and buy any tablet that runs Android, install the ROM and instantly have a Squeezebox Touch.
Enjoy!
It's not abandoned, no worries, but it's on hiatus for a while, too much real life in the way. But I maintain it for my own usage too, and don't have any plans to continue using anything but this. I had loftier goals of trying to rebuild the kernel but maybe another release with bug fixes and some of these audio priority tweaks would be sufficient.Dynobot wrote:I went back to mpdpup and poked around looking at various process and discovered that about 10 processes not audio related are 'reniced' to the highest priority. These processes like kpsmoused might be great for a standard install because it speeds things up like responsiveness of the mouse etc. but for mpdpup having the highest priority is a waist. So I promptly reduced the processes of everything to 0 except audio related processes.
I really really REALLY do hope that mpdpup will not become your standard abandoned Linux project.
@RoxGsm - no idea why you can't play hi-rez audio files. Everything up to 96Khz works out of the box for all sound devices. On some sound devices (my own included) you need to unplug/replug the USB device after the system has fully booted to get 176/192Khz working. Other users report no problems with any bitrates from the start.
@DenisP, I'm not really sure why you needed to put empcd in rc.local - the starting with '&' is a bit weird as to being required. Unfortunately I'm a bit loathe to use this as a fix because I used to start some other process with an ampersand and I seem to recall it caused some users problems. Anyway you should be able to tweak the empcd init script to use the ampersand, and it already has the logic to sleep until mpd is alive. /etc/init.d/30.empcd.
I will follow up on email as requested.
@Supersurfer - I have that same problem for a few albums on mPad, no idea what causes it - guessing it's either a subtle flaw in the MPD database that it displays, or purely a bug in mPad - either way it's something to take up with the mPad author - he seems to be fairly responsive to well described problems.
Last edited by ldolse on Sat 22 Jun 2013, 14:55, edited 1 time in total.
-
Supersurfer
- Posts: 13
- Joined: Sat 02 Mar 2013, 12:10
If the mPad author pushed it back to me that would mean he views it as a bug in mpd. The MPD devs are a bit more stringent about bug descriptions though, so unless you can figure out the exact cause and effect deleting the database is probably your best bet.
To delete your database and rebuild it you just need to stop mpd and then delete the database file - it's located at /mnt/home/mpd/database. When you re-start mpd it will build a new one. I'm not convinced this will fix the problem - I seem to recall that I still see it for an album here or there with a fresh database, but it may be related to folder renaming - I never dug into it too much.
To delete your database and rebuild it you just need to stop mpd and then delete the database file - it's located at /mnt/home/mpd/database. When you re-start mpd it will build a new one. I'm not convinced this will fix the problem - I seem to recall that I still see it for an album here or there with a fresh database, but it may be related to folder renaming - I never dug into it too much.
-
Mark van de Pas
- Posts: 5
- Joined: Thu 14 Feb 2013, 13:08
Hi Douwe,
Same here. Since I use mpdpup (instead of cmp2) I spent more time listening too music. Mpdpup not only sounds very good but the remote control through smartphone apps also makes it really comfortable.
Although I must give Cics cmp2 project much credits for guidance and introduction into ‘computer music’. Also the XP OS-slimming operations introduced by dedicated followers of the cmp-project were an eye opener for me.
Having learned from the cmp2 project, I immediately recognized the potential of Idols’ mpdpup project. Using a slimmed OS (puppy Linux), no video usage, ect. So the same core ingredients resulting in superb sound quality come from mpdpup but still with a very user friendly GUI (through use of a client for remote control).
I don’t think we should discus installing Tiny Core Linux on Idols mpdpup project pages. I did not post it for that reason.
I brought the Tiny Core distribution too Idols attention, so he could have a look at it and see if Tiny Core contains any idea’s and improvements Idolse could use for his mpdpup project.
Idolse already showed to be open for suggestions. See Idols implementation of: ‘wisdom of the crowd optimazations’. So looking at Tiny Core might inspire Idolse for other optimizations, IF THERE ARE ANY IN TINY CORE. But I don’t know that. May be it is just deadbeef sounding appealing to me. Or that there is mistakenly running some upsampling in the background which I happen to like.
So that’s why I asked if Idolse ever heard mpd on tiny core. May be Idolse and/or other users with linux skills are not impressed at all with mpd on Tiny Core. So there would be no reason for having a closer look at Tiny Core and too check if there are any optimizations in Tiny Core which also could be implemented in mpdpup.
Since Idolse is kept bussy in real life, Dynobot already tried. Which resulted in discovering 10 not-audio-related processes running in high priority mode. (Thank you Dynobot !) So see, it’s always good too have a look around and see if there are new ideas which could improve the sound quality coming from mpdpup.
Mark
NB. I could email you a short description on how I installed tiny core on the cmp-hardware too test drive Tiny Core + Deadbeef. That is real easy on cmp-hardware because the esi-juli@ card is supported by ALSA.
Same here. Since I use mpdpup (instead of cmp2) I spent more time listening too music. Mpdpup not only sounds very good but the remote control through smartphone apps also makes it really comfortable.
Although I must give Cics cmp2 project much credits for guidance and introduction into ‘computer music’. Also the XP OS-slimming operations introduced by dedicated followers of the cmp-project were an eye opener for me.
Having learned from the cmp2 project, I immediately recognized the potential of Idols’ mpdpup project. Using a slimmed OS (puppy Linux), no video usage, ect. So the same core ingredients resulting in superb sound quality come from mpdpup but still with a very user friendly GUI (through use of a client for remote control).
I don’t think we should discus installing Tiny Core Linux on Idols mpdpup project pages. I did not post it for that reason.
I brought the Tiny Core distribution too Idols attention, so he could have a look at it and see if Tiny Core contains any idea’s and improvements Idolse could use for his mpdpup project.
Idolse already showed to be open for suggestions. See Idols implementation of: ‘wisdom of the crowd optimazations’. So looking at Tiny Core might inspire Idolse for other optimizations, IF THERE ARE ANY IN TINY CORE. But I don’t know that. May be it is just deadbeef sounding appealing to me. Or that there is mistakenly running some upsampling in the background which I happen to like.
So that’s why I asked if Idolse ever heard mpd on tiny core. May be Idolse and/or other users with linux skills are not impressed at all with mpd on Tiny Core. So there would be no reason for having a closer look at Tiny Core and too check if there are any optimizations in Tiny Core which also could be implemented in mpdpup.
Since Idolse is kept bussy in real life, Dynobot already tried. Which resulted in discovering 10 not-audio-related processes running in high priority mode. (Thank you Dynobot !) So see, it’s always good too have a look around and see if there are new ideas which could improve the sound quality coming from mpdpup.
Mark
NB. I could email you a short description on how I installed tiny core on the cmp-hardware too test drive Tiny Core + Deadbeef. That is real easy on cmp-hardware because the esi-juli@ card is supported by ALSA.
Hi Idolse
I understand about being too busy in real life....I was extremely busy until recently hence by absence.
Now I am looking at about 6 months down time and will spend more time here to discuss MPDPUP. I forgot to post that I also increased the priority of MPD via the file in init.d. Just uncomment the line that has nice 15 and change it to nice -1. This gave the sound a nice low end lushness to balance out the very good detail gained by decreasing the other priorities to 0.
In the coming weeks I will be trying to figure out how to work with the devx file. I would really appreciate if you could help me get off the ground with it. I could do some testing and experimenting while you are busy.
I see there is one other person willing to contribute to writing manuals etc. Idolse please feel free to email / PM me to discuss how I can contribute. Having tried just about everything available I really do think MpdPup is the best thing since sliced bread. The concept is perfect and the OS is nearly dialed in to perfection too.
I understand about being too busy in real life....I was extremely busy until recently hence by absence.
Now I am looking at about 6 months down time and will spend more time here to discuss MPDPUP. I forgot to post that I also increased the priority of MPD via the file in init.d. Just uncomment the line that has nice 15 and change it to nice -1. This gave the sound a nice low end lushness to balance out the very good detail gained by decreasing the other priorities to 0.
In the coming weeks I will be trying to figure out how to work with the devx file. I would really appreciate if you could help me get off the ground with it. I could do some testing and experimenting while you are busy.
I see there is one other person willing to contribute to writing manuals etc. Idolse please feel free to email / PM me to discuss how I can contribute. Having tried just about everything available I really do think MpdPup is the best thing since sliced bread. The concept is perfect and the OS is nearly dialed in to perfection too.
mpd nice -1
DynobotDynobot wrote:Hi Idolse
I understand about being too busy in real life....I was extremely busy until recently hence by absence.
Now I am looking at about 6 months down time and will spend more time here to discuss MPDPUP. I forgot to post that I also increased the priority of MPD via the file in init.d. Just uncomment the line that has nice 15 and change it to nice -1. This gave the sound a nice low end lushness to balance out the very good detail gained by decreasing the other priorities to 0.
Great tip! Can you either repost directions to decrease the other priorities to or point me to a post? I have put in a bunch of your tweaks. all good, thanks
Want to make sure I have not missed these
the Nice -1 on MPD removed a nagging concern I had with the sound of an ALIX board running MPDPUP. While very good detail, it had a slightly mechanical sound compared to a well tuned CICS2 machine on slim XP. This added the lush almost magical fulness of sound that had hitherto been missing. Strongly recommended for all with a well resolved sound system.
Walter
renice
hi all, i found out a way to renice some processes, but for one time use only (see edit 2)
command:
ps axl
and look for the PID nr of the process you want to renice, for example kpsmoused has PID 36 and you want to renice to 19 (very low priority)
then type
renice 19 36
done!
check with
ps axl
you could put it in a script like jrling did
http://www.murga-linux.com/puppy/viewto ... &start=120
although i could not figure out how
Thanks Dynobot and jrling!
@Mark: you are right, i asked about TinyCore for learning purposes, and i know Idolse is open for suggestions (i proudly contributed to the crowd sourced settings). Since Dynobot confirmed mpd does not match with TinyCore i decided not tot try it.
In stead i tried the priority settings, with very good results!
i LOVE this puppy!
Douwe
edit: Dynobot's comman d to find out the PID of audio-related processes:
ps -eLo pid,cls,rtprio,pri,nice,cmd | grep -i "irq"
edit 2:
I found out that at each startup PID nrs change, so the renice commands change. hmm, not a real solution...
startup sequence is for me rather complicated, could not find where priorities are set. Any suggestions?
command:
ps axl
and look for the PID nr of the process you want to renice, for example kpsmoused has PID 36 and you want to renice to 19 (very low priority)
then type
renice 19 36
done!
check with
ps axl
you could put it in a script like jrling did
http://www.murga-linux.com/puppy/viewto ... &start=120
although i could not figure out how
Thanks Dynobot and jrling!
@Mark: you are right, i asked about TinyCore for learning purposes, and i know Idolse is open for suggestions (i proudly contributed to the crowd sourced settings). Since Dynobot confirmed mpd does not match with TinyCore i decided not tot try it.
In stead i tried the priority settings, with very good results!
i LOVE this puppy!
Douwe
edit: Dynobot's comman d to find out the PID of audio-related processes:
ps -eLo pid,cls,rtprio,pri,nice,cmd | grep -i "irq"
edit 2:
I found out that at each startup PID nrs change, so the renice commands change. hmm, not a real solution...
startup sequence is for me rather complicated, could not find where priorities are set. Any suggestions?
Re: mpd nice -1
Forgive my ignorance, but, I cannot find the init.d file you were talking, in the init.d directory can't find the file to define the priorities, can you please give me the path?wlowes wrote:
Dynobot
Great tip! Can you either repost directions to decrease the other priorities to or point me to a post? I have put in a bunch of your tweaks. all good, thanks
Want to make sure I have not missed these
the Nice -1 on MPD removed a nagging concern I had with the sound of an ALIX board running MPDPUP. While very good detail, it had a slightly mechanical sound compared to a well tuned CICS2 machine on slim XP. This added the lush almost magical fulness of sound that had hitherto been missing. Strongly recommended for all with a well resolved sound system.
Walter
Thank you.
Re: mpd nice -1
look in the /etc directory you will see another directory called init.d, within it you will se a file with mpd in the name, open it and on line 30 uncomment the line for nicebonalux wrote:Forgive my ignorance, but, I cannot find the init.d file you were talking, in the init.d directory can't find the file to define the priorities, can you please give me the path?wlowes wrote:
Dynobot
Great tip! Can you either repost directions to decrease the other priorities to or point me to a post? I have put in a bunch of your tweaks. all good, thanks
Want to make sure I have not missed these
the Nice -1 on MPD removed a nagging concern I had with the sound of an ALIX board running MPDPUP. While very good detail, it had a slightly mechanical sound compared to a well tuned CICS2 machine on slim XP. This added the lush almost magical fulness of sound that had hitherto been missing. Strongly recommended for all with a well resolved sound system.
Walter
Thank you.
What's running in an optimized system
Dynobot
could you show the results of
ps axl
for your system?
Might give me some ideas for what to kill and where priorities should be
thx
could you show the results of
ps axl
for your system?
Might give me some ideas for what to kill and where priorities should be
thx
Hi MarkMark van de Pas wrote:Hi Douwe,
Same here. Since I use mpdpup (instead of cmp2) I spent more time listening too music. Mpdpup not only sounds very good but the remote control through smartphone apps also makes it really comfortable.
I took similar CMP2 route and concur. Spend a lot more time listening now and love the smart phone client. XP slimming led me to the ALIX board with MPDPUP. I had not done the full Julie linear PS deal on CICS so ALIX was kind of a natural.
Walter