[mythtv-users] Lots of weird unexpected files in an unexpected place

[Chris Pinkham]

* On Fri Feb 07, 2014 at 12:50:34AM -0500, Jay Ashworth wrote:
> > From: "Raymond Wagner" <raymond at wagnerrp.com>
> > > 2) Why are they still there from last Nov 27?
> > 
> > Not sure. They should expire on their own.
> 
> Interesting.

They won't auto expire on their own, that was up to the client
that initiated the transcode.  If a mobile user was watching
something, then paused, then came back an hour later, I didn't want
the recording to have been deleted out from under the client.

If I ever get the time to get back to my work-in-progress on-demand
HLS transcoding, then these would be auto deleted because my new
code has the ability to generate missing segments on the fly,
allowing both deleting of these segments as well as skipping forward
to a segment which had not yet been transcoded.

> I'll need to figure out why that's the default place then, so I can
> move it.

It's in the 'Streaming' Storage Group as noted earlier.  This wasn't meant
be a long-term storage location originally, if users are using a client
that keeps transcoded files around for a lont time, they should create
a new directory somewhere with a lot of storage and make a 'Streaming'
Storage Group pointed at it.  I think this has been discussed quite a few
times on the lists over the years and also thought it was documented by
Robert somewhere.

> > > 4) Can I whack them safely?
> > 
> > They are referenced in the database. I don't know off hand if the HLS
> > server will clean up after itself if the transcoded segments go
> > missing.
> 
> Well, it already hasn't, so...

If you remove them all, and there are no current HLS transcodes running,
then you can "truncate table livestream;" safely.

--
Chris