Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Nitin Sidhu]

Hello!

I have in my travel kit a nanostation Loco M2. I can get it to work just fine with most consoles, but cannot get it to connect with the soundcraft Vi3000.
On the AP, set to network bridge mode, Static ip.
The Console is also on a static ip. HqNet is enabled.

The Visi app does not auto discover the console. Nor does adding it manually get it to connect.

Ipad is also on a static IP.

I had a similar issue with the A&H D-Live, but had no time to troubleshoot.

Any advise would be welcome.

Thank you all
Sidhu

[Bryan Hargrave]

Grab any ol' cheapo wireless router and use that. If that solves your issue, get a nicer one or add something to your network that routes and use your AP for what it is, access. Soundcraft uses some porting that (I believe) requires some actual routing and not just invisible cabling. Also, Soundcraft is really picky about subnets. Make sure it is closed up to 255.255.255.0 Anything else and it goes to crap fast. Metering will be spiked at all times for input and compression. Another tip, the console lives in 192.168.1.x world. If you are also using that, try changing your third octet to something else like 192.168.2.x

Keep me posted. I'm curious as I have done A TON of troubleshooting the Vi stuff and currently have everything working. Had to change my whole network just to make it work with the ViSi app.

Hello!

I have in my travel kit a nanostation Loco M2. I can get it to work just fine with most consoles, but cannot get it to connect with the soundcraft Vi3000.
On the AP, set to network bridge mode, Static ip.
The Console is also on a static ip. HqNet is enabled.

The Visi app does not audo discover the console. Not does adding it manually get it to connect.

Ipad is also on a static IP.

I had a similar issue with the A&H D-Live, but had no time to troubleshoot.

Any advise would be welcome.

Thank you all
Sidhu

[Nitin Sidhu]

thank you Bryan!

The subnets were correct and verified. Ill try and change the number to 2 when I get the opportunity. I had access to a linksys E900 and it works just fine with that. Plug and play, DHCP.

I have been considering changing my travel router for a while now. Not too happy with the Nanostation Loco. While I was getting great coverage at distance with the Nanostation M, the loco seems very average. The M was too big to haul around in my kit. The rocket was a nice option, but I could not find a compact antenna for it here. It seems the entire range is discontinued now.

Im looking for something with good range and good portability, pref with POE. Often I find myself on stage with FOH 100+feet away, where the Wifi resides. Any suggestions would be appreciated.

Thank you again
Sidhu

[Bryan Hargrave]

No problem. I am glad I could help out. As far as recommendations for hardware, I will let some other guys on here suggest. The stuff I keep in my bag might cause some cringes.... but it works. In my world, iPad control is an afterthought but that doesn't change the fact that it should work for you.

thank you Bryan!

The subnets were correct and verified. Ill try and change the number to 2 when I get the opportunity. I had access to a linksys E900 and it works just fine with that. Plug and play, DHCP.

I have been considering changing my travel router for a while now. Not too happy with the Nanostation Loco. While I was getting great coverage at distance with the Nanostation M, the loco seems very average. The M was too big to haul around in my kit. The rocket was a nice option, but I was having issues finding a compact antenna for it here. It seems the entire range is discontinued now.

Im looking for something with good range and good portability, pref with POE. Often I find myself on stage with FOH 100+feet away, where the Wifi resides. Any suggestions would be appreciated.

Thank you again
Sidhu

[Nitin Sidhu]

N In my world, iPad control is an afterthought but that doesn't change the fact that it should work for you.

it is indeed an afterthought. I mostly do monitors from FOH, and it does help when available.
Please do feel free to share your hardware. If it works for you, then it is good for you.

[Mark Rombouts]

Ipad seem to dislike static ip is my experience.

I usually run a airport express as router and than a a strong ap to connect to. Works great almost every time.

[Scott Holtzman]

Ipad seem to dislike static ip is my experience.

I usually run a airport express as router and than a a strong ap to connect to. Works great almost every time.

Why would you need a router?  Routers connect network segments together.

I have several of my kits set for static IP and access points with no DHCP.  Never had an issue.

[Bryan Hargrave]

Maybe he has Soundcraft consoles. See above problem and solution.

Why would you need a router?  Routers connect network segments together.

I have several of my kits set for static IP and access points with no DHCP.  Never had an issue.

[Scott Holtzman]

Maybe he has Soundcraft consoles. See above problem and solution.

I don't care of it's a nuclear reactor.  IP has an RFC standard and you don't need a router on a single subnet.  The only thing it's doing is DHCP, it is not participating in the movement of data.

That means something else is wrong.  My point is we can troubleshoot this and figure it out instead of voodoo hacks.

I guarantee you that Soundcraft didn't even write the IP stack, it's a standard.

If I was given access to a computer on this network with Wireshark I would be glad to help.   I love mysteries.  If someone is willing to lab this up in the shop give me a shout.

