Studio Session Analyzer Network Problems

[rolinhard316]

Hello!
So I have a fun one for you all.
I just installed my Flux Studio Session Analyzer & Studio Grabber on my Pro Tools 12.7 HP Z800 Windows 10 system with MBox Pro 3.

I installed SampleGrabber 3.5.25.43758 and Studio Session Analyzer 1.9.23.33903 which both seem to be the latest versions.

The problem is when I place the sample grabber plugin in a insert on my Pro Tools track and then launch Studio Session Analyzer on the same machine i get the following error: "Network: Connection to 198.105.244.228 : 46000 failed (I uploaded a screenshot to this post).

I looked through the knowledge base and tried disabling my firewall completely, I tried reinstalling, new project, installing the analyzer application on another computer and connecting back to this computer and all resulted in the same error.

Also for kicks I installed the analyzer and studio grabber on a Windows 10 HP Envy Laptop machine that has a Scarlett 2i2 gen 2 to see if that would work and to my surprise it worked perfectly.

What I noticed through all my testing is that on my working laptop the studio analyzer connects to the IP address of my laptop itself. However on my HP workstation the IP address that it says it is having problems with is a completely random address (198.105.244.228) that is not even in range of my actual IP address (192.168.2.105). So I am thinking that the problem lies somewhere here. Anyways I am totally stumped now having dumped a bunch of hours into this pursuit. I am really interested if anybody else out there has dealt with this.

[climber]

have you contacted them?

[rolinhard316]

I have contacted Flux. They only have email support so we will see what they say. My fingers are crossed!

[superdwyanepc]

Yeah, better ask the support for this.

[rolinhard316]

So its been a number of weeks. Support responded to me a couple times asking for additional information. I provided the additional information and they agreed there must be a problem. They asked me if I would be okay with them remoting into my computer and I agreed, however now its been two weeks of silence... My plight continues.

[matze7]

I have exactly the same problem (just the "wrong" IP-adress is different). Could the Support solve your problem?
Greetings matze7

[ilxxwuhe]

Hi,

(I just created this fake Avid account to help you out. I am not an Avid costumer.)

I was facing exactly the same problem, and since it was a network problem I tried to turn off Wi-Fi in my laptop and as soon as I did it I was able to connect to the Studio Session Analyzer with no problems.

I hope this helps you out.

Have a nice day

[matze7]

Hi ilxxwuhe,
thank you for your great help. Unfortunately, your solution didnt work in my case. But your Reply gave me new Opportunity to fix my problem, so i updated Pure Analyzer and SampleGrabber... and now it works. So you helped me nevertheless !!

Greets

[guitardom]

Originally Posted by rolinhard316

What I noticed through all my testing is that on my working laptop the studio analyzer connects to the IP address of my laptop itself. However on my HP workstation the IP address that it says it is having problems with is a completely random address (198.105.244.228) that is not even in range of my actual IP address (192.168.2.105). So I am thinking that the problem lies somewhere here. Anyways I am totally stumped now having dumped a bunch of hours into this pursuit. I am really interested if anybody else out there has dealt with this.

Just to geek this out,
198.xxx.xxx.xxx is a PUBLIC ip address, It is assigned by your internet provider and is most likely the address of your global address via your router. Only 1 person/internet connection will have this address.

192.xxx.xxx.xxx is a PRIVATE ip address. it is typically assigned by your router through NAT to give each of your internet capable devices that are connected to the router, their own address. Class c (192.xxx.xxx.xxx) is the default address by most all routers that pretty much everyone uses. Once the data leaves your router, it is tagged as the PUBLIC ip address, not the private.

The software is looking for a private ip address. There was probably something wonky about your network setup. Might have been resulted from a secondary router hooked up for use with a Ipad or something with your system.

[saptezsapte]

Mine is absolutely dead no matter what I do.