Enable and disable VNC server from admin menu

Hi @jofemodo ,

would it be possible to expand the admin menu like this?
[x] VNC Server Zynthian display
[x] VNC Server for GUI

I tried commands from your recommendation post #27 and #29 but without successful end.

3 Likes

I could use some help here too. I do not get any response on clicking the VNC Server option in the Admin UI.

I did the following
First downloaded en copied the image of the latest release on a clean SD card.
Then did a software update via the web config tool.
Then I could actually click the VNC server option, but could not get it to work with the VNC viewer.
So, with raspi-config, I enables VNC. After that I could use VNC viewer, but the VNC Server option did not work anymore.

I would like to use all the goodies.

Regards,
Bert

A couple tips:

I installed x11vnc a month ago.
I installed vncserver from raspi config.
I updated the pi from admin menu.
I also updated the pi from zynthian.local.

Ssh into the pi.
Make a vnc directory in your home folder. This vnc holds your password file.
Install the Tiger scraping server.
Restart your pi.

Always Remove all layers.
New Layer add your synth.
Open zynthian.local:5901
You should see a GUI.
Do not close the GUI in the screen…

Ssh into your pi (skip the Y).
Navigate to the home folder.
Launch x0vncserver.
Check your syntax until you see
Connections: accepted.
Open zynthian.local:5900
You should see the Display and knobs.

Don’t close the GUI. It might not reopen.
Remove all layers and Zynthian will clear the GUI for you.
Add new layer and Zynthian will launch the new one.

Hope this helps. Sam

2 Likes

Having been able to successfully back up the resources on zynthian-ceed.local, I’ve now rebuilt the machine on the most recent nightly and updated, and I’ve got vnc access!


I can now try out the zynseq/zynstep tutorial, and discover how many things I request he’s already done… :slight_smile:

Closing the vncwindows is a really fine way of killing an engine on the GUI, but leaving the GUI displaying them as active.

Is there now an ‘official’ way to access the xwindows GUI head a’la the webconf engine xwindows…?

I see Sam is running it on 5900. I’ve got to walk throu’ the systemctl build ain’t I …?

And I really should arrange an audio out on this machine !! :smiley:

this is the strangest poem i have ever read on the internet!!

4 Likes

This is what I have.
VNC viewer connects with the standard RPI VNC server whereas TightVNC connects to the VNC servers tat comes with Zynthian.

1 Like

The dungeons have just made a small investment on behalf of @samriccijr . . . .

I have the sequencer running on zynthian-ceed.local with audio no less !!

So time to work throu’ the tutorial!

4 Likes

If I get the GUI interface running it seems not to want to run the engines …

The Zynthian GUI modifies the VNC Screen ( for Helm) but the VNC screen does not modify the zynthian GUI…

Thanks to @samriccijr, I have both now.

1 Like

Maybe it is a stupid question, but is it possible to run ./zynthian_emu.sh from xterm from noVNC window to get the native GUI ?

Still can’t manage to make both live together - pi’s realvnc builtin server abn noVnc.

Whats the current process for getting the actual Zynthian desktop on VNC?

I can access the synth layer GUIs using the instructions, but not the actual desktop.

Ive tried following the wiki instructions, but it doesnt seem to work with the current build.

After many tries, for me works this sequence :

  • SD with Zynthian OS
  • put into Zynthian
  • power on and instal Zynthian
  • setup Zynthian by web-config on zynthian.localhost - setting kit, sound card, display and wiring and reboot
  • update Zynthian by web-config / software / update and reboot
  • start vnc server by raspi-config - this start instalation proces, I tried do this by web-config / terminal → http://zynthian.local/zynterm and I was successful
  • start vnc client on PC side and connect to zynthian on display :0

Do only this steps nothing more…

A little tip that I have just found out and will find very useful… You can automatically connect and login to noVNC by appending parameters to the URL, e.g.

http://zynthian:6081/vnc.html?autoconnect=true&password=raspberry

I use VNC a lot during development and this will save my sanity for just a few more days…

[Edit] I have added this tip to the wiki.

3 Likes

Uhh, that’s 100% secure

:see_no_evil: :hear_no_evil: :speak_no_evil:

But, yeah, I like it !

If I want it secure I might bother to change the default password… :blush:. Yep - not perfect but a useful tip for fast and frequent access.