[John Sulek]

Anything else and it goes to crap fast. Metering will be spiked at all times for input and compression.
Keep me posted. I'm curious as I have done A TON of troubleshooting the Vi stuff and currently have everything working. Had to change my whole network just to make it work with the ViSi app.

The meter spiking is a known software issue that was addressed in the latest console firmware update, both on the Vi_ and Vi_ _ _ engines.

FOH on my current tour runs the Visi app every day. We had this issue. Software update solved it.

[Nitin Sidhu]

Why would you need a router?  Routers connect network segments together.

I have several of my kits set for static IP and access points with no DHCP.  Never had an issue.

hi Scott!

That is what my limited understanding of Networking is too. Thank you for your offer of help. Ill start by taking some snapshots of the setup and post here.

Regards,
Sidhu

[Bryan Hargrave]

A couple of things caused the meter spiking. On the first update that pushed alongside the Vi1's update to v4.9 there was a bug that caused spiking and could be fixed for short periods of time by rolling back the system clocks. In terms of the subnet... Soundcraft doesn't consider that a problem and isn't going to change it. So yeah, ViSi runs fine and the meters look great after that update... unless you open up the subnet. Everything else on the network can be open, but the console and participating ipad have to be as closed up as possible. This has been my experience on 4 Si consoles and 2 Vi5000 and 1 Vi1. Also that of two other sound companies that I know using the Vi1 consoles. I can replicate that still today.

The meter spiking is a known software issue that was addressed in the latest console firmware update, both on the Vi_ and Vi_ _ _ engines.

FOH on my current tour runs the Visi app every day. We had this issue. Software update solved it.

[Bryan Hargrave]

I would actually love to troubleshoot a non router involved version of this with you. I spent about a week on the phone with Soundcraft discussing the pegged meter issue and ending up fixing it myself going back to a subnet of 255.255.255.0. Their only answers were that control is TCP/IP and metering is UDP port 333 or 3333. i cant remember off the top of my head. they even got wireshark screen caps from me. I use static addresses for all of my gear (roughly 100 addresses) and i couldn't for the life of me fix this without popping a router in there. so if you could make this work without one i would be very interested in teaming up so we should share a real result with the users that need one.

i can deploy a network that works and i think i know more than most cats but a lifetime spent in audio and production full time doesn't teach anything about advanced networking. ive been learning as i go because it is the future. luckily i enjoy the challenge and new knowledge.  i certainly don't have the experience you do with IT.

I don't care of it's a nuclear reactor.  IP has an RFC standard and you don't need a router on a single subnet.  The only thing it's doing is DHCP, it is not participating in the movement of data.

That means something else is wrong.  My point is we can troubleshoot this and figure it out instead of voodoo hacks.

I guarantee you that Soundcraft didn't even write the IP stack, it's a standard.

If I was given access to a computer on this network with Wireshark I would be glad to help.   I love mysteries.  If someone is willing to lab this up in the shop give me a shout.

[Scott Holtzman]

I would actually love to troubleshoot a non router involved version of this with you. I spent about a week on the phone with Soundcraft discussing the pegged meter issue and ending up fixing it myself going back to a subnet of 255.255.255.0. Their only answers were that control is TCP/IP and metering is UDP port 333 or 3333. i cant remember off the top of my head. they even got wireshark screen caps from me. I use static addresses for all of my gear (roughly 100 addresses) and i couldn't for the life of me fix this without popping a router in there. so if you could make this work without one i would be very interested in teaming up so we should share a real result with the users that need one.

i can deploy a network that works and i think i know more than most cats but a lifetime spent in audio and production full time doesn't teach anything about advanced networking. ive been learning as i go because it is the future. luckily i enjoy the challenge and new knowledge.  i certainly don't have the experience you do with IT.

This is a good week to do it, in town all week.

Shoot me a PM....

[Bryan Hargrave]

well, i got out the 5000 and plugged in my picostation set to AP, it all works fine. looks like i forgot how it all played out 6 months ago. like i said, ipads are an afterthought for me. must have fixed the subnet stuff too. but hey world, i sure as heck have some crazy email chains from soundcraft while we were all figuring it out at the same time.

i had too much chinese for lunch today, ill save the crow for dinner.

This is a good week to do it, in town all week.

Shoot me a PM....

[Scott Holtzman]

well, i got out the 5000 and plugged in my picostation set to AP, it all works fine. looks like i forgot how it all played out 6 months ago. like i said, ipads are an afterthought for me. must have fixed the subnet stuff too. but hey world, i sure as heck have some crazy email chains from soundcraft while we were all figuring it out at the same time.

i had too much chinese for lunch today, ill save the crow for dinner.

LoL I was actually looking forward to getting to the root cause.  Oh well, good stuff.....Carry on

[ProSoundWeb Community]