waveSharp 0.2 MacOS DOES NOT WORK on versions before Ventura

[TesterUW42]

I tried to use the precompiled waveSharp 0.2 MacOS on my 10.13.6 High Sierra.
I was able to run wavelet filtering and got a nice output image.
The image I processed was a 16bit TIFF that I had cropped down to 5564 x 5564 pixels in Photoshop.

The panels in wS was not updated correctly, but disappeared. After switching tabs they became visible again.
The vertical row of function buttons also disappeared in some situations, but by hovering with the cursor over their normal places they resurfaced.

[CorBer]

Hi,

Thats interesting news, I have not tested this myself as I do not have a Mac. I suggest trying to test using a far smaller file, files this size (5k * 5k) will often lead to very slow processing. To test the functionality proper use something like a 2-3Mp image.

cheers
Cor

[TesterUW42]

My goal was not to test functionality, but to see if it was possible to process images beyond the size limits of Registax6.
That worked well enough with some fiddling. I was able to generate the best image so far from an image set.
I realise that the program is in an early stage of development and find it exciting that I could get a nice result out of it at all.

I got the image I used from AutoStakkert3 that stacked several images from my Sony A7 III. and the result was expanded with Drizzle3.
The image was indeed huge.
To limit the size a bit I cropped away much of the black sky.

To improve the setting speed it might be a good idea to adopt the way AutoStakkert do, showing a limited area for setting the wavelet values.
High speed is mostly important when setting the parameters in a smooth way, even if you do not have the latest most powerful hardware.

I also noticed that wS only used one or a few of the processor cores!
Would it be possible in the future to expand processing to more cores or even do some of the processing be hardware on a capable graphics card?
I use a very good noise reduction program NeatImage for my images and that program can do both.

Unfortunately I am a programming analfabet and too old to learn that skill too, to be able to contribute here. :-(
Looking forward to future updates.

[CorBer]

Hi,

WS is currently not adapted for multicore processing and I even cannot guarantee that it will be possible to change this the future. Also be aware that I am developing mainly for planetary/solar/lunar imaging at high resolution, not for DSO.

BTW if you look at the manual you will find that we have allready an option to create an ROI to process on. This will -like you ask - reduce the processing time a lot, another way to control processing is to switch from automatic-to-manual processing.

cheers
Cor

[TesterUW42]

Hi Cor This is embarrassing. I must apologise, because my statement that waveSharp 0.2 MacOS works on earlier than Ventura is not correct. I am dyslexic and mix up both characters and numbers when reading. What I could use was the 0.1 version. I honestly thought that it was 0.2, but today I saw that it was 0.1.0.17, when looking for the new features the was added in 0.2 I really hope someone will compile 0.2 to make it able to run on earlier versions of MACOS Ventura. I have no idea how that is done. Sorry for the confusion Ulf

…

On Sun, Feb 26, 2023 at 11:43 AM CorBer ***@***.***> wrote: Hi, WS is currently not adapted for multicore processing and I even cannot guarantee that it will be possible to change this the future. Also be aware that I am developing mainly for planetary/solar/lunar imaging at high resolution, not for DSO. cheers Cor — Reply to this email directly, view it on GitHub <#18 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6D7E7C4BPLOQUXPBIUUOU3WZMXT7ANCNFSM6AAAAAAVH7ORV4> . You are receiving this because you authored the thread.Message ID: ***@***.***>