584
edits
Changes
Jump to navigation
Jump to search
Line 108:
Line 108: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→create_screens
Then the zynthian_gui Object is defined.
Then the zynthian_gui Object is defined.
==== Functions ====
===== create_screens =====
The zynautoconnector is started which establishes the jack client connection to the Jack Server that does all the actual audio and midi processing, and runs this in it's own thread and handles the locking to ensure components play nice.
The global references for the audio recorder, the mixer and the sequencer are instantiated from there modules
{| class="wikitable"
|+ Caption text
|-
! object !! module !! function
|-
| self.audio_recorder || zyngui/zynthian_audio_recorder || Audio Recorder
|-
| self.zynmixer || zynthian_engine_audio_mixer || Mixer
|-
| self.zynseq || zynlibs/zynseq || Sequencer
|}
A dictionary called screens is defined and this has string keys that points to the individually defined screen objects that display the appropriate screens is defined and the value of the dictionary si set to the instantiated object from the .zyngui modules.
# Create Core UI Screens
self.screens['info'] = zynthian_gui_info()
self.screens['splash'] = zynthian_gui_splash()
self.screens['loading'] = zynthian_gui_loading()
self.screens['confirm'] = zynthian_gui_confirm()
....
The main menu is set depending on the zynthian kit...
and the zynthian device manager is instantiated.
Then the threads and polling mechanisms are started .