Re: Latest State of Play with xPLRioNet & Gapless Opinion

["chrisalivesey" <chrisalivesey@xxxxxxxxxxx>]

Tony,

*Any* gapless implementation is the way forward. I've only played
around briefly with XPL because the vast majority of my audio is in
flac, so in the mean time I've reverted to Jrec/Trio. I don't know
if it can be done in XPL but I like the trio implementation of
gapless. It decodes flac/ogg natively on the unit and runs the
display and control components on the server. This results in
perfectly gapless playback (at least when using flac) and I've not
noticed any issues with timing on the display (although I don't
really care about this in the short term). One further note is that
adding support for flac and possibly ogg gives us two formats that
are natively capable of gapless to play around with. Thanks again
for you continued feedback and development of XPL!

Cheers

Chris


--- In ukha_xpl@xxxxxxx, "Tony Tofts" <tony@x> wrote:
> Hi all,
>
> Just an update on the current situation.
>
> The new push client for the Rio is working well and seems highly
stable
> compared to previous pull version.
>
> Still need to sort Shoutcasts and TTS though.
>
> The backlight is now under control of timers in xplrionet, so
shouldnt get
> stuck on anymore.
>
> One downside is that the TTS will no longer work with the old
xpl_riotts
> software, to use TTS you will have to use the new mp3 version
(which is a
> windows service that will be made available for download on the
xplrionet
> page. It is also an xpl_tts app, still using a vendor/device of
tonyt-tts to
> avoid breaking existing scripts).
>
> Will advise when it's all available for download.
>
> On the point of gapless playback, mentioned by someone the other
day, this
> _can_ be achieved from the server end but how do people want it
implemented?
>
> Gapless will prevent timely update of the display and timer (it's
feasible
> to embed the info in the stream, but i really want to avoid this
as it's
> pointless pressuring the rio to search all data for a flag).
>
> I think gapless should be implemented as a mode (like random or
mute) and in
> this scenario the timer will just count the total time for all
tracks played
> with the display updating a couple of seconds before a track
changes. This
> is the simplest, and to me, smoothest way to do it. Also this
means gapless
> can be implemented in an identical way on exstreamer/slimp3 and
future
> supported players. Opinions please?
>
> Regards
> Tony
>
>
> [Non-text portions of this message have been removed]