Remote-App and more: Some Bugs on my workflow

The new Daslight - for PC and Mac

Moderators: TomHat, simonB

kad-energy
Posts: 17
Joined: Wed Feb 03, 2016 10:14 am

Remote-App and more: Some Bugs on my workflow

Post by kad-energy »

Hello Dear Daslight-Team,
thank you for real update the Daslight5 compatiblety with Apple BigSur.
1. Remote-App
By using a MacBook Pro (Big Sur) and an iPad 10 (newest iOs) the pages on Daslight Remote are correct shown.
By using a MacBook Pro M2 (15.1.1 Sequoia) and an iPad 10 (newest iOs) the Daslight5 Software is found by the Remote App on
iPad but the pages are not shown.
2. Remote-App:
Whenever I put a fader-Button on ipad in the Remote app till zero - the fader jumps automatically
to a high level.
3. Outputs Daslight Gold Interface (DVC5):
I read past in the forum that there is a possibility to use Output 3 und 4 paralell with Output 1 and 2 to
control Universe 1 and 2 without any upgrades.
I used the Hardware Manager and newest firmware 4.08 is installed. Unfortunatly Output 3 and 4
are grey and could not be used.

Tanks
JohnNicolaudie
Posts: 48
Joined: Tue Sep 13, 2022 4:43 pm

Re: Remote-App and more: Some Bugs on my workflow

Post by JohnNicolaudie »

1. We have this same set-up and it works OK, so it may be that something is blocking your connection. Try going to System Settings -> Privacy & Security -> Local Network, and look at the setting for Daslight 5. If it is already on, turn it off and back on again. Try also disabling the firewall if it is enabled.

2. This is a known issue that has been fixed. It is currently being tested and should be released soon.
willm
Posts: 651
Joined: Wed Jun 08, 2022 3:19 pm

Re: Remote-App and more: Some Bugs on my workflow

Post by willm »

Hello,

Following up on your 3rd point - it is expected that the outputs 3 and 4 should appear greyed out, but they should also show the correct universe assignments (Universe 1 for port 3 and Universe 2 for port 4). You should notice that if you change the Universe assignment for Port 1 or 2, this will update the port 3/4 assignments accordingly also, and all 4 ports should be outputting DMX as expected.

Could you please confirm whether DMX is outputting correctly on ports 3 and 4, or not? Port 3 should mirror the exact same values as port 1 and port 4 should mirror the exact same values as port 2.

Kind regards,
Will
brendantwhite
Posts: 3
Joined: Sat Dec 07, 2024 11:02 am
Operating System: Mac OS X
Location: Adelaide, Australia

Re: Remote-App and more: Some Bugs on my workflow

Post by brendantwhite »

JohnNicolaudie wrote: Tue Dec 10, 2024 9:40 am 1. We have this same set-up and it works OK, so it may be that something is blocking your connection. Try going to System Settings -> Privacy & Security -> Local Network, and look at the setting for Daslight 5. If it is already on, turn it off and back on again. Try also disabling the firewall if it is enabled.
If I have the firewall enabled on my Mac, then I can't use Daslight Remote on my iPhone. It finds my Software Instance, but it can't see any of the pages.

What I want to do is leave the firewall on, but set Daslight 5 to "Allow Incoming Connections" in the firewall options. But that doesn't work - it still connects fine to the Software instance, but still can't find any pages.

If I turn off the firewall completely then it's fine, and Daslight Remote works perfectly on my iPhone. But I'd really prefer not to turn the firewall off completely, for security reasons.

Would it be possible to get Daslight 5 on the Mac to work with Daslight Remote on iPhone, with the firewall turned on, but with Daslight 5 set to "Allow Incoming Connections"?
I use Daslight for plays, not live music
JohnNicolaudie
Posts: 48
Joined: Tue Sep 13, 2022 4:43 pm

Re: Remote-App and more: Some Bugs on my workflow

Post by JohnNicolaudie »

So clearly Daslight Remote is working, but your firewall is blocking it when enabled. The fact that it can find the Daslight 5 instance but not connect implies that UDP packets are getting through (i.e. the discovery part), but that inbound TCP connections are being blocked. See if you can manually allow inbound TCP connections to port 2431. This may allow the Remote connection.
Post Reply