ok.
Not found it as yet 
You should attend more ZynthClubs - it was demonstrated quite some time ago!
Tell me something I donât already know !
@ronsum would you mind please revisiting the OSC app and add a description on its installation, configuration and use? We did a lot of work on this but I forget if / where we documented it. Your assistance here would be much appreciated and will free me to continue working on the mixer itself. Cheers!
@ronsum Calling Ronsum!
please escort @wyleu to the battlements. . . .
Only one return ticket required !! 
Iâm very happy to hear you have returned to working on the mixer. Some tips to get the app working well with the zynmixer and other zynthian features may be helpful to those users interested in using the android app. Itâs been quite a while since Iâve used it, so Iâll need some time to research before I write something up.
2 Likes
I see the ravens have taken flight! Iâm gathering the armor now.
1 Like
This feature looks really helpful!
I need to look at modifying the HID encoder box to work with OSC⌠How does one transport this across USB, I presume it uses Urlâs but Iâm unsure how to approach that.
@jofemodo has merged the latest development of zynmixer into testing for you all to enjoy. There are some changes which you can discover but here are the most evident:
- Mixer has become the main / home screen
- Bold press âbackâ to open the main menu which allows adding layers (amongst other things)
- Short press âselectâ to access layer control view
- Bold press âselectâ to access layer context menu
- Short press âlayerâ to toggle selected channelâs mute
- Short press âlearn/shotâ to toggle selected channelâs solo (this may change in future)
- Layer control view navigation is under review but in this version:
- Short press âlearn/shotâ to access presets
- From preset view short press âlayerâ to access banks
- Short press âbackâ to return to mixer view
- Short press âlearn/shotâ to access presets
- Globally bold press âlayerâ to access sequencer
- Globally bold press âsnapshotâ to access snapshot view
This is still a work in progress and there are some significant changes happening under the hood that need to be complete before we can progress this further but it seemed like a good idea to get this snapshot of development out there so you could see direction of development, enjoy (what we believe to be) a much improved workflow and start to familiarise yourself with the future of Zynthian.
Do enjoy and let us know what you think.
6 Likes
Ups!! Mr. @riban explained it a lot better than i could.
Be warned that this is only a glimpse of what is coming on the next months 
Enjoy!!
3 Likes
For those curious enough to read the code and try to envision what is coming on, you could take a look to the zyncoderâs âz2rfâ development branch 
1 Like
This only works if you have previously selected a layer (obviously). Well, now itâs obviousâŚ
Itâs nice, but for those of us who use only one layer, it seems to add complication. Maybe itâll grow on me.
Gonzo
It will grow on you⌠. If it remains irksome, let us know and there might be something we are willing to do about it - but for now, the mixer is the hub in our future development.
(Obviously) you need to select the channel you want to access but the first channel should be selected by default and only if you select the main fader will this not open a layer. (Future development will add a main layer to allow effects to be added to the main mix.) If you find a situation where a channel is selected but does not access its configuration with short press, please let us know the steps to reproduce.
The new interface is, as @riban says something you grow into. IT really does work well once you learn to shift between the sequencer and the mixer.
I would like to see some annotation of the functionality described but quite how to implement that is a problem I leave for vociferous debate . . .
From a zynthian user perspective, we have placed a clear distinction between individual layer ( have we lost that name, I canât remember?) manipulation and device output, and it makes it (IMHO) a powerful representation of the tools on hand.
For the traditional layer based user all that functionality is easily available ( apart from parameter CUIA manipulation, but we know about that one⌠
)
I would like to note that many zynthian users doesnât use the sequencer at all and simply use zynthian as a âkeyboard expanderâ (thatâs the primary use-case) or as a âstompboxâ (thatâs the second use-case):
Please, letâs keep the focus on improving zynthian for every use-case and letâs avoid thinking that owns use-case is the only use-case. Letâs think wider !!
@gonzoB , you can be sure that the âzynthian as a keyboard expanderâ use-case will not be forgotten. Itâs my primary use too 
Enjoy!
1 Like
5 posts were split to a new topic: Merging snapshots
I had a pi with the configuration above: it was last updated the 30th of May.
I did an update through Zynthianâs UI: 158 packages and 120 00 files and folders were updated, and a bunch of software was compiled. And it tooks a while ! 
But everything went smoothly, thatâs great 
But it works using touch interface.
Otherwise, itâs just great. I really like this remixed mixer. For those who are used to play with many engines, itâs really useful to have them all presented in that way.
My current setup has no encoders, so, it would be nice if from the mixer interface (or in a given engine context menu) I would be able to assign easily a slider/pot/encoder from my midi control surface to the audio level control.
Also, what about adding for each engine a ârecâ button that would drop midi output to a new pattern in stepseq ?
VoilĂ
Thank you @riban
But right now Iâm experiencing strange behaviors with stepseq.
2 Likes
Hi @riban,
I searched the wiki but unfortunately only found the current implementation of CUIA for OSC. Do you have some data on how to access the zynmixer via OSC?
TIA, Holger
Mixer OSC control and monitoring is likely to change with implementation of full API but at the moment it works like this:
- Listens on CUIA UDP port (default 1370) for standard OSC messages (actually uses CUIA over OSC mechanism for setting values)
- OSC client automatically registers for all notifications by sending any valid OSC message
- Changes of value or state are sent to all registered OSC clients via UDP port 1370 (see address & value below)
- OSC client registration times out after 12s since last heartbeat message
- Maximum 5 simultaneous clients regsitered for notifications
- Valid OSC messages {addresses, value type} (for channel specific messages, replace â0â with fader index (0âŚ15) or 16 for main mix:
- {/mixer/fader0, float} Channel 0 fader level [0.0âŚ1.0]
- {/mixer/balance0, float} Channel 0 balance value [-1.0âŚ1.0]
- {/mixer/mute0, integer} Channel 0 mute [0|1]
- {/mixer/solo0, integer} Channel 0 solo [0|1] *Setting main solo will clear all solo
- {/mixer/mono0, integer}} Channel 0 mono/stereo [0|1]
- {/mixer/heartbeat} Null message used to keep client registration active *Send every 10s to receive notifications
- {/mixer/dpm0a, float} Channel 0 peak programme level A-leg (left) *Notification-only
- {/mixer/dpm0b, float} Channel 0 peak programme level B-leg (right) *Notification-only
- {/mixer/dpmA, float} Main peak programme level A-leg (left) *Notification-only
- {/mixer/dpmB, float} Main peak programme level B-leg (right) *Notification-only
A GUI has been implemented in DAWOSC on Android by @ronsum and myself. It has a timer which sends heartbeats every 10s and has control and monitoring of the full mixer as well as some other CUIA features. It was looking quite nice but we havenât looked at it for a while. @ronsum was going to dig out the work we did which should still be valid although I havenât tried since we merged to Testing.
2 Likes