dtas-ctl queue cat in case player paused and song not started

dtas-ctl queue cat in case player paused and song not started

[Rene Maurer]

,----
| dtas-player &
| idle
|
| $ dtas-ctl queue cat
| --- []
| 
| $ dtas-ctl pause
| ---
| paused:
|   before: false
|   after: true
| 
| $dtas-enq /home/rene/tango.flac
| /home/rene/tango.flac OK
| 
| $ dtas-ctl queue cat
| ---
| - "/home/rene/tango.flac"
`----

IMHO the output of dtas-ctl queue cat should be
,----
| ---
| - - "/home/rene/tango.flac"
|   - 0s
`----

What do you think?

Best
René

Re: dtas-ctl queue cat in case player paused and song not started

[Eric Wong]

Rene Maurer <rmnet@mailc.net> wrote:
> | $ dtas-ctl queue cat
> | ---
> | - "/home/rene/tango.flac"
> `----
> 
> IMHO the output of dtas-ctl queue cat should be
> ,----
> | ---
> | - - "/home/rene/tango.flac"
> |   - 0s
> `----
> 
> What do you think?

I consider the zero offset to be implied.

Redundant data just adds to noise over socket and output; and
it waste 80 bytes(!) of memory in the player for (40 bytes if
you're on 32-bit).

I don't think anybody would run the following on the command-line:

	play foo.flac trim 0

Instead of:

	play foo.flac

Re: dtas-ctl queue cat in case player paused and song not started

[Rene Maurer]

Eric Wong <e@80x24.org> wrote:
> Redundant data just adds to noise over socket and output;

You are right. And on the other hand it's not a big deal to distinguish
between the output formats.

> I don't think anybody would run the following on the command-line:
> 
> 	play foo.flac trim 0
> 
> Instead of:
> 
> 	play foo.flac

I start the player in paused state; add songs to the queue (while
watching the queue with dtas-ctl queue cat). As said, no problem
without zero offset.