Good! Thank you! I’ll submit the PR asap!
Cheers!
UPDATE: Done! Here it is the PR:
Good! Thank you! I’ll submit the PR asap!
Cheers!
UPDATE: Done! Here it is the PR:
Testing an updated version ORAM 24-05-22.
So far I have not encountered any major nags, but I cannot find a way to save the current snapshot or access other snapshots.
When I long press the snapshot encoder, it opens the subsnapshots screen, instead of the customary view to load and save snapshots.
My machine is a V4 built on Pi 3B+.
A bold press of that encoder shows ZS3. A long press shows snapshot. Bold press is press, hold for a second and release. Long press is press and hold for about 2 seconds until the action triggers, then you can release.
Apparently I was not pressing long enough, even though I’ve done it dozens of times before
The only other thing I have bumped into is related to SooperLooper.
The undo and redo function behaves quite erratically. It used to be more consistent in the previous stable image.
I also noticed that the Capo effect tends to crash and mute the chain when changing values in the Step parameter.
It’s a pi6ty. Capo is a nice effect and deserves a fix. I will check. It could be 64 bits related.
Regards
I could not trigger this by adjusting the step parameter but it did crash when adjusting the fidelity parameter. The plugin closed but there was no entry in the Zynthian log.
I suggest raising a ticket in the issue tracker.
I’ve got troubles with StepSeq using only the touchscreen interface:
Having solved my initial chains issue to get splits/layers working, I now have an issue with MIDI chains.
I want to pass MIDI notes/events from the Zynthian to my PC midi interface.
I create a MIDI chain, set the MIDI IN to the port (a port on my ESI M4U, configured as Multitimbral) set the MIDI OUT to an out port on the M4U, and put a MIDI Thru effect on the chain. Nothing goes out.
I just re-updated today, so I am running the latest code.
Thanks
I have tried the Channel Map as well.
Hi @s_blakely!
You should not need a MIDI Thru effect. An empty MIDI chanin in Oram should pass MIDI input to MIDI output (as defined by the MIDI IN and MIDI OUT configs you describe). This is a change to previous versions - MIDI and Audio chains now pass MIDI / Audio through. And there is a special config: MIDI + Audio that does both!
Adding the MIDI Thru plugin should not block the MIDI thru so it does sound like you may have identified an issue. I would suggest removing the plugin and retesting then raising a ticket in the issue tracking system with all the detail you discover. I recommend using the “Report Issue” button in webconf dashboard as it populates the ticket with very useful info that assists us with triage and diagnosis.
[Edit] There is an issue reported already for this: #1053.
Try now - this should be fixed.
@riban
After updating today (5th June NZST), MIDI chain output now works. However, I cannot assign a MIDI Effect to the chain (in this case, MIDI Channel Map). I can page through the groups with the Upper Right encoder, but the Lower Right encoder does not move the selection cursor.
I was able to assign the effect using the touch screen, but the MIDI Channel Map is not mapping Channel 1 to Channel 2. I’ll keep playing around - at least I have some pass-through now.
The UI screen only displays some Boilerplate Latin text for help for all the MIDI effects - is this just not in place yet?
Thanks again
similar behaviour after updating for inserting special chain. The “Select” encoder has switched to float values instead of int values. Hence after long turning, the next special (puredata) could be selected.
I see 2 issues here:
seems to be fixed now.
zyncoder: oram (a7976d8)
zynthian-ui: oram (199670b)
zynthian-sys: oram (d542728)
zynthian-data: oram (db0355a)
zynthian-webconf: oram (c27fea2)
I have rolled back the change that caused this issue and highlighted it in github commit review. @jofemodo we need a different algorithm to detect small-valued float controllers.
@riban, should I ticket now or not, I am not sure. You just reverted and wrote a TODO into the code?
No - don’t bother adding a ticket. It is no longer causing the issue and @jofemodo has a note to reimplement the thing that caused this, in a different way. Cheers!
Hmmm, today I’ve flashed 2024-05-22 image and zynthian booted correctly.
But I can’t get my wifi working.
When providing password in admin ui following error is logged:
Jun 07 20:50:10 zynthian startx[1635]: Warning: password for '802-11-wireless-security.psk' not given in 'passwd-file' and nmcli cannot ask without '--ask' option.
Jun 07 20:50:10 zynthian startx[1635]: Error: Connection activation failed: Secrets were required, but not provided
Jun 07 20:50:10 zynthian startx[1635]: Hint: use 'journalctl -xe NM_CONNECTION=a483e146-eee3-4b10-92eb-6f7cf76100e7 + NM_DEVICE=wlan0' to get more d
and journalctl logs:
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.1997] device (wlan0): disconnecting for new activation request.
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2275] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 07 20:49:45 zynthian NetworkManager[792]: <warn> [1717789785.2536] device (wlan0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2537] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2567] device (wlan0): Activation: starting connection 'TP-Link_2D15' (a483e146-eee3-4b10-92eb-6f7cf76100e7)
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2579] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2596] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2617] device (wlan0): Activation: (wifi) access point 'TP-Link_2D15' has security, but secrets are required.
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2618] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2626] sup-iface[3e8bc41943b42460,0,wlan0]: wps: type pbc start...
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2660] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2667] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 07 20:49:45 zynthian NetworkManager[792]: <info> [1717789785.2678] device (wlan0): Activation: (wifi) connection 'TP-Link_2D15' has security, and secrets exist. No new secrets needed.
Jun 07 20:49:49 zynthian NetworkManager[792]: <info> [1717789789.0594] device (wlan0): supplicant interface state: scanning -> disconnected
Jun 07 20:49:49 zynthian NetworkManager[792]: <info> [1717789789.0651] device (wlan0): supplicant interface state: disconnected -> associating
Jun 07 20:49:49 zynthian NetworkManager[792]: <info> [1717789789.4916] device (wlan0): supplicant interface state: associating -> disconnected
Jun 07 20:49:54 zynthian NetworkManager[792]: <info> [1717789794.5088] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 07 20:50:01 zynthian NetworkManager[792]: <info> [1717789801.0936] device (wlan0): supplicant interface state: scanning -> associating
Jun 07 20:50:01 zynthian NetworkManager[792]: <info> [1717789801.4627] device (wlan0): supplicant interface state: associating -> disconnected
Jun 07 20:50:10 zynthian NetworkManager[792]: <warn> [1717789810.8278] device (wlan0): Activation: (wifi) association took too long
Jun 07 20:50:10 zynthian NetworkManager[792]: <info> [1717789810.8279] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 07 20:50:10 zynthian NetworkManager[792]: <info> [1717789810.8282] sup-iface[3e8bc41943b42460,0,wlan0]: wps: type pbc start...
Jun 07 20:50:10 zynthian NetworkManager[792]: <warn> [1717789810.8285] device (wlan0): Activation: (wifi) asking for new secrets
Jun 07 20:50:10 zynthian NetworkManager[792]: <warn> [1717789810.8374] device (wlan0): no secrets: No agents were available for this request.
Jun 07 20:50:10 zynthian NetworkManager[792]: <info> [1717789810.8374] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jun 07 20:50:10 zynthian NetworkManager[792]: <warn> [1717789810.8400] device (wlan0): Activation: failed for connection 'TP-Link_2D15'
Jun 07 20:50:10 zynthian NetworkManager[792]: <info> [1717789810.8426] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 07 20:50:10 zynthian NetworkManager[792]: <info> [1717789810.8623] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 07 20:50:14 zynthian NetworkManager[792]: <info> [1717789814.7035] device (wlan0): supplicant interface state: scanning -> disconnected
On stable the only workaround I needed to made wifi work was to update country in wpa_supplicant.conf, but after change to networkmanager connection is not possible.
This is working for me now.
Thanks for your hard work.
I have installed the latest testing image, fully updated:
zyncoder: [oram (a7976d8)
zynthian-ui: [oram (4980d55)]
zynthian-sys: [oram (d542728)]
zynthian-data: [oram (db0355a)]
zynthian-webconf: [oram (cce8b07)]
I can load my snapshot but MIDI Program Changes are ignored.
I have checked that they are received using midi log, but no PC is executed to load my subsnapshots.
I attach my snapshot so that you can check.
Thank you for your help!
003-marti-2024.zss (2.0 MB)