Recent changes to recalls

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 06:09:34 -0000

--- v43
+++ v44
@@ -144,6 +144,7 @@

 


 ## A closer look at effects
+First we look at recall initialization and afterwards at processing audio data with run etapes.

 ### Recursive initialization
 Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=150]]
The initialization occurs in one part.
The following procedures needs to be passed:

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 06:07:03 -0000

--- v42
+++ v43
@@ -146,7 +146,16 @@
 ## A closer look at effects

 ### Recursive initialization
-Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=150]]
The initialization occurs in one part.
+Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=150]]
The initialization occurs in one part.
The following procedures needs to be passed:
+
+* Allocating group id and recall countainer.
+    * Acts as a unique identifier for runtime.
+* Duplicating recalls and pass default properties.
+    * Set up functional runtime objects.
+* Resolve dependencies and inject.
+    * Dynamic connect of objects.
+* Initialized tree recursivly as entire initialization stage.
+    * The created context is now ready to be processed ...

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:59:09 -0000

--- v41
+++ v42
@@ -146,12 +146,12 @@
 ## A closer look at effects

 ### Recursive initialization
-Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=260]]
The initialization occurs in one part.
+Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=150]]
The initialization occurs in one part.

 



 ### The different run stages
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.
AgsRecallContainer matches related recalls. This means you pack recalls of same XML type eg. ags-echo to be grouped, litteraly:
+
As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=150]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.
AgsRecallContainer matches related recalls. This means you pack recalls of same XML type eg. ags-echo to be grouped, litteraly:

 * ags-echo-channel
 * ags-echo-channel-run

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:54:36 -0000

--- v40
+++ v41
@@ -144,6 +144,13 @@

 


 ## A closer look at effects
+
+### Recursive initialization
+Initilization recusivly is done by calling ags_channel_recursive_play_init().
[[img src=AGS_run_init.png alt=Run align=right width=260]]
The initialization occurs in one part.
+
+


+
+### The different run stages
 As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.
AgsRecallContainer matches related recalls. This means you pack recalls of same XML type eg. ags-echo to be grouped, litteraly:

 * ags-echo-channel

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:48:41 -0000

--- v39
+++ v40
@@ -144,6 +144,11 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.
+As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.
AgsRecallContainer matches related recalls. This means you pack recalls of same XML type eg. ags-echo to be grouped, litteraly:
+
+* ags-echo-channel
+* ags-echo-channel-run
+* ags-echo-recycling
+* ags-echo-audio-signal

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:43:28 -0000

--- v38
+++ v39
@@ -144,6 +144,6 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
+
As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.
These recalls implementing those functions generally inherit by AGS_TYPE_RECALL_AUDIO_RUN, AGS_TYPE_RECALL_CHANNEL_RUN or AGS_TYPE_RECALL_AUDIO_SIGNAL.
Run time values are written in real time using atomic operations. This is done by AgsPort and inherit by AGS_TYPE_RECALL_AUDIO or AGS_TYPE_RECALL_CHANNEL.

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:36:13 -0000

--- v37
+++ v38
@@ -144,6 +144,6 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated
+
As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated and you may have noticed it's recursive. The run phase is divided in 3 stages with dedicated pass within tree.
run_pre() is the very first etape. Its purpose is mainly of allocating or preparing buffers.
run_inter() is the second phase and acts as effect processor.
run_post() is the third phase and is usually used for doing clean-up.

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:30:38 -0000

--- v36
+++ v37
@@ -144,8 +144,6 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
-
-[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated
+
As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:29:45 -0000

--- v35
+++ v36
@@ -144,7 +144,7 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.
+As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.

 [[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated

recalls modified by Joel Krähemann

Joel Krähemann — Sun, 30 Nov 2014 05:28:15 -0000

--- v34
+++ v35
@@ -144,6 +144,8 @@

 


 ## A closer look at effects
-As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass. This object is running the stages as illustrated
+As mentioned before audio processing will be done within an AgsRecallAudioSignal subclass.

-[[img src=AGS_run.png alt=Lifecycle align=right width=260]]

+
[[img src=AGS_run.png alt=Run align=right width=260]]
This object is running the stages as illustrated
+
+