Convert .txt/.mat to .wav format

Question

bilal malik 2017-3-25

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/331918-convert-txt-mat-to-wav-format

评论： dpb 2017-3-28

I have a .txt and a .mat file, both containing the same data. I would like to convert either one(whichever is easier) to a .wav file so that I can play the sound and carry out audio processing. I understand 'wavwrite' is one way of doing this but so far I have been unsuccessful. I have tried:

>> load('data.mat')
>> hfile='data.wav';
>> wavwrite(y, Fs, hfile)

But when I run the code, it displays:

Undefined function or variable 'y'.

Does anyone know the solution to this problem or even an alternative method to convert a .txt/.mat file to .wav? Thanks

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

dpb 2017-3-25

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/331918-convert-txt-mat-to-wav-format#answer_260353

在 MATLAB Online 中打开

load('data.mat')

will leave whatever the variable in the file name is as the variable in the workspace. Clearly it wasn't y.

Try

whos -file data.mat

and find out what that variable was that was written, then use it in the wavwrite call. Of course, you'll have to define Fs, too.

NB: documentation indicates

>> help wavwrite
wavwrite Write Microsoft WAVE (".wav") sound file.
  wavwrite will be removed in a future release. Use AUDIOWRITE instead.
  ....

May want to take that into account.

15 个评论
显示 13更早的评论隐藏 13更早的评论

dpb 2017-3-26

编辑：dpb 2017-3-27

在 MATLAB Online 中打开

Well, you'll have to have an audio-capable recording device; CDs use the 44.1 kHz for a reason; that's what it takes to get audio quality sound.

What you'd have to have to cover the hearbeat depends on what the audible sound range covers which I don't really know...hmmm, gargle,gargle---well one medical instrumentation text shows

S1 30-45 hz
S2 50-70 hz
S3 <30   hz (weak)
S4 up to 600 hz (murmurs)

So, 250 hz Nyquist would seem to be marginal as to most of the above; what else? Well, there's not much resolution in the data, wonder if that is an issue?

Lesseee...

>> length(unique(int8(M*100)))/length(M)
ans =
  0.0365
>>

Ewww!!! That is likely a serious problem; you've only got 3% of the observations being differently recorded levels; that's bound to be distorting the sounds even if the frequency is high enough. You need, I'd guess, at least another significant digit and two or more would help out of your instrument. That may or may not be sufficient in and of itself, but it's somewhere to start.

ADDENDUM

Note that if you "blow up" the x-axis of your sampled data to look closely at the first beat, it's clear the signal is grossly undersampled--the instrument may be providing a much finer sampling rate in real time, but what you're capturing is 3-4X too slow for an accurate rendition of the waveforms...here's just that first section:

All there is is a peak and minimum, nothing about the intermediary shape. Wonder if the device might not be doing some internal peak-holding and them updating those data rather than actual sampled data points given the regularity of the sampled data over the time period. Whatever it does/is doing isn't nearly enough to do such analyses on accurately, though.

dpb 2017-3-27

As said before, no, there's no way to tell what a sample rate was simply from the sampled data stream unless you know precisely what the input was and it was, say, a pure sine then you could potentially at least find a multiple that could be plausible, but you still couldn't say precisely what it was, specifically.

I've never seen an Arduino altho it looks like the Due has higher capabilities than early versions that definitely can be made to operate at higher speed. Just how fast it runs appears to be dependent upon how you did the data collection.

In a loop if there are print() statements outputting data, it's quite possible it's not fast at all; if it's using DMA and buffering the A/D, apparently it is possible to run up some very high sample rates. Need more info than have to have any clue what the actual data you have was sampled at, but certainly does NOT look to me to be oversampled; I'd surely expect to see some smooth waveforms in that case, not just jaggies.

How long did the subject data series take to acquire might have some indication but you need a lot more details and digging into the guts of the acquisition to know anything for certain; certainly just the data file as is isn't of any real help.

bilal malik 2017-3-27

Thank you for your help dpb, much appreciated.

I will investigate the sampling rate issue and then after that look to try and convert it to a .wav file with the correct frequency.

dpb 2017-3-28

I found a blog (somewhat dated, so may not be signficant, but then again...) that has some discussion of how the Due A/D is internally programmed. Depending upon how your device operates, it may be significant.

<DJErickson Arduino> The bottom-most section discusses what he learned about the A/D speed and how to set. There are some articles and code samples by a Stimmer that show how to write interrupt-driven DMA transfers for high-speed acquisition; perhaps that's what the instrument is doing? Or do you have to write code and what you have is just a sensor? Be interesting to see what it is you're actually using...but maybe some of this will help in your quest.

Post back what you find out...

请先登录，再进行评论。