Technical Support for Jaksta Media Recorder
Asked by Andrew Nichols @ 15 Aug 2017 23:08 / Views: 119
Even though nothing was captured, I've attached a debug log of entering a 'performers room' (and staying for one minute).
From Andrew Nichols @ 28 Jun 2017 23:06
Version 184.108.40.206, July 1, 2017 :
"New HTTPS WebSocket proxy supports H5 Live protocol (reference implementation Jasmin.com)"
I just want to say THANK YOU.
Jaksta Media Recorder STILL THE BEST !
From Nss Dvl @ 08 Jul 2017 02:07
I still can't download HTML 5 based video from that website or others. I suspect they are still working on HTML 5 capture hence the lack of reply.
From Andrew Nichols @ 08 Jul 2017 03:07
Did you try the latest version 220.127.116.11 ?
I tested only the free chat with Mircosoft Edge, Flash is not enabled and It's works for me, the stream is recorded not downloaded and the container is MP4 not FLV.
From NssDvl @ 08 Jul 2017 07:07
So it does, in Edge but not without a duration error. Recordings' duration are blank in Jaksta, never 'Complete' and stated as 3 seconds during playback. I usually use Chrome, by the way.
From Andrew Nichols @ 09 Jul 2017 05:07
It worked for me for both, Edge and Chrome... until today. It doesn't work anymore with Chrome (tested version 18.104.22.168 and 22.214.171.124).
From Nss Dvl @ 08 Aug 2017 11:08
Still captures fine here. Chrome Version 60.0.3112.90 (Official Build) (64-bit)
Jasmin is still using the same websocket protocol we implemented support for in 126.96.36.199. Ie nothing has changed from what I can tell.
Please provide debug logs as per https://support.jaksta.com/discussions/topics/6000009063 if you are still having issues.
From CRS @ 10 Aug 2017 12:08
Using the same version of Chrome but it does not capture.
From Andrew Nichols @ 11 Aug 2017 03:08
Your logs are not in debug mode. Please follow the instructions in the link to collect them correctly (especially step 3).
Here it is again: https://support.jaksta.com/discussions/topics/6000009063
From CRS @ 11 Aug 2017 08:08
Sorry, thought I switched that on.
From Andrew Nichols @ 11 Aug 2017 10:08
Cant really tell as you have switched on debug after you started monitoring and there is only 19 seconds of data, but it looks like the websocket was already open when you started AUTO mode as there is no sign of the redirect going via JMR's internal proxy.
Try this to get us some valid logs:
1. Close your browser. If its chrome make sure all chrome processes are shut. Kill them off if you have to.
2. Open JMR, switch on debug mode and switch on auto
3. Now start your browsers and go to jasmin and watch a model.
4. Recording should start afew moments after the cam starts. If it doesnt, wait a minute and then collect the logs and post them here.
From CRS @ 14 Aug 2017 09:08
Right, debug mode and auto switched on before opening Chrome. Watched performer for two minutes before collecting logs.
From Andrew Nichols @ 15 Aug 2017 05:08
You are still switching on AUTO mode before debug is on so I cant tell what the config is when AUTO starts, but my guess is you have excluded websockets from the proxy cfg.
1. Close all your browsers and JMR
2. Run inetcpl.cpl from "Type here to search"
3. Connections Tab
4. LAN Settings button
5. Check the "use a proxy server .." checkbox to enable the advanced button.
6. Click the Advanced button.
7. Remove any wss:// and ws:// from the "do not use proxy server for addresses beginning with" text area - should look like screenshot below.
8. Click OK
9. Uncheck the "use a proxy server .." checkbox
10. Click OK
If that isnt it then please provide debug logs as per my last post ensuring debug is on before AUTO.
From CRS @ 15 Aug 2017 16:08
"2. Open JMR, switch on debug mode and switch on auto"
Anyway, it was the proxy settings so it works now. Thank you.
From Andrew Nichols @ 15 Aug 2017 23:08