lab 66 - useful tools

By

NAME

lab 66 - useful tools

NOTES

This is a light lab about writting some useful day-to-day tools, mainly language and music playing tools.

gask is a simple script for doing searches with google, which is nice when you want to consult something while writting a text, it returns the output in textual form so it can be used/plumbed etc.

the next tools are for rapidly looking definitions in english/spanish/... on a dictionary, and they're handy when you aren't a native speaker.

trgg (translate google) allows you to translate between any pair of languages that are supported by google, the usage of the command is trgg 'sl|dl' text, or |trgg 'sl|dl' where: sl: is the source language (by default english) dl: is the destination language (by default spanish)

while dorg does a search on the dictionaries using the services of www.dict.org site,

drae is is an interface to the "Real Academia de la Lengua" dictionary, so you can consult the meaning of spanish words.

And last but not least there's the google's define: keyword, that looks on the web for definitions of the arguments provided.

For interacting with google's services HTTP POST request support is needed, we can find it in webfsget as in the google-api lab, but we can also get it from hget.c and incorporate it to webgrab with a [-p post] option. That's the aproach followed.

oggplay, madplay and audio, those three scripts are used to play music in the mp3 and ogg formats, for writting them i've needed to modify wav2iaf(1) and auplay(1) to work with data piped to it's standard input and write the result to it's standard output. And last audio is a small utility to query/set the parameters of /dev/audioctl. With this tools it's very easy to set up a few plumbing rules, to handle music files.

Update: Added a rsscheck script to check updates in caerwyn.com and google-code by default.

FILES

lab 66 code

Comments

Anonymous said…
Seems slightly pointless to run madplay and then to pipe audio back into auplay. Though I can situations where it might be useful to decompress audio on another computer and play it back locally. I use shell file2chan like this :
load file2chan
{file2chan /chan/mp3 {} {fetchwdata} }| os madplay - &
then I export that /chan/mp3 directory and can play back music by copying mp3s onto it.
5:35 AM
Post a Comment

Popular posts from this blog

lab 110 - inferno archive edition

By
I've been occupied recently with archiving my digital media. I've been copying home videos on DV tapes to hard-disk, ripping audio CD's to WAV files, gathering photo collections, and trying to copy documents from Iomega disks, floppies, and my dusty old Acorn RiscPC. The plan is to have a copy of this data to give to each of my children. My Dad recently scanned and sent me all his photographs of me and my siblings growing up; he also included pictures of himself and my Mother when they met in Africa. With technology today each generation can build a digital library of family history to hand on to the next generation. In the past a family album may have been passed on to only one person. The accumulation of digital data still presents problems. It requires discipline to store files that are open and not locked into devices or proprietary formats. With digital preservation in mind I've tried to use file formats recommended for long term archiving. WAV files for audio, D...
Read more

lab 111 - wavloop

By
Image
WAV file format contains audio sample data and optionally meta-data that describe the offsets of sample loops and cue points. The loop offsets are used by sampler software to generate a continuous sound, and the cue points mark the point in the sample data where the sound fades away after the note has been released. A WAV file "smpl" chunk will identify the byte sample offset of the start and end of the loop in the sound data. Using wavplay.b as a starting point I tried to loop a sampled sound. My sample data comes from Virtual Organ software GrandOrgue and the sample sets created for it. In this case I'm using the Burea Funeral Chapel sample set. My first test was simply to treat the sample as-is and loop the sound using the given offsets. This did not give good results with a notable noise as the data from the end of the sample joined with the beginning. I realized nearing the end of writing this post that the mistake I made was treating the offsets as counts of...
Read more

lab 107 - midiplay

By
NAME lab 107 - midiplay NOTES Midiplay plays back MIDI files. It uses the synthesizer I described in lab 62 and the MIDI module from lab 73. The command takes only one argument, the path to the midi file. I've included one in the lab to demonstrate. Bind the audio device before using it. % bind -a '#A' /dev % midiplay invent15.mid The synthesizer has 16 note polyphony. It uses three oscillators, one at the pitch, one at half pitch, one at double pitch. There is also a filter, two delays and a vibrato. The sample rate is 8000hz and there is one mono channel (MIDI channel events are ignored). It performs well enough to work on my laptop without JIT turned on. All the synthesizer parameters can only be tweaked from inside the code at the moment. FILES lab - 107
Read more