m (Jkuehn moved page Lesson 17 to Lesson 17 Tut3 without leaving a redirect) |
No edit summary |
||
| Line 3: | Line 3: | ||
| ueberschrift = First Steps: {{PAGENAME}} | | ueberschrift = First Steps: {{PAGENAME}} | ||
}} | }} | ||
{{DMXC3_lesson/en}} | {{DMXC3_lesson/en}} | ||
{{NavigationTop-Tut3 | {{NavigationTop-Tut3 | ||
| | | LinkBackwards = Lesson_16_Tut3 | ||
| | | TextBackwards = Lesson 16 | ||
| | | LinkForwards = Lesson_18_Tut3 | ||
| TextForwards = Lesson 18 | |||
| | |||
}} | }} | ||
==Overview== | ==Overview== | ||
| Line 42: | Line 38: | ||
And now the question remains, how it will be allocated between the results of the analysis to beat the device properties and cuelist. You already have an idea? ... Of course, this is also consistent in the'' 'input Assigment''' concept introduced in( | And now the question remains, how it will be allocated between the results of the analysis to beat the device properties and cuelist. You already have an idea? ... Of course, this is also consistent in the'' 'input Assigment''' concept introduced in(Lektion_22_Tut3). | ||
{{Bild_mit_Unterschrift |DMXC3L17 PluginAudioAnalyserInputAssignment.JPG|2|Zuordnung der Soundevents im Input Assigment|center|600px}} | {{Bild_mit_Unterschrift |DMXC3L17 PluginAudioAnalyserInputAssignment.JPG|2|Zuordnung der Soundevents im Input Assigment|center|600px}} | ||
| Line 55: | Line 51: | ||
==Certificate== | ==Certificate== | ||
I have understood the topics of this lecture and want to continue with next course: | I have understood the topics of this lecture and want to continue with next course: | ||
Lesson 18 | |||
[[de:Lektion 17]] | [[de:Lektion 17]] | ||
| Line 62: | Line 58: | ||
__NOTOC__ | __NOTOC__ | ||
__NOTITLE__ | __NOTITLE__ | ||
{{NavigationTop-Tut3 | {{NavigationTop-Tut3 | ||
| | | LinkBackwards = Lesson_16_Tut3 | ||
| | | TextBackwards = Lesson 16 | ||
| | | LinkForwards = Lesson_18_Tut3 | ||
| TextForwards = Lesson 18 | |||
| | |||
}} | }} | ||
[[ | [[category:DMXControl 3]] | ||
Revision as of 00:21, 13 January 2013
Template:Hauptüberschrift {{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|
- preamble
- lesson 1: Installation and configuration
- lesson 2: The GUI panel concept
- lesson 3: Creating and patching fixtures
- lesson 4: The live view panel
- lesson 5: Setting properties with property panels
- lesson 6: Output plugins
- lesson 7: Summery and details - Setting
- lesson 8: Scenes (cues) and scene lists
- lesson 9: Fanning, chasers and other effects
- lesson 10: The programmer view
- lesson 11: Trigger concepts
- lesson 12: Editing scenes and scenelists
- lesson 13: Presets
- lesson 14: Summary and details - Programming
- lesson 15: Working with parallel scene lists
- lesson 16: Softpult
- lesson 17: Artnet
- lesson 18: Multi-media: Beamer tool, Matrix etc.
- lesson 19: Other clients and plugins (Android, iOS, ...
- lesson 20: Create new device definitions
- lesson 21: free topic
- lesson 22: Hints for testers and test reporting
- appendix1: Summary of commands ans shortcuts
- appendix2: Kernel menu tree
}}
Overview
Here the audio analyzer is presented which is implemented as a plugin in DMXControl 3.
Lecture 17: Audio Analyser
The audio analyzer is implemented in DMXControl 3 as plugin and and you will have to enable it via Plugin Manager. It then appears as a menu item under Windows -> Audio Analyser. The audio analyzer provides essentially the same features as the Soundanalyser(Soundanalyser) of DMXControl 2.
 |
This plugin is still in an experimental stage. |
Template:Bild mit Unterschrift
The main purpose of audio player is the automatic generation of beats from a song in order to trigger the beats in a beat-driven cue list.(see Lesson 11: Trigger).
The plugin contains several tabs:
- Devices is responsible for the configuration. Here you choose the particular audio input
- WithVU meter, Spectrum and Beat Detection you can select the different analysis method
- Mood should analyse automatically and in real time the mood of an audio signal and the "Automatic Sound Controlled Light Show" lead (Vision!)
- Using Beat generator You can manually create the Beats (Tap-key) or a special clock (BPM) pretend
And now the question remains, how it will be allocated between the results of the analysis to beat the device properties and cuelist. You already have an idea? ... Of course, this is also consistent in the 'input Assigment' concept introduced in(Lektion_22_Tut3).
Template:Bild mit Unterschrift
==Excercise==* Activate the AudioAnalyser. If your sound card does not have an internal redirection and you currently have no external player available, use the microphone input as a substitute.
Additional links and references
Certificate
I have understood the topics of this lecture and want to continue with next course: Lesson 18
| |||||||||||||