WPR/WPA Issues/Improvements

My apologies if this already exists and please direct me to example(s) if it does.

I am trying to capture short-duration events over long periods of time. The documentation for WPA indicates (and I have verified) that is does not work well with large data sets. I have found, for example, that occasionally I have been able to get it to open and process over one-hour of data, which was extremely helpful. However, more often than not, WPA either silently quits, or worse, blue screen and reboot.

First request: Fix the silent failures!

Second request: It would be extremely helpful if WPR could include some triggering and duration of capture rules that could mitigate the limitations of WPA to handle huge amounts of data.

Much like the features on data capture and analysis tools such as oscilloscopes, sometimes creative uses of triggering intermittent or short-duration events occurring infrequently are required to ignore the mountains of data that is not helpful.

Once I gather information to inform my intuition about what is occurring, I can then tailor data triggers and/or filters to discard data not relevant to solving the problem.

For example. I am currently investigating a short-duration event on the order of 2ms that occurs approximately every 15 minutes. Now that I have identified that, I would like to be able to capture data around those events, while discarding the mountains of data that are not currently of interest.

If I could specify, every time X occurs, capture 20 ms of data surrounding the event (for one example), it would be extremely helpful. I understand that a software solution to this on the recorder side might be deferred to hardware bus analysers/emulators/etc. However, if WPA could at least discard data not of interest, rather than choke of the data, it would be helpful.

Thanks!