Reproduce the noise of switching resolution

[kokoko3k]

Even if I usually tend to use the solutions that gives the higher final quality/gpu resources ratio, I made further changes/additions.

It is still very light, but i think we are done here, apart maybe for some minor tweaks!

• Tilt amplitude: the image will rotate around the X axis
• Wobblying amplitude: the image will have weavy artifacts
• Bars Size: The bar height can be changed
• Bars Smoothness: lowering will turn smooth bars into blocks

Using the default parameters with the retroarch image viewer, provided you shuffle between different resolution images, seems like when zapping through channels on an old TV

-EDIT-

Ah, as per Direct3D, I’ve seen lot of issues even in koko-aio; it is not really well supported by Retroarch.

[alexb3d]

@kokoko3k

Ahah, no, no way.

It’s a shame, the ambient sounds (such as the CD loading) generate a very pleasant retro-nostalgic atmosphere.

@Ranmori

This is the reason for my unclear story.

These are just suggestions, I have seen that in some cases it works.

I don’t think this is the case of Antonio, he knows how to manage the time he dedicates and I think he sees this as a challenge, something personal, and he rests until he doesn’t achieve it. When this happens, the only thing we can do is to keep up with him?

If you don’t get references, comment it here to search, 4 hands are better than two.

[kokoko3k]

@alexb3d

It’s a shame, the ambient sounds

Yeah! I wish there were a sound plugin that allowed to just play background sounds; there are many reproducing Arcade rooms ambient sounds on YT.

I know you can just leave them playing with the browser, but it would be nicer to have it integrated.

[Ranmori]

This time it is perfect for me!
Thank you for making this noise shader.

I don’t have one more complaint.

[bureydey]

I understand that the noise in the middle of the PS logo appearing is a subtle change in resolution at the moment the PS logo fades in if it is not de-interlaced.

[sonkun]

@kokoko3k I didn’t realize you made this feature a separate shader that’s now in the crt folder, I thought that would be exclusive only to your shaders. I just prepended “crt-resswitch-glitch-koko” shader right on top of one my presets then loaded up a ps1 game and now see all the resolution switching magic, amazing. I’m tempted to put together a quick update pack with that shader in the mix lol. Thank you for this nice shader feature.

[kokoko3k]

Yeah you can prepend it and it will just work.

But with very little efforts one can almost do a copy/paste into an existing pass to avoid unnecessary overhead too.

Not a suggestion, just a possibility.

[Jobima]

thanks kokoko3k, seems it work even with 4x of the ps1 resolution

edit: also thanks Ranmori for remind us of this

[Ranmori]

I’m not sure if there is a demand for “noise characteristics by specific model OR manufacturer”,

I was hesitant to share this because there are so many parameters available. Because I only use about half of the parameters I used.

But I decided to share how it looks on the SONY/aiwa Trinitron for Flat Type. It will look like this. It is important to note that this aiwa Trinitron was a subsidiary of SONY back in the day.

In the case of SONY Trinitron, the white lines appear brighter, and in fact, using this as a shader would be distracting, so we adopted the aiwa Trinitron model to reproduce this.

[kokoko3k]

Effect does not work on d3d11 because (checked) it is unable to access old frame sizes.

Now, since workarounding the issue requires the shader to be almost completely changed, the bug is not in the shader and since d3d12 seem to work, I just made a sanity check for d3d11 symptoms and disable the whole effect.
“no d3d11” has also been added to the first shader parameter.
The change will be published via online updater.

@sonkun @JosepMC

[Cyber]

@kokoko3k

screen shacking and a noise bar.

You have to be careful using extremely poor CRT footage in any format as a reference for finding examples of CRT behaviour and phenomenon unless you’re trying to recreate the “badness” caused by the recording medium as well or instead of what the CRT was actually doing or how it looked.

It might be better to isolate the CRT itself from any possible skewing of the data caused by poor recording practice or the nuances of the medium.

What I see here is an attempt to (mistakenly) emulate the lack of synchronization between the video creator’s camera shutter and the CRT’s electron beam.

I’m not too convinced that the desired artifacts are coming from the CRT itself, at least in those examples.

@Ranmori

It looks exactly like a CRT from back in the day.

I disagree with this statement, at least from my experience and memories of CRTs. I don’t remember resolution switching being so jarring at all. Never saw hum bars during that process either. Maybe I’m just really old and can’t remember things well enough.

@Ranmori

I wonder if the actual device should only be used when the resolution changes significantly? 640x480 -> 320x240 etc.

But even in that state,

