Welcome to Fractal Forums

Hi!
Because the original Kalles Fraktaler Thread (with now 14 pages and still growing) is getting more and more cluttered and hard to search I'd like to have a kind of bug-/wishlist where all bugs and whishes are collected (and striked through when done).
Kalle, may I suggest that you copy this thread and start it as threadstarter, so you can collect stuff in the first post? everyone could see what is planned, not planned, done, maybe with a rating system for bugs/wishes  for example like this:
-one *(nice to have one day) to ***** (absolute showstopper),
-b=bug, w=wish,
-plus number to easily find a bug. and f for kalles fraktaler, m for movie maker

Example: 22 B ***

just a suggestion, this is how we did it at the software company I worked some years ago.. feel free to modifiy.m
kalle, please don't understand this as a try to put pressure on you. just to make the contributions/wishes from the community a little more organized.


so here are my points, collected over the last months:


Kalles Fraktaler

1f W **** free adjustable image size for other ratios than 16:9. (see whish 1m)
2f W *** make colour selection easier in general (see following points)
3f W *** add undo to colour selection
4f W **  add colour cycling (by scroll-bar?) to colour section
5f W *** possibility to set the first 10 renders of zoom sequence to a (manually set?)higher iteration to show the usual final minibrot in good detail
6f B ** disable clicking when in "store zoom out/resume" mode to prevent accidental clicks that can cost hours of render time.
7f W * idea: make pseudo 3d possible by using darker version of colour to all points facing southwards and lighter facing northwards.. (know what i mean?)

Movie Maker
1m W ***  rotation halves resolution. unclear what to put in these fields. please enable us to use resolutions like 1920*1920 in KF to safe even more render time
2m W *** use multicore! especially when colour cycling is enabled, movie generation takes longer than actual rendering..
3m W ** softer transition of speed changes possible? they are still visible, even with many set points. optimal: a checkbox you can klick that will make a speed change gliding between the frame number where its checked and the naxt frame number. For example: Frame 1= Speed 25 X (checkedcheckbox) Frame 20 Speed 60  results in a movie starting at Frame 1 with speed of 25 gradually slowing down over the next 20 keyframes until it reaches speed 60 at frame 20.
4m W *** change palette after rendering the zoom sequence? if you can cycle or do smooth colours, this should be possible right?
5m W **  change colourpalette to previously safed (kf)palette at set points in zoom sequence to keep things interesting in long zooms
6m B ****! examine zoom palette: I can't enter the frame numbers manually, the textbox doesn't react to my input. to reach frame 300 of 600 I have to click for 20 minutes to reach the middle... very annoying
7m W *** fast lofi-preview if "preview only" is checked. right now it takes as long as a full render, so relatively useless. maybe automatically shrink to 1/4 or 1/8 the original size?
8m W ** preview starting from user defined frame numbers, to have a short look if that part in the end of the movie will turn out as planned
9m W **** adjust framenumbers-name so you don't have to calculate all the time. good solution maybe to show the last selected frame in the preview window, so you have feedback what frame you really worked on.
10m B *** Ability to handle higher resolutions (needed because of 1m), 7680*.. leads to crash everytime..
11m W *** New and easier way to handle frame numbers. should be the same as the name of the actual jpg, so you don'T have to calculate anymore.
12m W ** Speed Control: automatically calculate speed into seconds, so I can enter the time directly instead of calculating frames-->sec.
13m W ** "Stillframes" - ability to let keyframes stand still for a time (in which you can then change e.g. the direction/speed of colour cycling)


ok, that's a lot already. sorry  :embarrass:

there's more utopian stuff ;) but that'll have to wait probably..

regards,
chilli

*Bump*

No idea if this has been in use, but I think it's a good idea. No demands, just some wishes. Here are my votes:

Kalles Fraktaler
1f W *
2f W *** make colour selection easier in general (see following points)
3f W *****
4f W DONE (I think the Color offset does this?)
5f W *
6f B ***** (This is a Wish, not a Bug?)
7f W *

