Easy question, I just cant find it - Where is paused TV stored

[JuJuJurassic 42]

An easy question, I just can't find it in the documentation.

When watching live TV, if you pause it, where does it store the data? Once you resume it continues from the last "pause" So either the TV tuner stops transmitting or Emby stores it, which one is it? 

I want to make sure I have enough space available. Any guides to the amount of data relative to the time? MB per second or something similar

I'm using HDHome run

Thanks

[Q-Droid 848]

Emby continues to store the stream in the transcoding temp path.

Space usage depends on the bitrate of the raw stream. A safe calculation is raw stream bitrate x time x2. I've seen the raw stream stored in large segments and the playback/transcoded stream in smaller segments along with the m3u8 file. So you have two copies in the temp path. If you're watching and recording that can be three copies but if I remember correctly the third is in the item's media folder.

 

 

 

[JuJuJurassic 42]

Thank you for that, Much apprechiated  

[JuJuJurassic 42]

Sorry Q-Droid, but I'm trying to work out numbers for storage. I looked at "stats for nerds"  for a live stream of BBC1 from aHDHomerun box and got;

Stream

 

MPEGTS (6 mbps)

HLS (6 mbps 28 fps)

Converting to compatible container

Video

 

576i MPEG2VIDEO

Main 8 5 mbps 25 fps

Transcode (H264 5 mbps)

Deinterlacing

Dropped Frames

0

Audio

 

English MP2 stereo

256 kbps 48000 Hz

Transcode (AAC 192 kbps)

So for every second do I need 6mbx2x30 for 30 seconds, which would be 360MB? I think I must have this wrong.

Thanks

[pünktchen 1343]

The stream is MBit but the storage is MByte, so you need to devide the bitrate by 8.

[Q-Droid 848]

^this^. And you want to account for audio too though 2x raw stream could give you enough of a fudge factor. 

[JuJuJurassic 42]

Thanks pünktchen I missed that.

so it's (6/8)x2x30 for a 30 second clip, or 45 MB, much more reasonable. I have a spare SSD in the server with 200 GB remaining, so that should be more than adequate. I think around 40 hours -ish

I'll keep this as a separate post, for those searching for this information. I'll generate another post for transcode file sizes, for me, but also for the next person.

Thanks

[Carlo 4530]

Just to add to this, a dedicated NVMe or SSD is ideal for transcoding functionality.
The worst place to have a transcoding directory is on a spinning HDD that's nearly full.  Drives write from the outside of the platter (fastest) to inside (slowest). Typically, writes to spinning drives get more and more fragmented the fuller they are. This may sound like a double whammy but it's likely 10x slower or more which can make transcoding performance difficult to sustain.