I still haven't done much with this project for the BCD396T & BCD99T scanners.
All that needs to be done is to link the already written low low-level scanner functions to user level commands.
Rewriting the lower-level functions using Structures would also be nice.
Any recommendations or efforts in other areas might be also nice!
I can be contacted at either my SDF or Gmail email (see website at the bottom of this post), or this mailing list.... read more
Most of the code required for Dsctl to function is already written. Although it would be quite easy to finish, I don't see a need to spend any more time on a project that is not being utilized. Although saddened as Dsctl would make the BCD996T units easier to work with, not to mention, it's robustness compared to the win32 stuff.
No need to say anymore. If you want to pick up work from here, SVN is considered more current.... read more
Seems the first push of dsctl-0.2.0.tar.bz2 to the mirror did not take. Source Forge uses a primitive FTP with stripped down user rights for security purposes. Doing one thing astray leaves an uncompleted upload or worse. In this case, a zero byte sized file after I tried creating a bash script for easier uploads to ftp. :-/
Anyways, dsctl-0.2.0 is up for sure now!
Notes:
Much has been completed for this release including ncurses support for the status command.
A popular option for Icecast/Ices servers, "-i" will allow users to specify their Ices PID. This will allow dsctl to send a SIGUSR1 to the Ices process causing Ices to reread the metadata file. This will cause scanner alpha tags to be embedded into their ogg/vorbis stream (or other codec). (Users also need to designate the ~/.dsctl/metadata create metadata file within their /etc/ices2/ config file.)... read more
dsctl -i --icespid [pid] sends Ices2 SIGUSR1 for rereading metadata file. dsctl -h for more info.
(Specify metadatafilename ~/.dsctl/metadata within your /etc/ices2/ices-alsa.xml.)
Known Bug, and on my agenda to fix soon,with this, will cause dsctl to update and send a SIGUSR1 every .5 seconds which instead should only happen every time the metadata changes .
Dsctl also now reads config file info from ~/.dsctl/config
I've added, albeit, simple screenshot displaying a couple of Dsctl's features.
The svn version now sports autoconf/automake. This is in preparation for including termcap/ncurses support. It's something I'm going to play with until I get a "dsctl status" output I'm satisfied with, without breaking basic dsctl function for users whom don't want or don't have termcap/ncurses libs.
Another feature I want to experiment with, executing dsctl as a daemon with the option of activating on specified scanner activity and spawning, either, a temporary or permanent oggenc session.... read more
Dsctl SVN Version now has initial load support.
This just uploads a file created by "dsctl dump" and only uploads basic system data only omitting location settings and other settings. So, save your data with another utility before testing this feature.
I should have the rest of this load command coded for supporting the rest of the commands soon.
Example usage:
$ dsctl dump -b 115200 -p /dev/ttyS0 -m bcd996t > test.log... read more
This is an initial release.
The following commands are now available:
dsctl dump
dsctl key
dsctl version
dsctl status
For help with the above listed commands:
dsctl help [command]
The SVN version of Dsctl has %30 of the BCD commands completed. "sctl dump" for the BCD units is nearly complete and should move along fairly quickly, hence, should be completed soon.
Although I've yet to study all of the other commands specifics, most of the rest are simple to implement. (Uploading Systems and it's properties poses one of the next difficult tasks, but the structure of "load" command is already in place with Sctl... hopefully!)... read more
Subversion initial import is complete!
For now, this is probably the best way to checkout dsctl (sctl).
To checkout:
svn co https://dsctl.svn.sourceforge.net/svnroot/dsctl dsctl
To contribute, run "svn diff > my.patch" from within the root folder and post as an attachment to the mailing list.
(When I start receiving patches, I may require a simple "sign-off" your patch requirement prior to submittal stating you're work is not acquired from other copy righted sources. :-)
This patch is made against Sctl (sctl-0.2.3). (Sctl can be acquired from it's own Source Forge Project page.)
Preferred method of communication is the Mailing List dsctl-devel.