New preset / mashup with ORB & Flexi code - Star Forge - Page 9

Fumbling_Foo · 29th September 2018, 01:19

Yes, I do believe after a good amount of rest and a good amount of testing, I will publish the latest private builds, they are looking quite good

.

Old code that worked best and new code that looks intriguing fused together. Both Maelstrom and Synaescope have even been mutually symbiotic in developing each other as well. I'm proud to have introduced this new preset to the community

.

Cheers and enjoy

!

Fumbling_Foo · 30th September 2018, 16:35

I have v3 of Maelstrom ready, a significant update. Should be a good bit more refined.

BTW, Does anybody know if its possible and if so how to get the uv coordinates of "ret" or other tex2D variables? It seems straightforward enough to extract color values from UV coords, but I don't know of a way to do the reverse. In other words, how would I, say, create e.g. "float2 uv2 ..." such that GetPixel(uv2) gives me "ret" instead of "tex2D(sampler_pc_main, uv2)?

Perhaps there's a long way around, too. Synaescope just takes the warp shader and modifies it. What I'd like to do is take the final result in the comp shader of Maelstrom v3 and then modify that like Synaescope does the warp shader. I know, expensive, but I'm sure the result would be awesome

.

Cheers and enjoy

.

Nitorami · 30th September 2018, 20:33

Not sure if I understand the question correctly, but you cannot do the same with the comp shader as you can with the warp shader.

ret = GetPixel(uv2) is identical to ret = tex2D(sampler_main, uv2).

BUT there is a difference between warp and comp shader:

In the warp shader, GetPixel() is its own previous output, i.e. its content one frame ago. I.e. the warp shader can feed its own output back to its input like an echo. E.g. ret = GetPixel(uv)*0.9 in the warp shader causes a slow fading effect.

The output of the warp shader (ret) goes to the comp shader.
The comp can access this via GetPixel().
The output (ret) of the comp shader goes to the screen.

That is fixed in milkdrop, you cannot change it.

Fumbling_Foo · 1st October 2018, 05:05

Thanks for the information, martin. Saved me some trouble

. Good news is I found a suitable workaround just by pretty much copy/pasting some code from Maelstrom. So, without further ado...

Looks like there will be a v8 for Synaescope after all

. This is the biggest visual update in the whole lineup, using code from Maelstrom v3a. Overall a lot more colorful and clear now.

Cheers and enjoy the new hopefully awesome sauce

.

Fumbling_Foo · 4th October 2018, 02:23

I am not in the best of moods now, and my creative ability has suffered somewhat in the short term. There's still some work I'd like to do with the beat detection, as the presets tend to jump too much. Getting the beat detection just right has been just about the most difficult quality to nail down. The visuals a great though. I will give this another go and try and take about a week or so off.

In the meantime, I do have updates for both presets that I've tested A LOT against the last two versions and am just fed up right now with doing any more work with Maelstrom / Synaescope at the moment, so hopefully no glaring problems slipped by. On of the main improvements, for Maelstrom, was that I significantly reduced the presence of the flashing borders so my eyes wouldn't be boxed in and free to wander around the screen. I also updated the post processing a bit for both.

Anyways, cheers and enjoy

. I hope yall aren't as tired of these presets as I am working on them right now lol

.

Fumbling_Foo · 10th October 2018, 23:58

Maelstrom v4 features a more dynamic yet visually synaesthetic response to the music and the visuals. Also, I noticed that the flashing borders tended to focus my attention on the center. Reducing this effect I was more easily able to let my eyes freely wander around the screen and take in the whole picture.

The same is so with Synaescope v9. There seemed to be a little less of an effect borrowing and adapting Malestrom v4's comp shader code, but still the effect was positive and a bit different than Maelstrom's, even with such similar "post processing" code.

Cheers and enjoy

.

Fumbling_Foo · 15th October 2018, 15:57

Maelstrom v4a and Synaescope v9a are ready. Better beat response, especially for quieter music. Better post processing too.

Cheers and enjoy

.

Fumbling_Foo · 17th October 2018, 02:01

Here, both presets go up a version number because of even further advanced post processing.

Cheers and enjoy

!

Fumbling_Foo · 22nd October 2018, 17:49

Better beat response, less smearing, better lighting in post processing.

Cheers and enjoy

!

neebster · 25th October 2018, 06:19

Very intricate presets that scale well to 4k. Good stuff

Fumbling_Foo · 25th October 2018, 15:10

