Before a team member answer you, I’d suggest you try to move away all custom nodes from both modules folders if you have any installed, and give the hardware specs of your machine so the team can isolate the bug better.
It’s running for me.
2 Likes
Thanks for the reply :)
It’s a fresh install of MacOS 10.15.3 on a new Mac.
No custom nodes in both modules folders.
Hardware spec:
- MacBook Pro 16,1
- 8-core Intel Core i9
- 2,4 GHz
- 64 GB RAM
- AMD Radeon Pro 5500M 8 GB
- Intel UHD Graphics 630 1536MB
Great specs ! ;)
Mmm. One other thing the team might ask is to check the console (applications, utilities, console) for Vuo logs that you can paste as here if any.
Luckily the 201 update is a more minor update and happy that the 200 version is still working for you.
1 Like
Indeed, Console logs would be helpful. I wonder if it’s the same problem as this one. Sorry for the trouble, @DetAndreTeatret.
In addition to the suggestions on that bug report, one other thing to try:
- Quit Vuo.
- In Finder, go to the Go menu, hold down Option, and select Library.
- Navigate to Library > Caches.
- Find the org.vuo folder and throw it in the Trash.
- Launch Vuo.
Actually no, I think it’s a different problem from the one I linked above but the same problem as this one. Now we have enough information and will get it fixed ASAP.
1 Like
Yippi! SuperThanks!
Sorry for not being able to provide enough logs and information :)
This is all a bit new to me. Using quarantine-times to learn something new!
Stay safe and keep up the good work!