Movie Maker
1m W *
2m W ***
3m W ****
4m W *
5m W *
6m B * DONE (I think this is fixed?)
7m W *
8m W ****
9m W ******
10m B ******
11m W ****** (Isn't this the same as no 9?)
12m W *
13m W **
14m W ***** (NEW) make it possible to start a video at some deeper zoom level (no need to create the whole zoom-out sequence!)

My utopian stuff would be overlaying new palettes over the current one, using the layer modes (or blend modes) from The Gimp. Also to project the old palette onto the infinite waves, to have the best of both things.

Hi

Sorry for not replying on this.
I think your ideas are good and will give them a go.

I hope Botond would make a similar open interface when he eventually make movie support.
Perhaps using the same format? (even though it might be a little faster to change the x and y dimensions in the data :))

One bug to report- starting a zoom sequence with the 64 bit verson crashes. However, starting with the 32 bit verson works fine. I am running Linux Mint 17 64 bit, with 64 bit wine.

That is great that the 64-bit version works at all on wine, others (youhn) only use the 32-bit version.
Anyway, unfortunately I have no access to Linux.
I am about to upload the latest source code...

1 F W ***: A way to select a certain point which is inside an infinite spiral or a different shape (or to the end of an infinite needle or an infinite ''lightning bolt''.) which does not end into a minibrot. And let the program zoom into that point, the user can specify until which exponent it has to.

Quick update. I've been using the 64-bit version since a few weeks now. Only it crashes on zoom-out sequences, so for that purpose I sometimes switch back to 32-bit.

Hello,

Just started using Kalles Fraktaler.  I have it on a Windows 8, 64-Bit, laptop.  I downloaded the 64-Bit version, but when I run the program I get an error concerning the DLL (ldbl64.dll) not loading.  The program still seems to work but I have no way to know if it working as intended.  It is a bit slow but I don't know if that is due to program or my not-so-powerful laptop.

Any ideas?  Is there an issue with the DLL and Windows 8 64-Bit?

Thanks in Advance...
WKCook (A.K.A. - Diddy)

Hi Diddy

The ldbl64.dll file, included in the download zip, need to be located in the same directory as the exe file.
So you should extract them both into a folder somewhere on your hard-drive.

ldbl64.dll is not necessary but contains code for 80-bit long double and is invoked for locations deeper than e600 för standard power 2 Mandelbrot and earlier, i.e. e300, for other types and powers.

Kalles,

I did place it in the same folder.  Doesn't seem to make a difference.  As I said, the program appears to be working, just slowly.
I am currently zoomed in to 4.33e624.  Maybe it is just a Windows 8 issue.

Diddy

I have tested it on Windows 8 and it worked for me.
What is the exact message you get?

Thanks for the feedback

Kalles fraktaler works fine for me on a Win 8 laptop, no error messages. Maybe the OP needs to update their verson of KF?

I've been ZOOoooming for 3 days!  I will wait until I am satisfied and will get the error for you again.  It is slow but fun still.   :dink:

Currently at:

Re:  -1.28937501214747554233488930034144266735576739169911075151927291186376778324175378555014745137998047806477098267598085380735079224197127180225048227720688719312516863339803060057710116575149291210905257043684503094914542365795338908097615269027835112357984354725118004125134111531956822406589076325164550791963258136497556490815573962797025602561596225388804409726906389479559546635243459115205303818789238622946062864925371820245149422250155627456816744428128539979223598796040528533189719535658687287263235302816278508190819264636904656330888996509508281854448680371716602699576022380997847287430065419447525514867525367650813228880891636710994586040381774289665806393449531983245665381922605508604022163136802981328287987125912960258927660187929243716960659025

