[SOLVED] HueSaturation module reduces visual Quality! (Iterator Spectrum)

[HexaCube7]

Hi i think i found a bug when using the HueSaturation or similar modules in combination with a custom Iterator Bar Spectrum, it significantly reduces the quality of the displayed image components.

This only occurs when the module is put infront of the Translate and Iterator Modules which generate each individual bars and displaces them horizontally.
If you put the HueSaturation module behind those the visual quality stays the same however i need it infront because i want each indivual peak-visualizer to change colour depending on where it is. Putting it behind just changes all bars colours as one whole thing.

Demo Video here:
https://youtu.be/gAKmLqkQ1QE

I did not have this problem before, because i wasnt using peak visualizers like that yet, i was only using simply iterator spectrum bars with no peak indicators, so i was able to do the indivudual colour change in the same ColourHSB module that also gradually changes colour and fades through all Hues. However that rainbow-faded effect does not interact well with the "Peak" modifier so i had to split the "rainbow fade" and the "individual Hue change" into 2 modules, but two ColourHSB modules in line did not interact the way i need them to.

Edit: Notice in the end of the video how WITH the HueSaturation module connected the peak bars also move in a jumping-from-pixel-to-pixel fashion compared to the desired smooth motion of the desired sharp looking peak bars WITHOUT the HueSaturation module connected,

[Terry Payman]

Please post the Magic project, or a cut-down section of it that shows the problem. Then it can be quickly checked by others.

I've never seen any problem with the HueSaturation module and haven't got time to go looking if I have to guess at what's obstructed by the Magic window in your video.

[Sadler]

Use the ColorHSB or ColorRGB nodes instead of the HueSat node. The HS node operates on the window output which will capture the rectangle at the output resolution (say 1080p) covering only a few pixels - when this is later scaled up you get mipmap style blurring. This is a limitation with all video effects, not just HS. HS will also kill your framerates when used with an iterator. The other color nodes don't have these limitations.

[HexaCube7]

Please post the Magic project, or a cut-down section of it that shows the problem. Then it can be quickly checked by others.

I've never seen any problem with the HueSaturation module and haven't got time to go looking if I have to guess at what's obstructed by the Magic window in your video.

Here's the cut-down project. The HueSaturation Module is not connected but there.

[HexaCube7]

Use the ColorHSB or ColorRGB nodes instead of the HueSat node. The HS node operates on the window output which will capture the rectangle at the output resolution (say 1080p) covering only a few pixels - when this is later scaled up you get mipmap style blurring. This is a limitation with all video effects, not just HS. HS will also kill your framerates when used with an iterator. The other color nodes don't have these limitations.

Thank you very much for that info, i really lack such background knowledge. Especially didnt know it is this bad for performance.
I had tried the ColorHSB module inplace of the HueSat already but interacts in a strange way unknown way to me with the previous ColourHSB module.

Its like from the first ColourHSB module (responsible for the slow rainbow-fade) only one colour is let through, which the second ColourHSB module (the one that changes colour of the bar depending on its position) then modifies. When i am not playing any music and everything is still the bars only fade through red that gets darker and brighter again in a breathing fashion (like only moving the R-Slider up&down in an RGB control panel).

Other colours only show at higher positions when music is playing.
How do i solve this to be correct?

Here's the project with the second ColourHSB module in place:

[Sadler]

I've left your 'cutdown' version in the attached project and trimmed it a bit more in a duplicate scene so it's easier to analyse. As long as the bars remain white, you can use the HS after the iterator (as late in the chain as possible after all the scaling and translation). I liked your trick of translating the bars by half the scale to level them using the iterator frequency again - I tend to translate to the middle before scaling but they're probably the same in efficiency.

CUTDOWN_ColourHSB-peak__Hexa_Stream-Visualizer_Mk4-2dv.magic

(4.83 KiB) Downloaded 1417 times

[HexaCube7]

I've left your 'cutdown' version in the attached project and trimmed it a bit more in a duplicate scene so it's easier to analyse. As long as the bars remain white, you can use the HS after the iterator (as late in the chain as possible after all the scaling and translation). I liked your trick of translating the bars by half the scale to level them using the iterator frequency again - I tend to translate to the middle before scaling but they're probably the same in efficiency.
CUTDOWN_ColourHSB-peak__Hexa_Stream-Visualizer_Mk4-2dv.magic

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: Wait im an idiot when opening the file you sent i forgot you said you changed it in a duplicated scene... You're actually so smart using the HueSaturation module for the rainbow-fade instead of the peak-colourchange... That literally solved it! I still wonder if it is possible in some way avoiding the HueSaturation module, but thats jsut curioisty at this point, thx!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I see what you mean but the issue would be that if i put the HueSat module behind the module that create and displace the iterator bars the HueSat module would apply to them as one whole thing (unless there is anotehr way to do it), meaning it would not colour each separate peak-bar each depending on how high they are, but just all in one uniform colour similar like what the rainbow-fade effect is supposed to do.