pupRadio (with pupTelly)
version 0.2 is out
Added bookmarks... you can have many of them
See main post
Added bookmarks... you can have many of them
See main post
Puppy Linux Blog - contact me for access
to add the classical 2 stream-directories
http://dir.xiph.org/index.php
http://classic.shoutcast.com/
aragon
http://dir.xiph.org/index.php
http://classic.shoutcast.com/
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
I will add ogg to precord eventually but I'm bogged down myself at the moment too, with some unrelated matters I have to sort out.01micko wrote:Hi mcewanw and musher0
mcewanw,
When I was looking to add the record feature to pupRadio I was looking at arecord ....| lame ... and arecord | oggenc ...
github mcewanw
refreshing the contents of a combobox?
One simple way of doing that would just be to cause a restart pupRadio to occur if the user presses the Save bookmarks button. That works, I tried it.mcewanw wrote:bug with Bookmarks?
You seem to need to close the app and restart it before you see your new bookmarks.
I don't know of a way to refresh/(change_the_contents_of) a Combobox in a running gtkdialog. As far as I can see it doesn't allow <input></input> and then, refresh..., but maybe I'm wrong.
Do you or anyone know a method of updating the items in a Combobox other than a restart of the gtkdialog (or launching a new one)? It would be really useful to be able to do that.
github mcewanw
Yes, and your proposed workaround seems like a good idea. It would also work for Presets and eliminate the "Restart" button. I'll work on that and include the fix in the next version. Thanks.You seem to need to close the app and restart it before you see your new bookmarks.
I think it is a limitation of gtkdialog, although perhaps zigbert, Patriot or potong know better.I don't know of a way to refresh/(change_the_contents_of) a Combobox in a running gtkdialog. As far as I can see it doesn't allow <input></input> and then, refresh..., but maybe I'm wrong.
Cheers
Puppy Linux Blog - contact me for access
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
pupRadio on boxpuppeee 4.3.1
Hi 01micko,
I'm running pupRadio 0.3 with Xine in boxpuppeee 4.3.1 on an ASUS 1005HE right now, listening to Celtic Music Radio, Glasgow. (This station isn't quite the purist you might think. Content is more eclectic. One part of the fun is trying to separate accent and language. In Glasgow it isn't always apparent when people are speaking English. I'm told bus drivers now get a course one might call English as an alien language.)
A suggestion: when you launch the player from a preset or bookmark, copy the text for name and URL into the form. This will give an easy way of editing or retrieving names and links without a lot of programming. The user just needs to make changes and press the button to save. This would have saved me considerable retyping.
I'm now trying to figure out why the streams for BBC World Service and CBC Radio 1, which end in asx don't work. Anyone out there have this under control?
I'm running pupRadio 0.3 with Xine in boxpuppeee 4.3.1 on an ASUS 1005HE right now, listening to Celtic Music Radio, Glasgow. (This station isn't quite the purist you might think. Content is more eclectic. One part of the fun is trying to separate accent and language. In Glasgow it isn't always apparent when people are speaking English. I'm told bus drivers now get a course one might call English as an alien language.)
A suggestion: when you launch the player from a preset or bookmark, copy the text for name and URL into the form. This will give an easy way of editing or retrieving names and links without a lot of programming. The user just needs to make changes and press the button to save. This would have saved me considerable retyping.
I'm now trying to figure out why the streams for BBC World Service and CBC Radio 1, which end in asx don't work. Anyone out there have this under control?
1. " In Glasgow it isn't always apparent when people are speaking English"
Complete a Google search for "Parliamo Glesca".
e.g. Parliamo Scots?
Complete a Google search for "Parliamo Glesca".
e.g. Parliamo Scots?
Well out of that you guys, one thing... you Scots certainly like your radio
Cheers
___________________
ver 0.3.2 is out
See main post
Cheers
___________________
ver 0.3.2 is out
See main post
Puppy Linux Blog - contact me for access
V 0.4.1 is out
bugfix,, telly was playing radio....
See main post
bugfix,, telly was playing radio....
See main post
Puppy Linux Blog - contact me for access
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Re: pupRadio (with pupTelly)
Now testing 0.4.1 on an ASUS Eee PC 1005HE running Puppeee 4.3.1.
This reminds me of Theodore von Kármán's description of his own profession. The more you know about the theory, the funnier this is.01micko wrote:...Warning While all care is taken no responsibility is accepted...
An aerodynamicist is an expert who is willing to assume anything except responsibility.
prehistoric
Glad you can see some fun in my disclaimer
James
Good to know it works well for you
____________________________
v 0.4.2 is out, minor bugfix for Xine, you don't need it if you don't use Xine...
See main post
Glad you can see some fun in my disclaimer
James
Good to know it works well for you
____________________________
v 0.4.2 is out, minor bugfix for Xine, you don't need it if you don't use Xine...
See main post
Puppy Linux Blog - contact me for access
Feature request?
I really love your wee pupRadio app 01micko; small, fast and efficient (not like some of these other bloated and slow gtkdialog media players out there).
It is great as it is (pity I don't yet have broadband though ... sigh...), however, if you ever have the time there is something I'd really like to see. Not so much a change or addition to pupRadio itself, but a companion accessory. I'd like to have a commandline tool that can read your bookmarks and call up the same configuration last used by pupRadio (including the selected media player).
The reason I would like that is that such a companion app could be started up from Pschedule (just as I do with Precord). That way, streaming radio programs could be started (and stopped) automatically at a given time, whilst conveniently using pupRadio to configure the stations and provide the bookmarks. In conjunction with Precord (and Pschedule) you could also then get time scheduled recordings of the radio stations' offerings...
Good UNIX philosophy of chaining simple applications together rather than relying on big slow bloated application designs (bash and gtkdialog being too slow anyway beyond a certain complexity...)
Anyway, I'll write it myself eventually.... if you don't get round to it. (But you already know how your bookmarks and so on are organised). Timed recording of broadcasts is just such an attractive facility to have..! :-)
It is great as it is (pity I don't yet have broadband though ... sigh...), however, if you ever have the time there is something I'd really like to see. Not so much a change or addition to pupRadio itself, but a companion accessory. I'd like to have a commandline tool that can read your bookmarks and call up the same configuration last used by pupRadio (including the selected media player).
The reason I would like that is that such a companion app could be started up from Pschedule (just as I do with Precord). That way, streaming radio programs could be started (and stopped) automatically at a given time, whilst conveniently using pupRadio to configure the stations and provide the bookmarks. In conjunction with Precord (and Pschedule) you could also then get time scheduled recordings of the radio stations' offerings...
Good UNIX philosophy of chaining simple applications together rather than relying on big slow bloated application designs (bash and gtkdialog being too slow anyway beyond a certain complexity...)
Anyway, I'll write it myself eventually.... if you don't get round to it. (But you already know how your bookmarks and so on are organised). Timed recording of broadcasts is just such an attractive facility to have..! :-)
github mcewanw
Hi mcewanw,
Thanks for supporting pupRadio.
I like your idea.
There is no reason I can see that presets as well as the bookmarks can't be supported. Sounds exciting!
Cheers (and I will be on to it soon )
Thanks for supporting pupRadio.
I like your idea.
I will attempt to add command line support so be prepared for the odd question because I am still only an "apprentice" when it comes to bash/gtkdialog coding. It will be good experience for me and take the app to the next level.Timed recording of broadcasts is just such an attractive facility to have..!
There is no reason I can see that presets as well as the bookmarks can't be supported. Sounds exciting!
Cheers (and I will be on to it soon )
Puppy Linux Blog - contact me for access
Killer combination
I doubt you've had time to think about the issues of using pupRadio with Pscheduler as yet, but before you do, and get too deeply into a pupRadio-interface-to-Pscheduler design based on how Pscheduler currently works interface-wise, I thought I should let you know of a possible minor modification to the latter, which would probably help you produce a better commandline compatible extension to pupRadio.
First of all, it was pupRadio that actually made me think about using Pscheduler, and really I stuck a button for the latter into Precord with that in mind (so I've been planning to nudge you in this direction for 'ages'...:-)
I expect that most people never or hardly ever use Pscheduler, which is a great pity, because it is a very useful application. I have read of a few people who have used it to make it play an audio file to wake them up in the morning, but of course pupRadio with Pscheduler would give all that and more...
I've actually found Precord with Pscheduler quite fun to play with, except that it is dangerous!... I forgot I had scheduled Precord to start recording at a specific time in the evening, and later in the day I discovered Precord had been running in the background (completely invisible since commandline started) recording my every movements for several hours...
But, yes, it also occurred to me that I don't 'just' want to use Pscheduler/Precord to snoop on myself... or anyone else for that matter, but what was missing in the possibilities was... pupRadio...
However, once you look at the way Pschedule works, you will notice that once you press "Add task", for a new task, you are taken to a new dialog in which you need to manually enter the program to be run and to manually supply an optional name for the new task. The problem is the "manually" part... To interface nicely with Precord, pupRadio, or any other program (rather than a human) it would be really nice if Pschedule allowed such programs to send these details as parameters - but Pschedule doesn't have that facility at the moment...
The fact that you come to the Add task, Edit, Delete, Run GUI isn't an issue, In fact, I feel that that is a good arrangement, since it allows you to immediately manage existing tasks prior to activating your new one. But when you then press the Add task button (having got to the first Pschedule GUI from pupRadio or Precord) it is painful to have to then manually have to enter the stuff I mentioned, when your program could have that all prepared already for entry. Yes, cut and paste would work, but that would be an untidy workaround. However, there is light on that horizon...
I have discovered that it is an entirely trivial matter to give Pschedule the ability to read the "Command" and the "Task name (optional)" from the command line. In fact I now use a specially modified Pschedule myself for exactly that. Fortunately, none of the major functions of Pschedule care at all really about anything being added as command line parameters so the modification is simple and consists of only:
one additional line to the main program /usr/local/pschedule/pschedule
one small alteration to another line of that program (to pass the parameters onwards)
and then,
minor alterations to two lines in the pschedule function program /usr/local/pschedule/func_new
I'll contact Zigbert about it to see if he would put these changes into his official code base; small though these additions are, they make a huge difference to the functionality of Pschedule when it comes to using it with apps like ours. And Pschedule is potentially a very useful core application, so such an addition would be very valuable (as we are both showing...;-)
In case you want to try the Pschedule mod yourself, here are the simple details - assuming you activate line numbers in Geany or your favourite text editor... i.e. Geany -> Edit -> Preferences -> Editor -> Display -> Turn on line numbers (it took me ages to find that!...):
In /usr/local/pschedule/pschedule:
insert a new line 20 containing:
Modify line 104 (within BUTTON_ADD) from:
----------------------------------------
In /usr/local/pschedule/func_new:
Modify line 2 from:
and also in func_new, modify line 52 from:
Now, I can start Pschedule, from the commandline (or later version of Precord) with the likes of:
so as soon as I then press "Add task" these two essential details are automatically then filled in. I think that is what you (and I certainly) probably want rather than having to enter such details manually or with cut and paste?
I could supply a diff, but the changes are so simple, and if Zigbert is willing to make these simple mods it would probably be easier and best, in terms of checking/testing, that he just adds them manually to his original code.
I haven't tested these mods thoroughly yet, but on reading the code they seem to have no effect on anything else; they just add the new functionality, quickly and easily. The reason the change is so minor is that the existing MODE variable only really matters when it is "Edit" mode, and the above changes are only concerned with "Add task" mode.
Anyway, I'll wait on your comments before bringing the matter up with Zigbert in case you have some extra desires or thoughts that would be easily catered for (now or in the future). I doubt it would be easy to modify Pschedule for anything much more, however, and from my point of view the rest of the app is just perfect for my purposes anyway.
First of all, it was pupRadio that actually made me think about using Pscheduler, and really I stuck a button for the latter into Precord with that in mind (so I've been planning to nudge you in this direction for 'ages'...:-)
I expect that most people never or hardly ever use Pscheduler, which is a great pity, because it is a very useful application. I have read of a few people who have used it to make it play an audio file to wake them up in the morning, but of course pupRadio with Pscheduler would give all that and more...
I've actually found Precord with Pscheduler quite fun to play with, except that it is dangerous!... I forgot I had scheduled Precord to start recording at a specific time in the evening, and later in the day I discovered Precord had been running in the background (completely invisible since commandline started) recording my every movements for several hours...
But, yes, it also occurred to me that I don't 'just' want to use Pscheduler/Precord to snoop on myself... or anyone else for that matter, but what was missing in the possibilities was... pupRadio...
However, once you look at the way Pschedule works, you will notice that once you press "Add task", for a new task, you are taken to a new dialog in which you need to manually enter the program to be run and to manually supply an optional name for the new task. The problem is the "manually" part... To interface nicely with Precord, pupRadio, or any other program (rather than a human) it would be really nice if Pschedule allowed such programs to send these details as parameters - but Pschedule doesn't have that facility at the moment...
The fact that you come to the Add task, Edit, Delete, Run GUI isn't an issue, In fact, I feel that that is a good arrangement, since it allows you to immediately manage existing tasks prior to activating your new one. But when you then press the Add task button (having got to the first Pschedule GUI from pupRadio or Precord) it is painful to have to then manually have to enter the stuff I mentioned, when your program could have that all prepared already for entry. Yes, cut and paste would work, but that would be an untidy workaround. However, there is light on that horizon...
I have discovered that it is an entirely trivial matter to give Pschedule the ability to read the "Command" and the "Task name (optional)" from the command line. In fact I now use a specially modified Pschedule myself for exactly that. Fortunately, none of the major functions of Pschedule care at all really about anything being added as command line parameters so the modification is simple and consists of only:
one additional line to the main program /usr/local/pschedule/pschedule
one small alteration to another line of that program (to pass the parameters onwards)
and then,
minor alterations to two lines in the pschedule function program /usr/local/pschedule/func_new
I'll contact Zigbert about it to see if he would put these changes into his official code base; small though these additions are, they make a huge difference to the functionality of Pschedule when it comes to using it with apps like ours. And Pschedule is potentially a very useful core application, so such an addition would be very valuable (as we are both showing...;-)
In case you want to try the Pschedule mod yourself, here are the simple details - assuming you activate line numbers in Geany or your favourite text editor... i.e. Geany -> Edit -> Preferences -> Editor -> Display -> Turn on line numbers (it took me ages to find that!...):
In /usr/local/pschedule/pschedule:
insert a new line 20 containing:
Code: Select all
TASK="$1"; TASKNAME="$2"
Code: Select all
<action>. $PROGPATH/func_new</action>
to:
<action>. $PROGPATH/func_new \"$TASK\" \"$TASKNAME\"</action>
In /usr/local/pschedule/func_new:
Modify line 2 from:
Code: Select all
MODE="$1"
to:
MODE="$1"; TASKNAME="$2"
Code: Select all
if [ "$MODE" != "-edit" ]; then TASK='gxmessage "Happy Puppy"'; TASKNAME='Please enter the task name"'; fi #jake_take
to:
if [ "$MODE" != "-edit" ]; then "TASK"="$TASK"; "TASKNAME"="$TASKNAME"; fi #jake_take
Code: Select all
pschedule "precord rec out.mp3" "Record file task"
i.e. in the form:
pschedule Command [Task Name]
I could supply a diff, but the changes are so simple, and if Zigbert is willing to make these simple mods it would probably be easier and best, in terms of checking/testing, that he just adds them manually to his original code.
I haven't tested these mods thoroughly yet, but on reading the code they seem to have no effect on anything else; they just add the new functionality, quickly and easily. The reason the change is so minor is that the existing MODE variable only really matters when it is "Edit" mode, and the above changes are only concerned with "Add task" mode.
Anyway, I'll wait on your comments before bringing the matter up with Zigbert in case you have some extra desires or thoughts that would be easily catered for (now or in the future). I doubt it would be easy to modify Pschedule for anything much more, however, and from my point of view the rest of the app is just perfect for my purposes anyway.
github mcewanw