Great, thank you very much! I will try to get something done with TouchOSC. Let’s see how far I get.
Where can I find your DAWOSC interface?
I just remembered we put it in GitHub.
2 Likes
I just changed to the Testing branch and tried out the mixer with DAWOSC. There was some strange behavior with the faders. Moving the faders on the Zynthian would move the DAWOSC faders, but moving the faders in DAWOSC didn’t move the faders on the Zynthian. The solo, mute and pan controls worked fine in both directions. I need to go back and take a look at the DAWOSC mixer layer to see if the faders are setup correctly. For those who haven’t seen the mixer layout on DAWOSC, here’s what it looks like:
I’ll report back after further testing.
3 Likes
oh wow… this makes me to immediately want the zynmixer itself to be 8 lanes wide with funky dials and sliders. i know why it isn’t, i see the logic, but then i saw this.
The native Zynthian GUI shows a different quantity of mixer channel strips depending on screen resolution. On a standard unit you should see 8 channels plus main mix.
Hi @riban ,
In the thread about API proposal, for the mixer you said:
Multiple channels of audio mixed to a main stereo mix-bus
For those lucky who own a multichannel IN/OUT. USB sondcard, I think having the ability to have different mixes on the different outputs would be great.
2 Likes
Hi @riban Brian,
I started some tests with TouchOSC (the new version) but until now nothing happens. Just to be sure:
-
TouchOSC-Bridgeneeds to be enabled inAdminmenu? - The OSC path for the master fader should be
/mixer/fader16and NOT/cuia/mixer/fader16(because you mentioned CUIA above)? - I got a script running on TouchOSC which sends a heartbeat to
/mixer/heartbeat.
I tried to send a float (0.0 … 1.0) as you wrote… but I am not sure if this is currently a problem of zynmixer or of my current knowledge of the new TouchOSC…
Regards, Holger
I am not sure about TouchOSC-Bridge. I’m not sure if this is relevant.
OSC path is /mixer/fader16, not /cuia… but as observed by @ronsum, the faders are not currently working. Everything else seems to be. I am looking at the code now. You can try mute to test if your config is working.
[Edit] The path was changed to /mixer/volume by @jofemodo in commit 92abbc98caafc2ccceaddfe9a4ae626b166e9a81 on 28th October. The commit comment doesn’t explain the change so I don’t know the reason it was done. I have changed it back to /mixer/fader in Testing branch to fix interface between @ronsum’s DAWOSC layout. @jofemodo we can discuss if this should change but we may be moving everything anyway.
@ronsum some of the navigation is no longer valid in there but maybe we should reconsider the interface in light of recent changes. Maybe DAWOSC isn’t the best options and we could implement our own app. (I have something for Android I was working on for Ardour that we could use as a starter but I don’t have any experience nor tools to develop for Apple devices.)
1 Like
I agree, there are probably better options than DAWOSC. It does look nice, but I’m sure you remember, it’s not open and no longer supported. I’ll look to see what else is currently available. If I come across anything interesting, I’ll let you know.
Open Stage Control is looking promising.
There’s GitHub - jean-emmanuel/open-stage-control: Libre and modular OSC / MIDI controller. But it’s all JavaScript.
A server (Node app) wich could be headless communicate wirh clients in Osc or Midi.
They provide an editor for building cross platform frontend app based on Electron (The Chromium base JavaScript framework) using widgets in HTML5 and css.
It feels like we are looking for a solution to an undefined problem! The implementation of OSC within the mixer was to allow remote control, e.g. via a tablet which may be advantageous for a mix engineer of using Zynthian as a stage mixer. That is one of my workflows. The use of an Android or iOS app with some configuration seemed like a good way to allow custom interfaces to be built on a wide range of tablets and phones. Maybe a less configurable solution would be to extend the native Zynthian display, e.g. via VNC which of course is already available.
I think I may be too tired to be thinking straight about this! TFB.
Many thanks!
I managed to switch the master mute button (/mixer/mute16) from TouchOSC->Zynthian, but only one way.
After an update of Zynthian (testing) I tried also the master fader as /mixer/fader16 and /mixer/volume16 but without success. I hope I will find some time to enable or add some debugging to see what the problem is.
Regards, Holger
Oops! My bad! I committed to the wrong branch. Try now!
1 Like
Updated and then tested with DAWOSC. The faders are working correctly now.
Yep! Works currently oneway (TouchOSC->Zynthian).
I will try to build a TouchOSC-ZynMix Template.
Thanks again @riban!
Hi Brian @riban,
I am nearly ready with my TouchOSC interface for the ZynMixer. I have some small problems, especially with the export of the TouchOSC file from my tablet (app crashes, issue report sent to hexler).
But the communication is one-way only from TouchOSC to Zynthian. I checked this with tcpdump on my Zynthian: when I move a fader or press solo/mute on my Zynthian no packets are sent to TouchOSC.
I am not sure if two-way communication for OSC is already implemented yet?
Regards, Holger
Hi @C0d3man
Notifications are implemented but only for clients that are registered. This requires a client sending /mixer/hearbeat or /dawosc/hearbeat every 10 seconds.
Yep, I am doing this (I think). Will double check this and come back.
Got it!
I had a typo in the path of the heartbeat… works fine now!!!
I will upload the project when export of TouchOSC works.