Comments for Shazzam News

Comment on Pixel Shader Compare in Shazzam 1.4 by Saeid Habibzadeh

Saeid Habibzadeh — Wed, 04 Jan 2012 15:36:26 +0000

Thx 4 your Prompt Action.

Comment on Output directory and file changes for Shazzam v1.4 by waltritscher

waltritscher — Wed, 28 Dec 2011 23:44:34 +0000

If I understand your question it does not. The limitation for the instruction count is due to the Pixel Shader 2.0 specification. Unless Microsoft updates Silverlight shaders to PS 3 or higher then there is no solution.

Comment on Output directory and file changes for Shazzam v1.4 by Habibzadeh Saeid

Habibzadeh Saeid — Sun, 25 Dec 2011 15:02:11 +0000

Nice to hear, new version will coming soon.
does it cut 64. instruction barrier for silverlight?

Comment on Shazzam 1.2 – Multi Input Shaders Added by waltritscher

waltritscher — Thu, 10 Nov 2011 23:29:05 +0000

No there is not. The PS2 PS3 shader spec permits up to 4 samplers

Comment on Shazzam 1.2 – Multi Input Shaders Added by Bryan Croteau

Bryan Croteau — Sat, 08 Oct 2011 03:31:30 +0000

Is there any way to use up to 6 input samplers for the shader?

Comment on Shazzam 1.3 – Feature Overview by Tobias

Tobias — Thu, 08 Sep 2011 09:14:41 +0000

First I would like to thank you for a great application that really helps a lot when I need to work with Pixel Shaders!

I found a problem with ContrastAdjust.fx, it seems to have a bug when the shader is rendered in software in WPF (for example during a remote desktop session or forcing software rendering with RenderOptions.ProcessRenderMode = SoftwareOnly).

What happens is that transparent areas turn white, for example if putting the effect on a border with round corners the corners that should be transparent becomes white.

I fixed the problem by removing the following line from ContrastAdjust.fx:
pixelColor.rgb /= pixelColor.a;

Comment on Shazzam 1.3 – Eighty sample shaders included by Sergio

Sergio — Mon, 04 Apr 2011 01:49:44 +0000

Excellent work!

Comment on Shazzam 1.3 – Feature Overview by Steve

Steve — Sun, 06 Mar 2011 03:47:21 +0000

Never mind about the bug!
It’s a WPF/Silverlight bug. Nothing’s wrong with shazzam. More info here: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/2940eec8-6689-4ed7-b276-38e637640dd6/

Comment on Shazzam 1.3 – Feature Overview by Steve

Steve — Sun, 06 Mar 2011 02:41:34 +0000

Possible bug in Shazzam’s compiler.

First, let me say that this is a great app! Unfortunately, I’ve hit a really strange bug in when setting the alpha channel. Here is the simplest example that shows it:

sampler2D input : register(s0);
float4 main(float2 uv : TEXCOORD) : COLOR
{
float4 Color = float4(0,0,0,0);
Color.rgb = 1.0 – Color.rgb;
Color.a = 0.0;
return Color;
}

The output should be completely transparent, but it’s opaque (alpha value of 1).
Any ideas? I hope I’m submitting this bug in the right place.

Comment on Shazzam 1.3 – Feature Overview by buba

buba — Tue, 02 Nov 2010 12:52:42 +0000

Oh, would it be possible to implement it It is really useful when targeting PS2.0 and trying to stay within the limits. FX Composer by Nvidia has this functionality. In simple tool I wrote with XNA, before I found about Shazzam (which is way better btw), I used Effect.Disassemble(..) method and along with ASM code it returned there was this comment at the end “// approximately [_] instruction slots used ([_] texture, [_] arithmetic)” from which I parsed the info. Since XNA is just a wrapper around DirectX, there must be something with same functionality in DirectX.

Well, while I am at feature requests… It would also be useful to specify custom entry method name (maybe with comments like for parameters). I don’t know if WPF requires entry method to be named “main”, but it would be nice to be able to give descriptive names, since Shazzam is useful for more things than just WPF shaders.

Otherwise congrats on very good app. I find Shazzam much more user friendly for writing sprite effects and for post processing effects than Nvidia or AMD tools. Keep up the good work!