Bbachorz As i don't use a router, what you are saying is that this regular 30 second disconnection is also happening using a wifi router but thats not connected to the internet, this is very interesting, so its not just bluetooth disconnecting its also the router, i am going to do some more tests on this because when my problem went away is when i updated my software but because i was at home i was also hooked up to the internet, so perhaps i still might have an issue on stage , although my last test was at a gig all night on bluetooth without one disconnection, so things are still a bit fishy, are you on the latest operating software on everything?

I started having the same problem lately. Everything was running perfectly without any router for years (so the problem is not the ad-hoc connection), but now the connection is closed regularly.

I suspect it has to do with iOS 17.

@peter is there a way that we can do some bug tracking?

    musicadi

    @peter it appears that the connection is closed after exactly 30 seconds, so definitely a software issue.

    The weird thing is that after I get the “Connection closed” message on the slave device and tap “OK”, the song that was playing on the host is still playing on the slave even if I stop it on the host device.

    Could this be some power saving issue?

    Hi,

    I started evaluating ST3 a few days ago for my band, and so far, features wise, it matches my expectations. Just a little suggestion I will write in a dedicated thread, but anyway... thanks for the great work @peter! 🙂

    On the topic of disconnections, I agree on the need for a dedicated router. That's what we do for years with my band, and that works flawlessly for all our Wifi connected devices (for in-ear mixes control and other things), even on big venues.

    That being said, today was the first rehearsal using ST3, and we got plenty of disconnections. We were NOT using our dedicated stage router this time, only my studio router, in which to be honest I don't have a lot of trust...

    So I definitely have to run some more tests... but while writing a list of things to tests, I had an idea...

    The idea is the following: providing an option like “auto-reconnect to last session when connection drops out”

    Because what we were doing was just "closing the popup, going back to settings, and joining the session again"... if that was automated, that would just be good enough, I guess...

    What do you think?

    PS: as a developer myself, and having worked in the past on similar connected applications (multi player video games), I know it's a pain in the ***... so yeah, definitely @peter cannot do much except maybe some auto-reconnection mechanism...

    The auto-reconnect is a good idea and honestly the only option I have. Everything else is capsuled by iOS.

      peter That would be great, because it’s really annoying to get the “Connection closed” popup every 30 seconds. Maybe you could implement this as an option. I’ll file a bug report with Apple, maybe they will fix it 🙂

      @peter would it help if I provided you iPadOS logs? I would need to know which files or event names would be relevant though. I collected sysdiagnoses for both the host and the client right after the connection dropped, so I'm sure the cause is in the logs somewhere

      As far as I know the Multipeer Connectivity Framework that ST3 uses for the network functionality is not logging anything. And my experience with bug reports at Apple are really really bad. I get no feedback for months for most of my tickets. And after months they are usually closed as duplicates without any possibility to see the original ticket. A waste of time really.

        peter Oh, okay. Anyway, I reported this bug to Apple, let's see if they see it 🙂

        BTW, I remember that in earlier versions the connection was closed when the app in the host iPad was put in the background, and then you changed something, so it wouldn't close. Could this be causing the problem?

        The change was to prevent the host app from becoming inactive when running in the background. That has no implication on this problem.

        I’m having the same problem that others are having when using my two iPads at any performance. No problems when using iPads at home with WiFi. Did’nt have this problem before I updated. Is there anything I can do?

          Damir What iPad are you using? I’m on the latest (17.5.1) on iPad Pro 10.5 and still have the issue.

            musicadi Ouse iPad Pro 10.5 with headset out socket for audio, with iPad 9th gen with headset socket, and an iPhone 11 Pro Max all on 17.5.1 and latest ST3 3.8.17

            Leronyoung are you using your own router when performing or going via the venues?

            I would never use wifi from the venue. Always bring your own router!

              Damir

              I have two iPods on 17.5.1 and both on version 3.8.17. I have basically the same configuration that you have. Do I need to purchase a router? Is it possible to go back to previous version until this problem is resolved. Help. I perform a lot with these two iPads

                peter

                What external router would you recommend to solve my connection problem