Page 15 of 20

Posted: Thu 21 Mar 2013, 06:09
by goingnuts
depending on what info you need we could adapt goingnuts' pnmmon for that, though it has been a while since I have played with inotify directly (after I found out glib/gio has a wrapper)... I wonder though if it would be better to take a look at jwm traybuttons (for the icon part) and the clock (because it changes) to add something similar to my "sit" program (simple icon tray) ... I don't know if Joe W. would be open to it though since inotify is linux specific AFAIK and I think some of the bsds keep a port (maybe if we could ifdef it?). The great part is that the latest jwm has svg support (though it adds cairo/rsvg dependency) which makes for much simpler tray applet construction.
jwm-0.21 did have a build-in xload tray-thing beside clock - might be worth looking at that for a start. Can the svg be adapted to gtk1? (it is my impression that svg-support are linked to gtk2 but I might be total wrong)

starhawk: did you try to use mpg123/minimp3 to play mp3? xhippo it self holds no player but depends on external players so if one of the two actually give you some sound xhippo can be fixed...
As for startup sound place a script as below in /root/Startup

Code: Select all

#!/bin/sh
wavplay /usr/share/audio/justonemoment.wav
minimp3 /usr/share/audio/dog_bark.mp3
cat /usr/share/audio/2barks.au > /dev/audio 2> /dev/null &
Keef: thats a nice little gem (ram)! And a nice link to some potentially very useful apps - thanks.

