Forums › General Discussions › Exploring a recording in zero span mode › Reply To: Exploring a recording in zero span mode
Andrew
- This reply was modified 5 years, 3 months ago by
Andrew.
Hi Cyprien,
Thank you for your feedback.
I agree, more functionality could definitely be added to the I/Q playback. You are running into some of the limitations of the feature. I can acknowledge some of your points.
– There is no controls or keys for scrubbing through the file, such as step forward/back/etc, other than the single step button for advancing 1 step.
– There is not currently a way to go to an exact time.
– The rectangle viewport has a minimum size so it can always be grabbed easily. This might be deceiving for very large captures.
– The resolution on the rectangle position is 1 pixel. With your file at 8GB in size, 1 pixel might be a lot of samples. Finding a signal this way will be difficult.
It was originally designed for shorter captures, and the controls reflect that. I have added some of your ideas to my notes. When we are able to revisit this portion of the software I think we should be able to add much of this.
One suggestion I might have, is to increase your sweep time to the maximum allowed, which will clamp at 4M points. This will effectively make your rectangular view into the file as large as it can be. Then you more easily use the per view zoom/scroll when you have found a signal of interest. This may not work for all use cases.
Additionally, signals can also be video triggered in the file. If your signals of interest have clear RF level rises, use the video trigger to find your signals. This might introduce some lag at large file sizes.
I should also mention, there exists third party software solutions that have extensive capabilities in this domain. See our third party vendors at this link. https://productbundlesdemo.kinsta.cloud/support/third-party-software/ In particular, offerings from 3dB labs and Procitec have the types of features you are looking for.
I appreciate you taking the time to provide this feedback.
Regards,
Andrew
