Today we merged the testing branch (vangelis) into the staging branch (oram) to facilitate testing of the next stable release which is scheduled for approximately two weeks from now. We invite the community to help with testing this version before it is released as the stable version. Your assistance improves the quality for everyone, reducing risk of unexpected bahaviour of the stable release. It is advised that you keep your production system separate from your testing system, e.g. have separate hardware or SD card but you each know your own adversity to risk.
If you have been following the forum you may be aware of several of the resolved issues and enhancements. I donāt think it particularly advantageous to list them here - we can do that at the time of stable release.
If you are using the stable release then this will not impact you unless you chose to switch to staging. If you are already on staging then behaviour may change. Please report issues in the issue tracker using the āReport Issueā button in webconf and feel free to discuss here in this topic any subjects you are not sure are a bug.
To switch to staging:
Within webconf, select SOFTWARE->Version. (This was SOFTWARE->Repositories in previous versions of webconf.)
From the dropdown list, select āStaging (oram)ā.
Wait 15 seconds. (This delay has been removed in later version of webconf.)
Click āSaveā.
Select SOFTWARE->Update.
Click āUpdate Softwareā.
You may wish to reboot after this. It wouldnāt hurt!
If you are using testing (vangelis) then beware that it is about to change significantly with some development of the audio mixer. You may wish to switch to staging (oram) until this has settled down.
We want the next release to be the best zynthian release ever released. The more stable and fun to use. We need your help to polish those ugly hidden bugs. And we need your comments about the new features and UI improvements. And of course, we want your noise!! So please, send reports, send nice words, and send your zynthian recordings: audio, videos, etc.
I managed to update my V5 as you explained, but my V2 returns 500: Internal Server Error to the Software/Version (http://192.168.1.133//sw-repos) attempt.
Zynthian is the wonderful result of people willing to create a better world in which peope are enforced to freely express themselves via music and sound!
Great, thanks @riban and all the others.
Question about vangelisā audio mixer āchange significantlyā.
What exactly could we expect from this? Side chains? More flexibility? UI change only?
Regards and all the zynthianic love
We already have sidechains. The main change will be to move the mixer strip into the chain and to provide proper send/returns. I am working on merging into vangelis now so hopefully it should land in vangelis over the next few days.
So, Iām still trying to figure whatās wrong with my V2.
(returns 500: Internal Server Error when I attempt to access version on webconf - http://zynthian.local/sw-repos).
I already rebooted and made an update. Of course I can flash sdcard, but I wonder if this is something that should be figured instead of just overcomeā¦
Meanwhile, I noticed there is a small issue. With ssh, I get truncated software versions - just 6 hex chars instead of 7 chars like the webconf.
Should I report this as a bug, or is this a problem between my chair and my screen?
Thx!
Great, I am looking forward to this. One question though:
When I tried vangelis the first (and consequentially the last) time two month ago or so, I ended up in booting into software error and no chance to get to webconf anymore. I finally reflashed the image, because my limited understanding of things.
I recently switched to staging to resolve the endless update notification bug.
As far as I know switching to vangelis rn involves installing and updating some packages (apt) as well.
So hereās my question: If I end up with the same errors, am I able to revert to stable over ssh without reflashing? And how? Otherwise I would maybe just switch to stable right now.
(One p.s.: Is there a technical opportunity having zynthian-my-data on a seperate partition for keeping your user soundfonts on reflashing? I use Zynthian as my keyboard extender and am a big fan of sampled real world instruments, so itās 30gb for me)
EDIT: Sorry, was not intended as a reply to post #8
I had some trouble with my V3. It seg faulted when running oram-2409.5. I could not resolve this so I updated to staging (oram). It still wasnāt very happy so I did an apt update, apt upgrade and then restarted a couple of times. Now it is running oram okay.
This is usually not the case. We do sometimes break testing (vangelis) because it is the bleeding edge development branch which is why we suggest to only use it for testing and to use a separate boot device. If you are super good with git then you can usually dig yourself out of whatever mess you get into switching between stable. staging and testing. I have to do it all the time but we donāt recommend this for normal people.
Anything is possible. We try really hard to avoid breaking between stable and staging. We try hard (but not quite as hard) to avoid breaking between staging and testing. We bare try at all to avoid breaking between testing and dev branchesā¦
Following hints you gave to a similar situation last September, I peeked .git/config in zynthian-webconf and, oddly, vangelis was there. although I never gave a try to it. Must be some leftover of last month Oram-2409.3 Stable Point release attempts.
Since i could not succeed with git pull, and after trying apt update and apt upgrade as you mentioned, I gave up and Iām flashing sdcard at this very moment. I better get the box running for rehearsal later today
Anyway, V5 seems to be running fine with the 2502 release candidate, so all good.
Thx for your feedback!
Something here reminded me of this quote from Zen andā¦
"Romantic reality is the cutting edge of experience. Itās the leading edge of the train of knowledge that keeps the whole train on the track. Traditional knowledge is only the collective memory of where that leading edge has been. At the leading edge there are no subjects, no objects, only the track of Quality ahead, and if you have no formal way of evaluating, no way of acknowledging this Quality, then the entire train has no way of knowing where to go. You donāt have pure reasonā¦you have pure confusion. The leading edge is where absolutely all the action is. The leading edge contains all the infinite possibilities of the future. It contains all the history of the past. Where else could they be contained?
Iām in one of the 120 box cars that Pirsig mention. Iām looking out the window, looking ahead towards the locomotive. And i so want to be there. And, from time to time iām walking from one car to the next, and sit there, relaxing for a while. And then maybe the next hour or week, i move to the next car. And when i look out the window i can see that there are many cars still between me and tho locomotive. And i so want to be there!
Iāve been riding this train for bit more than two months. Thx again to the drivers and what else personnel up there in the locomotive. Itās such a beautiful travel. And it reminds me so much of life itself. I want David Attenborough to bere here talking about it! I want to go on with this nonsens babbel, but i will stop here and excuse my self for being off track (or is it on track?
Also updated here yesterday, but testing out today i had XRuns problem with Pianoteq!
Iāve opened a topic about it here
For now i just wanted to know if anyone had similar problems?
So far, everything seems to run smoothly here, both on the V2 and V5 official kits.
Nevertheless, I do have a feeling that somehow the rotary encoders are more sensitive than before on V2, making browsing the options faster. For me, the experience didnāt improve, they feel less reliable now, if that makes sense - sometimes I even slip to another selected option in the process of using the switch pressā¦
First and foremost, many thanks for all the progress.
Secondly, I would like to apologize for raising the issue here. I simmply do not understand how to post it in the issue tracker.
With this update there is no difference. I managed to capture an error notification. Maybe it is of use.
Configuration file ā/etc/dnsmasq.confā
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainerās version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** dnsmasq.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package dnsmasq (āconfigure):
end of file on stdin at conffile prompt
Errors were encountered while processing:
dnsmasq
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package listsā¦
Building dependency treeā¦
Reading state informationā¦