Im:  -0.4355477438221693598075970510825496613672553174015079470263755950641184688950541667789812791004520805126314541556345894771576467967828459990421896113738104296273639998050522344705387655379912011583223575110458539802803236365562340160397726320697889869903326954874952626244094624444245589976155378830430085782927707543226517790109060166574658697379050113527149590449703473522660851565681861748989405201520306616673291597516004122438791571530249786732207607858330908991927077880934188787237010170599675099580239412103897088703328034774548121337538401677919900566745512483805792576981819919424380425549948350984652494939712329987673044786124168796169873401413946522429926171601498169272841111099743495666724873197778683015451511156562348828535348609518932239988797

Zoom:  8.54533990273E739

I am patient.

Thank You . . . Diddy

What the hell do you mean by slow? KF is amongst the fastest fractal calculations available to humankind! Perhaps you mean the reaction speed of the GUI? Or the layout and control of the gui, which makes your workproces slow ... ? Compared to what other program or reference do you think it's slow?
Please explain.

 ;D
oh well, waiting several hours for a single still frame can feel slow.. I guess that is what Diddy meant.
Otherwise, I'd suggest to try rendering your location in an 'old' program like fractal extreme and come back in 10-20 years to tell us about how slow slow really can be.. ;)

Not shure if this would do. But Bump map post stransformation can do pseudo 3D. Bump mapping (using greyscale version of the image as a heightmap) can do miracles in transforming ordinary flat picture into pseudo 3D. Like this: http://www.fractalforums.com/new-theories-and-research/solidifying-transformation/ (http://www.fractalforums.com/new-theories-and-research/solidifying-transformation/)
Here is bump mapping
http://en.wikipedia.org/wiki/Bump_mapping (http://en.wikipedia.org/wiki/Bump_mapping)
But then you need some customisation or at least good 3D looks on default. Or most of bump mapping I encoutered in fractal software so far was pretty lame and unusable.

I have another feature on my mind I agitated for the Ultra Fractal. Colour palletes generated by mathematical functions like in old Fractal Explorer. So the colours looks more vivid and alive if compared with outdated Ultra Fractal gradients or Fractaint map files. Multivawe coulour method is nice but not as much as FE colour style.
Official site seems to be down.
http://www.eclectasy.com/Fractal-Explorer/index.html (http://www.eclectasy.com/Fractal-Explorer/index.html)
But unnoficial are not (but there is no way to get sold source code unless you knwo someone who bought it and I don't):
http://www.angelfire.com/art/fe/download.htm (http://www.angelfire.com/art/fe/download.htm)
It is sayd that this feature originated in Sterlingware but I hadn't used it.

@youhn:

Chill!  I have experience only with Ultra Fractal and it does not zoom this far.  My only point of reference is what I have read on this Forum...Fast, Fast, Fast.  So go calm down somewhere, please.

@Chillheimer:

Point taken.  At least your critique of my posts was more civil.  Still zooming on my original attempt.  I usually can't get started until after 6 or 7 at night. (After work)

I am down past e829 and still having fun...That's all that matters at this point.

Thanks for the replies . . . Diddy

With the ldbl64 library working it would be 3-4 times faster.
You could also try mandel machine :)

I found a bug:

I tried to render a movie with a histogram colouring for the celtic. When I changed the colouring-method I saw that there were 10 instead of 5 methods. The additional five have the same name as the first five. When I rendered the keyframes and wanted to render the movie when I started it the program crashed. When I select the first histogram to render the keyframes I get a black and white colouring and for I select the 9th option (second histogram option) the moviemaker crashed because it has only five options.

Yes, I agree with Dagomar!

Just a quick one: Could the pixel guessing (the little G indicator at the bottom of the screen) start to work after the first pass, instead a later pass? It would make some things about twice as fast.

Maybe two other things:

-A wave-system for colour/iteration -division.

