Kalles Fraktaler 2

[ratcat65]

Hello to everyone on the forum.
I have been using Kalles Fraktaler for a couple of weeks and getting accustomed to its various behaviours and occasional bugs.
I loaded a kmm file which was made in the previous version of the movie assembler into the latest version and the resulting movie has colour cycling at a much faster speed. I can't get it to cycle slowly the way the previous version did. A value of 1 or -1 produces much faster cycling than before.
Unfortunately I lost the older version of the movie assembler when windows 7 did a collapse today and I had to do a fresh install. The previous version isn't hosted on the site anymore and I need to re-do a movie in the slow cycling mode which were lost in an accidental overwrite.

[Kalles Fraktaler]

Hello ratcat65

I've seen your movies, thanks a lot for these!

You can specify float numbers for color cycling, so if 1 is too fast you can enter 0.1 instead

[youhn]

I know it's not totally appropriate to post images in a software announcement topic, but I just very much like the new color waves! 


Source: http://jeroensnake.deviantart.com/art/Transparent-waves-of-colors-453874875

Notice how the colors line up to create some sort of fake transparency effect.

[Pauldelbrot]

I know it's not totally appropriate to post images in a software announcement topic, but I just very much like the new color waves! 

Seems perfectly appropriate to me if it's to showcase what the relevant software can do.

[Kalles Fraktaler]

It's totally appropriate!
It's a fantastic image!
Thanks a lot!! 

[cKleinhuis]

indeed, it seems that i need to open up a kalles fraktales section as well, with dedicated gallery section

@kalle what about hosting kalles.exe on ff ? to provide a consistent download and versioning location ?

opening up a kalles fractaler section is not accounted by that, but might be helpful to keep track of versions that people use!

[Kalles Fraktaler]

indeed, it seems that i need to open up a kalles fraktales section as well, with dedicated gallery section

@kalle what about hosting kalles.exe on ff ? to provide a consistent download and versioning location ?

opening up a kalles fractaler section is not accounted by that, but might be helpful to keep track of versions that people use!

I don't mind hosting the exe on ff too, I can do the updates both on www.chillheimer.de and ff.
I think the updates now will decrease in frequency, but it's not the first time I think so though, and I have one more really really cool update on it's way.
I hope I have time for this update this weekend.

[Dinkydau]

Variable power mandelbrot sets with perturbation?

[blob]

Antialiasing! 

[Kalles Fraktaler]

Yes, variable powers!

Testing this takes too long time so I have put the update available, now version 2.5.1. Should be considered as beta, since it is not fully tested yet, but you are very welcome to help me!

There are 4 breakpoints for the datatypes used, and I think these has to be adjusted for higher powers. To test this it is necessary to zoom to that deepths to see where the datatypes breaks. Zooming to e4900 with high powers takes a while I guess, because it takes a lot of time even to e300...
But it is also possible to force long double or floatexp to be used though.

Power	double	Scaled double	long double	floatexp
2	<e300	<e600	<4900	>e4900
3	<e300	<e450(!)	<4900?	>e4900
4	<e300?	N/A	<4900?	>e4900
>4	?	N/A	?	>e4900

You can now enter any integer up to 70 as power, however I recommend max 7 since the glitch detection might not work on higher powers. I had to increase the threshold to detect glitches at all at power 7, and I haven't tested fully above that. Again, it takes long time to test.
Above 70, even double is not enough to render the un-zoomed m-set, at least not with my current implementation.

I also implemented the merge color optionally as sine wave, which youhn suggested

[laser blaster]

Awesome! KF just keeps getting better and better.

[ellarien]

I've been playing with 2.5.0 for few days now, and 2.5.1 for a day or so. I think zooming to > e300 with the higher-degree sets is not for the faint-hearted or under-cooled, even with perturbation; the higher the power, the harder the computer has to work for even quite small numbers of iterations, and things get dense quite quickly.

This  (power 6) took around half an hour to render at 3K width, and the iteration depth is only 20K:

may15_03 by ellarien, on Flickr

Code:

Re: 0.19009200738664003775048587995178562421318906985724823420747507642375015168586422
Im: -0.57206855350604207966820504558824438694743084644648755240244611252141286546718753
Zoom: 1.49657767662E51
Iterations: 19082

I guess it would have been completely out of amateur reach without perturbation!

The upside is that in this relatively unexplored territory I feel less embarrassed about sharing my modest attempts at movies, like this power-6 zoom down to 1e70: <a href="https://www.youtube.com/v/uff2T_0U1IU&rel=1&fs=1&hd=1" target="_blank">https://www.youtube.com/v/uff2T_0U1IU&rel=1&fs=1&hd=1</a>


