@jofemodo I was waiting for someone to notice that faux pas. Fixed in next release.
@MrDham That will be fixed in next update. I have been working on clock and sync. You should see significant improvement later.
@jofemodo I was waiting for someone to notice that faux pas. Fixed in next release.
@MrDham That will be fixed in next update. I have been working on clock and sync. You should see significant improvement later.
Another update.
ZynPad is starting to take shape but there is still an issue with synchronisation. It is supposed to start the sequence when the bar ends but is not quite doing that. I ran out of time tonight. Maybe I can fix it tomorrow…
Goodnight.
Nice update, thanks Riban!
A tiny criticism: The loop symbol hides the MIDI channel
Another day, another update. You might even like this one!
The pads are almost usable! They should allow triggering of sequences (which are currently just populated with patterns 1,2,3… but will in future be configured by song editor.) If the transport is not running then the pressing a pad will start the transport and the pad’s sequence will start immediately. Subsequent pad presses will start at the loop point*. The pad mode may be changed so that it plays once or loops. Each may be configured to play to the end of the sequence or to stop immediately. (This is indicated by (too) subtle colours. I need to improve the choice of colour.)
Proof that this works…
Please play with ZynPad and let me have your feedback. It is still a bit awkward to access the pattern editor and the song editor is not yet implemented. Any ideas on how to navigate between them would be appreciated - I haven’t thought much about that yet.
@spurkopf You can change the font size in webconf. I will look at how to improve display on different sized screens. (I do occasionally test but don’t have time to test everything on every display for every update - and this is alpha - you are my tests .)
And @jofemodo - jitter is fixed - thanks!
Hi Vincent
Step sequencer is currently in alpha testing. It can be accessed by switching your Zynthian to use the feature/stepseq branch from webconf->software->repositories then performing an update. Note that this is cutting edge so may break the Zynthian. It is not yet recommended for production use. I expect this to move to a beta stage within the next few days (or hours @jofemodo?) and appear in the stable release. It is still under development with much work yet to do.
LV2 plugins may be enabled or disabled in webconf->software->LV2 plugins.
Cheers
I’ve moved the previous discussion to a new Thread ‘Accessing The Webconf’, primarily to see If I could . . .
…
My posting has nothing to do with “Accessing the webconf”.
@spurkopf You can change the font size in webconf. I will look at how to improve display on different sized screens. (I do occasionally test but don’t have time to test everything on every display for every update - and this is alpha - you are my tests .)
And that’s why I’m here, the standard user with a standard kit and bad eyes. Maybe you should just write Channel, Midi-CH, or remove the arrows.
Apologies, it’s now back ! but perhaps a little out of place. You wouldn’t believe the housekeeping required round here
I’ll do something in future update. We are looking at hiding touch controls if user doesn’t want them and I can reduce the text length as you suggest. I will have a session where I work through all the options for different size displays but bear with me whilst I try to complete core functionality.
I only report if I notice something that could disturb other users, or if I think that should be considered. What you do with it is of course up to you. Otherwise, I don’t want to stop you in any way from programming.
Small update:
Hi @riban,
I just added a configuration option for enabling/disabling touch widgets.
It’s available from the webconf’s UI options and accessible from code:
zynthian_gui_config.enable_touch_widgets
Thanks!
OK @zynthianers!
I just merged feature/stepseq with master … in other words, the Step Sequencer is now available for everybody in the main branch.
Congratulations, @riban, for this fantastic piece of code. And thanks a lot for this huge effort!! You can be sure that a lot of @zynthianers will enjoy with it … and a few motivated heads will be crashed by some furious life-partner feeling unattended …
And now, my report after having played a little bit with the Patter Editor and the Zynpad:
First, the good!!
Pattern Editor:
ZynPad:
Pattern’s MIDI channel should be used. You compose a pattern for a sound (aka layer, aka MIDI channel)
By default, patterns could be ordered by MIDI channel (aka layer), having channels in columns and pattern phrases/variations in rows, something like that:
CH#1:Lead CH#2:Pad CH#3:Bass CH#10:Drums
p1 p10 p20 p30
p2 p11 p21 p31
p3 p12 p22 p32
p4 p13 p23 p33
Of course, we are reaching the point where it MUST be integrated with hardware pad-controllers, like the Novation’s LaunchPad, etc. We have to think about mapping … and perhaps reusing stuff from DAWs like Ableton Live … Take a look to this:
Regards,
OK!
Same patterns that 2 days ago plus some variation, but triggered with ZynPad …
Enjoy!
So now everybody can upload the ZynPad (nice name btw) into the Zynthian using a network connection ?
Amazing!
It has to be mentioned, you guys really know what you’re doing and form a great team.
I will join my voice to the chorus of congratulations and thanks… to @riban for sure, and also to anyone who has taken part in any way in the building process, from simply giving their opinion, expressing their expectations and préférences, to helping in the coding or architecture…