For about a week now, I’ve had the problem that my OSC connection only works in the direction of TouchOSC. That means, for example, that I can move the fader in Gig Performer and the fader changes accordingly in TouchOSC. Conversely, if I move the fader in TouchOSC, it no longer moves in Gig Performer.
This has worked without problems before, and without consciously changing anything, it suddenly no longer works.
I did an update of the macOS, but the problem was already there before.
With the protocol app in macOS (Where is Gig Performer running), I can see that data is arriving:
What I see is that in the upper picture (macos) the system is receiving apparently on ipv6 while GP is using ipv4. It could be that Mac always blend the two ip stacks this way, but in the linux/Windows network world I would have had to do quite some effort to make that work, so it doesn’t seem common to me (but I’m a network guy. Hardly a macos guy)
Maybe you can disable ipv6 on the Windows device to stop it from using ipv6 (assuming you want the Windows device controlling GP on the Mac device)
I just wanted to know that, so I could interpret the output of Protokol better. But you’re right: you seem to address 192.168.178.77 (ipv4), but Protokol reports it comes from ffff:192.168.178.46, which looks as an ipv6 to me.
I suggest you look into the ipv4/ipv6 issue. I guess that’s the problem.
Ah, okay… I didn’t know that. Yes, the windows system control GP on the Mac.
I will try to dissable ipv6 this evening.
Directly when I am back from work
That’s the right way to go with IPv4 and IPv6. I checked again what is coming in on macOS. IPv4 data is also coming in. I had accidentally set the protocol app to IPv6. But the IPv4 data did not arrive at Gig Performer. So that had to be the problem.
In the network settings in macOS, I then set the IPv6 configuration of the WLAN Connection to “manual” and/or “link local only”. After that, everything worked. Even when I set the configuration back to “automatic”. It’s a workaround, but it works for now.
It was probably something in the Gig Performer file…
The “workaround” didn’t last long …
I then created a new file, inserted a test OSC fader and it worked without any problems. I don’t know why I only came up with the idea now
An older version (early February, thanks Timemachine) of my main Gig Performer file also worked.
I then deleted all songs and rackspaces from a copy of my current file (which also had the problems). All rackspaces really had to be deleted. Even the older ones before the problems. And everything worked.
So I exported all the songs from my current file and imported them into the copy in which I had previously deleted everything. Problem solved.
Now everything is fine. I didn’t change anything in the songs and rackspaces.
Had also tried to export all songs to a new gig file (setlist mode) before. Didn’t work either.
I hope I have described it clearly
Learned once again: save files regularly as a „time backup“
If you have found out anything, please let me know. It’s not working again. I haven’t actually changed anything at all… …
On Friday everything was fine. I just start today and it doesn’t work.
Again, with a new gig File everything is fine…
So you’re saying that in the exact same scenario, it worked 3 days ago — nothing changed and then when you did exactly the same thing today, it didn’t work?
Yes… The only thing on Friday was that I saved the File…
I made some Rackspaces and Songs on Friday. Everything works fine during this. I saved the Gig File and shut down everything.
Today I opened the Gig File and it didn’t work.
Maybe something happened during “save progress?”
There’s nothing relevant in the gig file. How about your computer? Was it connected to a different network? Do you have a firewall running? Did you give GP full network permissions?
It is the same network and I have no firewall running … I will double check the permissions…
The crazy thing is, when I make a new gig file and I use the same OSC parameter in an example Fader everything works fine.
Like on Friday with my main gig file
But the IPv4 data did not arrive at Gig Performer. So that had to be the problem.