Posted: Thu 21 Mar 2013, 16:02
by starhawk
mpg123 and minimp3 are completely mute as well :( no errors in console, just no sound.

EDIT: wavplay doesn't work, either. Hmmm...

Posted: Thu 21 Mar 2013, 16:33
by starhawk
starhawk wrote:technosaurus, could you provide me with a libpthread.so suitable for that last Opera link, the 9.64 version? I can symlink as needed. It also complains (but ignores) that libjvm.so and libawt.so are missing.
Still need this, badly.

Posted: Thu 21 Mar 2013, 18:42
by goingnuts
Attached alsamixer - I do not know if it really helps but you might be able to view/adjust some of your sound-devices...
Another thing to try is
mpg123 -os,-ol,-oh output to built-in speaker,line-out connector,headphones
Also attached a static version of minmad referenced by Keef and aplay which is mentioned here (Comprehensive Sound Problem Solutions Guide)...

And the libpthread.so (fresh cut-out from greengeekĀ“s newly posted iso...)

Posted: Thu 21 Mar 2013, 22:42
by Keef
Starhawk

The simplest way to get a 'woof' on startup, is to put a script into the Startup folder. Something like this:

Code: Select all

#!/bin/sh
minimp3 /usr/share/audio/bark_bark.mp3
Assuming you've got minimp3 and a doggy mp3 file of course.
(Techno's minimp3 package has all you need).

Thats what the longwinded pet you mentioned before does, but with a GUI to turn it on or off, and to select the sound file.

[EDIT] Durr... don't know I missed the previous posts that already said this.

Posted: Fri 22 Mar 2013, 00:35
by technosaurus
goingnuts wrote:jwm-0.21 did have a build-in xload tray-thing beside clock - might be worth looking at that for a start. Can the svg be adapted to gtk1? (it is my impression that svg-support are linked to gtk2 but I might be total wrong)
IIRC as long as you build gdk-pixbuf and then librsvg (the module is in the librsvg package itself instead of gdkpixbuf) I'll have to check.

Re: tray apps ... maybe we are going about this all wrong - how about swallowing a gtkdialog1 app? ... it could monitor network, battery, volume, cpu, temperature, memory, savefile, weather, stock ticker, (this can be set by a single awk script) ... all in one (configurable) applet this would cut resource usage by only using one binary and also speed up loading of gtkdialog (because there is already a hot copy in ram)

That reminds me that I wanted to look into a way to allow running only a single instance of gtkdialog. I think if maybe we set up a pipe and use stdin as the gtkdialog input attached to that pipe it would be do-able from a while loop that just monitors a directory/file for new gtkdialog xml and cat's the new files (out to the pipe and into gtkdialog) ... I'm not sure how many windows gtkdialog1 is able to open simultaneously though (or how if at all) - It probably needs a way to tell the end of that window similar to </window> in gtkdialog2-4

Posted: Fri 22 Mar 2013, 22:39
by starhawk
Requesting another tray app -- one for volume. alsamixer works -- but I've still got one mute puppy here...

Posted: Sun 24 Mar 2013, 18:55
by goingnuts
technosaurus: gtkdialog1 can be swallowed by jwm so guess its more or less a question if we can make dynamic changing pixmaps or text to do it.

starhawk: So alsamixer works but does not give you sound or what?

Found an alternative xload-monitor (hot-babe-0.2.2-gtk1+2pets) and did a quick backport to gtk1 to a working state. Thought I better bury it here and not in the "Additional Software"-section...But the coding principle is interesting and could be used with other images - and it is more fun as-is than xload during a kernel-compile... Patch2gtk1 attached.

Posted: Sun 24 Mar 2013, 19:16
by starhawk
That's correct -- I can play CDs because that's handled 99% by the CD drive -- it just pipes audio to the computer and the computer dumps it to the speakers. I think.

But any sort of internal playback -- mp3 or wav -- doesn't happen. minimp3 and mpg123 both claim to be playing, but I get no sound whatsoever.

IIRC in mainline Puppies and most Puplets -- there are TWO volume controls. One is ALSA. The other is the volume tray app that doesn't exist in pUPnGO.

I suspect that in my case, the lack of a volume tray app may be causing problems. (I also want to say that I remember mucking around with either original pUPnGO or a very early pUPnGO2012 where we got the volume tray app put in, and suddenly I was able to fix the issue... but I can't remember for sure.)

Perhaps there's a way to simply pull that app from p412 and stuff it into pUPnGO2012? I mean, the pUPnGO2012+ version I'm working with started off at 116mb, so I'm not nearly as concerned about size as you are ;) Speed and size usually go hand-in-hand but I doubt I'd find another Puppy that's nearly this responsive on this system at this size. Heck, Puplite5 is ~79mb and it is nearly painful to use.

Posted: Sun 24 Mar 2013, 19:27
by goingnuts
Did you try this? Uses same functions as absvolume. What soundcard do you have?

Posted: Sun 24 Mar 2013, 19:52
by starhawk
Hadn't tried pmvol. I'll check it out shortly.

The CPi D***XT models use the Crystal 4237B ISA-based card. Driver is snd-cs4236.ko.

Posted: Sun 24 Mar 2013, 20:37
by goingnuts
If you look in /sys/bus/isa/devices - is it mentioned there?
You might want to run alsaconf - it has the possibility to probe non-pnp ISA-cards - cant test if it works but it tries...
Take alsaconf, alsactl, amixer and aplay from P412 and try to run alsaconf. It needs bash and dialog and maybe some additional libraries. I do have a static cut-down version but its too big to post here and as said above I cant test if it really works.

Posted: Sun 24 Mar 2013, 20:40
by starhawk
Had to install a GTK-1.2 pet to make it work. No probs there, but...

Code: Select all

GLib-WARNING **: getpwuid_r(): failed due to: No such user 0.
So it doesn't show up :(

Posted: Sun 24 Mar 2013, 21:01
by starhawk
A (very) small contribution of my own -- icons for SNS-Retro ;)

Two icons, one 24px and the other 48px.

Posted: Sun 24 Mar 2013, 21:16
by goingnuts
Nice...
Here is a static pmvol which works in pupngo2012 (here...)

Posted: Sun 24 Mar 2013, 22:16
by starhawk
I think there's something wrong with that driver, or with ALSAmixer. I'm really not sure what's going on -- the ALSA settings aren't persistent between boots, and even when I jack the volume all the way up with pmvol, having maxed out nearly every setting in ALSAmixer, it still doesn't play MP3s.

Very strange.

Maybe the driver's not quite an exact match?

Posted: Sun 24 Mar 2013, 23:20
by technosaurus
if you need to test your sound try

cat ....bark.wav >/dev/dsp
or
cat ...bark.au >/dev/audio

(path is in /usr/share/...? audio or sound or something)

then you can tell if it is mixer problem

I posted one called mmix to the old pupngo thread a long time ago - it is extremely light and works with oss vs. alsa ... worth a try if you may have an old oss only card

Posted: Sun 24 Mar 2013, 23:39
by technosaurus
goingnuts wrote:technosaurus: gtkdialog1 can be swallowed by jwm so guess its more or less a question if we can make dynamic changing pixmaps or text to do it.
I submitted a patch to thunor to add this capability to gtkdialog-trunk, though I made provisions to use only (slower) gio functions for portability rather than using inotify directly. My patch added a watch for all files, but he added an attribute flag to turn on watching and made it work for other widgets as well (anything that gets input from a file). I can look at my early versions of SIT to use inotify for gtkdialog1 since we are pretty much the only users (does anyone know what kernel version added inotify? ... need to know that if you plan on sticking with the older kernel - I am standardizing my current code on linux-3.8 for specific reasons, so its hard to tell) anyhow let me know if anyone is interested in this or has suggestions to make it better for a specific project they have in mind.

Posted: Mon 25 Mar 2013, 03:05
by starhawk

Code: Select all

cat /usr/share/audio/2barks.au > /dev/audio
...makes it bark! :D

Now: why on EARTH would the alsamixer settings not persist across boots? Started when I installed pmvol... I wonder if it has to do with this OSS-only stuff... what is OSS anyways?

Posted: Mon 25 Mar 2013, 05:38
by technosaurus
the .wav to /dev/dsp didn't though?

I also wanted to point this out:
http://www.newegg.com/Product/Product.a ... 6834760001
($40 netbook)

I ordered one myself and it seems like the perfect little testbox for an arm'ngo experiment. Craig has a zip file with the "firmware" inside as raw files with shell scripts, so it is straight forward to figure out what modules are needed and how to install it to disk ... though the uboot configuration may need further study as it is significantly different from grub, lilo, syslinux and isolinux