Pau, I’ve not tested at 96KHz, but it probably works at 256 buffer size, that gives the same latency that 48KHz and 128 buffer size.
Anyway, 96KHz is overkill for live performance. 48KHz is more than enough, specially with 128 buffer size, that gives 5ms latency.
Regards
Hello! I am using the latest version available together with an akai APC key25 (thanks @oscaracena ) but for a few days now I have been experiencing an error, and that is that I cannot program new beats from the akai… I can add them from the zynthian screen through ‘Pattern’ and then delete them from the MIDI device, but I can’t assign new ones. I have tried restarting and updating but there is no way… I don’t know if it is a bug or if I am doing something wrong.
Let me review this and answer you. Just need a bit of spare time 
My experience if it coulkd be useful for user and developers.
With my audio hat (HifiDAC NXEZ) I have to fix the istallation parameters when I install 2405 of May 22;
I’ve tested quickly oram-2405:
Setup is a Pi4b, 5inch DSI display, Pi headphones, no hardware controls
That’s enough for today 
Cheers
Zynthian treats all plugins similarly. You can have presets for effects, e.g. a reverb may have presets like Hall, Cathedral, etc.
I was debugging this case, maybe this log will be helpful:
ERROR:zynthian_state_manager.zynmidi_read: this function takes at least 5 arguments (4 given)
Traceback (most recent call last):
File “/zynthian/zynthian-ui/zyngine/zynthian_state_manager.py”, line 676, in zynmidi_read
if self.ctrldev_manager.midi_event(izmip, ev):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/zynthian/zynthian-ui/zyngine/zynthian_ctrldev_manager.py”, line 175, in midi_event
return self.drivers[idev].midi_event(ev)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_akai_apc_key25_mk2.py”, line 234, in midi_event
if self._on_midi_event(ev):
^^^^^^^^^^^^^^^^^^^^^^^
File “/zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_akai_apc_key25_mk2.py”, line 335, in _on_midi_event
return self._current_handler.note_off(note, self._is_shifted)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_akai_apc_key25_mk2.py”, line 1904, in note_off
self._toggle_step(self._pads.index(note))
File “/zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_akai_apc_key25_mk2.py”, line 2224, in _toggle_step
self._libseq.addNote(
TypeError: this function takes at least 5 arguments (4 given)
I have started testing the latest image with updates, and I am having an issue with MIDI and chains - the chain receives notes on the specified MIDI input, but ignores the selected channel.
My chain is has LinuxSampler set to take input from a USB MIDI interface (ESU M4U 1).
MIDI channel is set to 01.
This works OK.
If I change the output channel on my keyboard to channel 02, I would expect that the chain would not play. However, it does, and no matter what channel I set the keyboard to send on, the chain still plays.
Am I missing something?
If you haven’t updated for a while then you might have missed the updates to midi input. You can read the user guide for V4 and then the update for the testing version has a bit more info:
https://wiki.zynthian.org/index.php/Zynthian_UI_User_Guide_-_V1/V4#MIDI_input
https://wiki.zynthian.org/index.php/Oram_TESTING_Zynthian_UI_Users_Guide#Midi_Input
Cheers. Once I turned off Active and enabled MultiTimbral on the interface, I am getting the expected behaviour.
It would be great if everything just worked he we want our expect (intuitively), then we wouldn’t need instructional guides. Zynthian is very flexible with some really useful configuration so can work in various ways. This is one that can catch people out and, like you, I initially struggled with this concept of Active Mode (previously called, Stage Mode) but it provides a very useful workflow that, since recent modifications that allow a mix of modes, I find really good.
I sometimes wonder if we should have a sticky topic at the top of the forum or an welcome message sent to new users that recommends reading the guides on the wiki before asking questions. I know it can be a bore to RTFM but a lot of effort has gone into writing them and they are pretty… Fine! 
Have you considered contextual tooltips inside Zynth UI? This space on the right looks like as good a place as any. It’s another thing to maintain I guess but it could help from having to search the manual. A description for less obvious things rather than everything could be effective and not too burdensome.
Another idea…a UI splash page for new users. It just has some basic info about network connections, midi, configuration settings to consider on first setup. etc. It can show up on every boot until it’s told to go away.
A bit like this you mean?
We already show info when adding a plugin. We could expand this to provide more context help. It would need to be relevant and avoid crowding the interface. We don’t want text that provides little benefit and can make the UI less clear.
I am not a fan of popup help windows (tips) as they invariably give me a sense that I should probably read them but don’t want to right now and hence have a weight of guilt about disabling them. They are also reminiscent of the infamous Microsoft Clippy! 
I have considered some sort of demonstration / learning mode but it is a substantial undertaking and our experience is that the fast and dynamic development of Zynthian results in documentation becoming out of date quite quickly. (We try to resolve this promptly but we have limited effort.) So, in-program help, wizards, etc. could be too much effort to maintain.
[Edit] We could have, only on first boot, the option to partake in a core-learning exercise. After first boot the Zynthian could offer (and strongly recommend to new users) to show some core principles. This could be a simple Yes / No option and not shown again. It could explain the use of short, bold and long press for example which is a navigation mechanism that users really need to understand from the start of their journey. It could also be launched from an admin menu entry. It could also point users at the wiki / forum / docs.
[Edit] It could start with a Star Wars type scrolling text, like “Welcome to your new Zynthian. To skip this intro, press CANCEL. To run the welcome guide press CONTINUE. The guide will…”
Maybe the page shown by @LFO is quiet self explaining but they are others more obscure and I think a small tip could be helpfull.
Yes @le51 those were more the types of pages I was thinking rather than the one I used with my screenshot.
@riban So we’re going with option 3 then? 
I agree contextual help should be subtle and not add confusion or be annoying. I really think if you did a first boot splash screen, it should persist until explicity told to not show anymore. Because…how many people may have screen issues or soundcard misconfig causing a bootloop, the splash screen might ‘show’ once but never be seen when the user actually gets a successful boot with UI.
Yep! The addNote function has changed the prototype and now have and extra parameter “offset”:
bool addNote(uint32_t step, uint8_t note, uint8_t velocity, float duration, float offset)
@oscaracena , i took a look to your driver and i see it’s not a 2-lines change, so i will let you to do it, mate.
Enjoy!
@jofemodo I must be missing something, because I see it just as that, literally 2 lines of code. What I’m missing? When is that offset used?
Thanks for the info.
@jofemodo FYI, I have been attempting to configure some rotary encoders on my headless setup. I found the buttons were not performing as expected. So, I started loading up other hardware profiles without knowing really what I was doing. When I tried to go back (set to ‘dummies’ and reload custom profile), I found my settings were lost. All reset to 0
I saw the 2 lines change, but i wasn’t sure of these 2 being the only ones. Happy to know it was a little change only
Offset allows to delay the trigger of notes (events) so to any time along the step. It’s used when capturing without quantization, so what you play is captured as you play. Also, you can modify offset by hand as it’s a note parameter that can be edited from the pattern editor. Finally, note offset is also used internally for implementing swing and time humanization.
Regards,
@LFO, it always has been like this.Your custom configuration is not saved apart. If you overwrite with other configuration from the list, the custom config will be lost. Sorry.
Perhaps it could be improved, but it’s not a new bug
Regards,