The added capabilities are great, but I have found a few niggles.

-- Sometimes in a zoom-out sequence, if a glitch or minibrot falls across the edge of a frame, the parts outside the frame won't be properly solved on subsequent zoomed-out frames. Usually this can be fixed by going to that frame in the zoom sequence examination tool and doing a 'refresh', then adding references by hand.

-- Speaking of which, I love the ability to jump to a specific frame when examining the sequence, but it woud be nice if the number to enter matched the number on the kfb file instead of being the difference between that and the highest frame number.

-- It seems to cause problems (program hangs or goes into an endless loop) if I try to change the iteration limit while the calculation is running. The obvious work-around is not to do that. Changing the window or image size mid-calculation may also do bad things.

-- The minibrot finder doesn't seem to very useful with the higher-degree sets, but I'm not sure how hard it would be to tweak it. (Having said that, I just turned it loose on a filament of the power-3 set, and while it won't settle on one minibrot it quite happily took me down to e400 in a few minutes, at which point it seems to be stuck.) --Update: after a couple of hangs and restarts around e400 I got it chugging away again, and it finally zoomed in on a minibrot at 5e617. (I don't suppose that's a record? I'm happy to share the location, but it would make a really boring movie!) So apparently it does work if you can get deep enough to isolate a minibrot in the first place ... End update

-- Would it be possible to automatically switch off the new checking for the last few frames of a zoom-out? It gets slow when half the frame is occupied by the main 'brot.


Finally, thanks again for the new toys!

[Kalles Fraktaler]

Thanks ellarien. Yeah I already found your movies! They use a little higher resolution, but they are indeed lovely!
And with them I found an error on the transition of references, around e10

Glitches falling on the edges should be solved automatically for at least 2nd and 3rd power, but I found that glitches may sneak through for higher powers. I guess the threshold value needs to be adjusted further.

File name number in Examine Zoom sequence can be added, and I guess I never tried to change maximum iteration or background image size during rendering. Should be easily solved by stopping the render when these parameters are changed. You can also stop the render with the escape key before you do such changes.

The find minibrot expects two-fold symmetry, so it should work on even powers. But it definitely does not work for odd powers. That would be very tricky to achieve I think

If you start a zoom sequence at a deep minibrot with some million iterations, it will be very very slow when it is rendering the ending frames with the big main mandebrot occupies most of the view. You can stop the render, decrease the iterations, and then start the render again, not with resume but with store zoom sequence, because it checks the files already created and starts from the last number. Using escape key to stop rendering while changing parameters. I should make it automatic though.

Thanks for your list. There will be a new version soon

[ellarien]

Thanks ellarien. Yeah I already found your movies! They use a little higher resolution, but they are indeed lovely!
And with them I found an error on the transition of references, around e10

Thanks! I'm afraid bandwidth limitations make it hard to go much higher in resolution -- it takes me about an hour to upload 100Mb. I have another movie ready to upload where I avoided the e10 issue by recalculating the problem frames with no approximation, but I'm glad it was helpful.

The find minibrot expects two-fold symmetry, so it should work on even powers. But it definitely does not work for odd powers. That would be very tricky to achieve I think

I've done some more experimenting, now that I'm getting more of a feel for the higher powers. It works OK on 3, 4, and 5 if I find a good place to start -- somewhere with roughly circular patterns. 6 and 7 are trickier just because the minibrots are so close together, so it's hard to get a good zoom going, but I have found locations where it will auto-zoom for at least a few steps.

Thanks for your list. There will be a new version soon

Happy to help, and I look forward to the new version. One more quirk that I noticed yesterday: if I 'save as jpeg' with a different resolution from the current one, the frame renders with the new resolution before opening the save file dialog. That's fine, but then after saving it starts to render again -- at least the glitch-fixing passes, maybe not the whole thing -- which seems unnecessary and can be a bit of a pain when the image takes a long time to calculate. Again, it's easy enough to render at the required resolution before saving, so not a big problem.

Thanks again!

[kjknohw]

Nice update!

You can't save the infinite wave palettes?

Guessing starts at 2x2, not 4x4. This is important near a the black when using a high iteration count. 4x4 is more prone to artifacts, so maybe a toggle.

The find minibrots is broken even on the z^2 mandelbrot method for me. Has anyone had success with this? Although it is a minor feature.

Pauldelbrot uses a method that exploits "regularity near deep mandelbrots". This will be a fundamental speedup on-top of perturbation. You may even be able to apply it to when calculating the reference pixels. Is anyone working on combining these methods? Time for some amazing images!