#Is it a way to get over this problem?

1 messages · Page 1 of 1 (latest)

vivid shell
#

It happens when I try to change profiles or any change in the wootility.io

#

Oh I think I just figured it out... it was "Ulanzi Studio App" working. I saw someone saying about another software doing conflicts with Wootility in some post in the forums on the internet. .. and I remembered that my wooting was working just fine so I tried to remember what software I installed a while back ago and it was Ulanzi Studio app. I just closed it and my Wooting is working just fine. Is it a way to both work just fine tho?

coarse hornet
# vivid shell Oh I think I just figured it out... it was "Ulanzi Studio App" working. I saw so...

this is the first case I have heard of Ulanzi Studio app — does this control the keyboard RGB or interact with the keyboard at all? as we may want to look into this further to see why this is occurring?

for references In the past, software that controls the keyboard RGB would cause issues with maintaining a connection to Wootility

but we have made further improvements in Wootility and the keyboard's firmware to stop this issue from occurring, so this should not really happen now

vivid shell
coarse hornet
#

hmm in that case if it is not trying to change the RGB, it should not be causing issues

sounds like the studio app is interacting where it is not meant to causing issues

you can perform the tests below to see what errors occur

  • Close down the app

  • Launch Wootility (app)

  • Go to (settings)

  • Open error log (bottom left)

  • This will open a new folder

  • Close down Wootility

  • Delete main.log (so we can make a clean version)

  • Relaunch Wootility

  • wait for 5–10 seconds

  • Launch the studio app

  • Give it around 20–30 seconds to populate the (new) main.log file with the errors

  • Drag and drop the main.log file into the Discord

once i have this i will forward this to the software team incase this can be resolved on our side

vivid shell
#

I did your tests and I couldn't get the error to be happening.
So since I was always using the browser version, I tried things like this:

  • open the wootility app and then ulanzi app - ok
  • open the ulanzi app and then wootility app - ok
  • open the wootility web and open the profile and then ulanzi app - ok
  • open the ulanzi app and then open the wootility web - it starts to see the software/hardware you are using and then it gives an error.

I saw that the wootility web doesnt have the log to show you. But I caught a screenshot of the problem if it could give you smth.

#

I was using opera with the newest version of the wootility browser 5.0.6

#

well, at least I can use the app just fine. It's just a browser thing and for now I can use the app

#

it gives "wooting 60he found"
and then gives 2 erros saying that the communication with device timed out and the other saying the same thing, but in portuguese

#

this screenshots now are in the wootility browser

#

i hope it helps to see smth

#

also about the RGB thing, I saw that the Ulanzi Studio app has many features that comes with it. But as far as I could see is that they change some light features but its just sort of changing the lights of the hardware itself not the wooting... but I can search more about it, its somethijng called lightmaster

coarse hornet
#

hmm i will report this on slack (internal chat)

Thanks 🙂

vivid shell
#

Sure thing! I use slack too haha

Thank you sir, for your time. Glad for the support. I'm using the app just fine.

knotty otter
#

@vivid shell Please use the desktop version of the Wootility, trigger the issue and provide the error log.

#

Please also disconnect the Ulanzi device and check if you can still reproduce the issue.

So far I wasn't able to reproduce it with a W60HE+ and just the Ulanzi Studio app installed.

vivid shell
knotty otter
#

I also saw it happening with the app. The day that I reported this wasn't occurring because when I opened the app it didn't the check of the firmware/hardware that I'm using. It was "loaded" already so I could join.

I don't get what you mean.

vivid shell
#

The log has some older infos (day 21) but I just did right now. I saw that the log has timestamp so I dont think its a problem. If it is you can tell me so I clear it to you and try again

vivid shell
# knotty otter > I also saw it happening with the app. The day that I reported this wasn't occu...

I mean... when I did back that day to report to you guys that my app wasn't having this problem... it's because I did loaded my hardware in this step when you open the app. So when I closed the app I was just closing it pressing X but it was still opened (dumb me) in the windows tab. And I saw that it doesnt occur the error when I did it. But if I close it with the task manager and open it again... and open the ulanzi and then open the wootility, it occurs the error

#

