Re: [sigrok-devel] Outputting files from Protocol Decoders

2016-10-11 Thread Gerhard Sittig
[ summary: use an output module, see srzip for prior art ] On Tue, Oct 11, 2016 at 06:03 +, Chris Dreher wrote: > > It seems the streaming design of sigrok eliminates a lot of > file formats. Namely, most file formats with a size field that > precedes a large variable amount of data can

Re: [sigrok-devel] sigrok based oscilloscope?

2016-10-11 Thread Brüns , Stefan
On Dienstag, 11. Oktober 2016 19:54:30 CEST Soeren Apel wrote: > Hi Carl-Fredrik, > > > The persistence is more than just esthetics, it allows you to detect > > spurious anomalies since the little short deviation stays on screen > > long enough to be detected, if an oscilloscope doesn’t have > >

Re: [sigrok-devel] Outputting files from Protocol Decoders

2016-10-11 Thread Soeren Apel
I like this approach. What do you guys think about a meta packet that describes the meaning/content of the binary output? With that, the I2S PD could announce sample rate/channels/resolution (before or after starting output, wouldn't really matter) and the sigrok client could pass this meta data

Re: [sigrok-devel] Outputting files from Protocol Decoders

2016-10-11 Thread Chris Dreher
Unfortunately, the MIDI spec does not define any way to use multiple chunks while allowing for proper playback of the original data. There are 3 formats (aka "types") for MIDI files defined in the MIDI spec. Unfortunately, none of them allow for multiple chunks to played back sequentially.

Re: [sigrok-devel] sigrok based oscilloscope?

2016-10-11 Thread Soeren Apel
Hi Carl-Fredrik, > The persistence is more than just esthetics, it allows you to detect > spurious anomalies since the little short deviation stays on screen > long enough to be detected, if an oscilloscope doesn’t have > persistence and at the same time don’t render all frames you could > miss

Re: [sigrok-devel] Outputting files from Protocol Decoders

2016-10-11 Thread Chris Dreher
I like Gehard's suggestion as well. This design allows for PDs and the output module to split the work. Each output module will need to document 1) what metadata it needs and 2) what the PD's binary stream will look like. In most cases, I would expect the PD's binary stream to be very close

Re: [sigrok-devel] sigrok-devel@lists.sourceforge.net

2016-10-11 Thread Uwe Hermann
Hi Rudolf, On Fri, Sep 16, 2016 at 01:39:14PM +0200, Rudolf Reuter wrote: > I have developed a new sigrok decoder - gpib. > The project is hosted on Github, see: > https://github.com/rudi48/sigrok-gpib > > It would be helpful, if somebody could please test it, and give me feedback. Looks

Re: [sigrok-devel] Introduction, new to the list and hello from FreeBSD!

2016-10-11 Thread Soeren Apel
Hi Boris, thanks for continuing the work Uffe has done! It's highly appreciated. We wouldn't want to leave FreeBSD behind :) @Uffe: I thank you as well! All the best,  -Soeren On Wed, 2016-10-12 at 01:28 +0300, Boris Samorodov wrote: > Hi All, > > I'm new to the list. I've just adopted some

Re: [sigrok-devel] Outputting files from Protocol Decoders

2016-10-11 Thread Chris Dreher
Thanks, I really, really do appreciate the answers. It seems the streaming design of sigrok eliminates a lot of file formats. Namely, most file formats with a size field that precedes a large variable amount of data can not be supported in sigrok. This includes file formats that are 99%