Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Transcoding HLS streams
18-04-2023, 16:04
Post: #41
RE: Transcoding HLS streams
(05-04-2023 12:23)simoncn Wrote:  Yes, the stream will stop after 4 GB of data. This is the size limit for WAV but not for L16. You should be able to use any streamSize value for L16.

FAO Simon - @amsub got in touch with me and reported that however high a value he puts as StreamSize, the stream ends after 3.5 hours. I tried the same and found that the stream ends at 3 hours (why such a difference if we're both transcoding to L16?).

I'm guessing that something somewhere has its own max value for StreamSize regardless of what's been specified, and that it's probably the NP30, but just to be sure, attached is a debug log file started a few minutes before the stream ends.

I'm hoping that will clarify what part of the chain has decided that the stream has ended and whether or not anything can be done about it. I've had a look but I'm not confident of my interpretation. Please could you have a look at it?


Attached File(s)
.zip  MinimWatchLog (9).zip (Size: 3.19 KB / Downloads: 2)
Find all posts by this user
Quote this message in a reply
18-04-2023, 17:12
Post: #42
RE: Transcoding HLS streams
This log shows that the renderer (not MinimStreamer) has closed the stream after 2 GB of data were sent. The difference in elapsed time could be caused by different sample rates (a 44.1 kHz stream would play for longer than a 48 kHz stream).
Find all posts by this user
Quote this message in a reply
18-04-2023, 17:36
Post: #43
RE: Transcoding HLS streams
Thanks Simon, as suspected then, another 'feature' of the NP30. Fortunately it's no great matter to renew the connection, and I for one don't seem to listen to any one stream for that long in the normal course of events.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)