<?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 - Updates (in English)]]></title>
		<link>https://support.camerolla.com/</link>
		<description><![CDATA[Camerolla Community - https://support.camerolla.com]]></description>
		<pubDate>Wed, 08 Apr 2026 22:23:45 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[110.1.48.1 - 21st Feb 2023]]></title>
			<link>https://support.camerolla.com/Thread-110-1-48-1-21st-Feb-2023</link>
			<pubDate>Tue, 21 Feb 2023 16:14:37 +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-110-1-48-1-21st-Feb-2023</guid>
			<description><![CDATA[<span style="font-weight: bold;" class="mycode_b"><span style="font-size: medium;" class="mycode_size">Here's what changed in this update (110.1.48.1, released on 21st Feb 2023)</span></span><br />
<ol type="1" class="mycode_list"><li>Chrome has been updated from v103 to v110 now<br />
</li>
<li>VERY IMPORTANT fix regarding use of webcams in Chrome. As you might have experienced, if a webcam is already in use by some other app (eg a Splitter or OBS) but if you wanted to also use the WebEncoder in some website, on some PCs the browser would have failed at the step when you where asked to choose a camera. I've successfully changed some internal chrome-code to fix this issue (which btw exists also in Firefox, Opera, Edge, Brave, etc).<br />
</li>
<li>AutoLogin and Earnings detection for ManyVids<br />
</li>
<li>AutoLogin, Earnings and PayPerMin management for CamModelDirectory<br />
</li>
<li>Fixed autologin in YouTube accounts<br />
</li>
<li>Upgraded internal LovenseExtension from 30.5.0 to 30.5.4 (latest on their site)<br />
</li>
<li>Fixed a crash regarding some API communication with your portal (regarding Articles query)<br />
</li>
<li>Some changes on earnings detection in regards of multi-session technology. Internally it's saved now if the earnings detection came from a model who was online or from a trainer/admin who navigated her website instead from the office<br />
</li>
<li>Some changes on Chaturbate's earnings detection. Seems in some studios, earnings pages reported a "too many requests" error, thus i've increased the timeout between pages to avoid this in future<br />
</li>
<li>Many changes to the multi-session technology that exists in the product. About this, I will talk separatelly, bellow.<br />
</li>
</ol>
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: medium;" class="mycode_size">About the Multi-session technology + its session-in-the-cloud feature</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">What it is:</span> it is a functionality I've created that allows ONE user using ONE browser to be simultaneously loggedin in multiple accounts of a same website. For example, if we take Facebook as example, you can login in more than one FB account now using Camerolla. Basically you would have a TAB (or group of tabs) for one account, other TAB(s) for the 2nd account, etc.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Usability:</span> this functionality should be very handy especially for trainers/admins, because they can now keep multiple accounts opened, without the need to logout and relogin in order to check something on some other account.Furthermore, this could be very handy for Creators Agencies. Such agencies use sexters (instead of models) who literally use multiple accounts of a same website in their shift and type messages/etc.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The cloud feature.</span> The very cool feature added to it is that now an account's session gets to be saved in your cloud (your portal). How it works... well, it's crazy, but in short:<ul class="mycode_list"><li>first time user connects to a website, if will perform authentication (if no auth session exists already in cloud. Otherwise, session will be restored)<br />
</li>
<li>after successful auth, session gets stored locally in the browser. When the model closes Camerolla, then it is the time when the session gets sent to the cloud (i've also implemented some browser idle detection to send the session, but this was not heavily tested yet)<br />
</li>
<li>when the user opens Camerolla again next day, session gets "synced", and she doesn't need to login again, as data is already there, synced (except for the case when she returns after too much time and session expires meanwhile as per each site's policy)<br />
</li>
<li>etc<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Benefits of cloud feature:</span><ul class="mycode_list"><li>without need to relogin, users don't need to fillin the annoying captcha everytime (as it happens on BongaCams, Stripchat, Cam4 for some countries, OnlyFans, etc etc etc)<br />
</li>
<li>especially for OnlyFans case (as they might flag accounts for face verification when logging-in), this is crucial feature and this is the reason why OnlyFans agencies use apps such as GoLogin or Infloww or others, which are extremely expensive.<br />
</li>
<li>less time spending on opening a website, because you skip waiting till login happened<br />
</li>
<li>also a good thing for premium YouTube accounts which can be "shared" for a whole-studio. In case you'd want to have such a premium YT account for your entire studio, let me know and I will tell you what needs to be done to achive this.<br />
</li>
<li>take the scenario when the model loggedin in some site, then went home or something. Then some trainer opens her site, and gets loggedin automatically, very fast, because sessiion data existed in cloud already, etc.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Tests I've made:</span> I've tested this combined multi-session technology and also the cloud-feature of session data on all websites that we officially support, and it's working nicely now, as lots of bugs I've fixed in what I released ~3 weeks ago.However, on some websites restoring the session is not working becuase that is how the websites have been built. And here we have XLoveCam - who has browser-session cookies (which are invalid once the browser closes), AdultWork. On other websites, I've tested it for days and works very nice, such as BongaCams, CamContacts, Cam4, Cams (streamray), Chaturbate, Camsoda, CherryTV, CamModelDirectory, ePlay, Flirt4Free, ImLive, LiveJasmin, LoyalFans, ManyVids, MyFreeCams, OnlyFans, SecretFriends, Streamate, Stripcat, Swag, XLovecam, YouTube, etc.<br />
<br />
<span style="color: #8e44ad;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">ATENTION though!</span></span>The cloud feature is initially disabled for everyone, because despite I'm very smart, I don't have a studio to test this feature LIVE, in a real life scenario. I've made thousands of tests myself, alone, in my office... but what if something went bad somewhere.If ANY of you want to test this feature, please let me know and I will enable the feature for you. The only thing that could be bad is that for some model to receive cookies of some other model account... In theory this should NOT happen, but what if. So if you'll choose to test this feature, I will guide you on how to proceed in this case and I will monitor what is happening. If it will pass tests with few of you guys, they I will probably enable it to everyone so that all of you can benefit from it.]]></description>
			<content:encoded><![CDATA[<span style="font-weight: bold;" class="mycode_b"><span style="font-size: medium;" class="mycode_size">Here's what changed in this update (110.1.48.1, released on 21st Feb 2023)</span></span><br />
<ol type="1" class="mycode_list"><li>Chrome has been updated from v103 to v110 now<br />
</li>
<li>VERY IMPORTANT fix regarding use of webcams in Chrome. As you might have experienced, if a webcam is already in use by some other app (eg a Splitter or OBS) but if you wanted to also use the WebEncoder in some website, on some PCs the browser would have failed at the step when you where asked to choose a camera. I've successfully changed some internal chrome-code to fix this issue (which btw exists also in Firefox, Opera, Edge, Brave, etc).<br />
</li>
<li>AutoLogin and Earnings detection for ManyVids<br />
</li>
<li>AutoLogin, Earnings and PayPerMin management for CamModelDirectory<br />
</li>
<li>Fixed autologin in YouTube accounts<br />
</li>
<li>Upgraded internal LovenseExtension from 30.5.0 to 30.5.4 (latest on their site)<br />
</li>
<li>Fixed a crash regarding some API communication with your portal (regarding Articles query)<br />
</li>
<li>Some changes on earnings detection in regards of multi-session technology. Internally it's saved now if the earnings detection came from a model who was online or from a trainer/admin who navigated her website instead from the office<br />
</li>
<li>Some changes on Chaturbate's earnings detection. Seems in some studios, earnings pages reported a "too many requests" error, thus i've increased the timeout between pages to avoid this in future<br />
</li>
<li>Many changes to the multi-session technology that exists in the product. About this, I will talk separatelly, bellow.<br />
</li>
</ol>
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: medium;" class="mycode_size">About the Multi-session technology + its session-in-the-cloud feature</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">What it is:</span> it is a functionality I've created that allows ONE user using ONE browser to be simultaneously loggedin in multiple accounts of a same website. For example, if we take Facebook as example, you can login in more than one FB account now using Camerolla. Basically you would have a TAB (or group of tabs) for one account, other TAB(s) for the 2nd account, etc.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Usability:</span> this functionality should be very handy especially for trainers/admins, because they can now keep multiple accounts opened, without the need to logout and relogin in order to check something on some other account.Furthermore, this could be very handy for Creators Agencies. Such agencies use sexters (instead of models) who literally use multiple accounts of a same website in their shift and type messages/etc.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The cloud feature.</span> The very cool feature added to it is that now an account's session gets to be saved in your cloud (your portal). How it works... well, it's crazy, but in short:<ul class="mycode_list"><li>first time user connects to a website, if will perform authentication (if no auth session exists already in cloud. Otherwise, session will be restored)<br />
</li>
<li>after successful auth, session gets stored locally in the browser. When the model closes Camerolla, then it is the time when the session gets sent to the cloud (i've also implemented some browser idle detection to send the session, but this was not heavily tested yet)<br />
</li>
<li>when the user opens Camerolla again next day, session gets "synced", and she doesn't need to login again, as data is already there, synced (except for the case when she returns after too much time and session expires meanwhile as per each site's policy)<br />
</li>
<li>etc<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Benefits of cloud feature:</span><ul class="mycode_list"><li>without need to relogin, users don't need to fillin the annoying captcha everytime (as it happens on BongaCams, Stripchat, Cam4 for some countries, OnlyFans, etc etc etc)<br />
</li>
<li>especially for OnlyFans case (as they might flag accounts for face verification when logging-in), this is crucial feature and this is the reason why OnlyFans agencies use apps such as GoLogin or Infloww or others, which are extremely expensive.<br />
</li>
<li>less time spending on opening a website, because you skip waiting till login happened<br />
</li>
<li>also a good thing for premium YouTube accounts which can be "shared" for a whole-studio. In case you'd want to have such a premium YT account for your entire studio, let me know and I will tell you what needs to be done to achive this.<br />
</li>
<li>take the scenario when the model loggedin in some site, then went home or something. Then some trainer opens her site, and gets loggedin automatically, very fast, because sessiion data existed in cloud already, etc.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Tests I've made:</span> I've tested this combined multi-session technology and also the cloud-feature of session data on all websites that we officially support, and it's working nicely now, as lots of bugs I've fixed in what I released ~3 weeks ago.However, on some websites restoring the session is not working becuase that is how the websites have been built. And here we have XLoveCam - who has browser-session cookies (which are invalid once the browser closes), AdultWork. On other websites, I've tested it for days and works very nice, such as BongaCams, CamContacts, Cam4, Cams (streamray), Chaturbate, Camsoda, CherryTV, CamModelDirectory, ePlay, Flirt4Free, ImLive, LiveJasmin, LoyalFans, ManyVids, MyFreeCams, OnlyFans, SecretFriends, Streamate, Stripcat, Swag, XLovecam, YouTube, etc.<br />
<br />
<span style="color: #8e44ad;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">ATENTION though!</span></span>The cloud feature is initially disabled for everyone, because despite I'm very smart, I don't have a studio to test this feature LIVE, in a real life scenario. I've made thousands of tests myself, alone, in my office... but what if something went bad somewhere.If ANY of you want to test this feature, please let me know and I will enable the feature for you. The only thing that could be bad is that for some model to receive cookies of some other model account... In theory this should NOT happen, but what if. So if you'll choose to test this feature, I will guide you on how to proceed in this case and I will monitor what is happening. If it will pass tests with few of you guys, they I will probably enable it to everyone so that all of you can benefit from it.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[103.1.41.24 - 31st Jan 2023]]></title>
			<link>https://support.camerolla.com/Thread-103-1-41-24-31st-Jan-2023</link>
			<pubDate>Tue, 31 Jan 2023 17:56:12 +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-103-1-41-24-31st-Jan-2023</guid>
			<description><![CDATA[Here's what's new in (probably) the last release of this app which is still based on Chrome v103<br />
<ol type="1" class="mycode_list"><li>It seems that the flag we re-enabled at a client's request a while ago (WindowsMediaFoundation) is actually causing issues with selecting webcam when ANY webcam is already in use by other apps (or tabs). This being said, the WindowsMediaFoundation is again disabled by default in the browser, to ensure proper functionality again.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">It was really hard work, but I successfully implemented a new technology in order to support multi-sessions</span> <span style="color: #FF0000;" class="mycode_color">❤❤❤❤</span>. My previous implementation was okeish, simple (i like things simple)... and lots of you were happy about it, but it seems it had some issues and that is why it was removed previous release. Now, after more research and few hundred hours of work, I've implemented a new technology in this browser that allows it.<br />
BUT even more... a website's authenticated-session gets now saved to your portal, so next time when you will open the same website, the app will simply re-use your authentication data, without the need to login again. This means that on most websites you will not have to fill-in captcha again eachtime you login, etc.<br />
P.S. This opens the door to more opportunities for OnlyFans agencies 👀, meaning that more sexters could use the same creator's session in paralel - without needing to relogin/etc (except if session expires at some point, which is supposed to happen at times)<br />
</li>
<li>Fixed authentication issues on some websites (such as Camsoda or CamContacts) as I've discovered it was damaged (though nobody reported it back)<br />
</li>
<li>In OBS multi-rtmp we added the NEW TARGET button that you can use if you want to also restream to websites that we don't officially support by default. Initially we didn't wanted to allow users this option because opens the door to distributing the library to unwanted 3rd parties, but... let it be.<br />
</li>
<li>In OBS settings, now you have a 4th option. It happened that a few clients want to use XSplit or their own OBS, so they don't want our builtin functionality, and of course, everyone is free to use whatever they want. So, when you configure options for camsites, you are allowed to choose one of the following 4 options:<br />
</li>
</ol>
<div style="text-align: center;" class="mycode_align"> </div><ul class="mycode_list"><li>do nothing - use this option if you don't want any intteraction from our app (so your model can choose herself if wants to use WebEncoder or your own OBS or XSplit or whaever you have)<br />
</li>
<li>our dedicated OBS - means that for a camsite, the browser will open a unique OBS (so you can have multiple OBS instances running at the same time)<br />
</li>
<li>our OBS in Multi-RTMP technique - for having 1 OBS from which you re-stream to other websites when needed<br />
</li>
<li>force WEB encoder - use this option if you want to force the web encoder (where possible). For example on chaturbate, when the model will go online, if she clicks the "external streaming" button, whe will be redirected back to web-encoder right away.<br />
</li>
</ul>
 After this release I will focus on upgrading the Chrome to (probably) version 109.After that, more plans are on table]]></description>
			<content:encoded><![CDATA[Here's what's new in (probably) the last release of this app which is still based on Chrome v103<br />
<ol type="1" class="mycode_list"><li>It seems that the flag we re-enabled at a client's request a while ago (WindowsMediaFoundation) is actually causing issues with selecting webcam when ANY webcam is already in use by other apps (or tabs). This being said, the WindowsMediaFoundation is again disabled by default in the browser, to ensure proper functionality again.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">It was really hard work, but I successfully implemented a new technology in order to support multi-sessions</span> <span style="color: #FF0000;" class="mycode_color">❤❤❤❤</span>. My previous implementation was okeish, simple (i like things simple)... and lots of you were happy about it, but it seems it had some issues and that is why it was removed previous release. Now, after more research and few hundred hours of work, I've implemented a new technology in this browser that allows it.<br />
BUT even more... a website's authenticated-session gets now saved to your portal, so next time when you will open the same website, the app will simply re-use your authentication data, without the need to login again. This means that on most websites you will not have to fill-in captcha again eachtime you login, etc.<br />
P.S. This opens the door to more opportunities for OnlyFans agencies 👀, meaning that more sexters could use the same creator's session in paralel - without needing to relogin/etc (except if session expires at some point, which is supposed to happen at times)<br />
</li>
<li>Fixed authentication issues on some websites (such as Camsoda or CamContacts) as I've discovered it was damaged (though nobody reported it back)<br />
</li>
<li>In OBS multi-rtmp we added the NEW TARGET button that you can use if you want to also restream to websites that we don't officially support by default. Initially we didn't wanted to allow users this option because opens the door to distributing the library to unwanted 3rd parties, but... let it be.<br />
</li>
<li>In OBS settings, now you have a 4th option. It happened that a few clients want to use XSplit or their own OBS, so they don't want our builtin functionality, and of course, everyone is free to use whatever they want. So, when you configure options for camsites, you are allowed to choose one of the following 4 options:<br />
</li>
</ol>
<div style="text-align: center;" class="mycode_align"> </div><ul class="mycode_list"><li>do nothing - use this option if you don't want any intteraction from our app (so your model can choose herself if wants to use WebEncoder or your own OBS or XSplit or whaever you have)<br />
</li>
<li>our dedicated OBS - means that for a camsite, the browser will open a unique OBS (so you can have multiple OBS instances running at the same time)<br />
</li>
<li>our OBS in Multi-RTMP technique - for having 1 OBS from which you re-stream to other websites when needed<br />
</li>
<li>force WEB encoder - use this option if you want to force the web encoder (where possible). For example on chaturbate, when the model will go online, if she clicks the "external streaming" button, whe will be redirected back to web-encoder right away.<br />
</li>
</ul>
 After this release I will focus on upgrading the Chrome to (probably) version 109.After that, more plans are on table]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[103.1.41.20 on 7th December 2022]]></title>
			<link>https://support.camerolla.com/Thread-103-1-41-20-on-7th-December-2022</link>
			<pubDate>Wed, 07 Dec 2022 18:00:41 +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-103-1-41-20-on-7th-December-2022</guid>
			<description><![CDATA[Here's what has changed in version .20, released on 7th December 2022<br />
<ol type="1" class="mycode_list"><li>We added browser support + OBS support for LiveJasmin, since their FREE-SHOW accounts can go online with OBS for a while. We've enabled for them the same functionalities that you're used to. The model will simply press "go online" and she will only have to wait for the app to do all the clicking automatically.<br />
</li>
<li>When going online on chaturbate, the app will first ask if you want to reset the streaming token or not. So the model can choose if she wants to reset the streaming key or not.<br />
<img src="https://downloads.camerolla.com/20-p1.png" loading="lazy"  alt="[Image: 20-p1.png]" class="mycode_img" /><br />
</li>
<li>Added 2 new buttons on the interface, that most of you will find very useful: ISSUES and SHIFT REPORT.<br />
<img src="https://downloads.camerolla.com/20-p2.png" loading="lazy"  alt="[Image: 20-p2.png]" class="mycode_img" /><br />
The first one (ISSUES), is to be used by any user when they want to report a technical issue. Internal mailbox emails will be sent automatically to staff persons.<br />
The last one (SHIFT REPORT) is to be used to file shift reports, and that data will be available in the web panel similarly to how the Evaluations show-up:<br />
<img src="https://downloads.camerolla.com/20-p3.png" loading="lazy"  alt="[Image: 20-p3.png]" class="mycode_img" /><br />
</li>
<li>Disabled tab-grouping and colloring for models, because it was confusing for the models, especially beccause Chrome itself is "moving" tabs to where the "group" exists... and that was bad behavior.<br />
</li>
<li>This browser will now always run with DISABLE GPU for rendering the user interface. It was reported to me that on some websites, the users where seing black-screens, and this was caused by direct UI rendering to GPU. Please report to me if you see any more issues.<br />
</li>
<li>In case it's gonna be needed, please note that starting now, the browser accepts command line parameters for automatic login. Those are <span style="font-weight: bold;" class="mycode_b">--username and --password</span>. If you need help understanding how to use them, please let me know<br />
</li>
<li>Fixed OBS setup and detection on MyFreeCams and on Streamate (caused by recent changes in their UI)<br />
</li>
</ol>
<br />
 That's all folks, hope you enjoy this update!]]></description>
			<content:encoded><![CDATA[Here's what has changed in version .20, released on 7th December 2022<br />
<ol type="1" class="mycode_list"><li>We added browser support + OBS support for LiveJasmin, since their FREE-SHOW accounts can go online with OBS for a while. We've enabled for them the same functionalities that you're used to. The model will simply press "go online" and she will only have to wait for the app to do all the clicking automatically.<br />
</li>
<li>When going online on chaturbate, the app will first ask if you want to reset the streaming token or not. So the model can choose if she wants to reset the streaming key or not.<br />
<img src="https://downloads.camerolla.com/20-p1.png" loading="lazy"  alt="[Image: 20-p1.png]" class="mycode_img" /><br />
</li>
<li>Added 2 new buttons on the interface, that most of you will find very useful: ISSUES and SHIFT REPORT.<br />
<img src="https://downloads.camerolla.com/20-p2.png" loading="lazy"  alt="[Image: 20-p2.png]" class="mycode_img" /><br />
The first one (ISSUES), is to be used by any user when they want to report a technical issue. Internal mailbox emails will be sent automatically to staff persons.<br />
The last one (SHIFT REPORT) is to be used to file shift reports, and that data will be available in the web panel similarly to how the Evaluations show-up:<br />
<img src="https://downloads.camerolla.com/20-p3.png" loading="lazy"  alt="[Image: 20-p3.png]" class="mycode_img" /><br />
</li>
<li>Disabled tab-grouping and colloring for models, because it was confusing for the models, especially beccause Chrome itself is "moving" tabs to where the "group" exists... and that was bad behavior.<br />
</li>
<li>This browser will now always run with DISABLE GPU for rendering the user interface. It was reported to me that on some websites, the users where seing black-screens, and this was caused by direct UI rendering to GPU. Please report to me if you see any more issues.<br />
</li>
<li>In case it's gonna be needed, please note that starting now, the browser accepts command line parameters for automatic login. Those are <span style="font-weight: bold;" class="mycode_b">--username and --password</span>. If you need help understanding how to use them, please let me know<br />
</li>
<li>Fixed OBS setup and detection on MyFreeCams and on Streamate (caused by recent changes in their UI)<br />
</li>
</ol>
<br />
 That's all folks, hope you enjoy this update!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[103.1.41.19 - 25th November 2022]]></title>
			<link>https://support.camerolla.com/Thread-103-1-41-19-25th-November-2022</link>
			<pubDate>Wed, 30 Nov 2022 10:38:15 +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-103-1-41-19-25th-November-2022</guid>
			<description><![CDATA[<span style="font-size: medium;" class="mycode_size">BIG 💣 changes in this update</span><br />
<br />
This update comes with important changes that will improve your productivity and open your 👀 to new business opportunitiesFirst of all, let me tell you a bit about the smaller changes in this version, which are also important:<ul class="mycode_list"><li>fixed login in Lovense extension<br />
</li>
<li>fixed a latency issue with spying microphone (hopefully).<br />
</li>
<li>on Chaturbate. Since 19th october, it started happening that one model was streaming from other model's streaming-key and vice-versa. This happened to me and also to models in other studios, and accounts where banned. I've reported the issue to Chaturbate, even to Shirley, but it will take ages till they will take me seriously. So I've implemented <span style="font-weight: bold;" class="mycode_b">automatic reset of streaming token</span>, every time the model goes online, to always ensure a fresh token used for that streaming session.<br />
</li>
<li>removed webcam preview (retrieved from OBS) on XLoveCam. Despite I've made it 10fps, it still confuses camgirls and value/productivity was affected as it seems.<br />
</li>
<li>staff persons will be able to open as many accounts in the same browser, without needing to logout from previous accounts:<br />
<img src="https://downloads.camerolla.com/19-1.png" loading="lazy"  alt="[Image: 19-1.png]" class="mycode_img" /><br />
</li>
<li>tab <span style="color: #ff0000;" class="mycode_color">coloring</span> and <span style="color: #ff0000;" class="mycode_color">grouping</span>. The camsites opened will now get grouped by "stagename" and this will allow for easier and better management for your trainers.<br />
</li>
<li>automatic earnings detection will now work even when a staff person opens and logs-in in a camsite. For example if trainer Maria will open Streamray of model Christina, earnings will be detected once the trainer loggedin in her streamray account.<br />
</li>
</ul>
 Now, about the big update <img src="https://updates.camerolla.com/js/ckeditor/plugins/smiley/images/devil_smile.png" loading="lazy"  alt="[Image: devil_smile.png]" class="mycode_img" />🌸 Creator Agency functionalitiesNow you can extend your business from being only a cam-studio, to being also a <span style="font-weight: bold;" class="mycode_b">Creators Agency</span>.With Camerolla and our powerful app, you can now manage sexters and creators as-well. <span style="font-weight: bold;" class="mycode_b">And we've made things crazy simple</span>.You already know how to add Staff accounts and model accounts, no? Now a new type of account has been added to the system: <span style="font-weight: bold;" class="mycode_b">THE SEXTER</span> account.<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-2.png" loading="lazy"  alt="[Image: 19-2.png]" class="mycode_img" /></div>So, now you can build your own team of sexters, and here's how simple and effective we've made things:<ul class="mycode_list"><li>a sexter account, will only be able to access fansite accounts. For example, if you have model MARIA who has camsite accounts but also fansite accounts, here's what happens:<ul class="mycode_list"><li>a staff person will be able to see all type of accounts of this model (for example her XLoveCam account, her LiveJasmin account, but also her OnlyFans or LoyalFans accounts)<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">but the sexter</span> will only be able to see the fansite accounts (the sexter will NOT see the model's camsite accounts)<br />
</li>
<li>(we've made this as simple as this because you want to keep track of earnings in one place, so to avoid having a "model" account for camming, and another "model" account for fansites.<br />
</li>
</ul>
</li>
<li>in earnings pages, a sexter will only see statistics about the fansite accounts, and never see how much money a model earns from her camsites.<br />
</li>
</ul>
Note: For the moment we only support OnlyFans and LoyalFans. We will probably add support for Fansly and other platforms, if needed. When a Sexter is using Camerolla browser, he/she will be able to open as many creator accounts as he/she wants in the same browser via <span style="color: #ff0000;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">our multi-login technology</span></span> that we implemented directly in Camerolla:<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-3.png" loading="lazy"  alt="[Image: 19-3.png]" class="mycode_img" /></div>Also, when a sexter authenticated to a creator's account (let's say OnlyFans), the panel is notified about this and our app will start monitoring the earnings this sexter is earning for that creator account (we will monitor exactly how much money the sexter is selling from tipping and chatting).<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-4.png" loading="lazy"  alt="[Image: 19-4.png]" class="mycode_img" /></div>Later on, periodically, you will easily know how much money you have to pay your sexters, based on the percentages that you offer them, of those money earned from chatting and tipping.If you're managed to using the payments system of models, similarly you will also be able to create the payments for your Sexters, and you will know whom to pay and how much &#36;&#36;&#36;. Also, like any other staff person, they will be registered with shifts internally, so you know how much time they are working, etc. Thoug, in their case, being "active" or inactive is measured by monitoring if the PC is IDLE or not.Thanks to our intelligent multi-login functionality, your sexters will easily go online on any creator account without ever knowing the creator's password. But even more, your sexters will never be allowed to navigate to "sensitive" pages such as banking, credit cards or settings:<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-5.png" loading="lazy"  alt="[Image: 19-5.png]" class="mycode_img" /></div>]]></description>
			<content:encoded><![CDATA[<span style="font-size: medium;" class="mycode_size">BIG 💣 changes in this update</span><br />
<br />
This update comes with important changes that will improve your productivity and open your 👀 to new business opportunitiesFirst of all, let me tell you a bit about the smaller changes in this version, which are also important:<ul class="mycode_list"><li>fixed login in Lovense extension<br />
</li>
<li>fixed a latency issue with spying microphone (hopefully).<br />
</li>
<li>on Chaturbate. Since 19th october, it started happening that one model was streaming from other model's streaming-key and vice-versa. This happened to me and also to models in other studios, and accounts where banned. I've reported the issue to Chaturbate, even to Shirley, but it will take ages till they will take me seriously. So I've implemented <span style="font-weight: bold;" class="mycode_b">automatic reset of streaming token</span>, every time the model goes online, to always ensure a fresh token used for that streaming session.<br />
</li>
<li>removed webcam preview (retrieved from OBS) on XLoveCam. Despite I've made it 10fps, it still confuses camgirls and value/productivity was affected as it seems.<br />
</li>
<li>staff persons will be able to open as many accounts in the same browser, without needing to logout from previous accounts:<br />
<img src="https://downloads.camerolla.com/19-1.png" loading="lazy"  alt="[Image: 19-1.png]" class="mycode_img" /><br />
</li>
<li>tab <span style="color: #ff0000;" class="mycode_color">coloring</span> and <span style="color: #ff0000;" class="mycode_color">grouping</span>. The camsites opened will now get grouped by "stagename" and this will allow for easier and better management for your trainers.<br />
</li>
<li>automatic earnings detection will now work even when a staff person opens and logs-in in a camsite. For example if trainer Maria will open Streamray of model Christina, earnings will be detected once the trainer loggedin in her streamray account.<br />
</li>
</ul>
 Now, about the big update <img src="https://updates.camerolla.com/js/ckeditor/plugins/smiley/images/devil_smile.png" loading="lazy"  alt="[Image: devil_smile.png]" class="mycode_img" />🌸 Creator Agency functionalitiesNow you can extend your business from being only a cam-studio, to being also a <span style="font-weight: bold;" class="mycode_b">Creators Agency</span>.With Camerolla and our powerful app, you can now manage sexters and creators as-well. <span style="font-weight: bold;" class="mycode_b">And we've made things crazy simple</span>.You already know how to add Staff accounts and model accounts, no? Now a new type of account has been added to the system: <span style="font-weight: bold;" class="mycode_b">THE SEXTER</span> account.<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-2.png" loading="lazy"  alt="[Image: 19-2.png]" class="mycode_img" /></div>So, now you can build your own team of sexters, and here's how simple and effective we've made things:<ul class="mycode_list"><li>a sexter account, will only be able to access fansite accounts. For example, if you have model MARIA who has camsite accounts but also fansite accounts, here's what happens:<ul class="mycode_list"><li>a staff person will be able to see all type of accounts of this model (for example her XLoveCam account, her LiveJasmin account, but also her OnlyFans or LoyalFans accounts)<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">but the sexter</span> will only be able to see the fansite accounts (the sexter will NOT see the model's camsite accounts)<br />
</li>
<li>(we've made this as simple as this because you want to keep track of earnings in one place, so to avoid having a "model" account for camming, and another "model" account for fansites.<br />
</li>
</ul>
</li>
<li>in earnings pages, a sexter will only see statistics about the fansite accounts, and never see how much money a model earns from her camsites.<br />
</li>
</ul>
Note: For the moment we only support OnlyFans and LoyalFans. We will probably add support for Fansly and other platforms, if needed. When a Sexter is using Camerolla browser, he/she will be able to open as many creator accounts as he/she wants in the same browser via <span style="color: #ff0000;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">our multi-login technology</span></span> that we implemented directly in Camerolla:<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-3.png" loading="lazy"  alt="[Image: 19-3.png]" class="mycode_img" /></div>Also, when a sexter authenticated to a creator's account (let's say OnlyFans), the panel is notified about this and our app will start monitoring the earnings this sexter is earning for that creator account (we will monitor exactly how much money the sexter is selling from tipping and chatting).<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-4.png" loading="lazy"  alt="[Image: 19-4.png]" class="mycode_img" /></div>Later on, periodically, you will easily know how much money you have to pay your sexters, based on the percentages that you offer them, of those money earned from chatting and tipping.If you're managed to using the payments system of models, similarly you will also be able to create the payments for your Sexters, and you will know whom to pay and how much &#36;&#36;&#36;. Also, like any other staff person, they will be registered with shifts internally, so you know how much time they are working, etc. Thoug, in their case, being "active" or inactive is measured by monitoring if the PC is IDLE or not.Thanks to our intelligent multi-login functionality, your sexters will easily go online on any creator account without ever knowing the creator's password. But even more, your sexters will never be allowed to navigate to "sensitive" pages such as banking, credit cards or settings:<div style="text-align: center;" class="mycode_align"><img src="https://downloads.camerolla.com/19-5.png" loading="lazy"  alt="[Image: 19-5.png]" class="mycode_img" /></div>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[103.1.41.16]]></title>
			<link>https://support.camerolla.com/Thread-103-1-41-16</link>
			<pubDate>Wed, 30 Nov 2022 10:32:40 +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-103-1-41-16</guid>
			<description><![CDATA[Here's what has changed in this update.<span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">First of all, the requirements installer</span></span> (in case it doesn't auto-update (<span style="text-decoration: underline;" class="mycode_u">which can happen if OBS is opened!</span>), please manually run it from here <a href="https://ro.downloads.camerolla.com/browser-camerolla-reqs-103.1.1.39.exe" target="_blank" rel="noopener" class="mycode_url">https://ro.downloads.camerolla.com/brows...1.1.39.exe</a>) will add 2 things:<br />
<ol type="1" class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">a VirtualCam plugin compatible with OBS v28+</span> which is required for those that want to use OBS-Camera in apps like JasminFive - since things are not really working with OBS'es default virtual camera plugin).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">A lightweight RTMP server that we discovered is very powerful and fast</span> and doesn't consume any CPU resources named <a href="https://github.com/MonaSolutions/MonaServer" target="_blank" rel="noopener" class="mycode_url">MonaServer</a>.<br />
We use this RTMP server app in order to facilitate a well awaited functionality in OBS multi-rtmp.<br />
</li>
</ol>
<br />
We launched this upate to the requirements installer yesterday, so it will have time to propagate to you - the clients.Second, the well awaited functionality about MULTI-RTMP.<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Story: before this update, our app used to "decide" for a given model, which will be the MAIN site for streaming in OBS. The requirement was that the model had to first stream in that website, and only after that, to stream in the other additional sites. For example, if she had chaturbate, stripchat, camsoda, bongacams... she had to first login and start broadcasting on chaturbate, and only after that, go live on any other of her 3 camsite accounts.But even more... if she had a private show for example on a non-main website and she had to stop broadcasting on main, this would have been impossible because if she stopped main site, all other sites would have also stopped working, or causing crashes on some computers (probably due to nvidia encoding i guess).</blockquote>
<br />
<span style="font-weight: bold;" class="mycode_b">BUT FROM TODAY</span>, with the help of the local RTMP server i was telling you earlier, things are very simple!In OBS you will notice a new INFO in the MAIN SITE area:<br />
<img src="https://downloads.camerolla.com/obs-monaserver.png" loading="lazy"  alt="[Image: obs-monaserver.png]" class="mycode_img" /><br />
So what happens now is that your models can go online on all MULTI-RTMP camsites IN ANY ORDER they want, without issues.When you will be asked by your models about this change, please tell them that they can login in whatever order they want. But ask them never to stop streaming in OBS... as if they do that, it could cause issues with the other sites. Instead, ask them to use the STOP buttons in the multi-rtmp area.]]></description>
			<content:encoded><![CDATA[Here's what has changed in this update.<span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">First of all, the requirements installer</span></span> (in case it doesn't auto-update (<span style="text-decoration: underline;" class="mycode_u">which can happen if OBS is opened!</span>), please manually run it from here <a href="https://ro.downloads.camerolla.com/browser-camerolla-reqs-103.1.1.39.exe" target="_blank" rel="noopener" class="mycode_url">https://ro.downloads.camerolla.com/brows...1.1.39.exe</a>) will add 2 things:<br />
<ol type="1" class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">a VirtualCam plugin compatible with OBS v28+</span> which is required for those that want to use OBS-Camera in apps like JasminFive - since things are not really working with OBS'es default virtual camera plugin).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">A lightweight RTMP server that we discovered is very powerful and fast</span> and doesn't consume any CPU resources named <a href="https://github.com/MonaSolutions/MonaServer" target="_blank" rel="noopener" class="mycode_url">MonaServer</a>.<br />
We use this RTMP server app in order to facilitate a well awaited functionality in OBS multi-rtmp.<br />
</li>
</ol>
<br />
We launched this upate to the requirements installer yesterday, so it will have time to propagate to you - the clients.Second, the well awaited functionality about MULTI-RTMP.<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Story: before this update, our app used to "decide" for a given model, which will be the MAIN site for streaming in OBS. The requirement was that the model had to first stream in that website, and only after that, to stream in the other additional sites. For example, if she had chaturbate, stripchat, camsoda, bongacams... she had to first login and start broadcasting on chaturbate, and only after that, go live on any other of her 3 camsite accounts.But even more... if she had a private show for example on a non-main website and she had to stop broadcasting on main, this would have been impossible because if she stopped main site, all other sites would have also stopped working, or causing crashes on some computers (probably due to nvidia encoding i guess).</blockquote>
<br />
<span style="font-weight: bold;" class="mycode_b">BUT FROM TODAY</span>, with the help of the local RTMP server i was telling you earlier, things are very simple!In OBS you will notice a new INFO in the MAIN SITE area:<br />
<img src="https://downloads.camerolla.com/obs-monaserver.png" loading="lazy"  alt="[Image: obs-monaserver.png]" class="mycode_img" /><br />
So what happens now is that your models can go online on all MULTI-RTMP camsites IN ANY ORDER they want, without issues.When you will be asked by your models about this change, please tell them that they can login in whatever order they want. But ask them never to stop streaming in OBS... as if they do that, it could cause issues with the other sites. Instead, ask them to use the STOP buttons in the multi-rtmp area.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New BETA app, 9 october 2021]]></title>
			<link>https://support.camerolla.com/Thread-New-BETA-app-9-october-2021</link>
			<pubDate>Fri, 08 Oct 2021 20:05:51 +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-New-BETA-app-9-october-2021</guid>
			<description><![CDATA[Hello dear friends,<br />
<br />
Today I'm letting you know that, in the newest BETA that is yet to be released, I've added new important and spectaculaer features that you might find really really useful.<br />
On short, the software comes with a few features (that I will later detail and explain in replies to this topic):<br />
<ol type="1" class="mycode_list"><li>Automatic configuration of the configured MULTI OBS sites. On short, what you configure as MULTI in the camerolla://welcome page, will be exactly what you also see in the Multi-OBS feature of OBS. And this process is automatic.<br />
</li>
<li>The Camerolla browser will now detect each site's specific OBS streaming parameters, and will configure OBS automatically. This said, will detect things such as RTMP server path and key, and will configure OBS for you automatically.<br />
</li>
<li>Also, the browser will start and stop streaming in OBS automatically.<br />
</li>
<li>Aaaaaaand, live detection of tipping (and othher features such as gifts or toy-actions) - in order to reflect this in the known visual effects from OBS<br />
</li>
</ol>
Stay tunner, will come with details soon!]]></description>
			<content:encoded><![CDATA[Hello dear friends,<br />
<br />
Today I'm letting you know that, in the newest BETA that is yet to be released, I've added new important and spectaculaer features that you might find really really useful.<br />
On short, the software comes with a few features (that I will later detail and explain in replies to this topic):<br />
<ol type="1" class="mycode_list"><li>Automatic configuration of the configured MULTI OBS sites. On short, what you configure as MULTI in the camerolla://welcome page, will be exactly what you also see in the Multi-OBS feature of OBS. And this process is automatic.<br />
</li>
<li>The Camerolla browser will now detect each site's specific OBS streaming parameters, and will configure OBS automatically. This said, will detect things such as RTMP server path and key, and will configure OBS for you automatically.<br />
</li>
<li>Also, the browser will start and stop streaming in OBS automatically.<br />
</li>
<li>Aaaaaaand, live detection of tipping (and othher features such as gifts or toy-actions) - in order to reflect this in the known visual effects from OBS<br />
</li>
</ol>
Stay tunner, will come with details soon!]]></content:encoded>
		</item>
	</channel>
</rss>