Re: new attempt to solve an old problem with gkrellmsss

On Tue, 28 Sep 2010 17:32:43 -0400
Jack <[email protected]> wrote:

> On 2010.09.20 09:05, Jack wrote:
> > On 2010.09.17 19:14, Bill Wilson wrote:
> >> I've got  another tarball for you to try, same link:
> >> 
> >>    http://members.dslextreme.com/users/billw/test/gkrellmss.tar.gz
> 
> > I've played some more with this.  The error is coming from the  
> > ...._set_buffer_size call, but the particular error message of  
> > Invalid Argument doesn't make sense to me.  I tried smaller and  
> > larger values, all with the same error.  I tried using the  
> > ..._set_buffer_size_near call instead - same error.  I then tried  
> > commenting out that call.  No error.  In that case, the console says:
> >   ALSA set periods min 2 (1)
> >   ALSA set periods first 2 (1)
> >   ALSA pcm opened OK.  n_frames=940
> >   gdk_input_add: 5  bufsize: 3760
> > Calling ..._get_buffer_size also gives the same Invalid Argument  
> > error - but that is as a substitute for the set call.  I suppose  
> > setting it to 3760 would work, but I can't tell where that number  
> > comes from, and why bother to set it if it works without?
> 
> I've taken the new gkrellmss.so compiled from the tarball with that one  
> call commented out, and put in in ~/.gkrellm2/plugins, and it seems to  
> be working fine.  I'd still love to know if the error is due to some  
> misconfiguration on my machine, or do I just chalk it up to "blue magic  
> dust and phase of the moon?"
> 
> Anyway - thanks for getting me to a version that works.

The n_frames you get without setting the buffer size seems an odd size
to me and says that maybe your ALSA (due to your sound card maybe????)
has some hard wired limit on what the size can be.  If I don't set the buffer size on my
machine, I get a n_frames blowup of 349525 and this makes the plugin not
work in real time because it then takes seconds to fill up the buffer.

So gkrellmss needs to at least try to set the ALSA buffer size.  But if it fails
as in your case, I'm now letting the program continue on its merry way which
should reduce to your case of not making the call at all.  At least I expect that,
but to be sure, can you try one last test with a new tarball, same link again?

Run gkrellm on the plugin with the -debug46 flag to output the buffer size info.

On my machine the -debug46 is giving:

ALSA set periods min request:  2  actual: 3  dir: 0
ALSA set periods first actual: 3  dir: 0
ALSA set buffer size request: 3072
ALSA set buffer size actual:  3072
ALSA pcm opened OK. n_frames: 1024
gdk_input_add: 11  pipe size: 4096

Bill

______________________________________________
Gkrellm mailing list
[email protected]
Read archives-join-leave-set RSS feed:
http://archive.lists.netservicesgroup.com
This service is provided by The Network Services Group:
http://www.netservicesgroup.com