Kalles Fraktaler 2

[Dinkydau]

Can kalles fraktaler be used with CMD to create kfb files using given settings?

[Kalles Fraktaler]

No unfortunately not.
What version are you using?

[Dinkydau]

I'm using version 2.2.10.

[Kalles Fraktaler]

Have you continued the render, is it running now?
I have had a look at the bitmap and found a thing that I corrected recently, but that us included in version 2.2.10. I will look some more...
If my site is not accesible within a couple of days I will put updates somewhere else.

[Dinkydau]

Kalles Fraktaler crashed again after one frame of which the JPEG file was again incorrect. It's not running right now because I'm out of ideas. The strangest is that everyone appears to be able to render videos, and I have been able to do a few simple test videos, and now in a real world scenario all those strange things happen.

I haven't seen it fail in the middle of a render, though, so that's why I was wondering if it's possible to use it with CMD. Then it would be easy (or I should say "possible") to make a batch file and let all the frames be rendered separately. I used to make apophysis animations that way. It's a very flexible method. For example, multiple batches could be run at the same time to fill up empty CPU time when a reference point is being calculated using 1 core. Such renders can be easily resumed if anything happens. It's generally more reliable, and when a crash occurs the damage is easier to repair.

[Kalles Fraktaler]

Thanks to Chillheimer I am now able to make a new version of this experimental prototype of application available
The update can be downloaded from http://www.chillheimer.de/kallesfraktaler

The news of Kalles Fraktaler 2.2.11 are
* Super smooth coloring. The old color method is still accessible via the "Iterations" dialog (I put it there since it is affecting the bailout value and needs the whole view to be re-render)
* Option to select if jpegs are not to be created when making zoom sequence.
* I have gone through the code and tried to prevent the bitmap from being accessed from concurrent threads, which I think may cause the program to crash.

The news of Key Frame Movie Maker 1.17 is that the performance is improved, thanks to Yann Lby (via youtube) that gave me tips.

[panzerboy]

I get a "Failed - No file" when trying to download the movie maker.

The two versions of Kalles Fraktaler download and run okay.
The new smooth colouring looks nice 

[Kalles Fraktaler]

Thanks for that panzerboy, sorry I forgot to upload that file.
Please try again

[SeryZone]

I was downloaded new version! It is cool! You set high bail-out value! I was think that perturbation can't use high bail-out...

What's happened with your biphome.spray profile? I was download your 'Kalles Kalkylator' - cool program!

[simon.snake]

I've been generating another interesting zoom to e637 (it's taken most of the time to redraw the frames as a lot of them were generated offset from the centre).  I'm down to the last 3 or 4 hundred to check.

I have found out what all the items in the status bar at the bottom of the window except the last one, the S: value.

I'm sure I'll kick myself when I find out, so please put me out of my misery.

Thanks

Simon

[Kalles Fraktaler]

I've been generating another interesting zoom to e637 (it's taken most of the time to redraw the frames as a lot of them were generated offset from the centre).  I'm down to the last 3 or 4 hundred to check.

I have found out what all the items in the status bar at the bottom of the window except the last one, the S: value.

I'm sure I'll kick myself when I find out, so please put me out of my misery.

Thanks

Simon

S = Smooth coefficient, a value between 0 and 255.
It is displayed so that I might be able to see why any blob doesn't get solved automatically.
So it is more for debugging than being informative

[Kalles Fraktaler]

I've just uploaded a new version - 2.3
Thanks to Botond Kósa I got a couple of tips to speedup the render, which is now some 3 times faster.
On my machine the bench-mark view "tick-tock" was rendered in 8.5 seconds - it is now rendered in 2.7 seconds, on my machine.
Still a way to go to Mandel Machine that renders tick-tock in 1 second on my machine, but it is still a big improvement.

Also Key Frame Movie Maker is updated to version 1.18 since I found a bug related to the caching function I implemented in the last version - everything except the maximum iteration value was stored in the cache, which caused problems when one stop the zoom sequence render and lower the maximum iteration value, which I usually do in order to faster render the initial close passage of the main Mandelbrot.

I think this will be the last update on Kalles Fraktaler, since my knowledge in assembler optimizations is very limited (unless an insurmountable bug is found or something new revolutionary is discovered).
I leave with a warm hand to Mandel Machine to take the lead in the realization of the perturbation and series approximation methods.
Thank you all for your interest!

PS. But I will sure publish a movie once in a while with my program.

[Dinkydau]

The time to render tick-tock has been reduced to 0.97 seconds here, so it's not much of a difference, but that zoom I'm rendering at high-resolution and very deep, that's where I really notice the extra speed. Really 3 times faster? Even more, I'd say.

[Kalles Fraktaler]

The time to render tick-tock has been reduced to 0.97 seconds here, so it's not much of a difference, but that zoom I'm rendering at high-resolution and very deep, that's where I really notice the extra speed. Really 3 times faster? Even more, I'd say.

Tick-tock may not be the best view to use for comparison, since it is now rendered so fast that the overhead of image handling, glitch detection, etc is significant.
I was rendering an animation and when I stopped it the frames were rendered in 8 minutes each. When I continued it in the new version the following frames where rendered by 3 per minute...

[Kalles Fraktaler]

An insurmountable bug was found and fixed.
Minibrots between e300 and 4920 got distorted, which is now corrected.
Newest version is 2.3.1