@woland

I'm afraid this doesn't work. The destination computer requests the custom files that are not included in the 'run-only' version even if they are embedded in a User Actor.

At the moment, if I save a project as 'run-only' with custom-made actors that use shader code, they are requested by the destination computer, and need to be added to a folder for the patch to function. If I pick the code individually out of each custom-made actor, and place into a new GLSL Shader actor in each instance before saving, the code is then included in the 'run-only' version, and the recipient does not need to put additional files on the destination computer. This is highly desirable in situations where projects are being installed remotely, by non-specialist persons, but it's a fiddly task.

All I am asking is that saving a project as 'run-only' can by default embed the code contained in the custom GLSL Shader Actors, without having to re-insert them into many new actors through the patch. 

This would make the process less complicated for both sender and recipient. It seems to me to be in the interest of Isadora to be an install-friendly application for galleries, museums, etc.

You may also want to find a monospace font to use, this way you can calculate the space required for the word, since each letter will take up equal space. That should allow for a grid like layout to become possible. Rotation will be another monster.

@michel, I wasn't suggesting an email notification! Rather, the idea that when you clicked on a plugin it would say that I downloaded it on H=December 12, 2020, or something or something like that. Or perhaps when you looked at your profile, it shows you a list? I imagine that the tech is already built in, because it knows when you look at a topic or when the topic has been updated?

Happy holidays!

Hugh

@woland I need to make some updates to it, and then I will make it available! Poke me if I don't :)

@mark said:

@dako-arkYes, the error shows the the shader cannot be be converted. ""Cannot process ISF Shaders with Vertex Shaders"" means that the program does not yet have the ability to process a shader (.fs file) that has a companion vertex shader (.vs file). We will see to improve this tool, but for now this is a limitation.

ok ... I guessed.

I hope in your furious profiquo.npn job having no skills in this regard.

thank you so much

best wishes

 

@thierry said:

j'aurai besoin d'un peu d'aide . Je suis nouveau sur isadora et je n'arrive pas à convertir des ISF en GLSL Isadora . j'ai bien suivi le tutoriel ( Isadora Guru Session 11 vers la fin de la vidéo ) mais je suis sur pc et non mac .

Je peux utiliser Google Translate si vous souhaitez écrire en français. Je ferai de mon mieux pour vous aider. ;-)

Cordialement,
Mark

thank you mark

Best Wishes

@astrid

Remove the space between ISADORA_FLOAT_PARAM and (

So the second one ;) The first one is your example

// ISADORA_FLOAT_PARAM (noise_level, noil, 0.0, 1.0, 0.5, "This is the text that helps"); // ISADORA_FLOAT_PARAM(noise_level, noil, 0.0, 1.0, 0.5, "This is the text that helps");

These are great and thanks for sharing

@mark said:

next version will have this ability. (As well as a few others to make it easier to replicate ISF shaders.)

 Great news!

Best wishes

Russell

Please see Mark's answers here: 

https://community.troikatronix.com/topic/6652/step-by-step-instructions-convert-isf-shaders-to-isadora-glsl/2https://community.troikatronix.com/topic/6642/answered-convert-all-isf-command-won-t-run-on-catalinahttps://community.troikatronix.com/topic/6433/conversion-of-resolume-arena-xml-plugins-to-isadora/13

Hi there both, 
Ticket has been logged with id #4561383

Thanks !

@willyu said:

ahhhh a lot to learn!!!

 One of the reasons I haven't learned to write my own yet :)

@mark

Wow, thanks a lot, you all!  I am going to look at the code as soon as I get time....

Hi all ! if anyone can point how to solve this. I need to change something about this shader. It works fine but when I insert it as a Tex Map in the 3d particles it does like a very fast and sutil "black out" when the color changes. And because of that the particles dissapear for a second. I cant find in the code that behavior. 

Thanks in advance

Maxi

GLSL.zip

thanks. 

because there is no time I went back to a previous version of my patch, that solved it. 

I actually use a very large .png file (because it's the only way i know to show fotos in rapid random sequences, I pan around the big file, real smooth and 60fps).

the error is much more likely to happen when the scene jumps have a fade time > 0. I assume that means running both scenes and obviously may be problematic.

awaiting version 3 i do not think it's worth the while to check this all out. it may be ok in version 3.

cheers 

h

Thanks Michel for the reply. I just looked and I did name it correctly and the txt file doesn't show up in the GLSL column in Isadora. Will re-read the instruction page...

@crystalhorizon said:

shader converters

 I think these are very similar to what Isadora already uses, just the parameters are wrapped in JSON... where Isadora is using a comment structure.
Perhaps I will spend sometime converting a couple, and if successful right up a how to.