Zynthian Engine Preset Structure - Revision history

Wyleu: /* Jack */

2021-09-13T15:51:40Z

Jack

Wyleu: /* Jack */

2021-09-13T14:28:34Z

Jack

Wyleu: /* Jack */

2021-09-13T14:24:43Z

Jack

Wyleu: /* Jack */

2021-09-13T14:21:05Z

Jack

Wyleu: /* JALV starts to help */

2021-09-13T14:19:47Z

JALV starts to help

Wyleu: /* JALV starts to help */

2021-09-13T14:19:14Z

JALV starts to help

Wyleu: /* Deeper Still... */

2021-09-13T14:18:36Z

Deeper Still...

Wyleu: /* JALV starts to help */

2021-09-13T14:13:27Z

JALV starts to help

Wyleu: /* JALV starts to help */

2021-09-13T13:38:52Z

JALV starts to help

Wyleu: /* JALV starts to help */

2021-09-13T13:38:17Z

JALV starts to help

← Older revision		Revision as of 15:51, 13 September 2021
Line 111:		Line 111:

	<br clear=all>		<br clear=all>
		+
		+	== Where it gets stored ==
		+	So once an engine has been started up what else does it need to know?, given it's MIDI components, parameters and Audio in's and outs have been nicely presented to the user.
		+	How do we store all this state we are generating?
		+
		+	In the Pre LV2 age it was all explicitly defined in the code, but we can now do better. We want to be able to add,enable and disable these lv2 components that we could get hold of from 'sources' or indeed write ourselves and offer to others...
		+
		+	What maintains the LV2 zynthian universe?
		+
		+	Well there are three basic places lv2 bundles live.
		+
		+	* /zynthian/zynthian-plugins/lv2
		+	* /zynthian/zynthian-data/presets/lv2
		+	* /zynthian/zynthian-my-data/presets/lv2
		+
		+
		+	<br clear=all>
		+
		+	== LV2 Webconf configuration ==

← Older revision		Revision as of 14:28, 13 September 2021
Line 102:		Line 102:

	The World of MIDI is slower than audio but a little more involved, as we can do some manipulation in this space to really aid the performer. Transpose a keyboard by an octave? Play a chord when one note is pressed ( Bontempi Mode :-) ). By using an LV2 component to do this sort of manipulation and get all the definitions from the declared namespaces means we can make solid assumptions about precisely what effects on the sound environment we are controlling.		The World of MIDI is slower than audio but a little more involved, as we can do some manipulation in this space to really aid the performer. Transpose a keyboard by an octave? Play a chord when one note is pressed ( Bontempi Mode :-) ). By using an LV2 component to do this sort of manipulation and get all the definitions from the declared namespaces means we can make solid assumptions about precisely what effects on the sound environment we are controlling.
		+
		+	But there needs to be an important component in the zynthian world to handle the MIDI as it moves in and out of the zynthian, and this is the zynrouter. This engine is a C component and does magic :-D. This allows the zynth to manage several seperate MIDI environments that might well involve all kinds of complicated shenanigans. Oh there's a sequencer down there as well . . .
		+
		+
	And all from the zynthians setting up a few electronic conversations.		And all from the zynthians setting up a few electronic conversations.

@@ Line 103: / Line 103: @@
 The World of MIDI is slower than audio but a little more involved, as we can do some manipulation in this space to really aid the performer. Transpose a keyboard by an octave? Play a chord when one note is pressed ( Bontempi Mode :-) ). By using an LV2 component to do this sort of manipulation and get all the definitions from the declared namespaces means we can make solid assumptions about precisely what effects on the sound environment we are controlling.
 And all from the zynthians setting up a few electronic conversations.
 <br clear=all>

← Older revision		Revision as of 14:21, 13 September 2021
Line 104:		Line 104:
	And all from the zynthians setting up a few electronic conversations.		And all from the zynthians setting up a few electronic conversations.

−	~~'''JALV is the software container that the LV2 component runs in that presents the LV2 objects defined in TTL files to the zynthian.'''~~	+	<br clear=all>

