On Tue, Oct 11, 2016 at 18:43 +, Chris Dreher wrote:
>
> Theoretically, as Gerhard suggested earlier, an output module
> could go a step further and translate from one format to
> another similar format (ex: all audio-based PDs output WAV data
> but the output module can write it as WAV or AU
Sent from my Verizon, Samsung Galaxy smartphone
Original message
From: Soeren Apel
Date: 10/11/16 10:50 AM (GMT-07:00)
To: Gerhard Sittig , sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
I like this approach.
What do
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 t
ultiple chunks but it
is rarely used and each chunk is for alternative arrangements. Thus, none of
these formats are supported.
-Chris
From: Brüns, Stefan
Sent: Tuesday, October 11, 2016 7:13 AM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-dev
On Dienstag, 11. Oktober 2016 06:03:55 CEST Chris Dreher wrote:
> 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
[ 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 not
d features?
-Chris
From: Bert Vermeulen
Sent: Monday, October 10, 2016 2:50 AM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
On 10/10/2016 01:22 AM, Chris Dreher wrote:
> Here is a brief summary of
On 10/10/2016 01:22 AM, Chris Dreher wrote:
> Here is a brief summary of the original questions and their status here
> (TL;DR).
>
>
> 1. Once put() is called for OUTPUT_BINARY, is there anyway to go back
> and change those bytes?
No. It is a continuous stream, and the producer of that stream has
ut module.
On Thu, Oct 06, 2016 at 20:30 -0700, Chris Dreher wrote:
>
> > Date: Thu, 6 Oct 2016 09:23:16 +0200
> > From: gerhard.sit...@gmx.net
> > To: sigrok-devel@lists.sourceforge.net
> > Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
> >
&g
reher wrote:
>
> > Date: Thu, 6 Oct 2016 09:23:16 +0200
> > From: gerhard.sit...@gmx.net
> > To: sigrok-devel@lists.sourceforge.net
> > Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
> >
> > On Wed, Oct 05, 2016 at 11:36 -0700, Chris Dreher
> Date: Thu, 6 Oct 2016 09:23:16 +0200
> From: gerhard.sit...@gmx.net
> To: sigrok-devel@lists.sourceforge.net
> Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
>
> On Wed, Oct 05, 2016 at 11:36 -0700, Chris Dreher wrote:
> >
> > In looki
Take this with a grain of salt. Although I have a rough idea of
sigrok's general architecture, I'm not too familiar with intimate
API details.
On Wed, Oct 05, 2016 at 11:36 -0700, Chris Dreher wrote:
>
> In looking at how to output files from protocol decoders, I
> have the following questions:
12 matches
Mail list logo
