I'll just leave this here...

[A Former User]

@Christoph-Hart said in I'll just leave this here...:

Hmm, I'm at the end of my options to figure out why it's not working on your end - I just checked and it works on my mac mini which has an ancient GPU and shader version.

A last thing you can do is to download and compile the JUCE OpenGL 2d demo app here:

https://github.com/juce-framework/JUCE/blob/master/examples/GUI/OpenGLDemo2D.h

And see if these minimal shaders work.

Will do so Christoph. Thanks for the efforts... So this might be something on my end really! Maybe a GPU problem? I’ll check the JUCE example...

[Christoph Hart]

Maybe a GPU problem?

Yes that is most likely - I've tested it on NVIDIA GPUs and Intel HD graphics on Windows and macOS but I don't have any ATI GPU to test. I'm a bit surprised how flaky the GPU support for different GLSL features is given that it's such a common standard.

[A Former User]

@Christoph-Hart I forgot that I ran those 2 openGL demos from JUCE a couple of weeks ago. They both work fine on my system... I get the feeling that it is something really small and stupid that I am missing... (when is it not??...)

[Christoph Hart]

If you add some empty lines in your main method, does the line number at the syntax error message change?

[A Former User]

@Christoph-Hart The error I get for @Dominik-Mayer's example is this one:
No specific lines are mentioned. One error per compile...

And the following line 11 error is for Console.print(shader.getOpenGLStatistics());
The line number changes when adding empty lines.

EDIT: Just to be sure. Are there any specific flags, checkboxes that I need to set in Projucer that I might have forgotten?

EDIT 2:

I haven't seen this one before...

[Christoph Hart]

No, I was refering to the

ERROR 0:16'}': syntax error: syntax error

message. You can ignore any message that starts with Line XX, Column YY - these are HiseScript errors which you don't need to bother about for this issue. The OpenGL errors start with ERROR:

Try to reproduce the one above, then add a few lines in the main function and check whether the line number increases (so that it points to an error at the end of the file vs. at the beginning (where I had to add some boilerplate code).

[A Former User]

@Christoph-Hart I got the error... then added a few lines... got the same error... added a few more lines... same error... So it stayed the same, 3 times...

Though if you asked my how I reproduced them systematically... Couldn't say... there's (at least) no apparent system to it... clicking... compiling... changing windows selection seems to have an influence. (Canvas: Interface back to Script Editor... selecting panel... compiling with shift-f5 from the shader code window...) It's a nasty business.

So here's that nasty bugger once more:

[Dominik Mayer]

@UrsBollhalder

Just a random guess:
Did you make sure to get rid of the ""s around "shader"?. It should look like this:

g.applyShader(shader, [0, 0, this.getWidth(), this.getHeight()]);

Found this in your earlier snippet, but hope you've gotten rid of it by now..

All bests,
Dominik

[A Former User]

@Dominik-Mayer I think I got rid of it, yes! But I’ll double check when I get back!

[Brian]

I wonder if we could use a tool like this to come up with visuals?

Its very similar to Touch Designer and could help us peeps that are less code savvy

https://nodes.io/

[A Former User]

@briandoliveira said in I'll just leave this here...:

I wonder if we could use a tool like this to come up with visuals?

Its very similar to Touch Designer and could help us peeps that are less code savvy

https://nodes.io/

Nodes looks really interesting as well!! I have to take a closer look later.

Shader Code is quite special imho. It’s not immediately accessible I find. But the possibilities with OpenGL to create graphics that you can influence with a mouse or otherwise in real-time and hook it up to your instrument and its functionalities are quite astonishing. At least if you’re into that kind of thing. It’s like a multiverse filmstrip! 🤯🥳🤯

[A Former User]

@Christoph-Hart said in I'll just leave this here...:

No, I was refering to the

ERROR 0:16'}': syntax error: syntax error

message. You can ignore any message that starts with Line XX, Column YY - these are HiseScript errors which you don't need to bother about for this issue. The OpenGL errors start with ERROR:

Try to reproduce the one above, then add a few lines in the main function and check whether the line number increases (so that it points to an error at the end of the file vs. at the beginning (where I had to add some boilerplate code).

So this is today's macOS - HISE - OpenGL error:
Adding lines doesn't change anything. It'll come up fairly regularly... Maybe it helps...

[Christoph Hart]

But the line number is different. Can you check the file in another text editor to check whether there is a duplicate } at the end of your shader file? I remember there was an issue with the new code editor that somehow hides the last character...

[A Former User]

@Christoph-Hart said in I'll just leave this here...:

But the line number is different. Can you check the file in another text editor to check whether there is a duplicate } at the end of your shader file? I remember there was an issue with the new code editor that somehow hides the last character...

Well. That } was on me and my own stupidity! Didn't even have to open another text editor... Sorry...

But I could swear that unknown error is Catalina related... If I were on Mojave, it'd probably be working! Damn... This is bugging me...

[A Former User]

@Christoph-Hart I finally got it working on my MacBook Air 2014... Re-installed everything... Went back to Catalina and compiled HISE etc. Also openGL seems to be working. But I do get this a lot:
Interface:! ERROR: No definition of main in fragment shader

Also with the "simpler" examples on shadertoy.

Am I missing something?

@Dominik-Mayer's snippet works just fine now!
My 2019 MacPro beast machine still does throw me the Interface:! Unknown Error

[A Former User]

@Christoph-Hart Hey Christoph. I've been noticing some changes on the HISE / shader code - front...

I manage to get it to show the shaders occasionally. I still get an unknown error (both on my MacBook Air 2014 and my MacPro 2019). So, one out of 10 times I hit compile, it acutally shows me the shaders... but very inconsistently...

Really excited about this!

(dev branch, latest commit, 1f682f5)

This one I found while trying some shadertoy examples:

[A Former User]

@Christoph-Hart

[A Former User]

Is it possible to have multiple shader-panels in one interface?

[Christoph Hart]

Yes, you can even have multiple shaders per panel.

[A Former User]

@Christoph-Hart

Content.makeFrontInterface(600, 500);

const var Panel1 = Content.getComponent("Panel1");
const var Panel2 = Content.getComponent("Panel2");


const var shader = Content.createShader("shader");
shader.setFragmentShader("shader.glsl");

const var shader2 = Content.createShader("shader2");
shader2.setFragmentShader("shader2.glsl");

Panel1.setPaintRoutine(function(g)
{
	g.applyShader(shader, [0, 0, this.getWidth(), this.getHeight()]);
});

Panel2.setPaintRoutine(function(g)
{
	 g.applyShader(shader2, [0, 0, this.getWidth(), this.getHeight()]);
});

Something along those lines?