• Create Account

## Simple GLSL Image Processing

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

19 replies to this topic

### #1davertron  Members

Posted 11 April 2011 - 08:55 PM

I've been working on my first game in OpenGL and C++ for a little while now, and I'm trying my hand at GLSL for some simple image processing effects. Specifically, I'm trying to implement a simple gaussian blur. However, I'm having difficulty understanding conceptually how this is supposed to work. Here's how I think it's supposed to go from reading various forum entries/tutorials online:

Setup (one time at the beginning of my game init code):
• Enable texturing (glEnable(GL_TEXTURE_2D), glGenTextures(...), glBindTexture(...), etc.)
• Check glGetInfoLogARB for errors
So far, so good (at least I see no output from the info log, so I'm assuming that's good).

Then, to render each frame:
• Render my frame normally
• glFlush() (?)
• glUseProgam(0) (stop using my shader?)
• glCopyTexImage2d(...) (Capture rendered output to a texture)
• Calculate texture offsets based on window size
• Pass texture offsets to shader using glUniform2fv(...) (I think that this isn't totally necessary if my window size is always the same, then I could have the same texture offsets, but not sure, I've seen a ton of different shader code for the fragment shader that does this in seemingly different ways)
• Render full screen quad (optionally changing projection matrix to make this easier...) with texture coords
• glFlush()
Does that sound about right? I think this is what I'm doing, but I'm getting really strange output. If this general approach looks correct, I'll post some more specific code, but I wanted to make sure I wasn't wasting anybody's time if I didn't have the concept correctly.

### #2karwosts  Members

Posted 11 April 2011 - 09:09 PM

You're probably close, but theres a couple changes I would make:

#1) I don't think you ever need to call glFlush. The driver should keep track of what is dependent on what else, so you won't be able to pull from a texture or framebuffer until its ready.

#2) Instead of rendering your scene normally and then copying the texels to a texture, you can render directly into a texture via framebuffers. Look into the commands:
glGenFramebuffers
glBindFramebuffer
glFramebufferTexture

This should be a lot more efficient.

#3) When you render the fullscreen quad, you definately don't want to use the same projection matrix. The easiest is to just use no matrix at all (define input coordinates in normalized device coordinates). Just draw your quad with vertices (+/-1, +/-1, 0) and that will align with the fullscreen without any transform required.
My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #3davertron  Members

Posted 12 April 2011 - 06:42 AM

You're probably close, but theres a couple changes I would make:

#1) I don't think you ever need to call glFlush. The driver should keep track of what is dependent on what else, so you won't be able to pull from a texture or framebuffer until its ready.

#2) Instead of rendering your scene normally and then copying the texels to a texture, you can render directly into a texture via framebuffers. Look into the commands:
glGenFramebuffers
glBindFramebuffer
glFramebufferTexture

This should be a lot more efficient.

#3) When you render the fullscreen quad, you definately don't want to use the same projection matrix. The easiest is to just use no matrix at all (define input coordinates in normalized device coordinates). Just draw your quad with vertices (+/-1, +/-1, 0) and that will align with the fullscreen without any transform required.

Ok, I'll give that framebuffers a shot at some point, but I'm not very concerned with efficiency at this point, just want to get it working I've read about framebuffers though and it does seem like they are often used for this purpose, and if it makes it easier I'm all for it.

As I was re-reading my post this morning, I think I either made a mistake in my explanation above (and probably my implementation, but I'm at work so can't check my code right now), or I REALLY don't understand how the OpenGL pipeline works.

Also, I'm currently using an Orthographic projection (I'm building a Geometry Wars clone just to learn game programming so it's 2D), so would I still need to alter my projection matrix? I think I should easily be able to use my current projection matrix, but I could be wrong about this as well (all the example code for 3D does this by setting it back to normal I believe and using 0,1 (or -1,1, can never keep it straight...), but I was thinking I could skip this step since I already have an orthographic projection.

Thanks for your reply! I'll try swapping steps 1 and 4 of the render piece later when I get back, and if that doesn't work I'll try to come up with some example code to show the problem I'm having.

### #4karwosts  Members

Posted 12 April 2011 - 10:06 AM

As I was re-reading my post this morning, I think I either made a mistake in my explanation above (and probably my implementation, but I'm at work so can't check my code right now), or I REALLY don't understand how the OpenGL pipeline works.

Yeah, this sounds right. I'm used to using a shader for everything, so it looked right to me to have a shader bound to render your scene. If thats your blur shader you want it active during step 8.

Also, I'm currently using an Orthographic projection (I'm building a Geometry Wars clone just to learn game programming so it's 2D), so would I still need to alter my projection matrix? I think I should easily be able to use my current projection matrix, but I could be wrong about this as well (all the example code for 3D does this by setting it back to normal I believe and using 0,1 (or -1,1, can never keep it straight...), but I was thinking I could skip this step since I already have an orthographic projection.

You could make it work with an orthographic projection matrix, but my point was that you don't have to use a matrix at all. If you define your quad's input coordinates in NDC, than you can just let this be your vertex shader:

in vec2 vertex;
out vec2 texcoord;

main () {
gl_Position = vec4(vertex,0,1); //no matrix multiplies necessary
texcoord = vertex*0.5 + 0.5; //scale -1/1 range to 0/1;
}



My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #5davertron  Members

Posted 12 April 2011 - 10:20 AM

You could make it work with an orthographic projection matrix, but my point was that you don't have to use a matrix at all. If you define your quad's input coordinates in NDC, than you can just let this be your vertex shader:

in vec2 vertex;
out vec2 texcoord;

main () {
gl_Position = vec4(vertex,0,1); //no matrix multiplies necessary
texcoord = vertex*0.5 + 0.5; //scale -1/1 range to 0/1;
}



Awesome, yeah that would be ideal. I think I'll take your suggestions and try to implement them in a simple example (FBO + your simple vertex shader above) and then see if I can port it over to my game code. I need to move away from using glBegin()/glEnd() eventually anyway and move to vertex arrays or VBO's at some point too, but want to avoid a total re-write

### #6davertron  Members

Posted 12 April 2011 - 06:34 PM

Ok, I took a quick shot at using an FBO instead of drawing and then copying it to a texture. I must be doing something wrong, because all I get is a white screen, but I don't get any errors, so I feel like I'm close. I haven't implemented shader stuff yet, but that's next.

Here's the code:

https://gist.github.com/916742

You can comment out the FBO binding in the draw method as well as the "drawTexturedQuad" function call, and you'll see the normal frame.

### #7karwosts  Members

Posted 12 April 2011 - 06:42 PM

There may be other issues as well, but for one thing you're not allowed to have a texture bound to a sampler at the same time you are writing to it, you'll get undefined behaviour. Unbind the texture from the sampler when you're writing to the framebuffer, and unbind the framebuffer when you're reading from the texture.

Once you start working with offscreen rendertargets, it's probably a good idea to go pick up a free copy of gdebugger, it will make your life a lot easier.

EDIT:

Also you have to bind the framebuffer to attach a texture to it:
  glGenFramebuffers(1, &fbo_id);
glBindFramebuffer(GL_FRAMEBUFFER,fbo_id); //NEW
glFramebufferTexture2D(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, GL_TEXTURE_2D, tex_id, 0);
glBindFramebuffer(GL_FRAMEBUFFER, 0); //NEW


My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #8davertron  Members

Posted 12 April 2011 - 07:08 PM

There may be other issues as well, but for one thing you're not allowed to have a texture bound to a sampler at the same time you are writing to it, you'll get undefined behaviour. Unbind the texture from the sampler when you're writing to the framebuffer, and unbind the framebuffer when you're reading from the texture.

Once you start working with offscreen rendertargets, it's probably a good idea to go pick up a free copy of gdebugger, it will make your life a lot easier.

EDIT:

Also you have to bind the framebuffer to attach a texture to it:

  glGenFramebuffers(1, &fbo_id);
glBindFramebuffer(GL_FRAMEBUFFER,fbo_id); //NEW
glFramebufferTexture2D(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, GL_TEXTURE_2D, tex_id, 0);
glBindFramebuffer(GL_FRAMEBUFFER, 0); //NEW


Hmmm, I added that code, and added two lines to the draw method (to try not to have texture/fbo bound at the same time per your suggestion), but still same all-white screen. Perhaps I'm not doing it correctly though? I updated the gist with the new code in the draw method.

### #9davertron  Members

Posted 12 April 2011 - 07:20 PM

http://www.gamedev.net/page/resources/_//feature/fprogramming/opengl-frame-buffer-object-101-r2331

The first thing they do in the article is create a renderbuffer for use as a depth buffer. Is this something I need to do as well? I would think I don't need depth information considering I'm doing everything in 2d...but then again I don't fully understand FBO's yet so...

### #10karwosts  Members

Posted 12 April 2011 - 07:25 PM

I'm pretty sure you don't need a depth attachment if you don't want one, you should be able to render fine to just a color attachment. Be sure to disable depth test and depth write though when drawing to the FB.
My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #11davertron  Members

Posted 12 April 2011 - 07:28 PM

I'm pretty sure you don't need a depth attachment if you don't want one, you should be able to render fine to just a color attachment. Be sure to disable depth test and depth write though when drawing to the FB.

Is depth test enabled by default? I thought I would have to explicitly enable it with glEnable(GL_DEPTH_TEST). If I'm not doing that, should I have to worry about it?

### #12karwosts  Members

Posted 12 April 2011 - 07:33 PM

glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR_MIPMAP_LINEAR);

This is a problem if you don't build mipmaps. If you're not using them, you have to set the minfilter to not use mipmapping (GL_LINEAR for example), otherwise it won't sample the texture.

http://www.opengl.org/wiki/Common_Mistakes#Creating_a_Texture

Also this:
glGenFramebuffers(1, &fbo_id);
glBindFramebuffer(GL_FRAMEBUFFER, 1);

You probably meant to bind fbo_id, not "1". It may work but it is prone to breaking.

Is depth test enabled by default? I thought I would have to explicitly enable it with glEnable(GL_DEPTH_TEST). If I'm not doing that, should I have to worry about it?

You're right, its disabled by default. You should be fine.
My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #13davertron  Members

Posted 12 April 2011 - 08:11 PM

Ok cool, I figured it out. It was partially the GL_MIN_TEXTURE_FILTER I was using as you mentioned, and partially the way I was binding/unbinding textures and FBO, etc.

This stackoverflow question helped a bit: http://stackoverflow.com/questions/3466736/render-to-fbo-not-working-gdebugger-says-otherwise

And I've updated the gist new code: https://gist.github.com/916742

On to implementing my blur shader...

### #14davertron  Members

Posted 13 April 2011 - 08:44 PM

Alright, I've tried to implement a blur shader with some gaussian blur code I found, but no luck.

I've updated the gist at https://gist.github.com/916742, but the main problem is at line 274. The program always fails here with the message "linking with uncompiled shader". I can't seem to find much helpful online about this error, so if anyone has any ideas I'm all ears. I've included the shader source files at the bottom of the gist as well for reference.

### #15kiwibonga  Members

Posted 14 April 2011 - 01:29 PM

I'm still learning and using copy-pasted code from tutorials, so I have no idea if this is your problem, but here's the code I'm using to accomplish something similar:

	myShader = glCreateProgramObjectARB();

glLinkProgramARB(myShader);

I notice that you create your vert and frag shaders using glCreateShader, whereas I use glCreateShaderObject, and then attach that to the main shader program... Maybe this is it?

### #16karwosts  Members

Posted 14 April 2011 - 01:36 PM

I'm pretty sure glCreateShader is the right code. I've never even heard of glCreateShaderObject, and I can't find any documentation on it except for a couple blurbs from some powerpoint presentations from like 2002.

I'm going to guess that that's some extension that was around in the very early days of shading languages, but glCreateShader should be the correct way.
My Projects:
Portfolio Map for Android - Free Visual Portfolio Tracker
Electron Flux for Android - Free Puzzle/Logic Game

### #17davertron  Members

Posted 14 April 2011 - 01:42 PM

I'm pretty sure glCreateShader is the right code. I've never even heard of glCreateShaderObject, and I can't find any documentation on it except for a couple blurbs from some powerpoint presentations from like 2002.

I'm going to guess that that's some extension that was around in the very early days of shading languages, but glCreateShader should be the correct way.

I think you're right, a quick google for glCreateShaderObject doesn't seem to return anything useful. I'm still trying to figure out when to use the "*ARB" methods; it seems like you have to use some of them still, but most of the time I'm using the non-ARB methods.

I have a feeling it has something to do with the shader code, since I don't get that method if I change the fragment shader to a simple pass-through frag shader, but the results from the compile log for the gauss2.fs shader don't report anything wrong, so I'm kind of lost at this point.

### #18kiwibonga  Members

Posted 14 April 2011 - 02:27 PM

Oh yeah, should have tested... glCreateShaderObject isn't even defined in my environment.

Replacing the call with plain "glCreateShader" produces the exact same result.

### #19davertron  Members

Posted 17 April 2011 - 02:35 PM

Ok, so I've updated my gist with the working code: https://gist.github.com/916742

The main thing to notice is that the fragment shader has changed quite a bit: no more use of the "const" keyword, and no more initializing the offsets and gaussian kernel weights during the declaration (or even in loops). I'm not sure why I can't do that, but I'm guessing it's because my laptop is using an intel integrated graphics chip that doesn't support the most current GLSL language. That's the only thing I can guess, I've yet to test the old frag shader code on my desktop (which is nvidia).

Anyway, hopefully this helps someone else in the future.

### #20davertron  Members

Posted 17 April 2011 - 03:42 PM

Just updated the gist so that the texture offsets and kernel weights are calculated in the main program and then passed into the shader, since we should only have to calculate those once at the beginning of the program.

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.