yes, fair enough
It’s just that many DAW’s and hardware sequencers do allow to Solo midi tracks.
It’s not a crucial feature to me, so won’t create a ticket for that.
Sidenote: It would be nice to have if instead of VU meters, the MIDI tracks could blink note activity or something like that.
Related, on one occasion yesterday I had managed to have the yellow Solo enabled on my master out, with no way to undo it until after reboot. Not sure how I got in this situation
We have considered how to do similar control of MIDI but, we end up with extra controls or missing controls because some chains are MIDI only without the audio mixer controls whilst others are MIDI + audio (like synths) that need both. So how would we mute the MIDI of a synth track? One might say not to bother because we can mute the audio with similar effect but there are many other similar challenges.
This is similar to the first point. We considered it but that space is required for synth, etc. to show audio so the MIDI activity would conflict… howerver I have implemented per-chain MIDI activity in tha legend strip at the bottom of the screen. There are 5 normally hidden indicators: 4 yellow for pedals and 1 blue for MIDI activity.
This shouldn’t happen. Can you say what git commit you were on for zynthian-ui? I changed the solo behaviour recently. The main mixchain solo indicator should show the global solo state, i.e. yellow if any chain is solo and grey if no chains are solo. Pressing it should clear all solo. It is plausible there is an edge case where it can get stuck but it would be good to be sure you were on a version with the latest solo changes before I investigate.
Oh dear! It is implemented… It relies on a patched jalv. I wonder if that hasn’t been updated? I will have a look later. Please check the jalv version with jalv -V.
There is a gui layout issue on lower resolutions screens. In mixer / launcher view there should be a display of time signature and tempo:
The tempo is in beats per minute with 0.1 beat resolution (which is the resolution we allow changes).
The time signature is actually the beats per bar. We always use quaternotes for this definition so not a real time signature, but the x/4 notation is easy to comprehend and gives us a good clue that it refers to time signature.
Before the time signature there is a vertial line separator and the current beat counter. This counts from 1 to the beats per bar, so a 3/4 time signature would see this counting 1, 2, 3, 1… whilst the transport is running, e.g. when a sequence is playing.
The beat counter is obscured on lower resolutions screens (as reported here) which I hope to fix later. (I see this issue with my V3.)
I was reminded that we want to review the handling of transport, time, tempo, etc. It may be advantageous to separate the transport from the sequencer but that is quite a big task with lots of detail to consider, so I don’t want to bog down this thread with that discussion. When we start working on that we may garner opinion if we need it.
No disrespect about the job that you and others are doing for zynthian
But as I told in another post , I am nearly 70 years old and it becomes difficult to learn new things
Anyway
What I do not like in Vangelis (the OS not the Genius Composer):
I rather tell what I like in Oram OS
I like the choice of colors for ZynPAD and having a dedicated screen for that sort of Ableton Live or Bitwig feeling , that I do not feel with Vangelis OS
One of my Fav synth Dexed does not work..
The session mode on my LaunchPad Mini MK3 shows nothing when I add some chains
(unless I do not know how to use it)
The global switching between menus , screens , preset is for me much slower.
So back to Oram Stable.
Anyway No problem with other users thinking it is good for them
ZynPAD colours were carefully crafted so you are right to prefer them. However, they don’t align well with the LED colours available on Novation and Akai hardware panels, hence the change. I would love to see a theme mechanism introduced to allow users to select their own colour themes, but that is unlikely to hit the next release. Of course, we do get used to change so maybe these new colours may grow on us. (I am still trying to convince @jofe of their benefit!!!)
ZynPAD differs from the launcher view in Vangelis in a few ways. It is a fixed, square grid with a maximum of 8x8 pads. It is not scrollable. The pads fill the screen so are larger. You don’t have the mixer control / indications in zynpad. There is higher contrast in the header bar of each launcher. (I have suggested reintroducing this.) Each launcher has its own progress bar. There is free allocation of launchers to pads. The benefits are often also weaknesses like the flexibility of sequence assignment can lead to confusion. The option for multiple tracks and patterns has confused many. We decided to add some constraints to allow us to deliver the improvements - but of course that means some workflows are disadvantaged. (Arranger is currently not available.) I have already added a feature request about having a zynpad-like view. You may want to add some comment to that.
Dexed should work. Indeed it is the engine I have loaded on my V3 right now. There is a bug that I am trying to fix that does not complete the process of adding a processor (also done when adding a chain). Maybe that is causing the issue. We will definitely fix Dexed before releasing Vangelis. It is a firm favourite here.
@jofemodo is working hard at resolving hardware controller integration. We made substantial changes to the code in this area and are slowly resolving those issues. We should have all the hardware controllers working as well as they did in Oram before release.
View navigation is still a work in progress. This needs some more attention. I put in some new workflows but they are not yet refined. (For example, V4 users can’t currently (easily) access audio levels view. (I hope to resolve that later today.) Done!) It would be useful to hear some more detail about what elements of navigation are challenging.
Of course, Oram is the stable version that we are all encouraged to use for our day-to-day (production) use. Vangelis is in effect a technology preview (which we like to share early) and indicative of the next major release, hence we invite users to try it and to help us test and iron our these foibles. I appreciate everyone who takes the time to give detailed feedback. We learn more from criticism than we do from praise. (But a little praise is always welcome!)
That’s strange, my Mini MK3 seems to work with no problems. Instead, i confirm that when i try to load Dexed everything get stuck in the Adding Processor screen, and i have to do a brutal reboot.
Can you grab some logs? You can use webconf: INTERFACE->UI Log to monitor progress and copy and paste it here. If there is no useful log, you could try using the SHOW DEBUG LOGGING option and repeat the test. I am not having an issue loading dexed so your assistance will be most helpful.
Previously (in Oram) you had access to some parameters from the mixer (fader, solo, mute, balance) and some from the mixer options menu (mono, phase reverse, M+S) and some from the audio output menu (record). Now all of these are accessible from the control view (processor parameter adjust) whilst still retaining solo, mute and fader in the mixer view. All are MIDI learnable from the control view. I don’t see what the regression is here. I think it is easier to acces these parameters than it was before.
Will you please check if /zynthian/zynthian-plugins/lv2/dexed.lv2/Dexed.ttl exists and if so, paste a copy here. It exists on all of my machines, including the V3 that is an Oram image->Vangelis update machine, similar to yours (unless there has been a new oram image in the past couple of weeks.).
[Edit] There hasn’t. I am using 2025-11-05 oram updated to Vangelis.
[Edit] Sorry - I have reproduced this. It seems to be a bad edit to the ttl aimed at supporting the new filter gui widget. We should fix this shortly.
What a great work ! Congratulations ! I am waiting possibility to record clips… Wait.
Don’t know i it is a normal behaviour (i DI not bélière), but when you create a synth chain, the clips are named and linked to the midi channel input. But if i create 2 or more chain synth with the same midi input, the clips are the same on each chain… They should be new clips not linked to the midi channel.
