Jaksta

Hi Tiger21,

Thanks for you report. It lines up with our recent findings on this issue, although we still aren't certain what the initial cause of the problem is. We are still working on that.

James - are you still having some kind of problems with Big Sur? If it's still the conversion speeds that are an issue for you then please see my last post in this thread and then let me know if there are any discrepancies from your testing. Also, the V2.2.6 that Tiger21 is referring to would be the beta version that some of our users are running. It is not publicly available to download from our site, but if you would like to update to it then you can download the installer here - https://download.shedworx.com/jaksta/beta/2.2.6_293/JakstaMediaRecorder.pkg

When you first attempt to run the installer you may receive a Mac OS notification saying that it can't be opened because it cannot be checked for malicious software. Click 'OK' and then go to System Preferences > Security & Privacy > General and click on 'Open Anyway' down the bottom. It will either run the installer or another similar notification as the first will appear and you just need to click 'Open' and then the installer will run.

Regards

Liam

Jaksta Support

Hi James,

Good chance that's where the issue lies.

A good way to test this is to download and install the Jaksta Converter, then put the downloaded .m2ts file* into it and set the conversion output to the same type Jaksta Media Recorder is set to. It should then tell you what the conversion speed will be, and if it's either of 'Slow' or 'Slowest' then that will support my theory. You can even begin the conversion process as a test and see how fast or slow it goes.

Jaksta Media Recorder uses the same conversion engine as Jaksta Converter, so this would make for a solid comparison.

*You can get the pre-converted .m2ts file from your Downloads location, which is set in the Media Recorder Preferences > Downloads. You will also need to have the 'Delete Original After Conversion' setting turned OFF in Preferences > Conversion.

Regards

Liam

Jaksta Support

Hi James,

It's pretty hard to determine why a conversion might be slow, as it depends on many thins, such as:

• internet speed
• stream properties
• video size
• conversion type
• etc.

The list goes on.

If you want you can run a test on a standard YouTube video and set the conversion output to Default and then see if that is slow. If it is, you could generate a clean log like how I outline before and send that through for us to review. If it's speedy enough, then your other slow downloads  might be due to one of the reasons I listed above.

Regards

Liam

Jaksta Support

Hi James,

That is odd, but I'd say take the win!

So does that mean we can consider this resolved for now?

Regards

Liam

Jaksta Support

Hi James,

Can you please send me a screenshot of your Certificates list?

If it is indeed missing then that will be the problem. The next step will then be to work out if that is due to Big Sur in any way or a separate reason.

Regards

Liam

Jaksta Support

HI James,

If that's the case then there is a chance that is a certificate issue.

Can I please get you to do a check for me and do the following:

- Open: Keychain Access

- Select: 'Certificates' in the Category section in the bottom-left corner

- Double click on: 'applian.com' certificate to open up its details

- Under the Details section find the two lines that are titles 'Not Valid Before' and 'Not Valid After'

- Look at the dates and make sure that neither date is set to a value that would conflict with the current date

- Take a screenshot of the whole window and provide it here (make a point to also expand the Trust section and capture that as well)

Regards

Liam

Jaksta Support

Hi James,

No, nobody has reported this as a problem yet. We are currently looking into this to see if it's potentially a Big Sur related issue.

In the event that it's an issue specific to your system, there are a few checks you could do.

You can check the proxy settings by going into System Preferences > Network > Advanced > Proxies and viewing the Web Proxy (HTTP) and Secure Web Proxy (HTTPS) protocols. Both proxies should be configured with the same settings as seen in the below image. Manually adjust them if they are not correct.

These two proxy settings should both be active (ticked) when Jaksta monitoring is ON and deactivated (unticked) when monitoring is OFF. If you toggle the ON/OFF switch in Jaksta then you should be able to see the proxy settings go on and off at the same time.

If they look to be correct then you can check your Firewall settings and make sure that Jaksta isn't being blocked. Go to System Preferences > Security & Privacy > Firewall Options (click the padlock and enter your user credentials to unlock the ability to make changes) and check that Jaksta Media Recorder has a green dot and says 'Allow incoming connections'. If the dot is red then click on the dot and change it to 'Allow incoming connections'. If it is not on the list at all then click the '+' symbol and add Jaksta Media Recorder from the Applications folder.

If the problem persists after doing these checks then it would be good if you could send us a cleaen log to review.

To get a clean log, you will need to do the following:

• Open Jaksta Media Recorder (JMR)
• Go to Preferences > General > Find Log File
  • This will open a Finder window that needs to remain open for the remainder of the process
• Quit JMR
• Delete the log file in the Finder window
• Reopen JMR 
  • This will automatically generate a new log file in the Finder window
• Run one test capture on the problem site/stream (in your case you won't get this far, but just let the browser error appear and then proceed to the next step)
• Quit JMR once it fails and/or the error is reproduced
• Source the new log file in the Finder window and then attach it here (don't copy and paste the code in it - send the file itself)

Regards

Liam

Jaksta Support