Bug 889 - PV should allow viewing/saving PD binary output
Summary: PV should allow viewing/saving PD binary output
Alias: None
Product: PulseView
Classification: Unclassified
Component: Protocol decoding (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2017-02-05 18:31 CET by Uwe Hermann
Modified: 2017-02-05 18:31 CET (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Hermann 2017-02-05 18:31:46 CET
PulseView is currently missing a set of features related to decoder "binary" output that is already available in sigrok-cli (-B option).

Specifically, at least the following operations would be nice to have in PV as well:

 - Show a list of binary classes the respective decoder supports and their descriptions (probably on the left-hand side, where the other PD metadata stuff like channels, options, etc. are shown).

 - After a PD has run and the annotations are being displayed there should be some way to save the data from any/each of the supported binary output classes to a file (basically what -B in sigrok-cli does).

 - After a PD has run and the annotations are being displayed there should be some way to

   - view (at least certain) OUTPUT_BINARY data chunks; this could be both possible as well as very nice/useful for predefined "known-supported" types of binary output data e.g.

     - images (PNG, JPEG) or videos could be viewed/previewed (inside of PV as a popup, or via external programs, or both) when the user hovers above the whole PD trace, or specific chunks of the PD trace

     - audio output (WAV, i2c, ...) could be played back, either within PV directly or via external programs (vlc, mplayer, aplay, whatever).

     - etc. etc.

Generally, we'd probably want something like a mime-type(-like) system to let frontends know if the binary output class is of some "well-known" type (this would be part of libsigrokdecode, of course); each of the types supported by PV would then allow the user to either save to file or open/preview within PV or external programs. Unknown types only support "save to file" or "view as hexdump" or such.

As for saving: it should be possible to save both the whole data, as well as individual chunks (this makes sense for some use-cases, e.g. only saving certain "interesting" parts of a WAV dataset or PCAP dataset or only certain frames of a video, ...).

Some more ideas: