July 25, 2008 03:06pm pdt

1. Infinity08 327,824
2. evilrix 164,935
3. jkr 98,205
4. sunnycoder 76,070
5. ozo 73,705
6. josgood 37,437
7. jaime_oliv... 33,460
8. itsmeandn... 31,587
9. Kdo 30,000
10. fridom 25,953
11. Gurudenis 11,630
12. duncan_roe 9,650
13. JohnGaby 8,500
14. ravenpl 8,290
15. PaulCasw... 6,412

1. sunnycoder 862,613
2. Infinity08 860,683
3. Kdo 756,498
4. jkr 708,967
5. ozo 416,013
6. PaulCasw... 296,971
7. grg99 296,356
8. evilrix 194,800
9. jaime_oliv... 189,132
10. brettmjohn... 182,528
11. itsmeandn... 160,053
12. ankuratvb 157,866
13. fridom 156,557
14. imladris 138,967
15. cwwkie 129,383

03.12.2008 at 01:08AM PDT, ID: 23234303

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.5

Reading wave file using C

Zone: C Programming Language

Tags: C

Hello group,

I'm using C to read a wave file. First step is to verify parameters which could be found in Format Chunk and Data Chunk. Howvever, I have run into a problem. As far as I understand I have to read first 44 bytes to get information about Header, Format and Data Chunks.

In the specification (http://ccrma.stanford.edu/courses/422/projects/WaveFormat/) byte 44 is the starting address of DATA. However, when I look at the file using an HEX editor, I do see 64 61 74 61 (or data) start at byte 48th. I also ran into a document that shows DATA Chunk ID start at 36th byte. This is confusing ...

How is this defined? or am I missing something here?

Please let me know if you have done this before.

Regards.

Start your free trial to view this solution

Question Stats

Zone: Programming

Question Asked By: akohan

Solution Provided By: Infinity08

Participating Experts: 1

Solution Grade: A

Translate:

Loading Advertisement...

20080236-EE-VQP-29 / EE_QW_2_20070628