Sweet

[redi jedi]

i figured out how to send q1-q8(after the wave1 per-point) back to the preset per-frame/per-pixel sections :cool:
i'm gonna add new vars w1-w8 that will act just like the q vars but they are set to the value of the q vars after the per point code. this will also give us more vars to pass from preset code to wave/shape code and will be fully backwards compatible with all presets.

i also am increasing the max user vars, 30 just doesnt cut it :D

so..um.. well ya. milk on!

[redi jedi]

ok here we go, w1-w8 return q1-q8 after wave1 per-frame/point code. 10 extra user_vars.
just drop it in your winamp/plugins folder, does'nt overwrite orig MD

[redi jedi]

ok here we go, w1-w8 return q1-q8 after wave1 per-frame/point code. 10 extra user_vars.
just drop it in your winamp/plugins folder, does'nt overwrite orig MD

its to big for one post so i broke it up

[redi jedi]

part 2

[redi jedi]

part3

[redi jedi]

d/l all three and put in same dir, then open part 1, and extract to winamp\plugins

[Phat]

rock!

[redi jedi]

:D :D :D :D

[Rovastar]

Cool.

I have uploaded it here

http://www.milkdrop.co.uk/beta/vis_milkbeta.dll

to make it easier for peoplet to download.

[redi jedi]

thanks rova.
btw now i'm working on making it so you can use all the menu items for waves in the perframe and per point code. being able to edit samples on the fly will be cool, oh and enabled wont be included(as once the wave is disabled, it makes it kinda hard for it to turn itself back on) but i could prolly put that in the preset per frame, if anyone thinks that would be usefull(may save some fps)

[Phat]

YAY!

[redi jedi]

ya know, i had the HARDEST time finding that damn X button in VisualStudio 6, but i finaly did! :rolleyes:
anyway, made some presets for MDbeta, using Eos's frequency analysis, i used the w1-w8 vars i added to md to bring her bands analysis back to the perframe code, then i adapted my Beatdection to work with the new values.
also used her glowsticks waves for renders, and one of phats borders, anyway, you'll see....
i'm pretty happy with the way it works, the beats seem like there more in phase, i also put in my template w/eos's frequency code+my modded beatcode, incase someone wants to play with it, see how it works

[someusername]

I haven't downloaded it yet but it sounds cool. Great job dude. However i think we should wait for a while before we all start writing presets for it (until it's "officially" available for download)

[Phat]

"However i think we should wait for a while before we all start writing presets for it (until it's "officially" available for download)"

If by that you mean bundled with winamp, that would most likey take years.

Me and Eo.s just haven't had a chance to touch it yet.

[redi jedi]

i just wrote those to show the new function, dont really plan on making any more (takes away from programing time :D )

still working on the shape texture(stays from last preset change).
i came up with another idea - having a var in the shape/preset code, that defines wither or not to update the texture, like say;
if(q1(just for example)=1)
shape_tex = lastframe_tex;

that way, we could do on beat changes of the texture or whatever we want. mabye even the same thing for the echo(dunno) if i can figure out how to use dx8, i might beable to add diffrent blending options, like VIS.

[Phat]

more options = cool

[redi jedi]

if anyone has ANY ideas/wants(i'm running low) for new features please post them or e-mail me
the_good_sir_robin@yahoo.com

[StudioMusic]

Redi, this might be something you might be able to try, but something I have always wanted in milk. To have a counter show up for winamp volume when you are in fullscreen (you know the up and down arrow. If this seems like something you can do let me know. It will be years before I can do it. The learning curve for Visual Studio 2003 which I just installed is going to take me some time (which I do not have much of) still modding my last preset, so it is probably something that I will never get to and even if I did it will take me a long long time to figure it out. I am still working on the drum and bass track for my next song plus many other things. SM

[redi jedi]

i have only just started with renders, and i mean like a few hours ago when i found myself at microsoft.com browsing the directx information(not that i have an explaination on how i got there or, why it took me so long to leave) but if you mean like a "slider" bar that shows/tells you the volume level, i guess one might use a rectangle of some size to signify the full volume, and a rectangle of the same hight, but a width that is equal to the current volume * ratio of full vol/full rectangles width.... or something.
sorry if i make no sence, its late, and my for loop needs to end soon... zzzzzzzzz

[StudioMusic]

It made perfect since. Or maybe something like a counter that pops up when you hit the volume keys something like 1 to 100, if the volume was half way when you hit it it would say 50 and go higher and lower accordingly. SM

[shifter]

Hehe.. be careful what you ask for! i've been wishing for milkdrop updates for ages..

A couple of things i can remember thinking would be neat:

The ability to change the position of the texture on the shapes

An option for seamless texture wrapping i.e. instead of grabbing from the opposite side of the screen at the edges, it would use a flipped version of the nearest edge, if that makes sense?

Customisable post-processing filters :D

I have no idea how complex or otherwise these would be to implement, but having any of them would be sweet

[Rovastar]

Originally posted by Phat
"However i think we should wait for a while before we all start writing presets for it (until it's "officially" available for download)"

If by that you mean bundled with winamp, that would most likey take years.

Me and Eo.s just haven't had a chance to touch it yet.

It won't but we will need a stale version whatever is released.

Maybe plan for the end of the year.

To me the most important things that I want ot do on it are:

* Bug fixes remove all the bugs that people go on about.

* Have an option for enable/disable texel alignment so the presets all work correctly and authors don't have to like Zylot does add dx =dx + 0.0005, etc.

* convert it all to use DX9 standards.

None of those things are glory work for new features.

Next 3d shapes,etc

If you do fancy doing a feature for the author I would love to see improvements to the monitor function so that they will work in per_pixel for a given location.

[someusername]

I just meant that it would be pointless to start writing presets supported by a custom build which only 5 or 10 guys have their hands on. I know that Rovastar created a link for it at the website (that's "official" indeed) but it seems Redi Jedi is going to be working more on it, so we better wait and see where it gets and then start doing stuff for it.

For a requested feature, I can't think of anything too important; Perhaps we could use a read-only variable that will allow authors to compensate for the non-square pixel/resolutions. (I must say i've needed this at some time or another) I mean, you can draw a circle in some resolution, but it will look like an oval in some other. If you could know the video's resolution at run-time it would help come around that problem, you know what I'm talking about...

[Rovastar]

It is worth loooking at what is happening. At this stage I see it as playing with the source until we get outr heads together with something that we are happy to release.

As for 'offical' there is no link/announcement on my website at this stage. I just hosted it there because it is easier for me and everyone else to download.

I want to do work on this and will but time is always lacking.

When a new version does come out we will need new presets for it so we should be aware of what is happening beta wise.

[Phat]

We'll write presets for it, cuz 5-10 people having it just sounds exclusive to us...

There is also some stuff you should do Redi... Some stuff we don't like about how the decay value is calculated, and how the video echo is calculated. But Eo.S. can go into more detail, cuz it's what she does and all.. :)

[redi jedi]

wow, thanks for the responces guys!!

@SM - i think that could be done, prolly less processing power to draw two rectangles than to or three digits of text... dunno, like i said dont know much about rendering yet.

@shifter - i was hopeing to hear from you, as you seem to have really pushed the limits of what MD 1.04b can do.. as for changing the pos. of shape texture - i'm already working on that :D not really coming along to well though.. the texture wraps around the center when i try to change it, prolly just need to reasses the situation and try again.. as for wrap, i am looking for a way to do it, still totaly unsure at this point. and the custom post processing is mostly what i was looking at MSDN for:up: :up:

@yin - i've had that problem too, i think its caused by the ASPECT ratio being a constant .75(i think) mabye if it used a var. equal to the acutaly aspect it would work better.... oh and ya, i do plan on doing more to it, as of now i am only really qualified to do the backend logic stuff, but with MSDNs help mabye i can figure it all out

@rovastar - the only bug i can rember hearing about is the multimon - vj "bug" witch i guess should be easy to fix(set the cords for vj window on the oppisite monitor as the main screen). and i dont really understand what you mean by tixel alignment, can you explain it in more detail?
and when i was looking at MSDN i saw a section on updating to DX9, i dont think it was allinclusive, just what you might need to get it to work in DX9, i'll start reading up. as for per-pixel monitor, near as i can tell it can be done, but it will only export the last value, since the pixel code it caluclated before the render, or the application of the new monitor value. as for bulit in 3d- one of my higest prioritys found a line that said(after setting x and y for perpixel wave code) v[i].z=0; i said to my self... hummmm ... but it didnt work out right, think it froze winamp if it was anything outside of 0..1 but i guess we might be set-up for 2d drawing, and it ignors z, dunno, but its already there, we just need to figure out how to implment it.


when i am finaly done..if that ever happens, i will make an installer and stuff(i just learned how in class yesterday :D ) and thank you all for your comments/suggestions :up: :up: :up: :up:

:winamp: milk out - till you drop out :winamp:

[Rovastar]

The texel thing is from:

http://forums.winamp.com/showthread.php?threadid=83401

but seems to be coming back in fashion.

http://forums.winamp.com/showthread.php?&threadid=211891

A simple on/off tickbox in the config for this will help a lot and not lead to writing presets with code that fixes the problems when it can be done in the driver.

There may be more bugs I will hunt them down.

Go ahead do what you can. Realisticaly now I will not get to look at it properly for another 4 weeks now.

- Edit: Installers are easy BTW I just use NSIS (http://nsis.sourceforge.net/). USe it will VENIS editor ( http://spaceblue.com/venis/downloads.php) and the wizard and it is dead easy. I can drop you a sample script if needed.

That is what wianmnp uses and my downloads on milkdrop.co.uk

[Phat]

I did a quick edit of one of the beta presets.

btw, I think if anyone writes more presets for this beta, we should always list it as such in the file name, and the .zip.

That way it's easier to keep track of.

[Eo.S.]

Redi: I can answer assloads of questions about dx9 gfx & rendering as I program dx9 shaders for xbox360 as my full time job (http://www.gamespot.com/xbox360/action/theoutfit/screenindex.html), although I don't know how much I can provide on the specifics of how to actually code the backend part that communicates to the API.

As for mirrored texture wrap there should be a MIRROR setting for d3dsamp_addressu and d3dsamp_addressv in the definition of the texture sampler [as opposed to CLAMP or WRAP]. This might only be dx9 but i'm pretty sure dx8 has MIRROR.

feature requests/bug fixes:
supposedly there's some way of setting the mesh size in a preset, but no seems to know how to do it, or if it's really there at all.

Code to set or alter the vertex locations on a shape. As well as affect the texture coordinates of the vertices.

video echo is painfully slow, so much so that it would seem to suggest that MD is just calculating everything twice. Considering the fill rate of current video cards, drawing the texture to screen twice should be just as fast as without. Being able to give code for how the mirror and original are composited together would be good too [instead of just (a+b)/2]. Gamma also kills framerate, which suggests that it is done by CPU, instead of on GPU by direct x.

Because the bit depth per pixel is low, using high decay values like 0.998 gives you that ugly grey mess that never quite reaches black. An alternate decay method that subtracts a small number [e.g. 1-decay] gives a much smoother fade that always reaches black. I've done this a couple times in MD by inverting the image and covering the screen with a shape in additive mode on a very low opacity.
Also, being able to change the decay value per pixel would be sick.

Eo.S.

[Rovastar]

Originally posted by Eo.S.

feature requests/bug fixes:
supposedly there's some way of setting the mesh size in a preset, but no seems to know how to do it, or if it's really there at all.


AFAIK there is no way of doing that at the moment. What did happen was the global mesh values were available from 1.04 onwards so you could look them up in for use in the presets.

I think it was meshx and meshy variable or something. I used them a few times.

I hope that is clear.

[Rovastar]

FOr new beta presets. There should be a new subforum for OPen Source coming soon. It would be best if we keep them all in there first to save confusion.

Maybe prefix the thread title them "Beta v1.xx Presets - " or something.

[redi jedi]

@eos - lol good call

if (fVideoEchoAlpha > 0.001f)
{
// video echo
lpDevice->SetRenderState(D3DRS_ALPHABLENDENABLE, TRUE);
lpDevice->SetRenderState(D3DRS_SRCBLEND, D3DBLEND_ONE);
lpDevice->SetRenderState(D3DRS_DESTBLEND, D3DBLEND_ZERO);

for (int i=0; i<2; i++)
{
fZoom = (i==0) ? 1.0f : fVideoEchoZoom;

float temp_lo = 0.5f - 0.5f/fZoom;
float temp_hi = 0.5f + 0.5f/fZoom;
v3[0].tu = temp_lo;
v3[0].tv = temp_hi;
v3[1].tu = temp_hi;
v3[1].tv = temp_hi;
v3[2].tu = temp_lo;
v3[2].tv = temp_lo;
v3[3].tu = temp_hi;
v3[3].tv = temp_lo;

// flipping
if (i==1)
{
for (int j=0; j<4; j++)
{
if (nVideoEchoOrientation % 2)
v3[j].tu = 1.0f - v3[j].tu;
if (nVideoEchoOrientation >= 2)
v3[j].tv = 1.0f - v3[j].tv;
}
}

float mix = (i==1) ? fVideoEchoAlpha : 1.0f - fVideoEchoAlpha;
for (int k=0; k<4; k++)
v3[k].Diffuse = D3DCOLOR_RGBA_01(mix*shade[k][0],mix*shade[k][1],mix*shade[k][2],1);

lpDevice->DrawPrimitiveUP(D3DPT_TRIANGLESTRIP, 2, (void*)v3, sizeof(SPRITEVERTEX));

if (i==0)
{
lpDevice->SetRenderState(D3DRS_SRCBLEND, D3DBLEND_ONE);
lpDevice->SetRenderState(D3DRS_DESTBLEND, D3DBLEND_ONE);
}

if (fGammaAdj > 0.001f)
{
// draw layer 'i' a 2nd (or 3rd, or 4th...) time, additively
int nRedraws = (int)(fGammaAdj - 0.0001f);
float gamma;

for (int nRedraw=0; nRedraw < nRedraws; nRedraw++)
{
if (nRedraw == nRedraws-1)
gamma = fGammaAdj - (int)(fGammaAdj - 0.0001f);
else
gamma = 1.0f;

for (int k=0; k<4; k++)
v3[k].Diffuse = D3DCOLOR_RGBA_01(gamma*mix*shade[k][0],gamma*mix*shade[k][1],gamma*mix*shade[k][2],1);
lpDevice->DrawPrimitiveUP(D3DPT_TRIANGLESTRIP, 2, (void*)v3, sizeof(SPRITEVERTEX));
}
}
}
}

well it doesnt quite calculate everything twice, just renders twice, or more for gama... do you think using a texture, like the shapes, would be faster? i might be able to figure that out

[Eo.S.]

I'm guessing by 'renders twice' you mean the CPU is sending the image to GPU to draw on screen twice. If that's the case then doing it with a texture would be way faster because it would actually get accelerated by the GPU.

Can't say exactly how it look in C, but in HLSL for DX8, pixel shader 1.1 [that's geforce 3 and up]

video echo - assume that the full screen quad has 4 vertices, with xy values of [-1,-1] [-1,1] [1,1] [1,-1]

----vertex shader
struct VS_OUTPUT
{
float4 pos : POSITION0;
float2 texCoord : TEXCOORD0;
float2 texCoordB : TEXCOORD1;
};

VS_OUTPUT vs_main( float4 inPos: POSITION )
{
VS_OUTPUT Out = (VS_OUTPUT) 0;

Out.pos = float4( inPos.xy, 0.0f, 1.0f);

// get into range [0,1]
Out.texCoord = (float2(Out.pos.x,-Out.pos.y)+1.0f)/2.0f;
Out.texCoordB = float2(1-Out.texCoord.x,Out.texCoord.y);
return Out;
}

This gives a quad adjusted to the exact screen extents to the pixel shader, and two sets of texture coordinates, where the second is flipped on the x axis.

----pixel shader
float4 ps_main( float2 texCoord : TEXCOORD0, float2 texCoordB : TEXCOORD1 ) : COLOR
{
float4 result;
float4 A = tex2D( Texture0, texCoord );
float4 B = tex2D( Texture0, texCoordB );

result = (A + B)/2;

return result;
}

Texture0 is of course assumed to be the texture sampler for the milkdrop processed image.

as for gamma, this is really just multiplication, so we should be able to add

result *= gamma; before the return

except in dx8 we can't multiply by values over 1, we can get around this be adding the result to itself several times and then multiplying by gamma. This of course means that if we add enough times for 4x brightness, that a user set gamma value of "1.0" actually correspondes to 0.25 whem we multiply by "gamma" as our result begins with a value of 400%. Hope that made sense >^~^<

Eo.S. >^-^<

[redi jedi]

ok got the texture saving thing down, added a var to the shape code called tex_capture, working on puting it in the menu. also *hopeing* to have a saved texture for each shape(that would be soooo sweet).

@eos - i'll look into that texture thing, i just dont know how to flip them around, or blend them

[redi jedi]

var tex_capture add to menu -> done
diffrent tex_captures per shape -> done
i have to run it on auto tex size, i get an outof mem
error at 2000x2000 or whatever, but it runs pretty
good on auto, made a test preset with for shapes at
x=.25,.75 & y=.25,.75; and set eachone to capture on
equal(bc%4,shapenumber), just set a simple rot+cx/cy
OMG it looks SOOOO cool

also updated the menu text a little( added tex_zoom/ang/capture)

still working on changing the center of the texture(s) and the video_echo problem, dont know if i will do anymore tonight or not

[Phat]

I think there are a few variables already that are not listed, it would be good to get these pre-existing ones on the menu list. I think tex_zoom for per-frame isn't listed for shapes, the others escape me currently.

[redi jedi]

thanks phat - shape menus updated, still need to look at the rest...ooo that reminds me i'b gonna have to add the w1-w8 vars too

[Rovastar]

Originally posted by Eo.S.

Can't say exactly how it look in C, but in HLSL for DX8, pixel shader 1.1 [that's geforce 3 and up]


Are you sure about that?

My research is that PS 1.1 is GeForce4 Ti/Radeon 8500 or above

I think it is worrying at this stage to increase the bottomline spec of MilKDrop to this high spec. Lets not make MD too elitist.

[redi jedi]

i've been trying to redo the video echo part, without much luck, it might take me a while to figure out. i did think of a posible way to control the blend setting, gonna look in to it.
@rova - should i just e-mail you my updates insted of posting them in three posts?

@eos - i rember hearing something about how you guys had redone milkdrop in rendermonkey or something, if so can i get a copy of that, mabye i can figure out how to integrate it...

[Rovastar]

Feel free to email me them. I'll try and get you ftp access or something.

[Phat]

@ Redi, Nope. Not going to give out the DX9 code.

First off the back end is all different, it just has a lot of similar functions.

Secondly it needs it's own application really. Some thing that is WAYYY more user friendly.

Thirdly, we want to be the soul input, we don't want other people claiming it's there's (or was done for them) when they've done little work.

And lastly most of them use a version of RenderMonkey that is not publicly released.

Sorry if that sounds a little Elitist.

If you'd be into doing application programming for a new application, that'd be great.

Eo.S. Can provide some input into (And possibly code examples) for some new post processing stuff.

Like Bloom in Milkdrop, which could be added even without upgrading to dx9. There's a lot of new post-processing stuff that can be done in dx8.

But Eo.S will have to get back to you on more.

(I really like shifter's idea 'bout programmable post processing functions.)

[Eo.S.]

@eos - i'll look into that texture thing, i just dont know how to flip them around, or blend them

flipping the image is simply a matter of changing the texture coordinates when you read from the texture [you'll want to work in pixel shader support, refer to msdn for info on this, I don't know much about specific device render calls etc. But I can provide HLSL and shader microcode all day long].

For horizontal flip, the x texture coordinate simply becomes 1-x, for vertical, the y coordinate becomes 1-y.

If you implement pixel shaders, then the blending is easily done by having the pixel shader read the texture forward, and flipped, and then giving an equation to combine them
(a+b)/2 averaged together
1-(1-a)*(1-b) inverse multiply, adds the images together, but the result never goes above 1
abs(a-b) images "invert" each other
a*(1/(1-b)) equivalent to the "color dodge" layer mode in photoshop

otherwise you have to use silly alphablending crap that requires getting shit like srcblend and destination blend modes set correctly, very annoying and way slower than just reading a texture twice or more, compositing the results, and then drawing that to screen once.

[Eo.S.]

Are you sure about that?

My research is that PS 1.1 is GeForce4 Ti/Radeon 8500 or above

I think it is worrying at this stage to increase the bottomline spec of MilKDrop to this high spec. Lets not make MD too elitist.

This HIGH of a spec? WTF, you can't be serious. Either one of those cards cost less than $40, and only that much because it's just impossible to build hardware for less, you can buy a radeon 9600 for $50. Pixel Shader 1.1 is 4yrs old or more, even the Xbox is pixel shader 1.3+

If you own a computer and it's video card can't even support PS1.1 then you don't give a flying fuck about gfx, and obviously don't care about milkdrop either. You can't even play video games made in the last 2yrs at all.

We're trying to move forward here, not backward. If granny wants to run milkdrop on her 333MHz she can keep using MD1.4. We're not forcing everyone who's ever downloaded MD to upgrade and delete their old versions.

You might as well say that no one is allowed to post presets with 3d waveforms, cause the preset would run really slow on a few people's ancient computers.

And if you EVER want post-process effects, pixel shaders are an absolute requirement, unless you're fine with 5fps or less.

Eo.S.

[Rovastar]

MilkDrop is a mass downloaded app and bundled with Winamp. I think it is only fair to get a minimum spec that is reasonable.

Are we to upgrade the minimum spec of Winamp too?

After much time and hassle of asking we get MilkDrop bundled with Winamp. I don't want MilkDrop not meeting a realistic spec.

Pixel shaders from what I understand are not as widely supported as you first think.

At work I have Dell Optiplex gx270 with a 2.4Ghz CPU in it. It has a 96MB onboard graphics card an Intel 82865g. Intel as well as in Dell have these onboard graphics cards of HP/Compaq most of the time.

This graphics card does not support pixel shaders.

http://www.intel.com/support/graphics/sb/cs-014257.htm

And from what I understand brand new bog standard Dell or HP desktops still come with this onboard graphics too. A brand new dell 3GHz about 6-9 months ago had this card in it. The card is not bad it can run a fair bit of 3d stuff but not PS stuff it seems.

Not really a 333mhz granny PC is it

And you want wipe out all this userbase? The 2 most popular PC brands out there.

I actually was surprised by this myself that PS support had not been added to this card . I knew on-board card are not brilliant and I know newer ones are getting a lot better and seem to be like a GF4Ti/midrange GF5 card speed from the tests I have done but they don’t it seems have PS support.

We must consider the seriously. We do have a large userbase and I don’t want to alienate big parts of it.

We have to understand what userbase we have and what we are aiming for?

Pixelshaders will be great but maybe for version 2.

I obviously have no objections to option to ‘enable pixel shader 1.1’ support but I do object to this as a mandatory requirement by default. Hopefully you can understand why now.

We are all on the same side you know. :)

[redi jedi]

humm thats a tough one, would have to agree with rova in that distroing userbase is bad. although on the other hand, how many people have opened MD, seen one of the first giess presets(that was most likly only there to show authors what the proggy can do) and turned it off, never to look again?
an option to enable would solve the prob i suspose, mabye just a seprate release, after we update the original(since adding PS will prolly be alot of work)


oh and on a side note, i though of something last night..... super monitor! a seprate gui w/ an enable option in the config, that displays x number of varibals. mabye even a graph of the last y frames.... what do ya guys think?

[Phat]

"We are all on the same side you know."

No we're not, it's Pirates vs. Ninjas....

ARRRRRRRRRRRRRR...

lol

Btw, wouldn't there just be a way to auto-detect pixel shader 1.1? Then have a back up button on the config panel maybe?

[Eo.S.]

Rova, the computers at your work are specically purchased to have the most barebones gfx support possible. I've said it before and will say it again, if you buy a computer that doesn't even have hardware ps1.1 you just don't care about gfx. But it's hard to do that now
http://www.bestbuy.com/site/olspage.jsp?skuId=7439578&type=product&productCategoryId=pcmcat60700050016&id=1124431815544
$500 Compaq, found in the "PCs for productivity" section [that's barebones], ATI Xpress 200, even this supports PS2.0
the same goes for cheapest HP computer they have listed
http://www.bestbuy.com/site/olspage.jsp?skuId=7439373&type=product&productCategoryId=cat15108&id=1124431815188

http://66.102.7.104/search?q=cache:jGS9yy4W6mwJ:en.wikipedia.org/wiki/Direct3D_vs._OpenGL+ps1.1+software+render&hl=en
ps1.1 is geforce 3 and radeon 8500+

And if your video card doesn't support it

if (hal_caps.PixelShaderVersion < D3DPS_VERSION(1.1, 0))
{
//code that prevents you from loading presets that use ps1.1
}

so we don't even have to put a switch in the config panel.
This is milkdrop, not iTunes.

[redi jedi]

actualy we could just put the code that does the ps stuff in the if statment, not loading presets that use it would require adding a version number to the files, not that thats a big deal..

i think i'm gonna have to stop for a while, considering i owe my roomies about a G, i REALLY need to find a job... anyone wanna give me one? :D

i'll try to study pixel and vertex shaders, and DX9. i wanna pretty much rewrite MD, as i dont like the way it does alot of things, decay/bass/mid/treb all the post-processing....

[Phat]

@ redi, what do you do? (Other then being a cable guy?)

Are you going to fix the decay?

@ Fishbrain I see you.... you going to write some new presets?
;)

[redi jedi]

@phat well i do some programing, mostly vb.net, also asp.net and c++, i can wire almost anything(cable phone networks cctv...).. actualy i guess i CAN do just about anything... it a matter of what someone will hire me to do(seems like pretty much nothing) went and got my A+ and NET+ certs, still ant got shit, been appling my "A+" off for 2 months, only got two interviews... one of witch was for a convient store(no call back, bye the way)
really starting to feel like a worthless prick
:cry: :cry: :cry:

i might update a few more things, just at night and stuff, but what i've done so far has been like all day projects(thats what i cant do anymore)

[Phat]

@ Redi, Insanity Toy 3 runs WAY slower while text is being displayed. In order to get the frame rate all the way up, you have to take away ALL of the text, including the FPS meter.

In order to view the frame rate, pulse the frame rate meter, this gives you the frame rate of this frame, before the meter starts to slow down the preset.

It runs at about 60 fps on the 9700, 80 on our 9800. Both in Milkdrop 1.04 and while the text is hidden in you're new beta 1.04b. Currently it's only running about 20 to 30 with the text.

Btw I think I'm going to make another version of this preset for milkdrop 1.04, it looks hella cool in a different way broken. (Which is often the case with presets, delete the per-pixel or per-frame, and often there is a different cool preset hidden beneath the other code.)

(Yes I do have 'Try to fix slow text (uses more video memory)' selected in the config panel.)