<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Camerolla Community - Portal]]></title>
		<link>https://support.camerolla.com/</link>
		<description><![CDATA[Camerolla Community - https://support.camerolla.com]]></description>
		<pubDate>Thu, 16 Apr 2026 19:20:12 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Cum sa fortezi reinstalare OBS]]></title>
			<link>https://support.camerolla.com/Thread-Cum-sa-fortezi-reinstalare-OBS</link>
			<pubDate>Tue, 31 Mar 2026 13:27:32 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Cum-sa-fortezi-reinstalare-OBS</guid>
			<description><![CDATA[In momentul cand re-instalezi camerolla, ai optiunea (pe a 2a aplicatie care se instaleaza) sa bifezi fortarea reinstalarii OBS-ului:<br />
<br />
<img src="https://support.camerolla.com/uploads/force-obs-reinstall.jpg" loading="lazy"  alt="[Image: force-obs-reinstall.jpg]" class="mycode_img" />]]></description>
			<content:encoded><![CDATA[In momentul cand re-instalezi camerolla, ai optiunea (pe a 2a aplicatie care se instaleaza) sa bifezi fortarea reinstalarii OBS-ului:<br />
<br />
<img src="https://support.camerolla.com/uploads/force-obs-reinstall.jpg" loading="lazy"  alt="[Image: force-obs-reinstall.jpg]" class="mycode_img" />]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Extensia Lovense pierde logarea?]]></title>
			<link>https://support.camerolla.com/Thread-Extensia-Lovense-pierde-logarea</link>
			<pubDate>Tue, 31 Mar 2026 07:05:09 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Extensia-Lovense-pierde-logarea</guid>
			<description><![CDATA[Salutare,<br />
<br />
Daca se intampla, cu noua extensie Lovense, sa se piarda sesiunea de logare, extensia are nevoie de un hard-refresh in interiorul browserului Camerolla. Iata pasii ce trebuie sa ii faci:<br />
<br />
<img src="https://support.camerolla.com/uploads/manage-extensions.jpg" loading="lazy"  alt="[Image: manage-extensions.jpg]" class="mycode_img" /><br />
<br />
<img src="https://support.camerolla.com/uploads/refresh-extension.jpg" loading="lazy"  alt="[Image: refresh-extension.jpg]" class="mycode_img" />]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Daca se intampla, cu noua extensie Lovense, sa se piarda sesiunea de logare, extensia are nevoie de un hard-refresh in interiorul browserului Camerolla. Iata pasii ce trebuie sa ii faci:<br />
<br />
<img src="https://support.camerolla.com/uploads/manage-extensions.jpg" loading="lazy"  alt="[Image: manage-extensions.jpg]" class="mycode_img" /><br />
<br />
<img src="https://support.camerolla.com/uploads/refresh-extension.jpg" loading="lazy"  alt="[Image: refresh-extension.jpg]" class="mycode_img" />]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Cum sa reinstalezi Camerolla in situatii de downgrade]]></title>
			<link>https://support.camerolla.com/Thread-Cum-sa-reinstalezi-Camerolla-in-situatii-de-downgrade</link>
			<pubDate>Fri, 27 Mar 2026 18:56:45 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Cum-sa-reinstalezi-Camerolla-in-situatii-de-downgrade</guid>
			<description><![CDATA[Salutare,<br />
<br />
Se poate uneori sa lansez cate un update la Camerolla care inca are erori. Eu fac teste multe, dar nu pot nicicand sa descopar orice posibila problema intrucat nu sunt model ca sa stau si online.<br />
Astfel, pot fi situatii cand anulez un update iar voi veti fi nevoiti (din pacate), sa dezinstalati camerolla si apoi sa reinstalati versiunea mai veche care era ultima data functionala.<br />
<br />
Iata pasii necesari:<br />
<ol type="1" class="mycode_list"><li>dezinstalati Camerolla<br />
</li>
<li>eventual dezinstalati si Camerolla Browser Requirements <br />
<img src="https://support.camerolla.com/uploads/add-remove-programs.jpg" loading="lazy"  alt="[Image: add-remove-programs.jpg]" class="mycode_img" /><br />
</li>
<li>ideal ar fi sa dati si un restart la calculator, sa se curete windows-ul de ce ramane prin registry<br />
</li>
<li>instalati Camerolla din nou (daca nu mai aveti installerul, mergeti pe <a href="https://camerolla.com/latest" target="_blank" rel="noopener" class="mycode_url">https://camerolla.com/latest</a>), urmand toti pasii instalarii<br />
</li>
</ol>
<br />
<br />
<br />
In situatia in care, dupa reinstalare, remarcati ca browserul Camerolla nu porneste, cel mai probabil este deoarece noul profil de chrome existent pe PC-ul tau a fost upgradat la o versiune noua si nu mai este compatibil cu versiunea "mai veche". Din pacate, acest profil va trebui sters, astfel incat Camerolla sa genereze unul nou.<br />
Pasii pt a sterge profilul de Camerolla sunt urmatorii:<br />
<ol type="1" class="mycode_list"><li>deschide Windows Explorer (sau My Computer)<br />
</li>
<li>in bara de sus, scrie <span style="font-weight: bold;" class="mycode_b">%localappdata%</span> si apoi da-i enter<br />
<img src="https://support.camerolla.com/uploads/localappdata.jpg" loading="lazy"  alt="[Image: localappdata.jpg]" class="mycode_img" /><br />
</li>
<li>apoi navigheaza in folderul <span style="font-weight: bold;" class="mycode_b">CygnusTechnologies </span>si de acolo, sterge tot ce gasesti (ar trebui sa ai 2 foldere, Camerolla-Browser si CrashReports)<br />
</li>
<li>apoi reporneste Camerolla, care va genera un profil nou, pe care va trebui sa il configurezi din nou (anume, sa pui adresa URL a panoului si dupa restart, sa configurezi din nou setarile OBS pt site-urile pe care lucrezi)<br />
</li>
</ol>
<br />
<br />
<br />
<br />
Imi pare rau pt astfel de situatii, ma straduiesc sa livrez update-uri perfecte dar, din pacate, sunt si chestii imprevizibile care doar in testare reala pot aparea.]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Se poate uneori sa lansez cate un update la Camerolla care inca are erori. Eu fac teste multe, dar nu pot nicicand sa descopar orice posibila problema intrucat nu sunt model ca sa stau si online.<br />
Astfel, pot fi situatii cand anulez un update iar voi veti fi nevoiti (din pacate), sa dezinstalati camerolla si apoi sa reinstalati versiunea mai veche care era ultima data functionala.<br />
<br />
Iata pasii necesari:<br />
<ol type="1" class="mycode_list"><li>dezinstalati Camerolla<br />
</li>
<li>eventual dezinstalati si Camerolla Browser Requirements <br />
<img src="https://support.camerolla.com/uploads/add-remove-programs.jpg" loading="lazy"  alt="[Image: add-remove-programs.jpg]" class="mycode_img" /><br />
</li>
<li>ideal ar fi sa dati si un restart la calculator, sa se curete windows-ul de ce ramane prin registry<br />
</li>
<li>instalati Camerolla din nou (daca nu mai aveti installerul, mergeti pe <a href="https://camerolla.com/latest" target="_blank" rel="noopener" class="mycode_url">https://camerolla.com/latest</a>), urmand toti pasii instalarii<br />
</li>
</ol>
<br />
<br />
<br />
In situatia in care, dupa reinstalare, remarcati ca browserul Camerolla nu porneste, cel mai probabil este deoarece noul profil de chrome existent pe PC-ul tau a fost upgradat la o versiune noua si nu mai este compatibil cu versiunea "mai veche". Din pacate, acest profil va trebui sters, astfel incat Camerolla sa genereze unul nou.<br />
Pasii pt a sterge profilul de Camerolla sunt urmatorii:<br />
<ol type="1" class="mycode_list"><li>deschide Windows Explorer (sau My Computer)<br />
</li>
<li>in bara de sus, scrie <span style="font-weight: bold;" class="mycode_b">%localappdata%</span> si apoi da-i enter<br />
<img src="https://support.camerolla.com/uploads/localappdata.jpg" loading="lazy"  alt="[Image: localappdata.jpg]" class="mycode_img" /><br />
</li>
<li>apoi navigheaza in folderul <span style="font-weight: bold;" class="mycode_b">CygnusTechnologies </span>si de acolo, sterge tot ce gasesti (ar trebui sa ai 2 foldere, Camerolla-Browser si CrashReports)<br />
</li>
<li>apoi reporneste Camerolla, care va genera un profil nou, pe care va trebui sa il configurezi din nou (anume, sa pui adresa URL a panoului si dupa restart, sa configurezi din nou setarile OBS pt site-urile pe care lucrezi)<br />
</li>
</ol>
<br />
<br />
<br />
<br />
Imi pare rau pt astfel de situatii, ma straduiesc sa livrez update-uri perfecte dar, din pacate, sunt si chestii imprevizibile care doar in testare reala pot aparea.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Lovense extension issues]]></title>
			<link>https://support.camerolla.com/Thread-Lovense-extension-issues</link>
			<pubDate>Tue, 01 Oct 2024 08:57:22 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Lovense-extension-issues</guid>
			<description><![CDATA[Hello guys,<br />
<br />
In the last 2 weeks of september 2024 (and probably upcoming weeks too) there have been issues reported with Camerolla and Lovense extension in combination with Chaturbate site.<br />
Here are the requirements to see this issue happening:<ul class="mycode_list"><li>have camerolla installed<br />
</li>
<li>have OBS and the Lovense OBS Toolset installed<br />
</li>
<li>have the Lovense extension configured for Chaturbate inside camerolla (though this also happens in Google Chrome or other browsers sometimes)<br />
</li>
</ul>
<br />
When a model is streaming on Chaturbate, when a client wants to take that model into a private show, the private shows is somehow automatically denied by "something". The model most of the times doesn't have time to press the accept private button and even if accepts the private, it is somehow denied 1-2 seconds after that (most of the times, instantly).<br />
<br />
I've made tests on my own and it appears that IF the original multi-rtmp of Lovense OBS toolset is installed, the privates ARE NOT denied. But if Camerolla's multi-rtmp is present instead, the privates are denied.<br />
Why? I don't know. As a conspirationist, I tend to think that Lovense might be secretly streaming the private shows via their multi-rtmp plugin to their own servers, maybe they already have a huge collection of recorded private shows, i don't know... but this is only some theory of "why" they would deny the private show when their multi-rtmp plugin is missing. I don't have time to reverse-engineer their code to figure out if this is really happening, but i see no other reason why they could deny the private shows.<br />
<br />
So, here is what I have tested:<ul class="mycode_list"><li>if the lovense extension is installed in Camerolla but disabled for chaturbate (though keep it for all other sites), the private shows are working correctly on Chaturbate<br />
</li>
<li>i have tested by forcing their older extension which doesn't have this issue BUT models get "anxious" when they see their "upgrade notice" popup that shows the extension should upgrade<br />
</li>
<li>i have also tested with their lovense extension (latest version) but without Lovense OBS Toolset installed and in 90% of the cases, this also works ok<br />
</li>
</ul>
Now, I am faced with the situation that:<ul class="mycode_list"><li>models NEED the extension because of the effects and toy-reactions (dooh, obviously)<br />
</li>
<li>models also love thier OBS Toolset because of the visual effects (dooh, nice work they did)<br />
<br />
</li>
</ul>
Several clients tried to reach Lovense on various channels (including myself), either by email or by Discord. We did NOT received any response from them OR we were banned from their Discort channels.<br />
<br />
Now ... my hands are tied. They were forced to change the system their extension works due to Chrome manifest restrictions, thus the extension works differently now.<br />
But as of Camerolla, I don't know what to do to make everyone happy, so in the latest release, here is what I did:<ul class="mycode_list"><li>as of OBS, our multi-rtmp has been re-made so now it is named Camerolla MultiRTMP so it will not conflict with Lovense's MultiRTMP.<br />
</li>
<li>Camerolla itself (the browser) is shipped with their LATEST extension. However, if anyone of you wants to use the OLD extension, you can use --olderlovense parameter when starting Camerolla and this will be automatically handled by the browser.<br />
</li>
<li>t is up to you to decide if you want to use the OBS toolset or the extension on chaturbate, depending on how much you need the private shows on Chaturbate<br />
</li>
</ul>
Thanks for your time.]]></description>
			<content:encoded><![CDATA[Hello guys,<br />
<br />
In the last 2 weeks of september 2024 (and probably upcoming weeks too) there have been issues reported with Camerolla and Lovense extension in combination with Chaturbate site.<br />
Here are the requirements to see this issue happening:<ul class="mycode_list"><li>have camerolla installed<br />
</li>
<li>have OBS and the Lovense OBS Toolset installed<br />
</li>
<li>have the Lovense extension configured for Chaturbate inside camerolla (though this also happens in Google Chrome or other browsers sometimes)<br />
</li>
</ul>
<br />
When a model is streaming on Chaturbate, when a client wants to take that model into a private show, the private shows is somehow automatically denied by "something". The model most of the times doesn't have time to press the accept private button and even if accepts the private, it is somehow denied 1-2 seconds after that (most of the times, instantly).<br />
<br />
I've made tests on my own and it appears that IF the original multi-rtmp of Lovense OBS toolset is installed, the privates ARE NOT denied. But if Camerolla's multi-rtmp is present instead, the privates are denied.<br />
Why? I don't know. As a conspirationist, I tend to think that Lovense might be secretly streaming the private shows via their multi-rtmp plugin to their own servers, maybe they already have a huge collection of recorded private shows, i don't know... but this is only some theory of "why" they would deny the private show when their multi-rtmp plugin is missing. I don't have time to reverse-engineer their code to figure out if this is really happening, but i see no other reason why they could deny the private shows.<br />
<br />
So, here is what I have tested:<ul class="mycode_list"><li>if the lovense extension is installed in Camerolla but disabled for chaturbate (though keep it for all other sites), the private shows are working correctly on Chaturbate<br />
</li>
<li>i have tested by forcing their older extension which doesn't have this issue BUT models get "anxious" when they see their "upgrade notice" popup that shows the extension should upgrade<br />
</li>
<li>i have also tested with their lovense extension (latest version) but without Lovense OBS Toolset installed and in 90% of the cases, this also works ok<br />
</li>
</ul>
Now, I am faced with the situation that:<ul class="mycode_list"><li>models NEED the extension because of the effects and toy-reactions (dooh, obviously)<br />
</li>
<li>models also love thier OBS Toolset because of the visual effects (dooh, nice work they did)<br />
<br />
</li>
</ul>
Several clients tried to reach Lovense on various channels (including myself), either by email or by Discord. We did NOT received any response from them OR we were banned from their Discort channels.<br />
<br />
Now ... my hands are tied. They were forced to change the system their extension works due to Chrome manifest restrictions, thus the extension works differently now.<br />
But as of Camerolla, I don't know what to do to make everyone happy, so in the latest release, here is what I did:<ul class="mycode_list"><li>as of OBS, our multi-rtmp has been re-made so now it is named Camerolla MultiRTMP so it will not conflict with Lovense's MultiRTMP.<br />
</li>
<li>Camerolla itself (the browser) is shipped with their LATEST extension. However, if anyone of you wants to use the OLD extension, you can use --olderlovense parameter when starting Camerolla and this will be automatically handled by the browser.<br />
</li>
<li>t is up to you to decide if you want to use the OBS toolset or the extension on chaturbate, depending on how much you need the private shows on Chaturbate<br />
</li>
</ul>
Thanks for your time.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Howto manually add Lovense extension to Camerolla]]></title>
			<link>https://support.camerolla.com/Thread-Howto-manually-add-Lovense-extension-to-Camerolla</link>
			<pubDate>Wed, 24 Apr 2024 14:56:25 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Howto-manually-add-Lovense-extension-to-Camerolla</guid>
			<description><![CDATA[Hello guys,<br />
<br />
Its been years with the previous versions of the Lovense extension which worked like a charm, but recently the guys at Lovense have made some changes to the extension so that <span style="font-weight: bold;" class="mycode_b">I AM NOT ABLE to provide it pre-installed anymore</span> and also <span style="font-weight: bold;" class="mycode_b">the automatic login inside the extension will not work anymore</span>.<br />
<br />
But what is important is that I thrive to give you solutions to use it. So here is a guide about how to do this (though they also have a guide on their website aswell, most probably better than this that I created).<br />
 <br />
<ol type="1" class="mycode_list"><li>First, please download the extension (that I also modified a little, in case they will respond to my request to make some changes to re-enable automatic login inside it). Here is the link for download: <a href="https://downloads.camerolla.com/Lovense-Extension_v31.3.6.zip" target="_blank" rel="noopener" class="mycode_url">https://downloads.camerolla.com/Lovense-...31.3.6.zip</a><br />
</li>
<li>After you have downloaded the ZIP file, extract its contents somewhere on your PC, in a location that will not be deleted by accident by models or whatever<br />
</li>
<li>After this, please follow the steps which are better described by the images bellow, since its easier to explain the process like this:<br />
</li>
</ol>
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step1-goto-extensions-to-enable-developer-mode.png" loading="lazy"  alt="[Image: step1-goto-extensions-to-enable-developer-mode.png]" class="mycode_img" /></div>
<br />
P.S. The address in that bar is chrome://extensions - that is where you manage your installed extensions from camerolla.<br />
P.S.2. If you already have the previous Lovense extension installed there, please remove it first, as you will later add the newest one.<br />
<br />
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step2-click-load-unpacked.png" loading="lazy"  alt="[Image: step2-click-load-unpacked.png]" class="mycode_img" /></div>
<br />
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step3-pin-the-extension.png" loading="lazy"  alt="[Image: step3-pin-the-extension.png]" class="mycode_img" /></div>
<br />
<br />
Thanks alot for your input and support.<br />
In case in future the guys at Lovense will make changes so that their extension could also be used as a CRX file, I will make updates to bring back the previous way of doing things, but to be honest, I never had a good communication with them and they are unlikely to respond to my requests.]]></description>
			<content:encoded><![CDATA[Hello guys,<br />
<br />
Its been years with the previous versions of the Lovense extension which worked like a charm, but recently the guys at Lovense have made some changes to the extension so that <span style="font-weight: bold;" class="mycode_b">I AM NOT ABLE to provide it pre-installed anymore</span> and also <span style="font-weight: bold;" class="mycode_b">the automatic login inside the extension will not work anymore</span>.<br />
<br />
But what is important is that I thrive to give you solutions to use it. So here is a guide about how to do this (though they also have a guide on their website aswell, most probably better than this that I created).<br />
 <br />
<ol type="1" class="mycode_list"><li>First, please download the extension (that I also modified a little, in case they will respond to my request to make some changes to re-enable automatic login inside it). Here is the link for download: <a href="https://downloads.camerolla.com/Lovense-Extension_v31.3.6.zip" target="_blank" rel="noopener" class="mycode_url">https://downloads.camerolla.com/Lovense-...31.3.6.zip</a><br />
</li>
<li>After you have downloaded the ZIP file, extract its contents somewhere on your PC, in a location that will not be deleted by accident by models or whatever<br />
</li>
<li>After this, please follow the steps which are better described by the images bellow, since its easier to explain the process like this:<br />
</li>
</ol>
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step1-goto-extensions-to-enable-developer-mode.png" loading="lazy"  alt="[Image: step1-goto-extensions-to-enable-developer-mode.png]" class="mycode_img" /></div>
<br />
P.S. The address in that bar is chrome://extensions - that is where you manage your installed extensions from camerolla.<br />
P.S.2. If you already have the previous Lovense extension installed there, please remove it first, as you will later add the newest one.<br />
<br />
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step2-click-load-unpacked.png" loading="lazy"  alt="[Image: step2-click-load-unpacked.png]" class="mycode_img" /></div>
<br />
<br />
<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/step3-pin-the-extension.png" loading="lazy"  alt="[Image: step3-pin-the-extension.png]" class="mycode_img" /></div>
<br />
<br />
Thanks alot for your input and support.<br />
In case in future the guys at Lovense will make changes so that their extension could also be used as a CRX file, I will make updates to bring back the previous way of doing things, but to be honest, I never had a good communication with them and they are unlikely to respond to my requests.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Why earnings are not always being detected correctly]]></title>
			<link>https://support.camerolla.com/Thread-Why-earnings-are-not-always-being-detected-correctly</link>
			<pubDate>Tue, 02 Apr 2024 17:22:54 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Why-earnings-are-not-always-being-detected-correctly</guid>
			<description><![CDATA[Hello,<br />
<br />
Camerolla's earning detection works best if the following conditions are met:<br />
<ol type="1" class="mycode_list"><li>the model uses the app and keeps the websites opened (because the earnings detection is happening only when a website is opened, otherwise there is no detection happening)<br />
</li>
<li>the Windows on the computers is installed in English. Country can be set to user's location, but the Windows must be in English. Some websites show-up data in the user interface according to user's timezone and currency settings (for example, 1,354 could mean 1 point 354 or could mean 1 thousands 354, depending on PC settings).<br />
</li>
<li>the browser's settings should also be default<br />
</li>
<li>each website should better BE in English language. If the model changes its interface in some other language, detection will most probably fail. For example xlovecam, if you use ES as language, all earnings will have a different interpretation in the UI. Take a look at my 2 attachments so you can see yourself how things look like in different languages.<br />
</li>
</ol>
<br />
For example:<ul class="mycode_list"><li>in Spanish, a date is *15/03/24* , earned value is *0,47 €* (using COMMA as decimals separator)<br />
</li>
<li>in English, the date is *3/15/24* or "15/03/2024" and the earned value is *€0.47* (using DOT as decimals separator)<br />
</li>
</ul>
<br />
Camerolla DOES NOT interpret user's interface language. We cannot make it "work" for all websites in their all possible languages and "specifics".<br />
<br />
Now, about the detected earnings (as they are), there are 2 things:<ul class="mycode_list"><li>the day's earnings --- which means that 1st march is 1st march of stripchat, of streamate, of chaturbate... according to their timezones AND NEVER 1st march of the model's country.<br />
</li>
<li>the shift's earnings, which is a SUM of detected earnings in the shift's timeframe: START and END date. What does it mean is that the shift started at 07:12:22 and ended at 19:22:22 ... whatever earnings have been discovered in this timeframe are SUMMED and BELONG to that shift. But a trainer can manually change the earnings after the model left the studio (or loggedoff) and those correction will never fix the shift's SUM of values.<br />
</li>
</ul>
<br />
In theory, the data that exists in the first table (the one with the period's days) should match the total earnings as per each website. If doesn't:<ul class="mycode_list"><li>either the app wasn't used continuously and some earnings are missing<br />
</li>
<li>either the model received offline earnings after her last login<br />
</li>
<li>either the PC's settings (language/etc) are not standard / default and thus the detection is faulty.<br />
</li>
<li>either the model has changed website's language from English to some other language<br />
</li>
</ul>
<br />
Hope this topic will make some things clear for your business.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=5" target="_blank" title="">xlove-english.png</a> (Size: 45.31 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=4" target="_blank" title="">xlovecam-spanish.png</a> (Size: 47.84 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
Camerolla's earning detection works best if the following conditions are met:<br />
<ol type="1" class="mycode_list"><li>the model uses the app and keeps the websites opened (because the earnings detection is happening only when a website is opened, otherwise there is no detection happening)<br />
</li>
<li>the Windows on the computers is installed in English. Country can be set to user's location, but the Windows must be in English. Some websites show-up data in the user interface according to user's timezone and currency settings (for example, 1,354 could mean 1 point 354 or could mean 1 thousands 354, depending on PC settings).<br />
</li>
<li>the browser's settings should also be default<br />
</li>
<li>each website should better BE in English language. If the model changes its interface in some other language, detection will most probably fail. For example xlovecam, if you use ES as language, all earnings will have a different interpretation in the UI. Take a look at my 2 attachments so you can see yourself how things look like in different languages.<br />
</li>
</ol>
<br />
For example:<ul class="mycode_list"><li>in Spanish, a date is *15/03/24* , earned value is *0,47 €* (using COMMA as decimals separator)<br />
</li>
<li>in English, the date is *3/15/24* or "15/03/2024" and the earned value is *€0.47* (using DOT as decimals separator)<br />
</li>
</ul>
<br />
Camerolla DOES NOT interpret user's interface language. We cannot make it "work" for all websites in their all possible languages and "specifics".<br />
<br />
Now, about the detected earnings (as they are), there are 2 things:<ul class="mycode_list"><li>the day's earnings --- which means that 1st march is 1st march of stripchat, of streamate, of chaturbate... according to their timezones AND NEVER 1st march of the model's country.<br />
</li>
<li>the shift's earnings, which is a SUM of detected earnings in the shift's timeframe: START and END date. What does it mean is that the shift started at 07:12:22 and ended at 19:22:22 ... whatever earnings have been discovered in this timeframe are SUMMED and BELONG to that shift. But a trainer can manually change the earnings after the model left the studio (or loggedoff) and those correction will never fix the shift's SUM of values.<br />
</li>
</ul>
<br />
In theory, the data that exists in the first table (the one with the period's days) should match the total earnings as per each website. If doesn't:<ul class="mycode_list"><li>either the app wasn't used continuously and some earnings are missing<br />
</li>
<li>either the model received offline earnings after her last login<br />
</li>
<li>either the PC's settings (language/etc) are not standard / default and thus the detection is faulty.<br />
</li>
<li>either the model has changed website's language from English to some other language<br />
</li>
</ul>
<br />
Hope this topic will make some things clear for your business.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=5" target="_blank" title="">xlove-english.png</a> (Size: 45.31 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=4" target="_blank" title="">xlovecam-spanish.png</a> (Size: 47.84 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Online/Offline detection is NOT working correctly on some computers]]></title>
			<link>https://support.camerolla.com/Thread-Online-Offline-detection-is-NOT-working-correctly-on-some-computers</link>
			<pubDate>Mon, 26 Feb 2024 13:30:32 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Online-Offline-detection-is-NOT-working-correctly-on-some-computers</guid>
			<description><![CDATA[Hello,<br />
This is a topic that has raised many discussions over the years.<br />
Detecting if a model is ONLINE can be done in only a few ways:<ul class="mycode_list"><li>detection of keyboard and/or mouse activity --- which is not good because models are most of the time dancing/speaking, so this method fails<br />
</li>
<li>detection if various TABs in the browser are activated or not and if there's activity on them - fails because some sites have dedicated apps (such as Jasmin or F4F or others) and more-over, even if a site is open on some page, it doesn't necessary mean that the model is actually online on that site. And implementing a per-site "detection" is impossible<br />
</li>
<li>speaking with various site's Affiliate programs - which SHOULD report-back if a model is online or not. This method also fails because the data is mostly "not live" (but cached, 1 minute on average), not all the sites have such an affiliate program implemented and even if all would do, they are all different and constantly changing due to changes in the industry, and it would fail in a day-by-day usage scenario<br />
</li>
<li>monitoring the UPLOAD speed on model's computer. If does some upload, means that the model is streaming (dooh) and this is the solution we've chosen, despite it still raises some issues.<br />
</li>
</ul>
<br />
So, Camerolla uses the last method: measuring internet UPLOAD speed PER SECOND. Considering that most sites are doing HD resolutions, an upload speed of AT LEAST 15kb/sec means that the model is online, while less than that, she is offline.<br />
You may wonder WHY i chosen the 15kb/second ... well that is because there are some websites which use RTC and high-compression algorithms where the upload is (believe me or not) as low as that.<br />
<br />
Measuring the upload speed on a PC is a perfect solution BUT it still has some "hacks" (or issues).<br />
For example, a model can keep streaming using OBS to some website BUT in real she is offline and smoking or whatever...<br />
Unfortunately, the app itself cannot verify if the model is "for real" really streaming... if she discovered this "small issue" into tricking the system, i guess its good that you still have trainers/admins in your studios who monitor them --- and for such a case, there's a FORCE BREAK button inside camerolla, which will set a break for the model, despite if she actually is still streaming in OBS.]]></description>
			<content:encoded><![CDATA[Hello,<br />
This is a topic that has raised many discussions over the years.<br />
Detecting if a model is ONLINE can be done in only a few ways:<ul class="mycode_list"><li>detection of keyboard and/or mouse activity --- which is not good because models are most of the time dancing/speaking, so this method fails<br />
</li>
<li>detection if various TABs in the browser are activated or not and if there's activity on them - fails because some sites have dedicated apps (such as Jasmin or F4F or others) and more-over, even if a site is open on some page, it doesn't necessary mean that the model is actually online on that site. And implementing a per-site "detection" is impossible<br />
</li>
<li>speaking with various site's Affiliate programs - which SHOULD report-back if a model is online or not. This method also fails because the data is mostly "not live" (but cached, 1 minute on average), not all the sites have such an affiliate program implemented and even if all would do, they are all different and constantly changing due to changes in the industry, and it would fail in a day-by-day usage scenario<br />
</li>
<li>monitoring the UPLOAD speed on model's computer. If does some upload, means that the model is streaming (dooh) and this is the solution we've chosen, despite it still raises some issues.<br />
</li>
</ul>
<br />
So, Camerolla uses the last method: measuring internet UPLOAD speed PER SECOND. Considering that most sites are doing HD resolutions, an upload speed of AT LEAST 15kb/sec means that the model is online, while less than that, she is offline.<br />
You may wonder WHY i chosen the 15kb/second ... well that is because there are some websites which use RTC and high-compression algorithms where the upload is (believe me or not) as low as that.<br />
<br />
Measuring the upload speed on a PC is a perfect solution BUT it still has some "hacks" (or issues).<br />
For example, a model can keep streaming using OBS to some website BUT in real she is offline and smoking or whatever...<br />
Unfortunately, the app itself cannot verify if the model is "for real" really streaming... if she discovered this "small issue" into tricking the system, i guess its good that you still have trainers/admins in your studios who monitor them --- and for such a case, there's a FORCE BREAK button inside camerolla, which will set a break for the model, despite if she actually is still streaming in OBS.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to re-overwrite OBS MultiRtmp with ours]]></title>
			<link>https://support.camerolla.com/Thread-How-to-re-overwrite-OBS-MultiRtmp-with-ours</link>
			<pubDate>Thu, 08 Feb 2024 13:50:24 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-How-to-re-overwrite-OBS-MultiRtmp-with-ours</guid>
			<description><![CDATA[When it happens that Lovense's OBS Toolset is updatnig, it always messes up with all files and ruins your standard multi-rtmp usage.<br />
<br />
To fix this, here's what you need to do:<br />
<ol type="1" class="mycode_list"><li>Download our version of the plugin from <span style="font-weight: bold;" class="mycode_b"><a href="https://ro.downloads.camerolla.com/obs-multi-rtmp-qt6.dll" target="_blank" rel="noopener" class="mycode_url">https://ro.downloads.camerolla.com/obs-m...mp-qt6.dll</a></span><br />
</li>
<li>Close your OBS entirelly<br />
</li>
<li>open FileExplorer on your windows (WIN key + E) and manually navigate to this path: <span style="font-weight: bold;" class="mycode_b">C:\ProgramData\obs-studio\plugins\obs-multi-rtmp-qt6\bin\64bit</span><br />
</li>
<li>delete the obs-multi-rtmp-qt6.dll that exists in that directopry (which is the one from Lovense)<br />
</li>
<li>copy the file you donwloaded at step 1 in this path.<br />
</li>
</ol>
Now you can start using OBS as before Lovense's automatic update again<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1" target="_blank" title="">capture.jpg</a> (Size: 24.25 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[When it happens that Lovense's OBS Toolset is updatnig, it always messes up with all files and ruins your standard multi-rtmp usage.<br />
<br />
To fix this, here's what you need to do:<br />
<ol type="1" class="mycode_list"><li>Download our version of the plugin from <span style="font-weight: bold;" class="mycode_b"><a href="https://ro.downloads.camerolla.com/obs-multi-rtmp-qt6.dll" target="_blank" rel="noopener" class="mycode_url">https://ro.downloads.camerolla.com/obs-m...mp-qt6.dll</a></span><br />
</li>
<li>Close your OBS entirelly<br />
</li>
<li>open FileExplorer on your windows (WIN key + E) and manually navigate to this path: <span style="font-weight: bold;" class="mycode_b">C:\ProgramData\obs-studio\plugins\obs-multi-rtmp-qt6\bin\64bit</span><br />
</li>
<li>delete the obs-multi-rtmp-qt6.dll that exists in that directopry (which is the one from Lovense)<br />
</li>
<li>copy the file you donwloaded at step 1 in this path.<br />
</li>
</ol>
Now you can start using OBS as before Lovense's automatic update again<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://support.camerolla.com/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1" target="_blank" title="">capture.jpg</a> (Size: 24.25 KB / Downloads: 0)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Aw, Snap!]]></title>
			<link>https://support.camerolla.com/Thread-Aw-Snap</link>
			<pubDate>Mon, 23 Oct 2023 13:14:40 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Aw-Snap</guid>
			<description><![CDATA[Daca se intampla la vruen moment dat sa intampinati vreo eroare de tipul <span style="font-weight: bold;" class="mycode_b">Aw, Snap!</span>, conform developerilor de la Google - treaba asta se intampla doar atunci cand exista o eroare in profilul de chrome al browserului Camerolla (cauzata, de fapt, de "sandbox violation" - anume acea chestie cum ca orice tab imparte-si-nu memorie si alte exe-uri simultan).<br />
Pentru a repara problema, tot cei de la Google au recomandat ca solutia este sa se stearga profilul de Chrome si astfel, la un nou start al aplicatiei, sa fie unul fresh.<br />
<br />
Pentru a sterge profilul de Camerolla (chrome) faceti urmatoarele:<br />
1. Deschideti Windows explorer (sau my computer)<br />
2. In bara de navigare, dati copy/paste la textul acesta: %appdata%\..\Local\CygnusTechnologies\<br />
3. Stergeti tot ce exista in acel folder<br />
4. Re-porniti Camerolla si reconfigurati adresa de URL de client + setarile de OBS.]]></description>
			<content:encoded><![CDATA[Daca se intampla la vruen moment dat sa intampinati vreo eroare de tipul <span style="font-weight: bold;" class="mycode_b">Aw, Snap!</span>, conform developerilor de la Google - treaba asta se intampla doar atunci cand exista o eroare in profilul de chrome al browserului Camerolla (cauzata, de fapt, de "sandbox violation" - anume acea chestie cum ca orice tab imparte-si-nu memorie si alte exe-uri simultan).<br />
Pentru a repara problema, tot cei de la Google au recomandat ca solutia este sa se stearga profilul de Chrome si astfel, la un nou start al aplicatiei, sa fie unul fresh.<br />
<br />
Pentru a sterge profilul de Camerolla (chrome) faceti urmatoarele:<br />
1. Deschideti Windows explorer (sau my computer)<br />
2. In bara de navigare, dati copy/paste la textul acesta: %appdata%\..\Local\CygnusTechnologies\<br />
3. Stergeti tot ce exista in acel folder<br />
4. Re-porniti Camerolla si reconfigurati adresa de URL de client + setarile de OBS.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Probleme cu sunetul din youtube sau la modul general intre site-uri]]></title>
			<link>https://support.camerolla.com/Thread-Probleme-cu-sunetul-din-youtube-sau-la-modul-general-intre-site-uri</link>
			<pubDate>Fri, 28 Jul 2023 10:09:52 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Probleme-cu-sunetul-din-youtube-sau-la-modul-general-intre-site-uri</guid>
			<description><![CDATA[Buna,<br />
<br />
Una din intrebarile recente are 2 forme si aceeasi cauza:<br />
<ol type="1" class="mycode_list"><li>Sunetul modelelor (voce, gemete, etc) se aude pe site-urile din Camerolla DAR sunetul muzicii din YouTube NU se aude pe site-urile respective<br />
</li>
<li>Pe unele site-uri nu se aude sunetul modelelor de loc, de exemplu pe Streamate si ImLive, desi pe LiveJasmin se aude fara probleme<br />
</li>
</ol>
<br />
<br />
<br />
Cauza este de fapt o functionalitate super desteapta din Chrome care face un soi de noise-cancellation care ar trebui sa ajute utilizatorii din corporatii atunci cand sustin meetinguri in Zoom sau Teams sau Jitsi sau alte platforme de video-call.<br />
<br />
Solutia este sa navigati in Camerolla la adresa chrome://flags si acolo sa dati cautare dupa cuvantul AUDIO si apoi sa dati DISABLE la urmatoarele 3 optiuni, fix ca in poza aceasta:<br />
<hr class="mycode_hr" /><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/support/sound-params-for-streaming.jpg" loading="lazy"  width="800" height="600" alt="[Image: sound-params-for-streaming.jpg]" class="mycode_img" /></div><hr class="mycode_hr" />
Deci, setati pe DISABLED urmatoarele 3 optiuni:<ul class="mycode_list"><li>Allow WebRTC to adjust the input volume - asta ca sa nu se mai creeze probleme de volum intre site-uri<br />
</li>
<li>WebRTC downmix capture audio method<br />
</li>
<li>Chrome-wide echo cancellation - asta e de fapt optiunea care face ca sunetul sa nu mai fie disponibil intre site-uri<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[Buna,<br />
<br />
Una din intrebarile recente are 2 forme si aceeasi cauza:<br />
<ol type="1" class="mycode_list"><li>Sunetul modelelor (voce, gemete, etc) se aude pe site-urile din Camerolla DAR sunetul muzicii din YouTube NU se aude pe site-urile respective<br />
</li>
<li>Pe unele site-uri nu se aude sunetul modelelor de loc, de exemplu pe Streamate si ImLive, desi pe LiveJasmin se aude fara probleme<br />
</li>
</ol>
<br />
<br />
<br />
Cauza este de fapt o functionalitate super desteapta din Chrome care face un soi de noise-cancellation care ar trebui sa ajute utilizatorii din corporatii atunci cand sustin meetinguri in Zoom sau Teams sau Jitsi sau alte platforme de video-call.<br />
<br />
Solutia este sa navigati in Camerolla la adresa chrome://flags si acolo sa dati cautare dupa cuvantul AUDIO si apoi sa dati DISABLE la urmatoarele 3 optiuni, fix ca in poza aceasta:<br />
<hr class="mycode_hr" /><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/support/sound-params-for-streaming.jpg" loading="lazy"  width="800" height="600" alt="[Image: sound-params-for-streaming.jpg]" class="mycode_img" /></div><hr class="mycode_hr" />
Deci, setati pe DISABLED urmatoarele 3 optiuni:<ul class="mycode_list"><li>Allow WebRTC to adjust the input volume - asta ca sa nu se mai creeze probleme de volum intre site-uri<br />
</li>
<li>WebRTC downmix capture audio method<br />
</li>
<li>Chrome-wide echo cancellation - asta e de fapt optiunea care face ca sunetul sa nu mai fie disponibil intre site-uri<br />
</li>
</ul>
]]></content:encoded>
		</item>
	</channel>
</rss>