ProppFrexx in combination with D&R Webstation, don't communicate
-
- Posts: 13
- Joined: 25 Sep 2021 17:43
ProppFrexx in combination with D&R Webstation, don't communicate
Hi!
Recently i bought the D&R Webstation to use it with ProppFrexx Onair. I had installed everything like Benjamin Hartwich said in his video https://www.youtube.com/watch?v=IfZiGkI8Nj8. Everything is working fine: ProppFrexx is playing songs and on the GPIO Client monitor i see that the mixing console is communicating with the GPIO Client.
However: there's one problem. The GPIO-client is not communicating with ProppFrexx Onair.
On the Main Tab the connection is connected (tcpex://127.0.0.1:4767/ProppFrexxRemoteService) and also the D&R Mixer is connected (127.0.0.1 / Receive: 18152 / Send: 18153). In ProppFrexx Onair the GPIO Extension Service is also on for port 4767. And the same password is used on both Onair en GPIO-client.
What is wrong with the settings?
What i've tried:
- Shut down the Firewall
- Used other ports for instance the manual port 9042 --> Gives no connection
- Checked of there was a problem with the commands in the mapper of the GPIO-client, it was all fine, because i filled in the same parameters in the keyboard mapping and there everything worked fine.
I hope you could help me out with the problem, maybe you had the same issue? Let me know, thankyou in advance!
Recently i bought the D&R Webstation to use it with ProppFrexx Onair. I had installed everything like Benjamin Hartwich said in his video https://www.youtube.com/watch?v=IfZiGkI8Nj8. Everything is working fine: ProppFrexx is playing songs and on the GPIO Client monitor i see that the mixing console is communicating with the GPIO Client.
However: there's one problem. The GPIO-client is not communicating with ProppFrexx Onair.
On the Main Tab the connection is connected (tcpex://127.0.0.1:4767/ProppFrexxRemoteService) and also the D&R Mixer is connected (127.0.0.1 / Receive: 18152 / Send: 18153). In ProppFrexx Onair the GPIO Extension Service is also on for port 4767. And the same password is used on both Onair en GPIO-client.
What is wrong with the settings?
What i've tried:
- Shut down the Firewall
- Used other ports for instance the manual port 9042 --> Gives no connection
- Checked of there was a problem with the commands in the mapper of the GPIO-client, it was all fine, because i filled in the same parameters in the keyboard mapping and there everything worked fine.
I hope you could help me out with the problem, maybe you had the same issue? Let me know, thankyou in advance!
Re: ProppFrexx in combination with D&R Webstation, don't communicate
test performed via 'monitor' ?
correct sound settings windows?
-
- Posts: 13
- Joined: 25 Sep 2021 17:43
Re: ProppFrexx in combination with D&R Webstation, don't communicate
and does GPIO also start up together with Proppfrexx? I have an Airlite and I didn't get it working in the beginning, but in the end it worked. I don't know if there is a difference between an Airlite and Webstation.
-
- Posts: 13
- Joined: 25 Sep 2021 17:43
Re: ProppFrexx in combination with D&R Webstation, don't communicate
No thats the strange thing.. I have to open the GPIO client manual. Normally it would start when i start ProppFrexx right? How did you fix it?? I think the consoles are quite the same.
Re: ProppFrexx in combination with D&R Webstation, don't communicate
Try the real IP address in your connection address (e.g. not tcpex://127.0.0.1:4767/ProppFrexxRemoteService; but instead of 127.0.0.1 use the real IP address) - or just empty that field, as then it should auto discover the correct address.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
-
- Posts: 13
- Joined: 25 Sep 2021 17:43
Re: ProppFrexx in combination with D&R Webstation, don't communicate
Used my own IP Adress instead, no connection. Filled in nothing, main tab says connected, but no output at ProppFrexx Onair
Re: ProppFrexx in combination with D&R Webstation, don't communicate
Is the GPIO Ext. Service enabled in ProppFrexx ONAIR?
And does the main screen of the GPIO client says it is connected?
And make sure you use the correct port, default is 9042.
Please send a screenshot from ProppFrexx GPIO settings as well as the main screen of the GPIO client.
If yes, please enable temp. the Debug logging and send me the debug .log file generates (or check yourself, if you can spot anything).
Note, you can enable it for both: ProppFrexx and the GPIO client.
The logs can be found in the AppUserData folders of each… eg. %appdata%\radio42\…
And does the main screen of the GPIO client says it is connected?
And make sure you use the correct port, default is 9042.
Please send a screenshot from ProppFrexx GPIO settings as well as the main screen of the GPIO client.
If yes, please enable temp. the Debug logging and send me the debug .log file generates (or check yourself, if you can spot anything).
Note, you can enable it for both: ProppFrexx and the GPIO client.
The logs can be found in the AppUserData folders of each… eg. %appdata%\radio42\…
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: ProppFrexx in combination with D&R Webstation, don't communicate
you wrote that my audio settings are the same as yours. check the following: connect an analog sound source to your webstation and check in your audio settings (windows) which input it is visible on, called PROG by me (see earlier picture). This PROG must be selected in Proppfrexx under Input Devices. Finally, despite turning off the firewall, set it up again.
- Attachments
-
- PF_prog.JPG (31.17 KiB) Viewed 2813 times
-
- Posts: 13
- Joined: 25 Sep 2021 17:43
Re: ProppFrexx in combination with D&R Webstation, don't communicate
Hi!radio42 wrote: ↑26 Sep 2021 00:09 Is the GPIO Ext. Service enabled in ProppFrexx ONAIR?
And does the main screen of the GPIO client says it is connected?
And make sure you use the correct port, default is 9042.
Please send a screenshot from ProppFrexx GPIO settings as well as the main screen of the GPIO client.
If yes, please enable temp. the Debug logging and send me the debug .log file generates (or check yourself, if you can spot anything).
Note, you can enable it for both: ProppFrexx and the GPIO client.
The logs can be found in the AppUserData folders of each… eg. %appdata%\radio42\…
Here you can see my settings. Also the log of the GPIO Client.
and the code:
Code: Select all
25-9-2021 16:36:42: GPIO Debug Log started. v4.2.6.3
25-9-2021 16:36:44: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:44: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:45: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:45: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:45: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:45: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:46: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:46: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:49: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:49: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:49: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:49: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:50: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:50: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:51: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:53: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:53: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:55: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:55: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:56: AirliteCallback: Type=EVENT, ID=STATE_TRACK
25-9-2021 16:36:56: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:36:57: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:36:57: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:57: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:36:58: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:58: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:36:58: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:58: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:36:59: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:36:59: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:36:59: AirliteCallback: Type=EVENT, ID=STATE_TRACK
25-9-2021 16:36:59: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:00: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:37:00: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:00: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_A
25-9-2021 16:37:00: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:00: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:01: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_A
25-9-2021 16:37:01: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:01: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_A
25-9-2021 16:37:01: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:01: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_A
25-9-2021 16:37:01: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:01: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:15: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:15: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_A
25-9-2021 16:37:15: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:15: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:17: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:17: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_A
25-9-2021 16:37:17: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:17: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:17: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:17: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_A
25-9-2021 16:37:17: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:17: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:18: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:18: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_A
25-9-2021 16:37:18: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:18: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:20: AirliteCallback: Type=EVENT, ID=STATE_FADER
25-9-2021 16:37:21: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:21: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_B
25-9-2021 16:37:21: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:21: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:37:22: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:22: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_B
25-9-2021 16:37:22: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:22: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:37:22: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:22: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_PLAY_B
25-9-2021 16:37:22: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.
25-9-2021 16:37:22: AirliteCallback: Type=EVENT, ID=STATE_ON
25-9-2021 16:37:23: AirliteCallback: Type=EVENT, ID=STATE_MODULE
25-9-2021 16:37:23: DispatchCommand: EXEC_COMMAND2 ${autoplay}|Equals(0)|PLS_CURRENT_EJECTNOFADE_B
25-9-2021 16:37:23: DispatchCommand Reply: ERROR: De objectverwijzing is niet op een exemplaar van een object ingesteld.