companion-module-behringer-x32
companion-module-behringer-x32 copied to clipboard
bitfocus
X32 X-Live Card Controls
It would be nice to be able to control the x-Live Card options and function from Companion. Like start recording 32-in/32-out to SD card 1, and Stop recording. can be found in the setup -> card menu of the x32-edit.
Also being able to "press" buttons in the Sets A, B, and C. which can be found in the Assign menu in the X32-Edit program.
The x-live functionality will be tricky to implement as I do not have that card to test with. I shall see if there is sufficient documentation to work from.
The assign buttons should be easy to do when I have a chance
I don’t mind testing, but I only have the opportunity on Tuesdays and Thursdays.
Here is a screenshot of the SD-card control in the x32-edit software.
I'd love this functionality too! We use an x-live card as a back-up recorder. If there's anything we can do to help by testing etc please let me know. Thanks in advance!
I found some documentation that gives OSC information on the X-live cards. https://wiki.munichmakerlab.de/images/1/17/UNOFFICIAL_X32_OSC_REMOTE_PROTOCOL_%281%29.pdf (starting with "/-prefs/card" on page 51). Hope this helps.
Thanks so much for this! I actually stumbled upon this myself too and indeed, it does seem to document the x-live OSC material so hopefully that can be easily worked with! Thanks again! ~N
-- NICK RUTTER • Arts Photographer ––– m. (+44) 07944 005 627 ––– w. www.nickrutter.co.uk ––– t. twitter.com/nick_rutter
On Sun, 9 May 2021 at 15:50, MarauderSeeker @.***> wrote:
I found some documentation that gives OSC information on the X-live cards. https://wiki.munichmakerlab.de/images/1/17/UNOFFICIAL_X32_OSC_REMOTE_PROTOCOL_%281%29.pdf (starting with /-prefs/card on page 51). Hope this helps.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-behringer-x32/issues/20#issuecomment-835821765, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJDUNV2GCX7ST25ONIYGB3TM2OM7ANCNFSM4OWFPZ3Q .
@nick-rutter, if you haven't got this to work yet, here is what I done. Setup generic OSC, make a button and do osc: Send Integer; you would want to send /-stat/urec/state with value of 3 to record, value of 0 to stop.
When setting up the OSC, do you x32 IP address and Target Port setup to 10023.
Hope that this helps!
Hi there,
Thanks so much for sending this along - I eventually discovered that I could do exactly this and have been doing so with great success, thank you for taking the time to reach out!
All the best & many thanks, Nick
-- NICK RUTTER • Arts Photographer ––– m. (+44) 07944 005 627 ––– w. www.nickrutter.co.uk ––– t. twitter.com/nick_rutter
On Wed, 18 May 2022 at 20:18, jakebradley2001 @.***> wrote:
@nick-rutter https://github.com/nick-rutter, if you haven't got this to work yet, here is what I done. Setup generic OSC, make a button and do osc: Send Integer; you would want to send /-stat/urec/state with value of 3 to record, value of 0 to stop.
When setting up the OSC, do you x32 IP address and Target Port setup to 10023.
Hope that this helps!
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-behringer-x32/issues/20#issuecomment-1130412308, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJDUNX4F35IOVMEDCN6Z7DVKU7A7ANCNFSM4OWFPZ3Q . You are receiving this because you were mentioned.Message ID: @.***>
Question for both @jakebradley2001 & @nick-rutter -- how would one set a marker using companion?
I found the OSC command /-action/addmarker in both https://github.com/pmaillot/X32-Behringer/blob/master/X32PrefStat.h & https://tostibroeders.nl/wp-content/uploads/2020/02/X32-OSC.pdf -- but couldn't get it to work unfortunately. Any ideas?
I haven't done this myself but I'd imagine you use the GenericOSC instance/connection in Companion, which is aimed at the X32's IP and on the correct port (whichever it is that the X32 uses to listen for OSC commands).
Then just build a button in Companion that sends the custom OSC /-action/addmarker as a string or possibly 'without arguments' and see what you get.
I haven't done this myself but I'd imagine you use the GenericOSC instance/connection in Companion, which is aimed at the X32's IP and on the correct port (whichever it is that the X32 uses to listen for OSC commands).
Then just build a button in Companion that sends the custom OSC /-action/addmarker as a string or possibly 'without arguments' and see what you get.
Do you still have access the X32 Rack? If you would be able to check I'd be very grateful.
I tried almost every combination of commands, updated the X-Live card's firmware ... to no avail. Just wanting to check if someone else would be able to succeed in adding markers while recording.
Well, after testing with X32_Command (which worked fine), I now have the possibility to add markers.
Sending /-action/addmarker with a value of 1 works great now.
If only I could get the recording state back as feedback (which is not possible with Generic OSC), then my workflow would be complete.
Ah good stuff, glad to hear you've gotten that working, I'll be making a note of how to add markers myself as it was also on my to-do list.
As for the feedback based on the x-live card, yes - that's also something I'd really like to have. Until Companion adds a Generic OSC listener module, I don't think it's possible. You may be able to achieve it via an intermediary piece of OSC software which allows you to receive OSC info and then trigger actions (i.e. you could send OSC commands to Companion to change a custom variable, e.g. X32-xlive-status with a value of 'recording' or 'stopped' or whatever.
This is great news! Definitely going to be using this. Sent from my iPhoneOn Sep 3, 2022, at 10:14 AM, Taapo @.***> wrote: Well, after testing with X32_Command (which worked fine), I know have the possibility to add markers. Sending /-action/addmarker with a value of 1 works great now. If only I could get the recording state back as feedback (which is not possible with Generic OSC), then my workflow would be complete.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>