Thanks neebster, I really appreciate your feedback

. Yeah, I've never tested my preset at 4k, glad it does well at that resolution too

!

Fumbling_Foo · 25th October 2018, 17:55

A bit more colorful, towards fixing the sometimes excessive de-saturation.

Anyway's, I've been staring at small but cumulative changes in this preset for so long I was losing conscious awareness of the details and seeing mostly the general form, so I'm glad its intricate

. That's usually what's happened across the whole "Star Forge" project as I've tinkered with them. This is a mysterious but much welcomed effect of development on each line of presets. I make hypotheses as to how some bit of code is working, do guess and check strategies, and eventually perhaps I'll see a positive change in general. I reckon I unconsciously like more detail and those are usually the changes that make the next versions

.

Fumbling_Foo · 26th October 2018, 21:02

Z-ZOMG! Maelstrom has so many downloads already! Unique downloads or users downloading more than once

?

Fumbling_Foo · 28th October 2018, 17:40

Maelstrom v6 and Synaescope v11 are ready for release.

These versions include better detail and pattern evolution, as well as a fix for the peripheral patterns from per-vertex warping sometimes going out of spec.

Note: These versions were saved in winamp 5.8, so hopefully they will still be compatible with winamp 5.666.

Cheers and enjoy

!

Fumbling_Foo · 29th October 2018, 14:41

Live update here, I'm liking very much the new change. The beat response should be more interesting now with a new q variable.

Cheers and enjoy

!

systemcrasher · 1st January 2019, 20:52

Quote:

Originally Posted by Fumbling_Foo

Live update here, I'm liking very much the new change. The beat response should be more interesting now with a new q variable.

Cheers and enjoy

!

hello Fumbling_Foo.....
When i try to use both of those i always get a black screen no matter what version i chose.
help?

Fumbling_Foo · 27th January 2019, 14:52

Hi systemcrasher, I apologize for not stopping by sooner its been a while since I checked the winamp forums (been working with WACUP and I have newer presets there in the discord channel)

This fix should work on my older presets like these. So, at the top of the milkdrop file:

MILKDROP_PRESET_VERSION=201
PSVERSION=4
PSVERSION_WARP=4
PSVERSION_COMP=4

change these to:

MILKDROP_PRESET_VERSION=201
PSVERSION=3
PSVERSION_WARP=3
PSVERSION_COMP=3

There is a bug in milkdrop where if the PS version is set to 4, some graphic cards will cause it to throw an error / not display. This has been fixed in WACUP.

cheers and thanks for your and everyone's interest in my presets

!

Edit: I'm going to release my now latest work on the star forge project here, though it is PS version 4 and probably has too many instructions to work in PS v 3...

Fumbling_Foo · 13th February 2019, 18:35

Latest milestone of development at this time. Tested at and developed in 4k 30fps. Again, Shader Model 3 / PSVERSION=4 only

.

25th October 2018, 15:10	#331
Fumbling_Foo Senior Member Join Date: May 2016 Location: Mississippi, USA Posts: 285	Thanks neebster, I really appreciate your feedback . Yeah, I've never tested my preset at 4k, glad it does well at that resolution too ! Creativity turned into madness. And then back again.

26th October 2018, 21:02	#333
Fumbling_Foo Senior Member Join Date: May 2016 Location: Mississippi, USA Posts: 285	Z-ZOMG! Maelstrom has so many downloads already! Unique downloads or users downloading more than once ? Creativity turned into madness. And then back again.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

30th September 2018, 20:33	#323
Nitorami Major Dude Join Date: Mar 2008 Location: Erlangen Posts: 940	Not sure if I understand the question correctly, but you cannot do the same with the comp shader as you can with the warp shader. ret = GetPixel(uv2) is identical to ret = tex2D(sampler_main, uv2). BUT there is a difference between warp and comp shader: In the warp shader, GetPixel() is its own previous output, i.e. its content one frame ago. I.e. the warp shader can feed its own output back to its input like an echo. E.g. ret = GetPixel(uv)*0.9 in the warp shader causes a slow fading effect. The output of the warp shader (ret) goes to the comp shader. The comp can access this via GetPixel(). The output (ret) of the comp shader goes to the screen. That is fixed in milkdrop, you cannot change it.

25th October 2018, 06:19	#330
neebster Junior Member Join Date: Jan 2008 Posts: 41	Very intricate presets that scale well to 4k. Good stuff