This statement hints to me that there might be some doubt as to the accuracy and authenticity of the said effect but you just don’t seem to mind.

[Ranmori]

@Cyber

This statement hints to me that there might be some doubt as to the accuracy and authenticity of the said effect but you just don’t seem to mind.

Seems contradictory, but this is because there were CRT that only generated this noise when there was a big switch in resolution, I remember Panasonic was the one.

Also, at that stage, the shaders are not as complete as they are now and change is only good when the resolution changes significantly? And I just thought so. But with the addition of the percent increment parameter, it has been resolved.

And I believe this noise is a matter of personal preference when reproducing CRT. I preferred it. I think of it as equivalent to some people liking NTSC shaders and some not liking them.

[sonkun]

I’m not familiar with the d3d11 driver but I assume with the latest update Xbox series s users can get the proper effect switching to d3d12 instead.

[kokoko3k]

@Cyber

You have to be careful using extremely poor CRT footage in any format as a reference for finding examples of CRT behaviour and phenomenon unless you’re trying to recreate the “badness” caused by the recording medium as well or instead of what the CRT was actually doing or how it looked.

Of course, but.

I have provided something without claiming it to be correct, on purpose; because I am here to evoke memories and joyful moments from my childhood, not ‘just’ to leave an historical and accurate testimony for future generations; although that does interest me to a certain extent, it is not that much.

Also, never forget that your eyes act like a camera and your brain acts as a -possibly lossy compressed- memory for that footage.

If something tricks my and other brains in thinking what they see is the same as it was, then I accomplished that goal; if someone say that it remembers it to be a bit different, then we can add a parameter to accomodate that too.

If someone does not remember ANY glitch at all, disable it.

Bars were not present? You sure? Well! There is a parameter to morph them or to fade them till the void.

That said, we can discuss about the correctness of the result too, why not.
the “bars” are an aproximation of the real phenomen, which is the image content vertically shrinking, while still shacking and twisting very fast.

The afterglow effect may contribute to smooth out that by turning that very fast movement into something more solid, your -not perfect- eyes can contribute to that too.

Image should be NEVER displayed alongside the bars, because the image itself morphs into a bar, but on a real crt, all that happens so fast that is impossible to replicate on a mere 60h or, worse, 30fps running shader (the shader runs at core refresh).

All we can do is to imagine that those very fast glitch can be time compressed into a bar appearing “in the same frames” as the image.

Check this from real fresh footage just done by me, 900+fps, see the afterglow, see the image shrinked at bar size at second #12, then suddenly the synced image.

https://mega.nz/file/kX9znJQb#Mvpx9mjWNUvgk58RfVam80EChw85UM2gghKN27aNNLc

At 60fps the image kinda morphs into a noise:
https://mega.nz/file/pOsnWSCR#BDE8nbFUs102jEBN5LS1rtW64fkTC_Z1QxUWjT5G48s

This is upside down, sorry
https://mega.nz/file/8fECQKLJ#b6JwdQz7qclBgHR-11UZYbCiwonsheSX536W_5f0MeY

Those videos explain what the bar is for; where it should be placed seem to vary greatly from circuit to circuit (or even on the same circuit, from switch to switch) due to probably too much obscure things that i like to call randomness, so we paint them at image borders and give the user the ability to shake the image more, so that the bars would appear more or less centered.

[hunterk]

@kokoko3k

it is unable to access old frame sizes.

I haven’t looked at the actual code in question, but can you use textureSize() here? It’s more expensive than the built-in *Size uniforms, but I’ve had good luck with it in the past.

[kokoko3k]

Not from the vertex shader

[oldpainless]

Arey you guys talking about rolling hum bar? If so, that does not appear in person when viewing a CRT screen, only when trying to video it.

[hunterk]

no, it’s the blink that happens when the display momentarily loses sync due to the changing of the mode.

[Ranmori]

@hunterk

it’s the blink that happens when the display momentarily loses sync due to the changing of the mode.

Yesterday I told my wife, who was wondering how I was doing, and when I tried to explain the situation to her using an LCD TV, BRAVIA as a substitute, she started a PS2 game on the actual PS3 and when she went back to the PS3 XMB, there was noise and a white bar. lol

I have a 720p to lost signal (HDMI text appears), then 720p is input again, then 1080p, but at the moment of going to 1080p, white bars appeared.

I didn’t think that even today’s HDTVs would have noise on the resolution switch. Or maybe I just forgot all about it or didn’t care…

ps
This seems to be highly random and does not always produce a white bar. I tried to take a video of it just now, but no white bar appeared.

[oldpainless]

Ah, ok…makes sense.