• Advertisement
Sign in to follow this  

OpenGL Drawing Plasma for Audio Visualization

This topic is 4661 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I was wondering if anyone had a simple algorithm for drawing plasma. I am trying to write an OpenGL program to simulate that plasma before I can implement it in hardware. The problem is that my plasmas have very regular shapes. Also, since they will have to change depending on the audio that is input (like a winamp visualization) I need to be able to affect the plasma by playing with some of the variables. But they need to have smooth changes. The current algorithm I have right now is as follows: I have a 512x512 matrix (representing my screen raster) that holds values of intensity from 0 to 511 that were obtained by adding 2 cos and 2 sin. Now when I draw to screen, I go through the matrix and each intensity value refers to a specific color stored in an array. Making the pattern move is done through adding an offset to the color index with wrap around. The smoothest results are obtained by storing a gradient in that array. However, it's too regular. I get circles and squares, etc. I'm looking for the more diffuse plasma look. As well as one with variables that affect how the plama behaves but without too drastic a change. I'm posting some of my code here. If you have any ideas or suggestions, please tell me.
void initColorArray()
{
	int i;
	float tempR, tempG, tempB;
	long pos1;
	
	tempR = 1.0f;
	tempG = 0.0f;
	tempB = 0.0f;

	colorArray = (Color*)malloc(sizeof(Color)*512);

	// Array loaded with a gradient
	for(i = 0; i < 512; i++)
	{
		colorArray = createColor(tempR - i*1.0f/512.0f, tempG, tempB + i*1.0f/512.0f);
	}
	
	// A table holding a few cos and sin values so that I only need to compute them once
	for (pos1 = 0;pos1 < 360;pos1++)
	{
		tcos[pos1] = abs(cos(pos1*PI/180) * 128);
		tsin[pos1] = abs(sin(pos1*PI/180) * 128);
	}
}

void Move_Plasma(long pos1, long pos2, long pos3, long pos4, int pattern)
{
	// pos1 through pos4 affect the general shape direction of movement
	long i,j,color,p1,p2,p3,p4;
	p1 = pos1;
	p2 = pos2;
	for (i = 0;i < 512;i++)
	{
		p3 = pos3;
		p4 = pos4;
		for (j = 0;j < 512;j++)
		{
			color = tcos[p1 % 360] + tcos[p2 % 360] + tsin[p3 % 360] + tsin[p4 % 360];

			// Pattern here affects what colors in the gradient are referenced
			if(pattern == 0)
			{
				// do nothing
			}
			else if(pattern == 1)
			{
				color = (color + 10) % 512;
			}
			else if(pattern == 2)
			{
				color = (color + 20) % 512;
			}
			else if(pattern == 3)
			{
				color = (color + 30) % 512;
			}

			Color tempC = colorArray[color];
			glColor3f(tempC.R, tempC.G, tempC.B);
			glVertex3f((float)i*0.0097f, (float)(-1*j*0.0097f), 0);
			
			// p1 through p4 affect the movement and the general shape of the pattern
			// however, changing them changes the pattern instantly. 
			// There is no smooth transition
			// these 2 affect the number of patterns along the height			
			p3 += 1; // + sideways transmutation for this one
			p4 += 1; // + vertical transmutation for this one
		}
		// these 2 affect the number of patterns along the width
		p1 += 1; // + vertical transmutation
		p2 += 1; // + sideways transmutation
	}
}

Thanks in advance

Share this post


Link to post
Share on other sites
Advertisement
The trick is too use an algorithm to generate a texture (what you are doing at the moment, from what I understand), and then to have another algorithm which deals with the animation of the picture.
Specifically, I am thinking of using a mesh warping to morph your picture from frame to frame.
I read a great little article years ago that showed a very primitive method for doing just that, which resulted in the picture "flowing" around the screen in a very smooth fashion.
Think of the sort of effects that you get in WinAmp, that's what I am talking about. Now apply this flowing algorithm to a simple plasma cloud texture, possibly with colour cycling, and you should have a good basis to work with.

if you dont know what a plasma cloud is, look it up, it's a very simple algorithm too.

Actually, after a little bit more googling, I think I found the site I was thinking of. I leave it as an exercise for you to find the article about warp maps...

You might also wanna check out the Demomaking series on Flipcode, some of their stuff might be useful?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement