@20rushtonj what is the amount of grain value (Amount / Size) you selected / set in your Prot v4 examples you posted above?
did you add also “noise” or you left “noise” on “0”?
We have a fix for this that will be available in a future alpha. In the meantime, could you and @phil.stopford try logging in on the command line, using videoaiALPHA-login. It should print a URL to your terminal that will work even if the one it opens automatically doesn’t work.
1 Like
Thanks for following up about this. I attempted the fix and got the following error:
127.0.0.1 refused to connect.
After following these steps:
- Open terminal, enter videoaiALPHA-login (incorrect OAuth state error received)
- Copy URL into browser and receive error
Alternatively, I tried these as well:
- Open TVAI, click Activate (incorrect OAuth state error received)
- Open terminal, enter videoaiALPHA-login (incorrect OAuth state error received)
- Copy URL into browser and receive localhost error
I can also confirm i’m unable to activate mine, getting the same error on Ubuntu
That works for me - I got a link in the terminal which I could open in the browser and re-login in. That seemed to pass and the tool loads up just fine. I did not have Video AI running when using the login tool. After it reported success, I launched the VideoAI binary and it came up using the below, on Arch, so that the cuda and other libraries can be found:
LD_LIBRARY_PATH=/opt/cuda/lib:/opt/cuda/bin:/opt/TopazVideoAIALPHA/bin:/opt/TopazVideoA
IALPHA/lib /opt/TopazVideoAIALPHA/bin/Topaz\ Video\ AI\ ALPHA
1 Like
Noise in the Proteus v4 settings was at 0.
In the grain section Amount was 4 and Size was 2.
1 Like
@mlevine-2048 it seems like you have an entry in your Hosts file with that strange settings, loopback your traffic to your computer (your computer Winsock TCP/IP kernel) instead of going to the Internet. that prevents your computer connecting to Topaz due to DNS name resolution override loopback settings.
it is defiantly not a DNS resolution fault from your ISP as 127.0.0.0/8 (IP range) is a non valid internet address space. and Public DNS reject such settings if attempted to be created. also it would reject resolving to such an IP range.
You need to clear it from your “Hosts” file
On Windows the Hosts file is located at: "%SystemRoot%\System32\drivers\etc"
On MacOS (10.2 or above) it is lacated at: “/etc/hosts (a symbolic link to /private/etc/hosts)”
That will solve all your issues and all 3 methods would work
Please make sure you’ve logged out from the Topaz Labs Account - Topaz Labs page before trying those steps. If you’re getting far enough in the login process before it errors out, the login program may be closing before you have a chance to manually open the URL.
If you’re logged out, it should wait while you’re on the login screen which will give you time to actually copy-paste the correct link.
I have a feeling this is more due to how the Topaz authentication mechanism works. I imagine they’re running a local server on your PC which is open at a specific port and the webpage speaks to that port on localhost to send the authentication token. In this situation, the topaz server has likely already failed due to the token issue which causes it to turn off after failing and for the additional attempts at authentication to fail because they are unable to reach the local server.
I attempted logging out before trying the above steps and encountered the same issue. For additional context, I’m getting this error on the command line as well:
/usr/local/bin/videoaiALPHA-login: line 5: 41859 Segmentation fault (core dumped) /opt/TopazVideoAIALPHA/bin/login $@
The segfault happens when I click the generated link and I never do get to the login screen.
That is something you can only know for sure if I run Wireshark on your PC to trace network traffic of Topaz. I had something similar and after a wireshark analysis , I found it was an issue with DNS resolution. “no domain name found”. i fixed it with some commands in netsh. try 1st what i suggested and see if it is the right direction or not.
Thanks for the suggestion. I agree that could potentially help to resolve the issue, but is likely more effort than I would want to go through right now since they said above that this will likely be resolved in the next release.
I dual-boot Windows and typically use most commercial software (including TVAI, Premiere, Flowframes, etc.) on that installation while leveraging most open-source projects and development on the Linux installation, so it’s not a major issue for me personally, but something I’d like to see fixed so I can do more on Linux 
Use WSL in windows, it’s as fast as running linux bare metal.
1 Like
Oh, it’s not a speed thing, I just prefer Linux over Windows for a variety of reasons.
Me too I’ve been using linux since 1994 and was just saying that today I have no need to dual boot from windows to linux anymore and run archlinux with full systemd support under WSL 
1 Like
Same thing with me. 2020 iMac_Fully Loaded