← Older revision		Revision as of 14:19, 13 September 2021
Line 74:		Line 74:

	[[File:Zynthian jalv plugins.png\|right\|300px\|zynthian_engine_jalv class]]		[[File:Zynthian jalv plugins.png\|right\|300px\|zynthian_engine_jalv class]]
		+
		+	<br clear=all>

	There is a bit of defensive programmiing to prevent damaged files structures from stopping anything happening but the call is then handed up to		There is a bit of defensive programmiing to prevent damaged files structures from stopping anything happening but the call is then handed up to

@@ Line 83: / Line 83: @@
 This is where the lv2 namespace is maintained from and acts as the conduit from the zynthian to the lv2 namespaces.
+<br clear=all>
 So what is this JALV business then? Why don't we just go straight to thr LV2 componenets that actually does the heavy lifting?
 '''JALV is the software container that the LV2 component runs in that presents the LV2 objects defined in TTL files to the zynthian.'''
-Well it's time to meet that most Linux based concept.
+Well it's time to meet that most Linux based concept Jack.
 == Jack ==

← Older revision		Revision as of 14:18, 13 September 2021
Line 64:		Line 64:

	That's how it works for the explicitly defined Engines, but for going forward LV2 offers a much for implicit path, which allows lists to be populated from information derived from the LV2 TTL files.		That's how it works for the explicitly defined Engines, but for going forward LV2 offers a much for implicit path, which allows lists to be populated from information derived from the LV2 TTL files.
		+
		+	<br clear=all>

	== JALV starts to help ==		== JALV starts to help ==

← Older revision		Revision as of 14:13, 13 September 2021
Line 80:		Line 80:

	This is where the lv2 namespace is maintained from and acts as the conduit from the zynthian to the lv2 namespaces.		This is where the lv2 namespace is maintained from and acts as the conduit from the zynthian to the lv2 namespaces.
		+
		+
		+	So what is this JALV business then? Why don't we just go straight to thr LV2 componenets that actually does the heavy lifting?
		+
		+	'''JALV is the software container that the LV2 component runs in that presents the LV2 objects defined in TTL files to the zynthian.'''
		+
		+	Well it's time to meet that most Linux based concept.
		+
		+	== Jack ==
		+
		+	Jack is the Audio server that runs under the control of the Zynthian.
		+
		+	Jack takes the hardware devices presented by ALSA and allows connections to be established in a highly consistent and connected way. It's jack that takes the data from an input audio port be that a Zynthian input on an Card or a USB connected Mixer, and passes it throu' an Audio Device defined by the Zynthian ( the next section after Synths :-) ) and presents it to the output connectors and also sending it to other places like the Audio Meters on the Zynthian GUI. It also does all this magic for MIDI as well, because MIDI & Audio in the Zynthian World are rather important concepts!.
		+	Jack deals with all this stuff and the zynthian is defining the relationships in the Jack Audio world. So as Engines ain't our concern as far as how they do what they do, the actual audio environment we are running isn't processed by us. But Jack has been around for a while and seems to work pretty well and is also rugged :-D.
		+
		+	The World of MIDI is slower than audio but a little more involved, as we can do some manipulation in this space to really aid the performer. Transpose a keyboard by an octave? Play a chord when one note is pressed ( Bontempi Mode :-) ). By using an LV2 component to do this sort of manipulation and get all the definitions from the declared namespaces means we can make solid assumptions about precisely what effects on the sound environment we are controlling.
		+	And all from the zynthians setting up a few electronic conversations.
		+
		+	'''JALV is the software container that the LV2 component runs in that presents the LV2 objects defined in TTL files to the zynthian.'''

@@ Line 74: / Line 74: @@
 There is a bit of defensive programmiing to prevent damaged files structures from stopping anything happening but the call is then handed up to
 zynthian_lv2.get_plugins()in zynthian_lv2.py  to do the gory stuff. . .
 This is where the lv2 namespace is maintained from and acts as the conduit from the zynthian to the lv2 namespaces.

@@ Line 71: / Line 71: @@
 The list of engines visible came from a call to get_jalv_plugins()
-[[File:Zynthian jalv plugins.png
+[[File:Zynthian jalv plugins.png|right|300px|zynthian_engine_jalv class]]
 There is a bit of defensive programmiing to prevent damaged files structures from stopping anything happening but the call is then handed up to