Technical Support for Jaksta Media Recorder

Support | Windows | Technical | Jaksta Media Recorder | livestream downloads terminate early

livestream downloads terminate early

Asked by Clinton Solon @ 13 Jun 2018 12:06 / Views: 42

This info might be old. Please read more info about the best way to download from livestream now.

I download German TV from these two livestreams (geoblocked outside Germany, so I use Smart DNS Proxy)

https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/index_2296_av-p.m3u8?sd=10&dw=0&rebase=on

and

http://daserstelive-lh.akamaihd.net/i/daserste_de@38086/index_1992_av-p.m3u8?sd=10&rebase=on

Mostly, everything works fine, I schedule a recording with start time/date and duration, and I get an mp4 file which plays perfectly.

But  about one in ten of my downloads, on a completely random basis, fails by terminating early. The download shows complete, no error message of any sort, I get a useable file, but it's not all there, ie. of shorter duration than specified. Like a one hour recording might terminate anywhere between 1 minute and 59 minutes.

Now one in ten is quite a high probability in my opinion, and I never know when it's going to happen, so it's rather annoying.

So the question is, is this the best I can expect, or maybe there are some settings I should change?  Applian suggested I go to settings/internet downloads/advanced/http and set Max. number of segments to 1. That didn't help. Are there any other settings that might help?

I'm puzzled as to why the software doesn't give any error message or attempt to reconnect. Surely it must "know" that something's gone wrong when it signs off a download as complete after 25 min although the specified time was 45 min?

Help please.

Thanks,

Clinton Solon

ps - Windows 7 64bit Pro,  internet connection ADSL, full speed about 10 Mb/s


From @

Not sure why they would have told you to change that setting as those streams are HLS protocol which has settings under Settings > Internet Downloads > Advanced > HLS.


If no error is displayed then the stream has ended for some reason.


You will need to provide debug logs that show the stream terminating early so I can see if there is any reason for it that you will have control over.


https://www.jaksta.com/support/windows/technical/jaksta-media-recorder/how-to-generate-debug-logs-6000009063


Those streams are not geoblocked btw, I can get to them from Australia no probs and capture them.


From @

Ok so I turn on debug-logs and just leave it on until I get another failure. The I notify you and send logs.

Have I got that right?

That's interesting that the streams aren't geoblocked for you. They certainly are for me here in NZ

Clinton Solon


From @

Yes please.


From @

I've just had another early termination failure of a scheduled download. Unfortunately debug mode was OFF, because that seems to be the default option when Jaksta starts, and I wasn't there to turn it ON. Is there any way of setting the default option to ON? I can't alway be thereto turn it on.

Thanks,
Clinton Solon



From @

Follow the steps in the section to turn debug on permanently:


"If the application doesn't start or crashes on start"


https://www.jaksta.com/support/windows/technical/jaksta-media-recorder/how-to-generate-debug-logs-6000009063  




From @

Here's another download that stopped early. Scheduled to run for 50m, stopped after 8m58s. Screenshots and debug logs attached. I'll be very pleased if you can throw some light on why this is happening.

Thanks,

Clinton Solon


From @

After 8:14 mins the download started to receive Read time out errors and after multiple retires gave up.


What is causing the time out errors?  Well it is most probably your internet connection dropping or some other internet issue.  


You can control the timeouts and number of retries for HLS via Settings > Internet Downloads > Advanced > HLS.


Below is the relevant parts of the debug logs showing the time outs.


HTH



2018-07-10 20:39:15,131 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out.)
2018-07-10 20:39:15,132 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out.)
2018-07-10 20:39:18,987 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121192: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121192_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out.)
2018-07-10 20:39:18,988 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121192: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121192_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out.)
2018-07-10 20:39:31,835 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][warning] Failed to reload playlist: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/index_2296_av-p.m3u8?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Max retries exceeded with url: /i/de14_v1@392878/index_2296_av-p.m3u8?sd=10&dw=0&rebase=on (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x03305830>, 'Connection to zdf1314-lh.akamaihd.net timed out. (connect timeout=20.0)')))
2018-07-10 20:39:31,836 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][warning] Failed to reload playlist: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/index_2296_av-p.m3u8?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Max retries exceeded with url: /i/de14_v1@392878/index_2296_av-p.m3u8?sd=10&dw=0&rebase=on (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x03305830>, 'Connection to zdf1314-lh.akamaihd.net timed out. (connect timeout=20.0)')))
2018-07-10 20:39:36,444 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out. (read timeout=10.0))
2018-07-10 20:39:36,445 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (HTTPSConnectionPool(host='zdf1314-lh.akamaihd.net', port=443): Read timed out. (read timeout=10.0))
2018-07-10 20:39:43,931 [4] INFO  c3 [(null)] - HlsdManager: [cli][error] Error when reading from stream: Read timeout
2018-07-10 20:39:43,932 [4] INFO  c3 [(null)] - HlsdManager: [cli][error] Error when reading from stream: Read timeout
2018-07-10 20:39:44,344 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (404 Client Error: Not Found for url: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on)
2018-07-10 20:39:44,344 [4] INFO  c3 [(null)] - HlsdManager: [stream.hls][error] Failed to open segment 153121191: Unable to open URL: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on (404 Client Error: Not Found for url: https://zdf1314-lh.akamaihd.net/i/de14_v1@392878/segment153121191_2296_av-p.ts?sd=10&dw=0&rebase=on)




From @

Thanks for that info. As for the HLS settings, remember that you know what they do, but I don't!  Mine are still the default settings, I assume, because I haven't touched them - see screenshot attached.

 What changes could I make to them, that might make these disconnects less likely?

Thanks,
Clinton Solon


From @

There are tooltips on all of them that explain what each does.  Just hover your mouse over them.

As you are getting read timeouts try adjusting segment timeout and segment attempts to start with.


From @

Would you care to make a suggestion as to what I should set them to?

Also with HLS streams I am scheduling them with Normal URL, but Extraction engine URL works as well. Which one should I be using?

Thanks, Clinton Solon 


From @

I cant really say say it depends on your internet connection and why it is dropping.  I guess 30 for a time out and say 10 reties and see how you go.  Its a case of playing around with them given it doesnt happen all the time and your not sure what is happening with your connection.


You can use either normal or extraction engine url for HLS m3u8 urls.


From @

I've just had another failure, same URL, ran for 22m instead of 50. I had set segment timeout to 60, retries to 10.

Log attached. Got any more suggestions?

Would this sort of thing be much less likely to happen if I had a fast connection, say100Mbs, instead of my ADSL at 12Mbs?

Log attached.

Thanks,

Clinton Solon


From @

Here's the latest failure. Scheduled to run 55m, stopped after 39m. Log attached.

Clinton Solon


From @

Your logs are not in debug mode so dont show anything.  As I mentioned previously as you are getting timeout errors something is happening with your internet connection.  All as you can do is try adjusting settings but if the connection goes down there is nothing that the software can do.


From @

I'm still having too many failures where the download stops after less than scheduled time. To what extent do you think my slow internet connection ( ADSL 10Mbs) - might be a contributing factor? The only better connection I could get is wireless 4G broadband, about 20 to 50 MBs. Is that likely to improve things?

Thanks,

Clinton Solon


From @

Here are two more failures.

See homescreen.jpg

Item 51 scheduled for 20 Aug at 2030 for 50 min shows complete with errors,

Item 48 scheduled for 18 Aug at 2214 for 100 min, stopped after 1m.

Can you throw any light on why please? Logs attached.

Thankyou

Clinton Solon


From @

You are using an old version 17.  Please upgrade to 23 before submitting new logs.

https://www.jaksta.com/download/windows/jaksta-media-recorder

One finished because the max duration was reached and the other failed with

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

You can see both of these in the downloads progress log available on the properties window.


From @

Ok so download #51 was a one-time glitch that might never happen again, but what about #48?

If the maximum duration was reached then means I made a mistake and entered 1m instead of 100m. (I'm perfectly capable of doing something dumb like that). Is that what  happened? Does the log actually show a scheduled time of only 1m?

Comment please?

Thanks,

Clinton Solon


From @

Yes it showed the max duration of 1 minute being reached.  Please look in the progress log which you have access through via the UI and you will see these messages.


1. Select the download you are interested in

2. Click the Main Menu > Properties (or right mouse context menu > Properties or Alt-Enter hot keys)

3. Progress Log tab.

It shows all the details of the download/recording including errors.


From @

I've just updated to 7.01.23. It didn't store my HLS advanced settings. Tell me what "concurrent segments" (presently 5) and "segment live edge"(currently 3) do please?  Will they have any effect on chances of a download crash? If so,, what are best settings?

Thanks,

Clinton Solon


From @

Settings are carried forward as long as you dont uninstall first.

There are tooltips on all the settings that explain what they do.

Live Edge: No of segments from the end to start live HLS streams on. The lower the value the lower latency from the source, but also increases the chance of buffering

Concurrent Segments: HLS downloads are split into segments and each segment is downloaded independently. To improve performance segments can be downloaded concurrently. This setting defines the number of segments to be downloaded concurrently.

The best settings for a normal stream and normal internet connection are the default ones.  


From @

Here's something odd.

Download #56 was scheduled for 23.08.18 , 50min, but the file produced was only 44:30. The progress log shows it did in fact run for 50 min with no errors, so why the shorter file? It hasn't happened before.

 

Thanks,

Clinton Solon


From @

I scheduled a download to output file 08292030 Notruf Hafenkante 165 Held des Tages.mp4, start 29 August 18 at 20.30, duration 50 minutes. Download "completed" after 11m 30s. I can't interpret the logs at all - could you please explain in as much detail as possible what went wrong?

Relevant debug log attached.

thanks

Clinton Solon

ps - no answer yet to previous support request


From @

Previous question -  Around the 16 minute mark there was a bunch of segments that could not be downloaded as they did not exist. (404 error).  Then again around the 17.30 mark, 19.05, 19.12, 20.48, 22.29.  In all some 4 minutes of video couldn't be downloaded. 


This last question-


Errorred out due to a read time out:  


Error when reading from stream: Read timeout.






From @

This info might be old. Please read more info about the best way to download from livestream now.