Broken Parameters

[OrdinaireX]

Hey love the progress made on the plugin, I'm running the latest release and am running into issues with random parameters.

Not only am I not able to get Integer, Header, and XY parameters working (for things like setting the resolution), but I also have random floats not working. For example, in the file I've attached, the Particle Count and Particle Size parameters are not working in Resolume. Not sure what I'm doing wrong on my end.

Thanks so much!

O.X
PARTICLES - Seaweed.zip

[medcelerate]

I’ll have a look to see what may be the issue. Can you please send me your resolute log as well.

[OrdinaireX]

Sure thing, where can I find it?

[drmbt]

I'm seeing that header breaks everything, and that pulse comes in as toggles, momentary comes in as pulses. Something must not be parsed correctly when converting.

When this gets stable it will be such a game changer, you're doing a huge service to the communty. The last major super important thing is figuring out how to get floats ranged properly, there absolutely has to be a way to get normMin normMax parameters represented properly as floats with a range bigger than 0-1

[medcelerate]

It's probably in your appdata folder

…

On Sat, Nov 30, 2024 at 7:43 AM Vincent Naples ***@***.***> wrote: I'm seeing that header breaks everything, and that pulse comes in as toggles, momentary comes in as pulses. Something must not be parsed correctly when converting. When this gets stable it will be such a game changer, you're doing a huge service to the communty. The last major super important thing is figuring out how to get floats ranged properly, there absolutely has to be a way to get normMin normMax parameters represented properly as floats with a range bigger than 0-1 image.png (view on web) <https://github.com/user-attachments/assets/f3de53d3-93fe-4b70-b519-e88623bb3298> — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHYKRGLNT5YPQWWXV5YOV3L2DGXITAVCNFSM6AAAAABSTYMLS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBYHE2TAMJZGY> . You are receiving this because you commented.Message ID: ***@***.***>

[OrdinaireX]

Resolume Arena log.txt
Here you are.

[medcelerate]

Ohh you're having an issue because of the header. That's somethign I've known about but haven't gotten around to sorting a way to fix it as I never use those types of params.

[medcelerate]

I found the source of this issue with the header parameters. It will take a bit of a rewrite to be able to solve it, but I know how to.

[medcelerate]

Ok so there is now a version with a fix when header parameters are included. https://github.com/medcelerate/FFGLTouchEngine/releases/tag/v1.1.1

[medcelerate]

I'm seeing that header breaks everything, and that pulse comes in as toggles, momentary comes in as pulses. Something must not be parsed correctly when converting.

When this gets stable it will be such a game changer, you're doing a huge service to the communty. The last major super important thing is figuring out how to get floats ranged properly, there absolutely has to be a way to get normMin normMax parameters represented properly as floats with a range bigger than 0-1

So there is a way to do it under the hood, but in the UI it will only ever be between 0 and 1. Unfortunately this is due to limits in the resolume FFGL SDK that I do not have control over.

[OrdinaireX]

Hey I am able to get my .tox working well now. Super good to know that the parameters will always be between 0 and 1, I can plan my files accordingly. Might be worth putting that information in the description.

Thanks for the continued support!

[OrdinaireX]

Would it be possible to add functionality for saving the default values of the XY parameters? I'm not able to use intergers to set the resolution of files for some reason. I've only had success with the XY type parameter, but everytime it loads in resolume to 0 when it should default to 1.

Ideally it would be nice to be able to use an integer parameter, but even that has a max value of 1000, when 10000 would be ideal to allow for large stage resolutions (Max I've experienced is 16000 pixels wide)

PARTICLES - Seaweed.zip

You can see in my attached tox, where the Render TOP is setting the resolution.

[medcelerate]

I can look at how x y parameters are set. It is strange integers are not working for resolution, you should be able to use values above 1000 as I believe under the hood they are just double precision floats.

[medcelerate]

I have found the issue for the integer problem, it is in the latest release. Was a limit set by the ffgl config. That limit is now much higher.