-Have you tried to implement the omnibrot? The first one will not be implemented/hard to implement (according to what you said about the goniometric functions), because the first type contains a sinus fuction. But the second only contains a exponetial function (z=z*z*exp(1/z)+c), do you think it will be possible to do that? (I dont know how the plane transformation should be done which is required for this to make the set correct.)

Another thing for the moviemaker. I saw that it is now possible to have the infinity-waves and a normal palette. Could it be possble that you let those two ''layers'' have two different colorcycling speeds? For example the normal palette 1 and the infinity-waves -1. Or the palette 1 and the infinity-waves 2. It this possible to do?

Asking for possibilities ... on this forum ?!!  :hmh: :fiery:

What do you mean with the wave-system for colour/iteration-division? Do you want to vary the density of colors based on iteration level? Or waves in the time domain, for the movie maker?

My wish for the movie maker is to do more with the Color division control. In the current situation, you have to set each key frame. Instead I want to set the rate of change in color division control, just as with the cycle control. Enter a speed value once, and it is set until the program hits a keyframe with a new value.

Thats how exactly how it should be described.

Bug: zooming beyond E 300 gets really slow suddenly.
Temporary fix: Set iteration value to something low like 1, then set it back to what it was before.

Can you please verify that you have version 2.7.8?
And please tell me which type of fractal, because only plain Mandelbrot is using scaled doubles between e301 and e600.

2.7.8 must have fixed it. I can't seem to reproduce it! I found the bug with 1.7.6 using the Mandelbrot set, however.

While hardly a show stopper, my in-official wish list is to do with the cross-hair.

It only shows whole pixels and the lines (the cross-hairs) are centred on one pixel, thereby making the cross-hair off centre in the small window.  Could this be centred into the window and have a border of half pixels (quarter in the corners), or reduce (by one) the number of pixels being displayed in each direction in the window?  Additionally, if I put my mouse cursor to the edge of the screen the relevant cross-hair line keeps flickering in the area that is off-screen.  I imagine this is using additional resources to keep flickering like that, and is also distracting.

I sometimes leave the program running but don't want it to use many resources while I am doing something else (like browsing) so could the cross-hair window either stop functioning, hide or become inactive when the KF window does not have focus?

Alternatively, could KF have an option to show/hide the cross-hair window?  If I'm brave enough to have two instances of KF running at the same time (it works better if they're in different folders) then there are two cross-hairs on display at the same time, thereby doubling effort.  If I could turn one off it would be better for my ageing laptop.

If you require any additional information please let me know.

one more from me again, but maybe this is very simple :)
in the movie maker, would it be possible to make colour cycling movies of only one picture? no zooming, just moving through the palette.

I'd love to have nice movies of beautiful static locations..

Maybe this can be done close to realtime, so one might preview it in kf directly, when scrolling through the colour ofset? that would be awesome... :)

@chilli http://www.fractalforums.com/programming/gradient-editor-design-for-a-fractal-explorer-program/msg76666/#msg76666

I would like to see this functionality in KF too, if kalles doesn't do it first it will have to wait until I get KF ported to Qt+Linux ;)

In Kalles Fraktaler I'd like to load a previously calculated fractal and apply a new palette to it.
You can 'save map' but you can't 'load map'.

Ehm, it's called "Save palette" and "Open palette" and for me it's working.  :hmh:

No, loading fkb files directly, without re-rendering.

Yeah, that would be nice. Also I think the keyframe movie maker could still use features like that.

when I run fraktal_sft64_2.7.8 exe (using wine) I get a few stray pixels, selecting "Reset" seems to randomize them?
not sure where to poke at the code for this or if it happens for others.

Im running into a problem where the rendered frames have a too low iteration count. Can you make the solve glitches function in the examine zoom sequence menu also add iterations to a frame if needed instead of just references?

hmmm... kfr 2.7.8 (using wine) locks up when zoom is low
menu -> Actions -> Location -> Zoom =  between 1.0 and 2.0
causes freeze  :sad1:

Do you think you can implement the manowar-fractal?