With this text output, you can find out more how the 'x' and 'y' coordinates work, and many other things. I found that a picture with 1000 pixel width and height has 500 SIZE and equal OUTPUT_WIDTH, OUTPUT_HEIGHT. In my personal experience, I have in my early attempts of LUA-scripting misused 'local' variables sometimes, which could cause rather puzzling problems of seemingly functional code which didn't function properly.Īlso, the script can be used if you are simply curious about the value of some certain variable, for example OUTPUT_WIDTH. Sometimes several problems converge into an error, and the sooner you can find out how the variables work, or don't work, the sooner you find what the underlying mechanisms are which leads to your problem. Thank you also for offering other users a good and simple example of how to use the filter.ĭebugging is sometimes quite a task, especially if you have just a vague idea of where the error/s occur. When it finds a code it recognizes from its settings, it will store the data which are sent through the Red, Green and Blue channels, which are then sent to be printed in the window. What the does is to scan the Alpha Channel of the, searching for. The is set to pick up 9 different pre-made, which are set to be easy to remember: ![]() This can be anything between 0 and 1, but should be set to a specific number which is not used by the script you want to debug. The is just a small user-defined 'key' which tells the that you are sending three channels of debugging-data. I have reserved the Alpha channel for the. You can send three channels of information, through the Red, Green and Blue channels. The point here is to set up a situation wh ere you may want to send information to the which is located in the next mapscript. Now, open the script.Īs you can see, this above script simulates a hypothetical debugging situation.Ī pixel fr om a small Free Polygon is sent into the Debug Simulation, which senses it from checking the alpha-channel (variable 'a' in the script). Happened during saving to disk (aka final rendering).This window is useful for anyone who is interested in writing LUA-scripts for FilterForge and need to debug their code or want to know the value of some variable in their script.įirst, start up the Text Window Mapscript - v.03 (or higher): Using Midtone Enchancher filer on 14 Mp Photo with Bitmap aliasing option on. Looks like FForge has some memory handling issues. My FF4-demo crashed while testing this, report sent. I could do that (it looks simple filter) but I'd ask author first fors permission. ![]() You should ask fiter maker if he's willing to tesr/make an upgrade. I have no idea if the newer filters have speed optimizations. Are you using pro version? FilterForge is hevily CPU depependant, so having multiple cores (like 6 or 8 ) help a lot? Normal version uses only 2 cores.įilterForge is 32 bit program and thus limited with it's memory use, have you checked if that's the issue? That much slowdown sounds a lot like swap-trashing.īig blur filter (like this 70pix side = 70*70 = 4900) means that app needs to do a *lot* samplling.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |