diff options
Diffstat (limited to 'src/engine')
| -rw-r--r-- | src/engine/AudioBuffer.hpp | 2 | ||||
| -rw-r--r-- | src/engine/PortImpl.hpp | 2 | ||||
| -rw-r--r-- | src/engine/QueuedEngineInterface.hpp | 14 |
3 files changed, 4 insertions, 14 deletions
diff --git a/src/engine/AudioBuffer.hpp b/src/engine/AudioBuffer.hpp index 513c188f..b93e2267 100644 --- a/src/engine/AudioBuffer.hpp +++ b/src/engine/AudioBuffer.hpp @@ -74,7 +74,7 @@ private: size_t _size; ///< Allocated buffer size size_t _filled_size; ///< Usable buffer size (for MIDI ports etc) State _state; ///< State of buffer for setting values next cycle - Sample _set_value; ///< Value set by @ref set (may need to be set next cycle) + Sample _set_value; ///< Value set by set_value (for completing the set next cycle) FrameTime _set_time; ///< Time _set_value was set (to reset next cycle) }; diff --git a/src/engine/PortImpl.hpp b/src/engine/PortImpl.hpp index be96a910..a2eaf2c9 100644 --- a/src/engine/PortImpl.hpp +++ b/src/engine/PortImpl.hpp @@ -65,7 +65,7 @@ public: * * Audio thread. * - * \param poly Must be < the most recent value passed to prepare_poly. + * \a poly Must be < the most recent value passed to prepare_poly. */ virtual bool apply_poly(Raul::Maid& maid, uint32_t poly); diff --git a/src/engine/QueuedEngineInterface.hpp b/src/engine/QueuedEngineInterface.hpp index 73c790c8..89810434 100644 --- a/src/engine/QueuedEngineInterface.hpp +++ b/src/engine/QueuedEngineInterface.hpp @@ -41,20 +41,10 @@ class Engine; * This is the bridge between the EngineInterface presented to the client, and * the EventSource that needs to be presented to the AudioDriver. * - * This is sort of a state machine, \ref set_responder sets the Responder that - * will be used to send the response from all future function calls. Stateless - * protocols like UDP/OSC can use this to set a different response address for - * each event (eg incoming UDP port), but engine/client interfaces that don't - * need to change an 'address' constantly can just set it once on initialisation. - * Blocking control interfaces can be made by setting a Responder which signals - * the caller when the 'response' is 'sent'. - * + * Responses occur through the event mechanism (which notified clients in + * event post_process methods) and are related to an event by an integer ID. * If you do not register a responder, you have no way of knowing if your calls * are successful. - * - * FIXME: this isn't really "queued" entirely, since some events aren't queued - * events and get pushed directly into the realtime event queue. Should that - * be separated into a different interface/client? */ class QueuedEngineInterface : public QueuedEventSource, public EngineInterface { |