"it's because I did loaded my hardware in this step when you open the app" [...] this step, when the hardware will be known by the app

knotty otter
#

So can you reproduce the issue without the Ulanzi device being connected?

vivid shell
#

No. When I close the Ulanzi it works just fine

knotty otter
#

As mentioned, so far I wasn't able to replicate the issue with just the app. So it would be nice to know if the presence of the Ulanzi device (the media deck or so) plays a role.

vivid shell
#

you have a point

#

I didnt occurred with only the app. Only if the device is connected

knotty otter
#

Ok, good to know...

You are on the stable firmware v2.10.1. Please go to the beta Wootility and install the latest beta firmware from there and re-test it.

vivid shell
#

is it? 5.1.0-beta.4

#

sorry, I just read it now. I will do it

knotty otter
#

This is the version of the beta Wootility. The firmware should be v2.11.0-beta.3.

vivid shell
#

okay, i did

#

let me try again with the device connected

#

of ulanzi

knotty otter
#

Can you still reproduce the issue?

vivid shell
#

it didnt occured. I tried also to close the browser, open in a new tab with annonymous... no problem at all with the ulanzi device connected

#

So its okay now!! with this update

knotty otter
#

Ok, great... The beta firmware has some improvements which are related if other apps also try to communicate with the Wooting.

It seems Ulanzi Studio does this. But it's weird that the Ulanzi device need to be connected for that.

vivid shell
knotty otter
#

If you want you can now use the stable Wootility again. But so far I recommend to stay on the beta firmware.

I don't know when the beta firmware changed will get merged to stable. But after the next stable update you no longer need to use the beta firmware.

vivid shell
#

I'm fine with it! Thank you for your time to looking it, Rock, and wooting team. You guys deserve more because its too good

knotty otter
#

No problem, we love our products and try to improve them if possible.

vivid shell
#

hey guys.

I just logging in my PC and I joined in the beta.wootility and I just got the same error... I didn't change anything lol
I even tried to join in a new tab in annonymous and it changed nothing - still gave me an error.
I can try to send the logs but I can't find it (the button to get the logs) in the website. You guys can still see that i'm in the same version from yesterday

I'm here to help tho if you guys need.

knotty otter
#

To bad... Please use the latest desktop version of the beta Wootility and provide the log from that. The web version don't allow to export the log. You can find the link [here](#📰│wootility_updates message).

#

Maybe it helps... Otherwise I need to see if I can get my hands on the device. So what specific product from Ulanzi do you own?

vivid shell
#

The new one is 5.1.0-beta.4

vivid shell
#

the link: https://www.amazon.com.br/dp/B0DD662YW5?ref=ppx_yo2ov_dt_b_fed_asin_title

It's from the brazilian website so Idk if it helps to know about it. Anything more you can ask. But I think the log has the version and the errors you might need

knotty otter
#

I ordered the device so I can try to reproduce the issue. I will let you know when there is an update.

knotty otter
#

I got the product but the software can't find it. So I'm not able to reproduce the issue yet.
I need to wait for the reply of their CS team. I read that I might need to update the firmware to be able to use the software.

The Studio software now doesn't even start.

vivid shell
knotty otter
#

I figured out why the app isn't working. I run it in a VM and when the 3D acceleration feature is disabled the app terminates after a few seconds.

vivid shell
#

Ah okay! Sure

#

I just finished it mine so I didnt have any trouble...

knotty otter
#

Needed to return the device as it doesn't work and the support wasn't able to help.
Need to see how I can get a working one.

vivid shell
#

Omg, I'm sorry for that!

I wish I could help more to see this problem...

knotty otter
#

It's not you fault. Other people had issues with the device too. But it makes it much more difficult to check out why the Ulanzi software causing issues with the Wooting. So it will delay the investigation for sure.

vivid shell
#

Okay Rock, thank you!!

knotty otter
#

So the second device also don't work. While the first got detected as a USB device after a few seconds for the second it takes minutes and both weren't detected by the Ulanzi software at all.

So as two units from Amazon (one from Amazon US and one from Ulanzi directly) don't work it doesn't make much sense to me to buy another. Meaning as I'm not able to reproduce the issue and so I sadly can't help.