Skip to main content

Topic: Resource Hacking VIS AVS (Read 1168 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • stem0man
  • [*]
Resource Hacking VIS AVS
Noticed today while beginning to learn AVS presets using the Winamp AVS Plugin (2.83) the word
"Winamp" in the editor window. Easily changed using Resource Hacker to "AdVanCeD ViSUALiZaTION StUDIO".

It's waaaayyyy neat. Probably change the About dialog too.

Tried to add a button to one of the render dialog boxes but it didn't appear (but did manage to block
out text when I first positioned it incorrectly) it was invisible but affecting.

Makes me wonder if adding elements would allow further access to whatever the in Windows the
plugin is communicating with...I might figure it out but then I'd probably have to "dream in code"
or something....


  • ExUser
  • [*][*][*][*][*]
  • Read-only
Resource Hacking VIS AVS
Reply #1
You know that the source code for AVS is freely available, right?

  • stem0man
  • [*]
Resource Hacking VIS AVS
Reply #2
Yeah, I had heard something like that. I'll have to get my C binoculars on and browse
through I did a few years back looking through the Audacity source code trying
to figure out how to write Nyquist plugins!  I prefered looking through the LISP OOP
sourcecode, but I thought I might find out something useful............

Oh yeah, as an added bonus (to you for reading this thread), going through the
AVS settings, I noticed that the FPS is by DEFAULT set to around 60 frames per
. As most film is 24-30FPS and most animation is 12FPS, setting this
lower makes sense (and probably reduces processing power as less frames
probably need to be processed). The result is a much, how shall I say, smoother
graphics animation. Less headache and (probably) less chance for epiliptic attacks
or immediate hypnosis...

Of course, this setting applies to all plugins (not just specified plugins) and needs to
be set in the DISPLAY options AND the FULLSCREEN options. I suppose you could
mention your programming FPS in a comment or something or a README....
  • Last Edit: 12 December, 2012, 06:55:08 PM by stem0man