From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC packer done, kind of
Date: Tue, 23 Nov 2004 07:27:40 +0100 [thread overview]
Message-ID: <1101191260.26578.43.camel@pegasus> (raw)
In-Reply-To: <20041123014732.3a03b10e.henryk@ploetzli.ch>
Hi Henryk,
> Ok, I'm now basically finished with sbc_pack_frame (joint stereo is not
> handled yet). Though I tested it only with mono and two simple test
> signals (one impulse and a sawtooth) because I can't load audio data
> from files. (Marcel?)
these are good news. So I really must code the sbcenc tool now. In what
fields do I have to put the PCM stream and what other things must I set?
> Next thing (after joint stereo) would be some cleanup of sbc.c and
> finally convertion to kernel indentation. I tried the Lindent script but
> don't like what it does to the code, because most of it is nested in
> some kind of for(blk ..) { for(ch ..) { for(sb ..) { ... } } } structure
> and wasting a full 8 columns (out of the precious 80) for each of those
> loops doesn't feel right to me.
Actually that is the main point behind using tabs with the size of 8
spaces. Code that uses too much nested structures become unreadable and
you start thinking of how you can make this easier and make it looking a
little bit nicer. In most cases the answer is inline functions.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-23 6:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 0:47 [Bluez-devel] SBC packer done, kind of Henryk Plötz
2004-11-23 6:27 ` Marcel Holtmann [this message]
2004-11-23 6:48 ` Henryk Plötz
2004-11-23 9:24 ` Marcel Holtmann
2004-11-23 19:49 ` Henryk Plötz
2004-11-23 21:03 ` Marcel Holtmann
2004-11-24 3:21 ` Henryk Plötz
2004-11-24 5:01 ` Marcel Holtmann
2004-11-24 6:34 ` Marcel Holtmann
2004-11-25 4:22 ` Marcel Holtmann
2004-11-25 5:07 ` Henryk Plötz
2004-11-24 7:55 ` Brad Midgley
2004-11-24 14:39 ` Marcel Holtmann
2004-11-24 17:36 ` Brad Midgley
2004-11-24 17:44 ` Marcel Holtmann
2004-11-24 19:33 ` Brad Midgley
2004-11-25 6:07 ` Marcel Holtmann
2004-11-24 20:37 ` Henryk Plötz
2004-11-25 2:49 ` Marcel Holtmann
2004-11-25 5:02 ` Henryk Plötz
2004-11-25 5:30 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1101191260.26578.43.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.