I have just pushed some fixes to the dev branch. Anyone wanting to test it out can do so. It should be fairly stable and functional but you play at your own risk. You can basically add and remove USB audio interfaces and they should appear and disappear in the audio input and output routing menus. Hotplug can be enabled/disabled in the admin menu.
Well that was easy…
1/ Update switch zynthian-ui to Feature/hotplug_hotplug and save
2/ Reboot
3/ Turn on Hotplug USB Audio
4/ Plugin USB to 14" jack lead
5/ Add audio 3 as an Audio input.
The pedalboard now has a third audio input!!
This is a BIG development!
6 Likes
Detection of plug/unplug is a bit slow. I will look at that later in the week.
1 Like
Hi @wyleu ,
How do you ‘Update switch zynthian-ui to Feature/hotplug_hotplug’
I cannot select this ‘Feature/hotplug_hotplug’ in Webconf… (On github I see it)
I am on valngelis…
Or… how do I merge repositories so I can have the Wanthalf on screen buttons and the Riban usb audio automount…
Cheers,
Maarten
You can’t (easily) do that. When hotplug audio gets merged to vangelis then @wanthalf may merge it into his dev version.
You can test the dev version by:
- Accessing webconf in browser
- Select SOFTWARE->Repositories.
- Enable “Advanced view”.
- Select “Custom” version.
- Select “Feature/Hotplug_audio” for zynthian-ui.
- Save.
- Update.
- Reboot.
- Pray!
- Enjoy!
- Report progress here.
1 Like
It’s in webconf → software-repositories.
select save and then reboot.
I always find it sensible to check on the webconf front screen that it’s actually loaded it first on the restart. It’s not that it’s unreliable, but you want to be sure you have the correct version before playing with a new feature.
A remember this is development code. You are making your own rook soup from here ! But it appears pretty stable so far.
Yeah! You should report that. 
It’s a bug. I think selecting customg and advanced then refreshing might work.
Hi Riban…
What about manually on the command line?
Cheers
Thanks. At least I know now tha I am not crazy… 
Cheers
git -C /zynthian/zynthian-ui checkout Feature/Hotplug_audio
/zynthian/zynthian-sys/scripts/update_zynthian.sh
1 Like
Hi Riban,
I think something is nok…
I get:‘error: pathspec ‘Feature/Hotplug_audio’ did not match any file(s) known to git’
I will wait until wanthalf is ‘synced’
Thanks again guys for the fast and knowledgeable resposes…
Cheers,
maarten
Hi @riban ,
My mistake… without realizing it… I had the origin path in zynthian-ui/.git/config to ‘url = GitHub - wanthalf/zynthian-ui: User Interface for Zynthian’ in stead of url = GitHub - zynthian/zynthian-ui: User Interface for Zynthian’.
Changing it made it possible to select ‘Feature/Hotplug_audio’
Really FANTASTIC!! Now the keyboard can be routed to a different amplifier!!! (unfortunately my z5touch soft buttons are goen…)
This is a really great feature!! Thanks!
Cheers,
Maarten
3 Likes
Well done! Please test it and give feedback. It would be good to move this to vangelis soon.
1 Like
I tried yesterday to update my zynthian with no luck, first time I’ve seen the update working, but “no space left on device” at the middle of the update. No surprise : error ahah
Second time, I recreated the SD card with the latest stable, changed the software repo, and error again, I did not read the doc about that 
I will try again this evening
How big is your SD? I ran out of space yesterday on a 32GB (I think) but that is a dev machine that has lots of stuff on it. (People should stop asking for new plugins…) This shouldn’t be a problem so report it, ideally with webconf “Report Issue” button.
hI @riban
I notice that when the instrument chain is set to Chain inputs = Main Mixbus and nothing is selected in the MAIN audio out window the audio of the instrument is sent to output 1 and 2…
Perhaps I am missing something?
Deselecting Chain inputs = Main Mixbus makes it possible in direct outputs to select any of the outputs and have the piano left on the LEWITT and right on the SCARLETT…
So… Great!!
Cheers,
Maarten
I didn’t understand that but it looks like you have solved it.
Each audio chain (synth, audio effects, etc.) allows routing with its audio out menu to any direct output and to any other audio effect chain. These are arranged as individual outputs which allow stereo to mono routing and also as consecutive pairs that allows stereo ouput routing.
Each audio effect chain allows routing with its audio in menu from any physical audio input. These are presented as individual inputs allowing mono to stereo input routing or, if consecutive inputs are selected, stereo input selection.
The input and output routing screens differ with the pairing of ports. I wonder if that should be more consistent?
I think that selecting only Chain inputs = Main Mixbus of the instrument chain and NO audio output of the MAIN (mixbus) chain (the most right ‘chain’) should lead to NO audio…?
(Have to laugh… its clear English is not my native language )
i also noticed that the audio input and output in the MOD-UI host are always audio in/output: 1 and 2? It is alway called captue 1&2…
Cheers,
Maarten
PS otherwise I will wait until it is merged in the Wanthalf branche. I wil make the snapshots which wil be a lot more clear… (I hope 
)
Would you? could you?
The more use the reporting system gets the slicker it becomes and then more people use it…
It helps us all.
Normal house rules apply…
1 Like