Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.
Talk:Saving Microphone stream to wave format in Windows Phone
Hamishwillee - Nice article
I gave a very minor subedit and added an abstract. Please check it out.
The use case you've given is saving to IsolatedStorage, and you've also said that you're converting to .wav so file can be used everywhere. The hole in the argument is therefore that once in IsolatedStorage its not available everywhere. I suggest you put an explicit note on how the file an be retrieved.
I don't believe that its possible to save the file to the device media library (correct me if I'm wrong) but another cool thing to show would be uploading to skydrive - or at least point to other articles that show that.
02:40, 4 September 2012 (EEST)
Galazzo - SkyDrive
I created an article on how upload files to SkyDrive and added a link to it.
Hope is useful,
14:38, 6 September 2012 (EEST)
Hamishwillee - Yes is isSkydrive article looks good!
10:24, 10 September 2012 (EEST)
Dmehers - Your code?
It looks to me like you lifted most of the code from my blog post http://damianblog.com/2011/02/07/storing-wp7-recorded-audio-as-wav-format-streams/Could you please include an acknowledgement if you do that.
18:04, 29 March 2013 (EET)
Chintandave er - @Dmehers
Thanks for asking to author and adding your blog link to this article. I think that would be enough.
Thanks, Chintan Dave.Wiki Moderator.
Chintandave er 21:30, 30 March 2013 (EET)
Hamishwillee - Please wait for response before modifying the article
The wiki policy is to acknowledge the source of used materials as you have suggested. However if your article has been reused a lot on Internet without reference it is more than possible that to a casual search this code is "in the public domain" - ie it has no obvious source. In that case he would not necessarily have even seen this source, and even if he did, to assume you were not the original author either. Note that even if the code was in the public domain if it forms a large portion of the article I'd still hope for some acknowledgement that bits of it have been taken from the Internet (if only to explain what value is added though the duplication of material).
I've asked galazzo to comment. Please give him a reasonable amount of time to do so.
06:17, 2 April 2013 (EEST)
here I am, sorry for delay, but it's a very busy endless period.
@Dmehers it's the first time I have a look to the blog you mentioned. @Hamishwillie you got the point. Googling it's easy to find this code from other sources with no author's references, and this is a fact as it's a fact that the code lines are the same. So @Dmehers I'm sure you are the first who wrote that lines, but honestly there is no clear evidence of it surfing the web.
Another fact is that, Inside my articles I always added references when I had the unique source, so I would have no problem to add the refenerce link.
I really don't feel I did what you asserted as wave is a "file format", and there is no way to write a code different from whose published except for function's signature and changing debug messages and comments!
If the file format says that at offset 20 must be written the "file format" and the C# instruction to write that information is :
stream.Write(BitConverter.GetBytes((short)1), 0, 2);
... sorry, but I didn't believed I could have done wrong to someone.
From my point of view, It didn't thougth that worth neither to change function's signatures, comments or debug messages of a standard code I found as a day someone could say that his way to write the wave file format is unique.
If so, from my developer point of view I would have to add references to all blogs that write about how to treat wave format.
My position could be wrong and I can apologize with all people affected.
Finally, hoping to close this talk:
@Dmehers I've never visited the blog mentioned. Sorry if you thought I grabbed intentionally that code.@Hamishwillie, @Chintandave, @Dmehers ( all users ) feel free to add all link you think worth to add to references to accomplish to site's policies.
18:18, 2 April 2013 (EEST)
Hamishwillee - Thanks Sebastiano, Dmehers
I have added an acknowledgement note up the top that should satisfy everyone - it states that the code is from the Internet (unattributed) and that Damien asserts he is the author. These sorts of things do happen, and as long as we all show goodwill (as done here) and appreciate there there is no bad intent no harm is done.
Thanks everyone for being grown up about this.I will delete all comments on this article next time I visit.
02:16, 3 April 2013 (EEST)
I'm sure it wasn't intentional. Most of my comments came from the spec I referenced, but if you search for the method call I used then I think it's clear the code originally came from my posting.
19:35, 5 April 2013 (EEST)
Hamishwillee - All fineI think we're all happy now. Next time round I'll delete all comments because they have been addressed.
01:45, 6 April 2013 (EEST)
The link to FFT project went dead and was deleted. Can you please put the project in a zip file (at least the source) and attach to wiki?
02:38, 27 June 2013 (EEST)