Jaksta

Everything works normally while I’m monitoring or recording, but recently every recording has started failing as soon as it finishes. After the final step, tagging, the file breaks. Some recordings show as 0 bytes as if nothing was captured, some show an error, some say ‘manually stopped’ even when I didn’t stop them, and others show as completed but contain no data.

This has been happening for about a week, getting progressively worse, and today every single recording is broken and shows nothing.

I've been having this same exact issue as well, and I wonder if this is a site-specific problem, or something Jaksta needs to fix. It doesn't happen with all. The shortcut I've found is to actually stop the recording the moment I'm done with it, instead of letting it automatically stop like normal. That has helped a great deal, at least until this particular issue is fixed. 

Stopping recording manually causes a "cancelling" loop where rather than stopping it just continues to record until the stream that it's recording finishes which again results in the errors.

I've also tried using both the Split Every functions but those just again end up never stopping and keep recording until the end of what it is recording but this time it would start a whole new recording every "x" minutes that I've set it to, like a new recording every 59mins as an example.

I have no idea what the Split At does and what the 8 number slots stand for and it is hard to do any tests as everything is broken and refusing to stop when it should

I have this too. I seems to work find on MyFreeCams, but when I try and record on Chaturbate it gives me a '0 bytes' file after it's finished recording.

Chaturbate is incredibly tough again. Very few rooms will record and now state that Jaksta is recording 'audio only 192'. I've never had to touch settings in years. Always set to save as mp4's. The resulting recording states a file size within the Jaksta app, but once the file's folder is opened it is 0mg. Complete error. I've also tried to use the 'auto' setting but the identical failure of audio only recording. All being 0mg. Seems Chaturbate has scrambled/blocked Jaksta settings again. Using the newest 2026 version. Been a huge fan of this great app for years. Please help.

Having the same issue for last few days, It's happening to most links, one or two are working okay:

Hey guys, we pretty much gather here because of Chaturbate and hoping for an update!

But supporters don't answer here anymore, you can write them directly - and please do - starting at this destination:

https://support.applian.com

During your ticket you can set a priority ("urgent") and pick the product "Jaksta" but JMR merged with Applian and the code wizard behind JMR left the company afaik. Really hope we can continue, otherwise if anyone knows an alternative please post it here :)

Also, I don't think there is any place to disuss Jaksta/JMR besides currently this thread?

I do have 2 long standing problems and hope for some input/help if you encounter the same using JMR:

1) Very often JMR (Monitor and manual URL download) can not pick up a public + live Chaturbate stream first try and will need maybe 10 to 20 checks (!) until the stream starts downloading. It means I'll miss a big amount of videos. Anyone with the same problem?

2) I have problems with tagging rules since JMR 2024 ! It will not correctly name downloaded streams with the rule ["when files are tagged apply the following naming rule"] found in settings -> naming rules.

For years i had this entry: {Y}-{M}-{D}_{H}-{MI}-{S}

and this makes the file.mp4 be named like this: 2026-03-22_02-03-07

but with JMR Version 2024 / 2025 / 2026 the very same rule gives me the monitor name:

sarah.mp4

and the next video will be counting upwards:

sarah (1).mp4

... sarah (227).mp4 ...

and so on, which is not helpful and i want to see the recording data+time as title. Is this possible?

Can someone test this tagging or maybe tell me if a different rule works for them as it should?

Any help appreciated, told the support about both but no help/solution given.

Attached: my settings.

I have the same problem with some recordings (only audio in the recording line), but what is strange is that if I delete the license and only apply the trial, it records normally, unfortunately only for one minute :-(

Contacted support and this is what they said.

"The Dev is already aware about this issue, and he said he will work on the improvement and possibly include it in the next release.  Let me know if you have any questions. " 

Only question now is when said update would drop.

@RA

I think your first problem ties in a lot with what going on with Jaksta atm as I also go through it. My fix is either to just spam the download button after the current one switches from "extracting" to "complete (error)" until one goes to "connecting" instead. I find adding a stream to a dedicated monitor has a higher and quicker chance of actually making a successful connection. and when it doesn't I just turn the monitor off and on until it starts one, which more often than not starts either immidiately or after 2-3 tries.

My settings seem to be the same as your naming rule though i do add the {title} before the date, no clue if that would help as not once have I ever had a problem with the naming rules in all the years I've used JMR. Also worth checking the naming rule tab in the advance options and make they're all turned on?

I got the similar reply from support. Indeed how long until the update. In all my years any difficulty had been corrected in a couple of days or so? I suppose there have been exceptions. It's been well over a week. Otherwise most of the common recordings are working fine. The scramble of CB definitely happens here and there. 

this is happening to me also, specifically with CB, not with all files but ive noticed recently that alot of recordings are showing as 0 bytes and errors when they seem to be recording without issue to being with. i have purchased quite a few jaksta licenses and tried with older and the latest versions but all are having this issue. very frustrating and i hope this gets fixed ASAP