WBPP won't register frames from a specific filter for no apparent reason - Forums

Topic starter

May 31, 2025

Hello all.

I'm facing a problem I don't understand why is happening. WBPP (v2.8.1) won't show in pipeline or diagnostics the registration of B frames but will register any other filters of the same target.

It seems like it happens randomly for some filters for some of my targets. It shows no errors, no warnings, no nothing. It just refuses to register.

I don't know if it is a bug or if I'm missing something really important... I never had this issue until last month.

It also seems that it won't weight images as well, making it harder for me to use the NSG script for gradient correction, as it relies on subframe weighting to sort frames.

Subframe weighting and registering boxes are checked. I also tried using both auto and manual registration reference modes.

Below is 2 frames of G to show that other channels will work, except one specific. It is not a B problem, it happened to L the other day on another target. Had to use star alignment to register my frames for stacking, but I don't like this workaround.

Helpful Engaging

JohnAdastra

May 31, 2025

I've been noticing the same issue recently and which did not occur in the past. Sometimes registration will fail with one to all filters, and even occurs with OSC subframes. My solution to get most frames to work is to run them all through a batch process of BlurXterminator, correct only. This seems to sharpen the stars to the point where WBPP registration likes them better. However, this is time consuming based on the speed of your machine and whether or not you have CUDA acceleration enabled through your GPU. The other fix is to take the frames out of the linear state so the stars are more easily spotted, but this limits your processing options later. A friend uses three star alignment in PI on the calibrated frames, which he claims works better than star alignment or the registration in WBPP, but I have not tried that myself.

Helpful Engaging Supportive

Mauricio Christiano de Souza

Topic starter

May 31, 2025

I've been noticing the same issue recently and which did not occur in the past. Sometimes registration will fail with one to all filters, and even occurs with OSC subframes. My solution to get most frames to work is to run them all through a batch process of BlurXterminator, correct only. This seems to sharpen the stars to the point where WBPP registration likes them better. However, this is time consuming based on the speed of your machine and whether or not you have CUDA acceleration enabled through your GPU. The other fix is to take the frames out of the linear state so the stars are more easily spotted, but this limits your processing options later. A friend uses three star alignment in PI on the calibrated frames, which he claims works better than star alignment or the registration in WBPP, but I have not tried that myself.

Yeah. My problem doesn't even let me try registering to get to this part yet. WBPP skips the registration part and just gives me a successful calibration. So changing the registration won't do it...

Oscar H.

May 31, 2025

it has been working fine for me so far

I use basically default settings in WBPP

Rodney Watters

May 31, 2025

I notice that the reference frame selection is blank. What settings are in WBPP for the reference frame? Is it set to auto or have you provided a specific reference frame?

Well Written Concise

Charles Bradshaw

May 31, 2025

Mauricio Christiano de Souza:
Hello all.

I'm facing a problem I don't understand why is happening. WBPP (v2.8.1) won't show in pipeline or diagnostics the registration of B frames but will register any other filters of the same target.

It seems like it happens randomly for some filters for some of my targets. It shows no errors, no warnings, no nothing. It just refuses to register.

I don't know if it is a bug or if I'm missing something really important... I never had this issue until last month.

It also seems that it won't weight images as well, making it harder for me to use the NSG script for gradient correction, as it relies on subframe weighting to sort frames.

Subframe weighting and registering boxes are checked. I also tried using both auto and manual registration reference modes.

Below is 2 frames of G to show that other channels will work, except one specific. It is not a B problem, it happened to L the other day on another target. Had to use star alignment to register my frames for stacking, but I don't like this workaround.

You only calibrated two frames. You need three or more to register. Why are your frames not calibrating?

Well Written Concise

Mauricio Christiano de Souza

Topic starter

May 31, 2025 · Edited: May 31, 2025

Rodney Watters:
I notice that the reference frame selection is blank. What settings are in WBPP for the reference frame? Is it set to auto or have you provided a specific reference frame?

It is blank because I tried resetting to 'factory standard' settings. But didn't work as well. I provided a specific reference frame earlier and also tried auto. Both times WBPP didn't generate the registered frames.

Mauricio Christiano de Souza

Topic starter

May 31, 2025

Charles Bradshaw:
You only calibrated two frames. You need three or more to register. Why are your frames not calibrating?

The prints are for illustration only, I have more frames to register, 150 B frames to be exact.

They do calibrate but won't register.

calibrated folder:

registered folder (195 L frames and 150 B frames missing):

Mauricio Christiano de Souza

Topic starter

May 31, 2025

Oscar H.:
it has been working fine for me so far

I use basically default settings in WBPP

I also use the default settings. I think this might be a bug from an update... I don't know. I think I will start a topic on PixInsight forum as well.

Richard Shagam

May 31, 2025

Just a gripe, but I recently switched to mono processing with a MiniCam8 and have since been frustrated with WBPP, myself. With my OSC camera, I could ignore most combinations of darks, biases and flats and still get stacking to work (albeit with any background flaws you might expect). Now, like the original poster, I have inconsistent results. For the time being, I've gone back to Siril to do my stacking. More work, but I usually get results. Something must have happened to WBPP at the same time I switched cameras. Or I'm just plain missing something!

Well Written Concise Engaging Supportive

Mauricio Christiano de Souza

Topic starter

May 31, 2025

I found a way to quick fix my issue for people experiencing the same:

In the lights tab, click on the registration settings (gear icon), and change any registration parameter you wish. This will make WBPP allow your frames to be registered and will work as it should.

So, for me this is clearly a bug that probably came from the last update. I will try to report this to PixInsight developers and hopefully they will fix it.

Helpful Supportive

Richard Shagam

May 31, 2025 · Edited: May 31, 2025

Thanks for the advice.
Just don't use taboo words likeSiril or .fit files when interacting with the PI forum!

Rodney Watters

May 31, 2025

Another quick one whilst I think of it. I find it to be good practice to always do a full reset of WBPP before starting a new batch processing run. Click on the reset tab and select the option to do a full reset, clear all file lists and clear cache. Then reload all off the calibration files and lights and give it another go. I’ve seen posts on the PI forum where this can fix issues.

Helpful Concise