0 Members and 2 Guests are viewing this topic.
In AIMP 5.40 I currently use a thread mouse hook (WH_MOUSE) and learn the canvas position from the first Click, which is fragile and depends on the skin.
2. KeyboardA focused visualization gets no keys; everything goes to AIMP (Space = play/pause). Optional key events for the focused visualization would help, or a note in the SDK docs that plugins should register actions via IAIMPServiceActionManager for hotkeys.
Draw is called at a fixed ~32 fps, also in fullscreen on 120/144 Hz displays. Fast animations judder. Suggestion: a flag or method to request a higher rate, e.g. monitor refresh rate.
all samples since the last call, or a ring buffer with a running sample counter or timestamp per block;
the sample rate and channel count of the data in TAIMPVisualData (maybe in Reserved). Today I read AIMPSoundOut\DeviceFreq from the config, which is undocumented.
The spectrum values are not normalized (a sine at 0.5 gives about 365). A note on the scale in the docs would help.
Album art via IAIMPServicePlayer::GetInfoAIMP_FILEINFO_PROPID_ALBUMART is empty there, even for a FLAC with an embedded cover. Only IAIMPServiceAlbumArt::Get2 returns it, and that works well. Either filling the property or a note in the docs would save research.
8. IAIMPExtensionCustomVisualizationThere is no name and no Initialize/Finalize. Draw runs at 32 Hz from startup, even when nothing is playing. A short description of the intended use (data feed for external windows?) would help.
This type of visualization provides an ability to render visualization outside of the visual display of player, and not depended from user choice.
My frame implements it, but in 5.40 DialogKey/SelectFirstControl are never called. Tab only moves between AIMP's own controls (tree, buttons) and never into a plain Win32 frame. Is there a condition for the helper to be used? Just a small example would help.
The double click no longer switches to fullscreen, and the wheel no longer changes the volume.
The double click no longer switches to fullscreen
two more actions, for example AIMP_VISUAL_ACTION_DOWN and AIMP_VISUAL_ACTION_UP, and a way for the plugin to say "handled". AIMP would then not start moving the window, and MOVE would keep coming while the button is held, also outside the display. Then plugins with draggable controls would not need a hook at all.
Does AIMP call Draw(RGBQUAD* Buffer, …) instead of Draw(HCANVAS, …) once the plugin returns this interface?
Is the buffer always the size of the display (from Initialize/Resize) with a stride of width × 4?
Is it faster than drawing into the canvas, also in 64-bit and in fullscreen