Hello guys,

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 I AM NOT ABLE to provide it pre-installed anymore and also the automatic login inside the extension will not work anymore.

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).
 

1. 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: https://downloads.camerolla.com/Lovense-...31.3.6.zip
   
2. 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
   
3. After this, please follow the steps which are better described by the images bellow, since its easier to explain the process like this:
   

Hello,

Camerolla's earning detection works best if the following conditions are met:

1. 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)
   
2. 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).
   
3. the browser's settings should also be default
   
4. 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.
   

• in Spanish, a date is *15/03/24* , earned value is *0,47 €* (using COMMA as decimals separator)
  
• in English, the date is *3/15/24* or "15/03/2024" and the earned value is *€0.47* (using DOT as decimals separator)
  

• 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.
  
• 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.
  

• either the app wasn't used continuously and some earnings are missing
  
• either the model received offline earnings after her last login
  
• either the PC's settings (language/etc) are not standard / default and thus the detection is faulty.
  
• either the model has changed website's language from English to some other language
  

Attached Files

Thumbnail(s)
       

Hello,
This is a topic that has raised many discussions over the years.
Detecting if a model is ONLINE can be done in only a few ways:

• detection of keyboard and/or mouse activity --- which is not good because models are most of the time dancing/speaking, so this method fails
  
• 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
  
• 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
  
• 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.
  

When it happens that Lovense's OBS Toolset is updatnig, it always messes up with all files and ruins your standard multi-rtmp usage.

To fix this, here's what you need to do:

1. Download our version of the plugin from https://ro.downloads.camerolla.com/obs-m...mp-qt6.dll
   
2. Close your OBS entirelly
   
3. open FileExplorer on your windows (WIN key + E) and manually navigate to this path: C:\ProgramData\obs-studio\plugins\obs-multi-rtmp-qt6\bin\64bit
   
4. delete the obs-multi-rtmp-qt6.dll that exists in that directopry (which is the one from Lovense)
   
5. copy the file you donwloaded at step 1 in this path.
   

Attached Files

Thumbnail(s)
   

Daca se intampla la vruen moment dat sa intampinati vreo eroare de tipul Aw, Snap!, 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).
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.

Pentru a sterge profilul de Camerolla (chrome) faceti urmatoarele:
1. Deschideti Windows explorer (sau my computer)
2. In bara de navigare, dati copy/paste la textul acesta: %appdata%\..\Local\CygnusTechnologies\
3. Stergeti tot ce exista in acel folder
4. Re-porniti Camerolla si reconfigurati adresa de URL de client + setarile de OBS.

Buna,

Una din intrebarile recente are 2 forme si aceeasi cauza:

1. Sunetul modelelor (voce, gemete, etc) se aude pe site-urile din Camerolla DAR sunetul muzicii din YouTube NU se aude pe site-urile respective
   
2. Pe unele site-uri nu se aude sunetul modelelor de loc, de exemplu pe Streamate si ImLive, desi pe LiveJasmin se aude fara probleme
   

• Allow WebRTC to adjust the input volume - asta ca sa nu se mai creeze probleme de volum intre site-uri
  
• WebRTC downmix capture audio method
  
• Chrome-wide echo cancellation - asta e de fapt optiunea care face ca sunetul sa nu mai fie disponibil intre site-uri
  

To delete the Camerolla browser profile, follow this guide:
1. open windows explorer
2. in the address bar, navigate to %appdata%/../Local/CygnusTechnologies
3. Make sure that Camerolla is closed
4. from the folder listing that shows up, delete the Camerolla-Browser directory

Here's what changed in this update (110.1.48.1, released on 21st Feb 2023)

1. Chrome has been updated from v103 to v110 now
   
2. 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).
   
3. AutoLogin and Earnings detection for ManyVids
   
4. AutoLogin, Earnings and PayPerMin management for CamModelDirectory
   
5. Fixed autologin in YouTube accounts
   
6. Upgraded internal LovenseExtension from 30.5.0 to 30.5.4 (latest on their site)
   
7. Fixed a crash regarding some API communication with your portal (regarding Articles query)
   
8. 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
   
9. 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
   
10. Many changes to the multi-session technology that exists in the product. About this, I will talk separatelly, bellow.
    

• first time user connects to a website, if will perform authentication (if no auth session exists already in cloud. Otherwise, session will be restored)
  
• 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)
  
• 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)
  
• etc
  

• 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)
  
• 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.
  
• less time spending on opening a website, because you skip waiting till login happened
  
• 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.
  
• 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.
  

Here's what's new in (probably) the last release of this app which is still based on Chrome v103

1. 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.
   
2. It was really hard work, but I successfully implemented a new technology in order to support multi-sessions ❤❤❤❤. 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.
   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.
   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)
   
3. Fixed authentication issues on some websites (such as Camsoda or CamContacts) as I've discovered it was damaged (though nobody reported it back)
   
4. 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.
   
5. 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:
   

• 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)
  
• 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)
  
• our OBS in Multi-RTMP technique - for having 1 OBS from which you re-stream to other websites when needed
  
• 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.
  

Here's what has changed in version .20, released on 7th December 2022

1. 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.
   
2. 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.
   
   
3. Added 2 new buttons on the interface, that most of you will find very useful: ISSUES and SHIFT REPORT.
   
   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.
   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:
   
   
4. 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.
   
5. 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.
   
6. In case it's gonna be needed, please note that starting now, the browser accepts command line parameters for automatic login. Those are --username and --password. If you need help understanding how to use them, please let me know
   
7. Fixed OBS setup and detection on MyFreeCams and on Streamate (caused by recent changes in their UI)