From: Rene Maurer <rmnet@mailc.net>
To: dtas-all@nongnu.org
Subject: Re: how do you use dtas?
Date: Sun, 6 Dec 2015 13:38:21 +0100 [thread overview]
Message-ID: <20151206133821.476225e9@loco5> (raw)
In-Reply-To: <20151205020028.GA13812@dcvr.yhbt.net>
I use dtas for audio play back over USB.
Queue only (maybe I will replace this with dtas-tl in the future).
As I normally do a lot of things with python I have written some minimal
wrappers so I can use dtas together with python.
Commands in use:
dtas-enq
dtas-ctl source ed sox sink ed .... (sound card control)
dtas-ctl source ed sox command= .... (low/highpass and fadeout control)
dtas-ctl state dump /tmp/playerstate.yml
dtas-ctl clear | current | pause | play | seek | skip
Example workflow (this is how work as Tango DJ):
1. Start dtas-player:
dtas-player &
dtas-ctl source ed sox sink ed default env.AUDIODRIVER=alsa \
env.AUDIODEV=hw:1,0 env.SOX_OPTS=
dtas-ctl source ed sox command=exec sox "$INFILE" $SOXFMT - $TRIMFX \
$RGFX sinc 35 sinc -9k
2. Start QuodLibet
I use QuodLibet to manage my music library. I decide what to play next
and I use a plugin I have written for QuodLibet to add the next song(s)
to the dtas player queue. While playing for the audience (with dtas) I
use QuodLibet for pre-listening.
3. Start my own dtas queue viewer and minimal control application.
This is a very small application (using tk) that shows the content of
the queue and enables some control (mainly play, pause and fadeout).
4. I have planned to use more EQ settings depending on the decade of
the music (Music from the the thirties (Shellac) differs a lot from the
music of the fifties (Vinyl) which differs a lot from digital music of
these days).
Best René
Eric Wong <e@80x24.org> wrote:
> Just wondering how folks are currently using dtas these days.
>
> dtas-ctl ... (which commands)
>
> dtas-enq ...
>
> dtas-tl addtail ...
>
> dtas-console + interactive mode?
>
> etc?
>
> I mainly use "dtas-tl addtail|add|remove|clear" for casual listening,
> sometimes "dtas-enq", and dtas-console for pausing/seeking; etc.
>
>
> For EQ-ing on my own recordings:
>
> 1) I'll write a YAML file with a custom "command:" param for -splitfx
>
> 2) add the YAML file (via dtas-tl add/addtail or dtas-enq)
>
> 3) Edit the YAML files with my favorite editor;
> relying on inotify (via sleepy_penguin RubyGem)
> to pick when my editor saves the file.
>
> This lets me hear EQ changes whenever I save the
> YAML file in my editor (or the playback stops when I make a typo).
>
> To loop a section of a track I want to focus on, I'll set:
>
> dtas-tl repeat 1 && dtas-ctl trim START_TIME LENGTH
>
> ("dtas-ctl trim off && dtas-tl repeat false" to resume normal
> playback)
>
next prev parent reply other threads:[~2015-12-06 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 2:00 how do you use dtas? Eric Wong
2015-12-06 12:38 ` Rene Maurer [this message]
2015-12-07 4:43 ` Eric Wong
2015-12-06 17:42 ` Rene Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://80x24.org/dtas/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151206133821.476225e9@loco5 \
--to=rmnet@mailc.net \
--cc=dtas-all@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/dtas.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).