This is a bug that has been around for a long time. I previously reported this problem a few years ago but it has not been fixed. When downloading media on a Mac from Chaturbate a file is created in the Jaksta folder called "Chaturbate - Free Adult Webcams, Live Sex, Free Sex Chat, Exhibitionist & Pornstar Free Cams.ts". If another streams is started another file is created named "Chaturbate - Free Adult Webcams, Live Sex, Free Sex Chat, Exhibitionist & Pornstar Free Cams (1).ts". When a third stream is added a file named "Chaturbate - Free Adult Webcams, Live Sex, Free Sex Chat, Exhibitionist & Pornstar Free Cams (2).ts". When these streams are ended and converted by Jaksta the files are removed from the Jaksta folder and placed in the "Converted" subfolder with the ".mov" extension replacing the ".ts". The original file names are preserved.
When a new downloading session is starting Jaksta places the new downloading streams in the Jaksta folder with the identical file naming as before. When these streams are ended and converting they overwrite the files from the previous conversions with the same names, effectively deleting the existing converted streams.
The downloading streams filenames also do not contain the performer's name, only the name of the the web site. The performer's name should be included in the filename or the converted files will be difficult to determine who the performer was later.
Please include the performer's name in the filename and include a date time stamp to keep the converted files from being constantly deleted and overwritten.
Apologies for the delayed response.
In simple terms, the cause of this particular issue is that Jaksta is not able to get specific metadata from the streams to use in the file naming. That would prevent the duplicates and overwriting of files from occurring.
My first suggestion would be to try using a different browser(s) and see if you get a different result. Sometimes the browser can affect the gathering of metadata, and this can alter the end file name.
Unfortunately it is no easy thing to build in custom metadata capturing (for specific sites), such as the performer's name. All we can do is tell Jaksta to capture what the stream offers within a certain capacity. I will still mention this to our developers and see if there is something they can do.
If you would like to assist us in our investigation and development, a clean log file would be helpful.
To get a clean log, you will need to do the following:
Why is there no response from Jaksta support to my bug report?