# Missing Data in single shot in MSO **URL:** \ **Category:** Logic MSO\ **Created:** [August 28, 2026, 3:17pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799 "2026-08-28T15:17:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![BitBob](https://avatars.discourse-cdn.com/v4/letter/b/ecb155/32.png) [@BitBob](https://discuss.saleae.com/u/BitBob)\ **Post date:** [August 28, 2026, 7:12pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799/2 "2026-08-28T19:12:52Z")
> [@sebastian.wissig](#): > > We also have the bug that single shot is set, but the trace runs forever. This seems similar to my post (issue #2: **One Shot Trigger Problems** ) … you might be able work around the one shot trigger issue by extending the holdoff, as long as your capture buffer/transfer time is less than the holdoff time. If sampling at maximum sample rates and capturing multiple channels, you might not be able to get it to trigger & stop. > [@Limitations of Logic MSO digital streaming (derived from analog)?](https://discuss.saleae.com/t/limitations-of-logic-mso-digital-streaming-derived-from-analog/3733): > > I was running into some problems trying to decode a quad-SPI flash memory device. Specifically, I was trying to configure a ‘one shot’ capture of the entire power-up transaction, but running into two problems: The digital data packet loss on derived digital signals (even though all analog data was captured successfully) The ‘one shot’ trigger failed to actually STOP the capture properly Background: Initial serial communications is ~ 5 MHz SPI, but switches to ~20 MHz QSPI mode. The SPI is n… Meanwhile, regarding: > [@sebastian.wissig](#): > > We see gaps in the digital trace. … are the gaps all ~12ms wide at start of capture? If so, I think it is a known issue, per: > [@Repeatable "Channel Inactive" "blips" on digital channels cause SPI decoder to be thrown off](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660): > > Hi All, Everytime I use a digital channel in a free running capture there seems to always be a drop in communication (or something) towards the beginning of the capture. This seems to happen towards the beginning of the capture and has a tendency to throw of the SPI decode (SPI with no CS) and can’t be easily recovered since deleting data before/after a point in the capture is not yet possible with the Logic MSO app (deleting data before/after tended to resolve framing issues on the logic pro). … And > [@Single shot oddities](https://discuss.saleae.com/t/single-shot-oddities/3685): > > Logic MSO just arrived today but not getting it to do what I need. I saw some of the prior questions in the forum that explain what I need - single shot with controlled capture length (pre and post trigger) from a digital input(s) is not available yet. I think this older forum post covers my use case: [Single Shot Recording duration settings and few other questions - #2 by timreyes](https://discuss.saleae.com/t/single-shot-recording-duration-settings-and-few-other-questions/3658/2) in which case this is sort of a me too post - though I’m trying to work around it by using the scope to trigger. … --- _[View the full topic](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799)._