If there are workflows that need to be done from the main UI, let’s add them. Most of these kind of VNC operations are for unusual activities like converting presets between native and LV2.
ZYNSAMPLER NEWS!
Our wonderful @jofemodo has added file loading to the excellent samplv1 and is in the process of improving its integration in zynthian. This is fantastic work that makes samplv1 our sampler of choice - to the extent that we are retiring zynsampler. We will retain a long-form audio player but with fewer features, e.g. we lose MIDI trigger and associated parameters like envelope, loop markers, etc. You will see updates to vangelis over the next few days as we roll out these changes. I make this announcement because some of you may be using zynsampler and may need to adjust your workflows. We now have these audio clip players:
- samplv1 - Advanced sample playing with MIDI trigger.
- clippy (audio clip) - Clip launcher with time warp used in laucher for sequence / tempo synchronised clip playing.
- Audio Player - Record and playback audio files with some features like time/pitch stretch (including varispeed), crop, multichannel mixdown, etc. Useful for playing back recent recordings, playing accompanying audio for practice, etc. This can be the global player or added to a chain, e.g. for a DJ type workflow.
- Internet Radio - Primarily for streaming web streams but also has a playlist for local files.
Update regularly to see updates and keep those bug reports coming into the issue tracker.
[Edit]
A little history… I wrote the audio player to provide a replacement for the standard tools we were using so that we had more control and features. That then expanded into a fully fledged sampler with MIDI control and a host of features. Some of these features were built to support a clip launcher. We subsequently went through a developement phase for the launcher that resulted in clippy. We also managed to get samplv1 to integrate well in zynthian. These two provide the functionality that was making the audio player (later renamed zynsampler) so complex. We can now revert to a simpler audio player. We may even be able to use an existing upstream player which could remove the burden of supporting this codebase. Win-win-win!
Not sure if this is a good place to ask, but will any of these solutions provide a simple multitrack recording functionality with the possibility of overdubs?
They won’t. The closest we have is sopperlooper (which I maybe should have listed above). We are avoiding getting too deep into DAW design. We support multitrack tracking and playback but not the more complex full-DAW functions like overdubbing. That feels like a step too far. There are some great free and low cost DAWs available for all OS platforms that provide this.
I do understand this, but I think that capturing ideas (not loops) with multiple instruments might be well inside the conceptual frame of a keyboard extender. The recording I uploaded in the NAM thread was done by global recording → load and playback in clippy → repeat.
So what do you think about destructive overdubbing in the global recorder (mix playback and record)?
Edit: (…or a 4-track-Portastudio implementation inside zynthian…)
I like the idea. I want to use my zynthian as a one-stop solutoin for most of my audio requirements and for sketching ideas it is quite good with MIDI + 1 audio. You can add a feature request to the issue tracker.
Although I understand that there would be technical challenges or code compatibility issues to overcome, it would be a fantastic solution, for finally being able to do real sound design on the Zynth itself.
The other day I boldly decided to deep-customise a complex Osirus preset without VNC connection (which I find sluggish and hardly functional), and without a graphical overlay it literally felt like trying to browse a Sumerian clay tablet one squared millimeter at a time!
![]()
Just had a short pre work jam and can report that “delete all fx” from master chain causes total silence because it’s probably deleting some of the dummy fx processors as well (audio input?).
Don’t know about other occasions (deleting all fx from any chain or similar).
Hi @hannesmenzel !
Do you mean “deleting all audio FX in an audio Input chain” or in any type of chain?
Could you give the steps to reproduce? Indeed, if the issue is reproducible, you should open a ticket.
Thanks
I meant specifically deleting all fx from the master chain from its menu.
Edit: But I can confirm that it is also on audio chains.
Here are the reproducing steps. In any master OR audio input chain
- Add any FX
- Remove all FX from its menu
- Hear silence.
Hi @HansR !
We have finally moved all pre-generated presets from the zynthian-my-data directory to a new location at:
/zynthian/zynthian-plugins/lv2-presets
Most users don’t need to know about this, but i’m telling you because you complained about the fact that user’s preset directory contained “factory presets” and this caused trouble to you.
This changes will avoid further issues because now the user’s presets dir is totally empty on a fresh burned SD image.
Anyway, i would like to note that some plugins, like Osirus & Ostirus, will auto-generate its factory presets in the user’s presets folder (zynthian-my-data). This is hard-coded in the plugin’s source code and we should recompile the plugins to change this. AFAIK, only these 2 plugins behave like this.
Regards,
Thanks!
I put off updating for 1.5-2 weeks and tried to update yesterday. It appears to be successful, I can’t spot any obvious errors but after completing, the update symbol remains in the top bar. I have run it four times or so and rebooted in between but the symbol remains.
Have you made any manual changes? Thses can block updates.
I wonder if it’s to do with git. I’m made a branch for driver development.
If you modified git repos by hand, it’s very probable this is the cause.
Regards
Not sure, but if you created a new local branch and that is active you may need to return to the current development branch by doing
git checkout vangelis
In the directory where you created your new branch
And then try the update again?
start with git status…
If you see uncommitted files or un staged files this will be the cause.
Git sticks, well like a very sticky thing…
I did the request in the tracker.