I have a problem using zynsampler. I uploaded some drums loop on sd card and my typical use is to put a drum loop and play something while the loop is running.
The problems are:
sometimes when i change the loop it start at wrong speed (too slow or to fast), I can change it but is annoying.
sometimes the loop is correct, or it ends too soon or it play only one times.
All that problems are erratics, other than control in the UI is there something that i miss? like metronome, or changing the loop while is playing at changed speed?
I would recommend using an Audio Clip chain rather than zynsampler for this. You add a new chain and choose type “Audio Clip” then select the sample to populate each launcher button. This is our new way to support this workflow. Zynsampler is likely to be reduced in scope because it has a lot of overlap with other modules and we don’t want to maintain too many bits of code.
Audio Clip (aka Clippy) has the ability to stretch (warp) audio to fit the tempo without changing its pitch. It is still in its infancy but mostly works.
@riban forgot to say that clippy is only available on Vangelis. Anyway, if you want to use audio loops and sequenced samples, you should consider jumping to Vangelis and start using clippy.
I tried Clippy, it works ok with original tempo of the loop. The only way, that I found, to change tempo is to change the bpm from metronome ( tell me if is’t correct), but when I change bpm it change tempo of the loop but it degrade the sound (with zynsampler or sooperlooper I did’t hear that degrading of sound) and insert a fraction of second of silence at the end of the loop (loosing the tempo).
The meachanism for warping / stretching is the same as used for zynsampler. Maybe there is a bug somewhere. Will you please explain and demonstrate (audio samples) the effect you are getting?
There shouldn’t be a gap. The audio is stretched to fit the length of the phrase. This is assuming warp is on and the beats (in the phrase) is set of detected correctly. No crop - which I am not sure is working properly anyway. Your orginal clip should be edited correctly so that it loops exactly from last frame to first frame.
When changing tempo, the audio is warped. This will cause it to stop playing and it won’t be available to play until the warp is complete and the clip is triggered again, so if in loop mode, you can adjust the tempo but there will be a mute until at least the next loop.
Here is the workflow, I’m not referring to the silence when changing tempo but to the slightly degraded sound and little gap at the end when upbit or downbit from original tempo (90bpm in this loop)
It sounds like one the duration of the loop is correct but with partial silence. Raise a ticket in GitHub using the button in webconf and I will try to reproduce.
I think current practice is that the default branch (the trunk) contains the production version.
That would mean that Vangelis becomes default when it reaches production status. Moving a development version to default introduces a lot of confusion.
There is some sense in this suggestion. The development branch is the one we are most heavily without on and the stable branch is tagged on release. We will have a think…
As development clearly switched from oram to staging since a while,
and oram is still the default branch in github for zynthian-ui etc,
can the vangelis branch be set to default in the GitHub repos?
This would improve up the usability of the web based GitHub and help folks to branch from vangelis instead of oram.