This one should help where pMusic occupies your system at first run.
I could get the same behavior if starting pMusic from menu or terminal first time (not by clicking on a file in Rox) and there were no connection to internet.

rodin.s
Reading your logs make me realize that if someone (could be you ) enable NLS for ffmpeg it could give wrong info to pMusic....
In RC7 all ffmpeg commands are run with english output - LANG=C.
This is not a specific pMusic 3 issue, but has been there from the beginning.

It is critical that pequalizer is at least v-0.8.2. before that the -s option is not recognised and you could put any unrecognised option there and pequalizer will start anyway. That's the only reason I can think of for it starting unwanted. Slacko-5.3x users need to know this so I adjusted my post._________________Puppy Linux Blog - contact me for access

No, I don't have any NLS for ffmpeg, It's in English when I run 'ffmpeg -h'.
Also progress bar doesn't work only on one song. Everything is OK with other ones. Maybe my system is just too slow for pMusic (900MHz 512RAM). Sometimes I think that it would be great application if it was written in C/C++. Now I have that grey GUI while playing a song and it became normal when no song is playing. But sometimes it's OK.

Pmusic cannot be set on Master Mono sound card channel as to allow sound volume using the below right volume button.
It perists keeping «Master» setting. I caanot force it on Master Mono, which controls the speaker volume.

No, I don't have any NLS for ffmpeg, It's in English when I run 'ffmpeg -h'.
Also progress bar doesn't work only on one song. Everything is OK with other ones. Maybe my system is just too slow for pMusic (900MHz 512RAM). Sometimes I think that it would be great application if it was written in C/C++. Now I have that grey GUI while playing a song and it became normal when no song is playing. But sometimes it's OK.

This is getting interesting. I hope I can bother you some more.... You have the perfect PC for testing.

I could of course advice you to change to the LowPowered frontend found here. Also reachable from the preferences window.
I could also advice you to do some manual tweaking like turn off trackinfo in the preferences, and increase the update_interval in the config file (/root/.pmusic/pmusicrc). pMusic can't run when editing this file because everything will then be reset when pMusic closes.

Skip what is below, my mind was half-dead.
....I will look more into this

But right now, I feel like trying to figure out what's wrong - because there is something wrong. You have several instances of func_progressbar running, and that is not logical. I will be a bit technical now, and I don't know how interesting that is to you, but it sure is for the understanding of how gtkdialog works.....

I will remove the & in the forth line. There is no reason for running func_progressbar in the background and it might be the reason for several running instances of func_progressbar. As we see of the code snippet, the update interval is set as a attribute of the <timer> widget. The obvious question is: When I now remove the &, will the <timer> fire a new <action> signal based on the update interval before the previous <action> is completed.... Sergey, you are the one who can test this. Please try the next version of pMusic and post your terminal output as last time.

If <timer> don't care about the status of its actions, we will see the same problem of several running fun_progressbar. And if so, <progressbar> could help us, because it works different. The <progressbar> widget was used earlier for the same use as <timer> does today. For <progressbar>, there is no option to set the update interval, so this is done by the sleep command instead. The sleep time will be between each instance of func_progressbar. It is simply not possible to run more than 1.

Thank you
Sigmund_________________Stardust resourcesLast edited by zigbert on Thu 08 Nov 2012, 10:29; edited 2 times in total

Hi again Sigmund !
Great ! now the volume button and the alsa's Master Mono bar moves accordingly, as also the speakers volume!
BUT....
No longer more Equalizer when selecting File/Equalizer; pequalizer does not start either from command line...

Note the Dependency check comment :

Quote:

...line 215: [: ver: integer ...

it's maybe another ffmpeg version id format is expected by the execution of line 215.

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