Oram questions

Using Zynthian
,
1

Hello again. I am setting up the machine from scratch to solve the Pianoteq issue. Is it true, that the WIFI cannot be managed from webconf anymore?

2

And what happened to MIDI OUT? I am having the problem, that I enter first zynthian via USB and want to pass the messsage via DIN to the second zynthian. But the message isn’t routed to the DIN ports. I can’t see the checkboxes in webconf either.
And why is there no default MASTER CHANNEL anymore? Don’t I have to set it to 16?

4

“Anymore” is too bold, but currently it’s not possible and it’s not planned to re-implement this in the webconf. Maintaining duplicated interfaces for each option is hard, specially for complex ones, like the WIFI config.

Regards

1 Like
5

This has changed a lot. The old approach was simple, but very limited. You have to create a “route” so MIDI-IN can get out the zynthian. The more simple way is creating a MIDI chain with “all channels” selected and no processors (none). This will act as a MIDI-THRU to the selected MIDI-OUT devices (you have to select the MIDI-OUT devices from the chain options submenu!)

Regards,

1 Like
6

Master MIDI channel is not enabled by default. Most users doesn’t need it and we prefered to make available the 16 MIDI channels by default.

Cheers,

1 Like
7

Because you didn’t find the time? In that case I might help, if you tell me about the changes.

8

I am having trouble maintaining subsnapshots between system update I guess. Or it is a bug:
I am using subsnapshots, that are changing the midi channels or “splitkey”. And i am using program changed based channels and the action-ui based one on the buttons.
Now I am in a stage, that only the subsnapshots from today are working and the old ones keep the new midi channel setup I created today.
I didn’t have the time to look into the logs yet…
In case you can explain… Otherwise I will have a look into them in the next days

9

Please, send the broken snapshots so we can work to fix the portability issues

10

Hi @mheidt !

Today i fixed this issue:

I think it could be related (indeed the same!). Please update and test.

Please, note that sadly, some of your ZS3s could be lost. Due to nature of the issue, when loading ZS3s from a snapshot, they were lost in the next save, while new ones are saved correctly. A little disaster that i hope is solved forever!

Regards!

2 Likes
11

@jofemodo I attached my snapshot with a lot of sz3. It’s simular to the one i used with previous versions. If you load one that has 4 sf brass samples layered on midi channel 9, I get the red alarm icon and xruns (original v4 model). The original v2 model didn’t have any issues with this layering via midi channel cloning.
001-SoulFoundation.zss (886.7 KB)

12

When I mute all channels, the red alarm sign is still showing. So maybe there is some potential for optimization.

13

Let me check your snapshot … but this smells like some “feedback loop” in MIDI routing :wink:

14

the latest update didn’t fix it. did you find the time to check?

15

Ups I didn’t check yet.

16

I bypassed it. It seems, that one of those sfz files is a group file. I used polyphone and made a sf2 and instead of 4 sfz engines, I am using one fluidsynth.

17

on oram branch after last update I see this in the logs:
Nov 14 12:40:22 zynthian startx[915]: File “/zynthian/zynthian-ui/zyngui/zynthian_gui_zs3.py”, line 62, in build_view
Nov 14 12:40:22 zynthian startx[915]: if super().build_view():
Nov 14 12:40:22 zynthian startx[915]: ^^^^^^^^^^^^^^^^^^^^
Nov 14 12:40:22 zynthian startx[915]: File “/zynthian/zynthian-ui/zyngui/zynthian_gui_selector.py”, line 162, in build_view
Nov 14 12:40:22 zynthian startx[915]: self.fill_list()
Nov 14 12:40:22 zynthian startx[915]: File “/zynthian/zynthian-ui/zyngui/zynthian_gui_zs3.py”, line 96, in fill_list
Nov 14 12:40:22 zynthian startx[915]: title = f"{state[‘title’]} ({id})"
Nov 14 12:40:22 zynthian startx[915]: ~~~~~^^^^^^^^^
Nov 14 12:40:22 zynthian startx[915]: TypeError: string indices must be integers, not ‘str’

And every click event is dead…

and if I try to load a snapshot:
Nov 14 12:48:34 zynthian startx[911]: File “/zynthian/zynthian-ui/zyngine/zynthian_chain_manager.py”, line 347, in remove_chain
Nov 14 12:48:34 zynthian startx[911]: self.state_manager.purge_zs3()
Nov 14 12:48:34 zynthian startx[911]: File “/zynthian/zynthian-ui/zyngine/zynthian_state_manager.py”, line 1489, in purge_zs3
Nov 14 12:48:34 zynthian startx[911]: if state[“active_chain”] not in self.chain_manager.chains:
Nov 14 12:48:34 zynthian startx[911]: ~~~~~^^^^^^^^^^^^^^^^
Nov 14 12:48:34 zynthian startx[911]: TypeError: string indices must be integers, not ‘str’

18

Hi @mheidt !

Are these snapshots from the older stable version or they were created with oram?
Could you include the snapshots?

Thanks!

19

Please, remove last snapshot (save it before for analysis) and start from scratch. Then do your tests.

Regards,

20

It’s the snapshot I was sending earlier. It’s one I created on oram a couple of weeks ago. But suddenly it doesn’t work anymore after the update I did a couple of days ago.
I am building a new snapshot on vangelis on a different machine. I would have expected a break when I copy a vangelis to an oram…
But if I am the only one suffering from the break, I am fine. At least now I expect the vangelis snapshot to run on oram :slight_smile: