Various aspects tuning

gourmet

3rd December 2002 20:26 UTC

Various aspects tuning
Wanted ability to tune various aspects of AVS from preset code - window size, pixel doubling and even overlay mode. Of course, beat detection and else. Probably some people dont' want allow presets change these parameters. Therefore it must be flag disabling internal tuning. Of course this flag must not be accessible from preset code.

unknownkw

3rd December 2002 20:47 UTC

The idea to include default display mode is a nice one, but why we force users to use such setting? Someone may only have a slow computer to view it, or may be something else...

Tuggummi

4th December 2002 12:10 UTC

What good is it if you can turn it off? It won't be 100% sure that the preset is viewed as it should if the feature can be turned off :igor:

Besides it would totally piss of n00bs and then they would come to this forum and yell: "AN AVS PRESET CHANGED MY SETTINGS!!!%¤#! HOW DO I PREVENT THIS!!!"!¤#"!%¤"# PLEAAAAZZZZ HELP!!!! IM DESPERATE!!"

I can't deny though that it is a nice idea, the window size setting would allow to create really different presets, but i don't think that's absolutly necessary since you can code scopes and dm's to work in all different kind of resolutions.

gourmet

4th December 2002 15:20 UTC

Guys read again - I told there must be flag disabling internal settings change. That means in Settings\Display must appear setting with 2 values:

On - Enable preset change internal settings of AVS
Off - Disable preset change internal settings of AVS.

If user is smart enough it can turn this on. For others it is off. And preset itself cannot ever change this.

gourmet

4th December 2002 15:25 UTC

since you can code scopes and dm's to work in all different kind of resolutions.

What if preset uses solid bitmap for background? If you set line width in pixels in Set Render Mode - then AVS doesnt' scale it automatically.

dirkdeftly

4th December 2002 19:51 UTC

y'know there's an edit button for that, gourmet

Anyway, n00bs wouldn't know how to turn it off (whether it was default or if they did it themselves). That, and who the fuck is going to use it? This falls under the same category as your SSC alpha blending...

gourmet

4th December 2002 20:18 UTC

Again - if you will not ever use it - that doesnt' mean nobody will. I will. Fuck.
:mad:

dirkdeftly

5th December 2002 06:59 UTC

I didn't say I wouldn't (even though I won't). I'm saying nobody else will, for the obvious reasons Tuggummi stated. If you're too stupid to see that it's not my problem :hang:

gourmet

5th December 2002 07:57 UTC

If you dont' wanna it become your problem - think more before reply to my post.
:cool:

UnConeD

5th December 2002 15:18 UTC

I don't see the point in controlling overlay mode from code... how do you think people would react when they're browsing presets and suddenly their desktop background changes?

Similarly, why control beat-detection? Write your own beat detection then...

The only option I do want is the ability for effect-lists with a different internal resolution.

For example, a half-size (or percentage size) effect list that is rescaled to normal size when blended with the rest. Similar, a fixed-resolution effect list. If they add the option for bilinear-filtering or not, this would be a better replacement than messing with the user's pixel doubling setting.

Besides, if a preset were to include code to change an option, where would it be turned back? We'd have to add an 'on unload' piece of code to every component just for this purpose. Seems wasteful to me.

gourmet

5th December 2002 16:34 UTC

Ok there are points to talk about...

I don't see the point in controlling overlay mode from code... how do you think people would react when they're browsing presets and suddenly their desktop background changes?

Overlay mode assumes that some overlayed color must be set on desktop. It is controlled by user. Of course, WinAmp could automatically change this color and run in overlay mode. For example set desktop to 0x000001 and overlay this. But it MUST warn user about it and do nothing if user declines. I do not insist on auto-overlay feature. But some presets have good look on desktop. And I'm sure many users even dont' know about desktop overlay ability. We can show it.

Similarly, why control beat-detection? Write your own beat detection then...

Hm. Why should I write my own if I could just change settings of AVS? It already has two modes - they are completely enough. I noticed my presets better look with "standard" detection. But some others with "advanced". I want set option as I see.

Besides, if a preset were to include code to change an option, where would it be turned back? We'd have to add an 'on unload' piece of code to every component just for this purpose. Seems wasteful to me.

I had an answer for this question before. But right now I just got better idea. All this can be implemented as APE. Name it - "Override settings". You can get idea from it's name. If such APE appeares in tree - AVS ignores it's default settings and uses provided by preset. And in this APE it MUST be ability set window size and position. Just imagine - window can change it's position and size while working. If expressions and variables will be available in this APE - window can even dance on screen... Jump on beat... Wow... I want this.

Of course if there is no such APE - AVS goes as now. Of course it must apply default settings each time when preset starts. Then if user selects even old preset - AVS will appear as usual.

UnConeD

5th December 2002 18:47 UTC

If expressions and variables will be available in this APE - window can even dance on screen... Jump on beat... Wow... I want this.

No offense but this sounds like a HORRIBLE idea. Why the hell would I want the window to dance on screen? And besides, how much 'dancing' can a rectangle do? It would only make it harder to view the preset, IMO. Just think about it practically. A rectangle that is bouncing around on the screen. How would you change the preset if it keeps moving around? How would you close it?
This sounds like one of those things that might be cool in your head, but suck practically.

Hm. Why should I write my own if I could just change settings of AVS? It already has two modes - they are completely enough. I noticed my presets better look with "standard" detection. But some others with "advanced". I want set option as I see.

This depends hugely on the music playing as well. There is no reason to say something will work better with one beat detection than with another.

Don't get me wrong, I'm all for progress, but you're thinking from a preset author's point and not a user. Any feature that is added should be made to allow the user to see prettier presets, nothing else.

Users *hate* anything that changes without their knowledge. I would hate it if a preset changed my overlay color or turned overlay on/off.

If only one feature could be added to AVS, I would certainly not want this, because I would turn it off the first moment it annoyed me, and never look back again.

dirkdeftly

5th December 2002 19:36 UTC

Dude, think for two seconds. If the AVS window suddenly started moving around on the screen without you telling it to, what would YOU do? If you simply accept what's happening I suggest you run Norton a few times and see how many virii you've let sit around your system for years on end.

Nobody but NOBODY wants to have messages popping up for 'Can AVS switch to overlay mode?' and 'Can AVS change your window size?' and 'Can AVS change your color settings?' whenever they open presets. Like I said before, if some n00b all of a sudden sees AVS switching corners of the screen every few seconds he'll wonder what the fuck is happening to his computer, NOT what's happening to his AVS window. Thus anyone who actually uses 'aspect tuning' is never going to be very highly regarded in the AVS community. You want your presets to get deleted a minute after they're installed? Fine by me - just do it somewhere else.

gourmet

5th December 2002 22:04 UTC

First of all I wanna set window size and change "pixel doubling" from preset. About dancing window - I would like see it on my screen. It can not only jump but float or change it's sizes. On your 3D preset camera can be synchronized with this window (if only global variables appear...). It will look as you see at large 3D world throgh floating window. About how to close it - it must stop changes if music mutes. But again - this is just an idea which I like see. As user.

And here is another problem with AVS - how to tell user what he will have while preset runs. What he must do to get preset properly looking - as author recommends. Of course there is Misc\Comment window - but to access it user has dive to preset code. O course README.TXT can be compiled and shown while installation. But it lays deeply in directories structure - not useful for further views. Special intro preset can be created and placed first in stack. But how much text can you place there? This all is not so useful to use and to create. I did not see detailed introductions. I'd prefer ability place some readme.html file to collection directory. And this file must appear on top of collection. When clicked - this file openes in internal WA browser. This allows do many things. So many.

dirkdeftly

5th December 2002 23:47 UTC

You're not listening, gourmet. NOBODY WANTS AVS TO DO THINGS THEY'RE NOT TELLING IT TO DO. If I'm just randomly switching presets, I do NOT want a pop-up asking me if I want my settings changed. No one else does either. If I'm not in control of my computer, it's virtually useless to me - my computer is here to do what I tell it to; it always has been and it always SHOULD be.
And I will say once again: If you're new to the world of AVS - not just writing, but watching - and all of a sudden you get a popup saying "The screen's going to start moving now" and every time you try to stop it you can't get a hold of it, you're not going to like AVS very much. Think about what you're asking for...just because YOU want to see that doesn't mean everyone else will.

UnConeD

5th December 2002 23:57 UTC

The only idea is like is the minibrowser integration... but only if the browser is already open.

gourmet

6th December 2002 00:04 UTC

You're not listening, gourmet.

Of course. But you are not reading. :D

NOBODY WANTS

Didnt' your Mom tell you? - Speak about yourself.

LOL

gourmet

6th December 2002 00:08 UTC

The only idea is like is the minibrowser integration... but only if the browser is already open.

Why AVS cannot open minibrowser if .html file selected? It is not just implemented. Or there are any internal problems with it? As programmer I cant' find principle problem.

UnConeD

6th December 2002 00:09 UTC

Argh... because when I'm watching presets I don't want the friggin' minibrowser to open in my face. I want to watch presets. It has nothing to do with physical limitations, but what you should and should't do.

dirkdeftly

6th December 2002 03:01 UTC

It's like a popup - but worse.

Didnt' your Mom tell you? - Speak about yourself.

Was that supposed to be funny? Was that even supposed to have a point?

gourmet

6th December 2002 10:09 UTC

because when I'm watching presets I don't want the friggin' minibrowser to open in my face

Of course in auto-switching mode AVS must open only presets. Minibrowser has not appear. It must be opened if only you select "readme" in top of collection list from presets folder.

dirkdeftly

6th December 2002 17:35 UTC

You're making this far too complicated - for the AVSer AND the user. Remember, not all (in fact few) users will be able to understand any of this. If your idea were implemented, no one would use AVS because of the hassle involved.

gourmet

6th December 2002 18:19 UTC

For authors:

1. Ability to store .html or .txt file appeares. File must me stored in same folder where collection of presets lay. Simple txt will be shown in browser as non-formated text. HTML will be shown as hypertext with ability place links to author's home page, WinAmp pages, skins, pictures and so on. File can have any name but ONLY ONE such file will be accepted bu AVS. One call of
findfirst("*.html"|"*.txt")/*in C-like terms*/ will be made and accepted by AVS, other files will be ignored.

For users:

1. One item with file's name appeares on top of presets list in collection submenu. When selected WinAmp openes minibrowser and shows this file there.
2. When auto-switching presets AVS openes only .avs files.

I do not see here anything complicated.
That is not more complex than create or view single-page Web-site.

Looks like you never did programming and never worked with users. They are smart. Beleive me - I'm university graduated MS in computers and work in this area last 15 years. I created software with powerful interface (even before and after MicroSoft appeared). Users were glad use it.

Clashman

16th December 2002 14:05 UTC

Originally posted by gourmet
For authors:

1. Ability to store .html or .txt file appeares. File must me stored in same folder where collection of presets lay. Simple txt will be shown in browser as non-formated text. HTML will be shown as hypertext with ability place links to author's home page, WinAmp pages, skins, pictures and so on. File can have any name but ONLY ONE such file will be accepted bu AVS. One call of
findfirst("*.html"|"*.txt")/*in C-like terms*/ will be made and accepted by AVS, other files will be ignored.

I'd have to agree that a README file for a preset pack that used anything that you suggested should, indeed, be included. However, it should be displayed before installing the preset pack - perhaps in the installer, for example?

But also extracting it to the pack's storage area is a good idea, so that you can prove to anyone else who might want to see these "cool new presets" that you've downloaded (and starts screaming "DUDE, YOU'VE GOTTEN A VIRUS!" when this stuff happens) that "No, it's not a virus, it's supposed to happen, see right here in the readme? See right here in the preset tree? There ya go, proof positive..."

For users:

1. One item with file's name appears on top of presets list in collection submenu. When selected WinAmp openes minibrowser and shows this file there.
2. When auto-switching presets AVS opens only .avs files.

I do not see here anything complicated.
That is not more complex than create or view single-page Web-site.

1. TGHat would make perfect sense - having the minibroser only open the file when it's selected in the "Open..." dialog box.

2. THIS SHOULD BE COMMON SENSE. AVS is compatible with AVS files - ONLY. It can render bitmaps and AVIs, but it CANNOT - REPEAT, CANNOT - read HTML. For that you'd need the minibroswer, Internet Explorer, Mozilla, Opera or Netscape Navigator.

gourmet

16th December 2002 17:02 UTC

I'd have to agree that a README file for a preset pack that used anything that you suggested should, indeed, be included. However, it should be displayed before installing the preset pack - perhaps in the installer, for example?

It can but default installer script doesnt' contain this feature. You have to rewrite the script to add this. I thing it is not useful for most developers. Better include readme feature to NSIS by default.

But also extracting it to the pack's storage area is a good idea, so that you can prove to anyone else who might want to see these "cool new presets" that you've downloaded (and starts screaming "DUDE, YOU'VE GOTTEN A VIRUS!" when this stuff happens) that "No, it's not a virus, it's supposed to happen, see right here in the readme? See right here in the preset tree? There ya go, proof positive..."

Yessss.....

THIS SHOULD BE COMMON SENSE. AVS is compatible with AVS files - ONLY. It can render bitmaps and AVIs, but it CANNOT - REPEAT, CANNOT - read HTML. For that you'd need the minibroswer, Internet Explorer, Mozilla, Opera or Netscape Navigator.

The only changes of AVS code must be - findfirst() html or txt file in presets folder, display it's name on top of presets list. If this name selected then just DDE it to WinAmp mini-browser. Period. All other non-avs files will be ignored. When doing auto switching presets AVS will ignore all non-avs files. As it does it now.

Why use other viewers if you already have mini-browser near and skinned?

Clashman

17th December 2002 13:21 UTC

Originally posted by gourmet

The only changes of AVS code must be - findfirst() html or txt file in presets folder, display it's name on top of presets list. If this name selected then just DDE it to WinAmp mini-browser. Period. All other non-avs files will be ignored. When doing auto switching presets AVS will ignore all non-avs files. As it does it now.

Why use other viewers if you already have mini-browser near and skinned?

I was merely making a point - the point being that AVS, by its design, ins incompatible with, and thus unable to display, HTML files. And, as I also said, in order to display them, you would need an HTML-enabled program or program plugin on your system.

Examples would be:

1) The Winamp Minibrowser
2) Netscape Navigator
3) Internet Explorer
4) Opera
5) Mozilla

I could go on, but I think I've made my point. Also, some people don't always use the Winamp Minibrowser, so, if the Minibrowser isn't enabled, they can choose to either:

1) Activate the Minibrowser to read the HTML/TXT readme
2) Use the default Web broswer on their system (usually Internet Explorer or Netscape Navigator) to view the HTML readme

or

3) open Notepad/WordPad/other word processing software to read a TXT readme.

gourmet

17th December 2002 15:56 UTC

I was merely making a point - the point being that AVS, by its design, ins incompatible with, and thus unable to display, HTML files. And, as I also said, in order to display them, you would need an HTML-enabled program or program plugin on your system.

Sure and in common case user already has it. Can you imagine any one networked computer running WinAmp and not having Web-browser? I can imagine but I would greatly surprised by it and I'd not recommend it's owner open HTML files. :D

I could go on, but I think I've made my point. Also, some people don't always use the Winamp Minibrowser, so, if the Minibrowser isn't enabled, they can choose to either:

Yes, if WinAmp mini-browser is not installed - then AVS has to run "default browser". If it failes then just message - "Not available display text file."

Even WA-mini-browser containes Internet Explorer builtin as DCOM object. (may be not IE but "default browser" - I didnt' dive deep)

3) open Notepad/WordPad/other word processing software to read a TXT readme.

Not necessary. All browsers you listed can clearly read and display .txt files. Just use default browser for txt. Easer select codepage if needed. And this is more universal and easer to implement - no code needed to tune to operating system. Just "open default Web-browser" even for .txt file. Simple.

dirkdeftly

17th December 2002 18:11 UTC

God, gourmet, would you just drop this?

UnConeD

17th December 2002 18:27 UTC

I agree with Atero... if you're so bent on it, write it yourself as a 'misc / comment HTML' ape or something, it's not that hard. But aside from Clashman no-one seems to want it. I think it's a horrible feature, and I'd refuse to download any pack that popped up annoying HTML when I'm viewing it.

(Idem for installers that close down your Winamp, change your preset-switching options, change the resolution, etc.)

Clashman

17th December 2002 19:48 UTC

Just 'cause you two think Gourmet's idea sucks doesn't mean EVERYONE does (case in point: ME).

Also, who ever said that the readme had to pop up every time a preset from the pack was loaded? It could easily pop only the first time a preset was loaded.

Example script for such a thing (in the completely fictitious but easy to understand ClashScript language):


if TimesLoaded>0 and Preset LoadedFromDirectory=yes then noexecute #onload

This checks the PresetLoadedFromDirectory flag, which answers the query "Was a preset loaded from directory c:\Program Files\Winamp\wacs\avs\{directory}?" and the Times variable, which answers the question "How many times was a preset loaded from this directory?". If both answers are negative, then the #onload string executes.


#onload(c:\Program Files\Winamp\wacs\avs\{directory}\*.avs) set PresetLoadedFromDirectory=yes,TimesLoaded=1,loadfile(c:\Program Files\Winamp\wacs\avs\{directory}\readme.txt)

This sets the Preset Loaded From Directory flag in the script to "yes" and the variable Times to "1" - these are the key flags for the previous ClashScript line.

gourmet

17th December 2002 20:50 UTC

Looks like you didn't get idea... Preset or else will not pop-up anything if you dont' want. Only if you choose first line in presets collection placed in separate folder - then browser with readme text will appear. This line can be separated from presets name by line - dont' click on it and you wont' get help. Even this line can be last...

About write APE - I'll think. If only it is possible create an APE which can access and change presets list collected by AVS. Right now I have no C++ compiler installed on home computer. At work I do rather different things.

dirkdeftly

17th December 2002 22:08 UTC

How many times will we have to tell you this: *MOST* people will NOT know how to turn that feature on or off - once they turn it on it gets really annoying and they rant at us and stop using AVS, if they can't turn it on it's pointless.

gourmet

17th December 2002 22:27 UTC

You (and only YOU - guy with cat face) can tell this as many times as you wanna. Cause you finally lost discussion line... :p

For others I post here picture - how it can look. This is a possible look of collection submenu. Right to this menu is common presets menu. Picture made in Photoshop of course. And I have a point - readme file can be automatically opened ONLY while collection installation. And better after request "View readme file" (Yes\No).

dirkdeftly

17th December 2002 23:26 UTC

Fine then, completely shut out our logic and we'll shut out your stupidity. I agree with UnConeD - if you're so fucking bent on making this work even though NOBODY else wants it, then make your own fucking APE and watch your packs get twenty downloads and twenty 0 star ratings.

And yes I mean WE - I'd bet a million bucks 99% of the community here is smart enough to see how blatantly stupid your idea is.

gourmet

17th December 2002 23:44 UTC

WOW! GUYS! Here is a man with

$1 :D:D:D :D:D:D (one million)

and he wants give'em out!

Lets' just calculate - how many people are here and how many of us wanna have feature to create readme option. If we will get more than 1% of community - then we will share this $1 000 000 between all who said "Yes, I want this feature"! COMMON!!!

dirkdeftly

18th December 2002 01:43 UTC

Ahem, if I may quote? Considering there's only about 20 people in this community in the first place...

Looks like you didn't get idea

Majority rules - and I'm pretty damn sure you aren't going to get more than 20%, let alone 50%. Even if you DID get half the community, that's still half that are opposed, and that's half the people's AVS that you're going to be virtually smashing to pieces since half the people that see yours are going to say 'screw AVS, it's a piece of shit.'

But no, it's all about you. You want it. You're going to get it. You are NOT going to give up, by God, you're not going to listen to any decent logic, you're not going to think about the downsides, you want it and you WANT IT NOW. Have some consideration, asshole :mad:

Nic01

18th December 2002 02:09 UTC

On gourmet's idea :

Yes, but no...

Switching windowsize is all I want - It will help other people to get the most out of a preset, but...

1) Newbies will make this a source of problems. Defaulting it to off will only delay their pleads for help, not prevent it.
2) Newbies with fast comps might set it to a high resolution, which will annoy people with slower computer.
3) Newbies will have bad reactions to presets that change AVS around (Example : AVSociety packs...)
4) It's likely that only experienced people will use it properly - Newbies will do odd things with this, trust me.
5) Default resolution for non-windowsize changing preset.

So, my final decision? No. I like the idea and it might come in handy, but only experienced artists will use it properly, and with the sheer amount of newbies...

UnConeD

18th December 2002 08:21 UTC

a) Make APE that pops up a browser window/ minibrowser (using DDE)
b) Make a preset including only this APE as "Readme.avs"
c) Make sure this preset shows up at the top/bottom of the preset list (extract them in the order you want them to show up)

Voila, you have your annoying feature without bugging anyone else :P.

gourmet

18th December 2002 09:56 UTC

you're not going to listen to any decent logic

Bother. You have no logic in your posts. Create preset or else and publish here - then I'll suppose you can think logically. Who are you? Owner of NullSoft? Author of AVS (with it's limited scripting language)? I'd better follow UnConed recomendations but not your's. Cause you have no recomendations. I tried find any component submited by you. No one. Since Jun 2001 - date of your registration - you didn't submit anything. You are just a "poster". Poster posting postings. They are not significant at all. You dont' give any positive idea cause you have no them. You are just characters on my screen wasting bits in RAM of my computer. Then shut up and go read manuals in the corner. Probably you will get smarter than lame moron. Someday.

Make APE that pops up a browser window/ minibrowser

When I'll have time - maybe I'll make it. Now I'm a businessman and have few of time to create anything more complex than presets. And I have another more complex idea about 3DVS - same as AVS but with OpenGL built-in. I'm going download and read NullSoft programming docs after NewYear. Until this I'll have no much time. And I have a point - readme feature must be supported by AVS intebally. To simplify create readme - just drop a text to folder and viola.

Can anyone tell me - does AVS allow for APE change collection submenu content?

dirkdeftly

18th December 2002 17:48 UTC

I've submitted 4 packs - the nullsoft search engine just sucks, that's all. The first 3 were getting used to AVS, the other one was The Forward Flow 1.0 and it's on the presets forum somewhere, and on deviantART; I haven't gotten it submitted because some WA.com glitch won't let me. TFF2.0 is done, the installer needs work before I'm submitting it. TFF3.0 is started with 4 presets so far.

You, as far as I know, have submitted 1 pack of VU-meters, the easiest effects on earth.

Now, I've told you several reasons why this idea won't work; UnConeD and Nic01 have just repeated them. Newbies will not like this because they won't be able to figure it out - you were a newbie once (and as far as I can tell, you still are), think about it: You, at one time, fiddled with the undocumented settings of AVS to figure out what they did. Chances are nine out of ten people new to AVS are going to do the exact same thing and freak out when they see the window changing or jumping around on the screen when they don't know why, even if you provide a readme - who reads readme's anyway?

The only part of this that could possibly be useful would be radio buttons for "Snap window size to..." for 4x3, square etc. Otherwise we get complaints like "AVS is freaking out!!! PLZ HLP!!!!!1" As Nic01 said, with the sheer amount of n00bs that play with AVS we're gonna get swamped with shit like that.

I don't know how I can make that any clearer to you... :hang:

gourmet

18th December 2002 19:51 UTC

I already told you - when you wanna answer me - think several times. Probably you tried. Unsuccessfully...

You, as far as I know, have submitted 1 pack of VU-meters, the easiest effects on earth.

1st - they are not effects. Dont' mix up effect and complete preset.
2nd - may be they are simple (for me) but no one created same before.
3d - You cannot calculate. There were 2 packs of VU-meters. Even you tried tell something stupid in comments for second pack. And there is already another one pack of presets submitted by me. All 3 packs appeared in 2 mounths. And latest packs already had several updates.
4th - "The easest" 1st pack earned more than 50 000 downloads in 2 mounths... If you would more clever - you'd probably understand - not complexity is important. "All genious is simple" - that is ancient truth.

I can point you to some WA2 skins and tool for creating skins. I posted them years ago under another nickname.

because some WA.com glitch won't let me

I've got those glitches - but asked about them, got answer from Rovastar and finally uploaded all. You cannot? That's not only server problem but more your's. Weak? Try Centrum.

I've got "The page cannot be displayed" while trying see your pack TFF on deviantart.com. 3 times. All other pages I see properly. Loser? Try other servers.

you were a newbie once (and as far as I can tell, you still are),

The mark "major dude" or "junior member" relates ONLY to registered nickname but not to a person. Name registered and relative to this site only. Do you understand what is "relative"?

Here I first typed then removed some words about much more complex (if you like complex) things I made and do now. At least I hardly used USENET since 1988 and Internet since 1994. If you still will think that I'm a junior - then I'll post some more words about me. Dont' call me junior or you will sorry.

see the window changing or jumping around on the screen

I talk only about readme feature through all latest several pages. README FEATURE for all kinds of presets. If you didnt' notice that probably you cannot read. I cant' help you in this.

who reads readme's anyway?

All who can read. That doesnt' relate to you.

I don't know

That's right!

Of course if I start talk to anybody - I suppose he is more smart than he finally shows...

dirkdeftly

18th December 2002 22:34 UTC

A bit full of ourselves, aren't we...?

First of all I meant AVS newbie, which you have to have been because you can't be experienced at AVS the first time you use it - it's not documented at all. Even my AVS Primer (which I forgot to mention) isn't enough to go off of when you first are introduced to AVS.
I don't give a shit how many downloads you've gotten, you're still not good enough of an AVS-er that you can brag about them. Complexity doesn't actually matter in your actual presets; it's how complex you can make them that shows your experience.

I don't remember your second pack - frankly I didn't pay much attention to them. Also, just because you were first doesn't mean it's good. The reason nobody (else)'s done VU meters is because nobody has bothered with them.

And honestly, I wouldn't go to that much trouble just to get my packs submitted at WA. The Winamp AVS reviewers (staff and users alike) are assholes - you saw what happened to Whacko VI...The only reason I submit to deviantART is because it's quick and easy - I'm not "big enough" in the AVS community yet that they'd actually get very much attention. I'd MUCH rather post them here, to the people I know and who aren't just going to shoot it down at first sight.

Whether the AVS window is jumping around on the screen or popping up some annoying HTML document every time you load, it's still fucking annoying and nobody's going to look at any presets they saw that used this. Newbies would either abuse it and/or get fed up with AVS because of it. Once again - if you're so bent on getting this into AVS, WRITE YOUR OWN FUCKING APE.

gourmet

18th December 2002 23:12 UTC

Winamp AVS reviewers (staff and users alike) are assholes

Guys - I'd offend to this... And he took the right to speak on behalf of you all...

Whether the AVS window is jumping around on the screen or popping up some annoying HTML document every time you load

He finally prooved he is idiot... Sorry guys. I'll never answer him more. Unfortunately I cant' block his posts in threads I create?...

UnConeD

18th December 2002 23:31 UTC

Argh shut up both of you. You haven't contributed anything significant to this thread in about 10 posts each.

Gourmet: if you want this feature, code it yourself or find a coder who'll do that for you. An APE cannot modify the menu's itself, but I layed out an easy way to get around this earlier, without having to recode AVS at all: i.e. everyone's happy.

Atero: if you don't like it, don't respond to it.

Oh and why the heck should the author of a thread be able to control who posts in it? There's no difference between replying to an existing thread or creating a new thread. In fact, implementing something liek this would probably make people create new, unnecessary threads for their questions because they want to be in control.

dirkdeftly

19th December 2002 04:17 UTC

What, can't think of any more blatantly incorrect assumptions to spew? Good. Cos I'm fucking tired of your bullshit.

Oh, and maybe I should revise my statement: The consistent user reviewers are assholes. The staff reviewers are just blissfully ignorant of reality.