pMusic 6.0.0
Version 3.2.1
See main post
Changelog
- Bugfix: Balance slider. (thanks to 666philb)
- Bugfix: Several similar msg about mono-channel pops up when moving slider. (thanks to 01micko)
- Bugfix: Search fails if include ' in searchstring.
- Bugfix: Remove debugging gxmessage when deleting RadioHits preset.
- Bugfix: Jump_to_time stops progress bar.
- Bugfix: Searching for radio-stations, country-info is pointed to a too narrow tab.
- Bugfix: Clear active playlist when choosing 'New Playlist'.
- Bugfix: Graphical theme fails showing svg-header with ONLY_THIS_GTKTHEME=false in them
See main post
Changelog
- Bugfix: Balance slider. (thanks to 666philb)
- Bugfix: Several similar msg about mono-channel pops up when moving slider. (thanks to 01micko)
- Bugfix: Search fails if include ' in searchstring.
- Bugfix: Remove debugging gxmessage when deleting RadioHits preset.
- Bugfix: Jump_to_time stops progress bar.
- Bugfix: Searching for radio-stations, country-info is pointed to a too narrow tab.
- Bugfix: Clear active playlist when choosing 'New Playlist'.
- Bugfix: Graphical theme fails showing svg-header with ONLY_THIS_GTKTHEME=false in them
Sigmund,
On the same laptop the balance now works, so that's good
Ha.. even retrovol shows that the sound is off balance
Mick
On the same laptop the balance now works, so that's good
Ha.. even retrovol shows that the sound is off balance
Mick
- Attachments
-
- capture13238.png
- (37.93 KiB) Downloaded 632 times
Puppy Linux Blog - contact me for access
Hello Barry
I am now in a fresh install of Racy-5.4.93, and can not reproduce your bugreport. First I mounted my pendrive, played mp3, stopped from menu, and unmounted pendrive. - No problems.
Then I went through the same task in terminal to see if any output. This is what I got.
Do you have more info?
Sigmund
I am now in a fresh install of Racy-5.4.93, and can not reproduce your bugreport. First I mounted my pendrive, played mp3, stopped from menu, and unmounted pendrive. - No problems.
Then I went through the same task in terminal to see if any output. This is what I got.
Code: Select all
# mount -t auto /dev/sdc1 /mnt/sdc1
# pmusic /mnt/sdc1/Saint\ deamon\ -\ Pandeamonium1.mp3
# umount /dev/sdc1
umount: can't umount /mnt/sdc1: Device or resource busy
# pmusic -s stop
# umount /dev/sdc1
#
Do you have more info?
Sigmund
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
It was actually the "play/pause" button that I pressed to stop the playing, as there is no actual "stop" button. Then I chose "quit" from the "file" menu.zigbert wrote:Hello Barry
I am now in a fresh install of Racy-5.4.93, and can not reproduce your bugreport. First I mounted my pendrive, played mp3, stopped from menu, and unmounted pendrive. - No problems.
Then I went through the same task in terminal to see if any output. This is what I got.
Code: Select all
# mount -t auto /dev/sdc1 /mnt/sdc1 # pmusic /mnt/sdc1/Saint\ deamon\ -\ Pandeamonium1.mp3 # umount /dev/sdc1 umount: can't umount /mnt/sdc1: Device or resource busy # pmusic -s stop # umount /dev/sdc1 #
Do you have more info?
Sigmund
However, testing now, racy 5.4.93, the problem has gone away!
[url]https://bkhome.org/news/[/url]
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Some months ago I raised the issue that when playing streams if you click the "pause" button the playing would pause but the data would continue downstreaming unless you quit the application completely.
A "stop" control was introduced, but only in the drop-down of the "Track" menu. Clicking that does stop the streaming.
Not sure if this is related to what Barry observed, but would it be worth considering putting a conventional square "stop" button in the GUI ?
A "stop" control was introduced, but only in the drop-down of the "Track" menu. Clicking that does stop the streaming.
Not sure if this is related to what Barry observed, but would it be worth considering putting a conventional square "stop" button in the GUI ?
Oscar in England
It might be a solution to actually stop when pause a stream. pMusic has no way to buffer the stream, so it won't continue where stream is paused anyway. What it does is just sending a pause-signal to the process, so it is still running. The downside by stopping instead of pausing would be that connection is lost, so it will take time to get a new connection. For many radio streams this connection time is rather long.OscarTalks wrote:Some months ago I raised the issue that when playing streams if you click the "pause" button the playing would pause but the data would continue downstreaming unless you quit the application completely.
A "stop" control was introduced, but only in the drop-down of the "Track" menu. Clicking that does stop the streaming.
Not sure if this is related to what Barry observed, but would it be worth considering putting a conventional square "stop" button in the GUI ?
This has nothing to do with Barrys issue. He want pMusic to kill all pids when it quits - and it is supposed to do so...
Sigmund
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
test of bug in 3.2.3,
I just tried Barry's procedure, 3.23 under LuPu 5,2.8zigbert wrote:[This has nothing to do with Barrys issue. He want pMusic to kill all pids when it quits - and it is supposed to do so.
The problem did not occur.
Re: test of bug in 3.2.3,
Thank you for testingsheldonisaac wrote:I just tried Barry's procedure, 3.23 under LuPu 5,2.8zigbert wrote:[This has nothing to do with Barrys issue. He want pMusic to kill all pids when it quits - and it is supposed to do so.
The problem did not occur.
Sigmund
Hi Sigmund,
Which version of gtkdialog exactly is required for the latest pmusic? We are having problems trying to upgrade Fatdog to 3.2.3. Fatdog currently has 2.6.2 (ancient!), probably stuck with that because we were stuck with gtkdialog 0.8.0. Recently kirk upgraded to gtkdialog 0.8.3 (as gtkdialog4), so I tried to install pmusic 3.2.3 again just now - and it failed to run (gtkdialog failed to launch pmusic gui).
pmusic -D reports is like this:
Any idea? We probably can't stay at 2.6.2 too because apparently the gtkdialog update has broken 2.6.2 too
cheers!
Which version of gtkdialog exactly is required for the latest pmusic? We are having problems trying to upgrade Fatdog to 3.2.3. Fatdog currently has 2.6.2 (ancient!), probably stuck with that because we were stuck with gtkdialog 0.8.0. Recently kirk upgraded to gtkdialog 0.8.3 (as gtkdialog4), so I tried to install pmusic 3.2.3 again just now - and it failed to run (gtkdialog failed to launch pmusic gui).
pmusic -D reports is like this:
Code: Select all
grep: /root/.pmusic/pmusicrc: No such file or directory
/usr/local/pmusic/func_config: line 35: /root/.pmusic/tmp/window_title: No such file or directory
R E Q U I R E D
bash [OK]
coreutils, awk, sed, diff [OK]
gtkdialog >= 0.8.3 [OK]
ffmpeg >= 0.11 [OK]
aplay (alsa) [OK]
R E C O M M E N D E D
streamripper (extended radio-rip/play) [MISSING]
cdda2wav (play/rip audio-CD) [OK]
wget (connection to www) [OK]
O P T I O N A L
pBurn (burning audio-CD) [OK]
pFilesearch (File-search engine) >= 1.28 /usr/local/pmusic/pmusic: line 224: [: too many arguments
[MISSING]
pSchedule (podcast managing) >= 1.12 /usr/local/pmusic/pmusic: line 228: [: -ge: unary operator expected
[MISSING]
pEqualizer (10 band equalizer) [MISSING]
Any idea? We probably can't stay at 2.6.2 too because apparently the gtkdialog update has broken 2.6.2 too
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
jamesbond
A wild guess...
The later pMusic gives a damn in gtkdialog2/3/4. It ONLY looks for gtkdialog! This can be reset in one of the first lines in /usr/local/pmusic/pmusic.For what I know, there could be reasons for keeping old versions of gtkdialog, but I find it logical that '/usr/bin/gtkdialog' points to the latest.
Sigmund
A wild guess...
The later pMusic gives a damn in gtkdialog2/3/4. It ONLY looks for gtkdialog! This can be reset in one of the first lines in /usr/local/pmusic/pmusic.
Code: Select all
export GTKDIALOG=gtkdialog
Sigmund
Thanks, that does it .
I haven't symlinked gtkdialog4 to "gtkdialog" for two reasons:
a) It is my impression that gtkdialog updates are not always backward compatible (meaning newer gtkdialog could "break" old applications, especially complex ones).
b) I have not validated all gtkdialog apps in Fatdog to work with gtkdialog4
Anyway, with that fix, pmusic 3.2.3 is now on its way to Fatdog
Thank you again.
I haven't symlinked gtkdialog4 to "gtkdialog" for two reasons:
a) It is my impression that gtkdialog updates are not always backward compatible (meaning newer gtkdialog could "break" old applications, especially complex ones).
b) I have not validated all gtkdialog apps in Fatdog to work with gtkdialog4
Anyway, with that fix, pmusic 3.2.3 is now on its way to Fatdog
Thank you again.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
jamesbond wrote:I haven't symlinked gtkdialog4 to "gtkdialog" for two reasons:
a) It is my impression that gtkdialog updates are not always backward compatible (meaning newer gtkdialog could "break" old applications, especially complex ones).
Fallacy!
Slacko lead the way here with always having only 1 gtkdialog binary, symlinked to 3 and 4 for backward compatibility. ...and there was minimal breakage. Mostly it was bad code, things like substituting X for password chars and also some bad calls to images.
Puppy Linux Blog - contact me for access
Sorry to plug my crap here, just to point out, Akita has included ONLY the very latest gtkdialog ever since thunor took the reigns and it's always worked fine, except one revision, which i reported and thunor fixed.. And 01micko is right, the only other breakages were due to bad code in the shell scripts - mainly cos the older gtkdialogs used to ignore certain syntax errors, so we used to get away with them...01micko wrote:jamesbond wrote:I haven't symlinked gtkdialog4 to "gtkdialog" for two reasons:
a) It is my impression that gtkdialog updates are not always backward compatible (meaning newer gtkdialog could "break" old applications, especially complex ones).
Fallacy!
Slacko lead the way here with always having only 1 gtkdialog binary, symlinked to 3 and 4 for backward compatibility. ...and there was minimal breakage. Mostly it was bad code, things like substituting X for password chars and also some bad calls to images.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]