Got my zynthian today, and i’m jumping from error to error

Building Zynthian
1

Hi there!

i’ve been trying to figure out what’s happening for the last two hours.
i got a zynthian second hand, but the box is pretty recent and the seller explained to me that he didnt used it much.

image
image2422×1094 267 KB

here are the error i get when i try the JV/pitchedDelay, or any MD thing

Some FX just kill any process.

The error talks about some network error so i tried wifi, and ethernet and nothing seems to work. Mod-ui is not accessible from the browser and worse, as soon as i get this error, the zynthian is not responsive anymore.
The config_ui still seems to be accessible though.

I have no idea where to start to debug,

thanks a lot!
ju

1 Like
2

Hi @julientaq, welcome- you have entered a world of fun with a lively and friendly community.

You have described a few problems and changed the log file several times. It will help us to diagnose your issues of we take a methodical approach.

Please use the Clear All option to reset the Zynthian and restart it then describe the exact steps you take to trigger one issue and include the log for that issue. We can try to figure it out then move on to the next issue later.

1 Like
3

Hi @riban
I got a good time last night working with some plugin and my squier, this is definitely a world of fun
:slight_smile:

So i did clean all and rebook, and this is what i got in the end

i get that when i go into start mod-ui and choose any of the 5 options then the UI is completely blocked, and i’m forced to reboot from the web interface.

i’m set up using rj45, and the wifi is out.

let’s figure this out :muscle:

thanks for helping!

4

So these are your steps?

  • Clean all
  • Reboot
  • Layer menu
  • New Special Layer
  • MOD-UI - Plugin Host
  • Clavinet AutoWah

UI is unresponsive. Yep! I see that too. @jofemodo any ideas? I’m not available much today but did stop for tea and was able to reproduce this on an V4 updated to latest Stable (2109).

@julientaq did you update your device or flash a new image of 2109?

1 Like
5

I made a clean reinstall when it got home yesterday with the latest image :slight_smile:
always start clean with new toys.

Mod-ui is really what i want to try, but the rest is pretty funny to work with!

6

There is a procedure I use to ensure things are ok.

First is webconf. A zynth with a crashed GUI is possibly still connected by the webconf and once you have that you have GUI logs and a terminal. So that will lead you down one path .

Second is the webconf sensible? Probably more for the none kit users, but a good sanity check. is it set to custom?

MIDI defaults are worth a look. is the 12M limit on for the USB ports? are there any MIDI rules in place.

next you want to look to the GUI, why isn’t it coming up? In my world it’s nearly always a missing file in a test branch or a jack misalignment. jornalctl via the terminal will tell you an awful lot but once again he webconf and the GUI log will help. Debug mode is great up to a point but the interface tends to barf a bit at big text files.

From there you can start to look at hardware.

Start with the test audio in the GUI admin. Our fine Cuban friend is confirmation. I kind of know when stereo image is right on this particular piece :smiley: But this is an Alsa only test and confirms the Zynthian Audio output hardware. It’s amazing how that turns out to be a problem. It should be clear with no hum or noise.

This will also tell you if the phase matches on your Left & Right ( you still dont know if everything is the wrong way up :slight_smile: ).

load a simple sound as Layer 1 on MIDI 1 I tend to use Fluidsynth Yamaha Grand Piano, cos I haven’t sorted out my favourites yet :-), but other engines are available, lot’s and LOT’s of others … :slight_smile:

Play the MIDI test file in Admin.
You should hear take 5 … and confirmed the MIDI side of jack is all good.

That at least is a base working zynth.
There is the brute force approach of just forum searching key phrases from pertinent error messages, which is great unless someone has cut & paste a error log image ( I do it all the time, it saves indent hashups which is a horrible side effect of python textual cut & paste.)

There are a couple of developer notes on zynth start up (Zynthian GUI start up walkthrou' - ZynthianWiki) for those that want to be slightly more methodical about all this.

Comprehension beats cut and paste every time. :smiley:

7

yes!
i’ve been through all that.

(also, i’m using a kit so i assume i’m all good with the right setup).

Midi in works, synth work, sounds out works, (the raspberry headphones out doesnt, but i don’t really need it).

I also spent some time search on google and the forum, i maintain an open source js library, i know how people should do. And i haven’t found anything.

i’m gonna dig for mod-ui error exclusively, that may help.

I’m just really stuck with mod-ui.

8

Sorry @zynthianers!

I made an error when passing the staging-2109 to stable and some critic updgrades were not compiled into the last stable image. I’m generating a new one right now and it should be ready in a couple of hours. I will replace the current stable link when it’s ready.

For those of you that already downloaded the stable, you can try this recipe:

export ZYNTHIAN_FORCE_UPGRADE="yes"
update_zynthian.sh
reboot

If connection is good and everything works as expected, it should fix the problems.

People that succesfully moved from staging-2109 to stable-2109 shouldn’t have the related problems and no action is required.

Best regards,

9

Thanks a lot! Will try that tonight!

10

Here is the fixed stable image:

https://os.zynthian.org/2021-09-25-zynthianos-stable-2109.zip

Enjoy!!

2 Likes
11

I’ve been waiting for this one. Another all-nighter…

12

And i’m all set after the update.
This is great!
Thanks a lot for this quick fix!
ju