10-27-2015 06:09 PM
Hi all,
Not a major issue right now, but interested if anyone knows why.
Using LV2011 full development and working with the basic acquire sound VI's. Its very strange, but i set the sampling frequency to say 48000 Hz and samples/ch to 96000 assuming i would get 2 seconds worth of data, but i get 1.5 seconds and only 72000 data points. Its not cutting exactly half a second off, ive done a few different variations. There is nothing special about this VI im using, i did the same thing with the express VI and got the same results.
Anyone have any clues?
Thanks,
Matt
Solved! Go to Solution.
10-27-2015 06:17 PM - edited 10-27-2015 06:21 PM
Post code please. You're doing something wrong.
I get all the samples:
Cheers
--------, Unofficial Forum Rules and Guidelines ,--------
'--- >The shortest distance between two nodes is a straight wire> ---'
10-27-2015 06:22 PM
Hi james,
Project Is below. Currently working in acquire and log sound wave vi. Ive just noticed it records exactly 75% of the number of samples i request.
Thanks for any help,
matt
10-27-2015 06:28 PM - edited 10-27-2015 06:32 PM
I ran your code and I got 72000 datapoints, which is how many you configured the acquisition for. What are you comparing your 75% to? Did you forget that you set the # of data points to 72k?
This is the relevant section of your code, right? (I added the Array Size part)
Cheers
--------, Unofficial Forum Rules and Guidelines ,--------
'--- >The shortest distance between two nodes is a straight wire> ---'
10-27-2015 06:31 PM
Configured it for 96000 and only got 72000, conifgured it for 72000, got only 54000.
10-27-2015 06:33 PM
Sorry,
Some of that post got covered by the photo,
But i configured it for 96k, got 72k. Configured it for 72k, got 54k. It is exactly75% everytime. I am a little lost for words.
10-27-2015 06:34 PM
Yes that is the relevant section of code. If i run that or run the express vi its the same thing. I wonder if it is because it is labview 2011.
10-27-2015 06:41 PM
It's gotta be a weird buffer thing then... Maybe my computer is able to fill the buffer up to the top, but yours isn't.
In the "relevant code" above, use a 2x buffer for the configuration, but still only pull 96000. I say 2x, so that if you change your # data points in the future, you only have to change one number, not the buffer too. So you should end up writing 192k in to the Config function and 96k in to the Read function.
Cheers
--------, Unofficial Forum Rules and Guidelines ,--------
'--- >The shortest distance between two nodes is a straight wire> ---'
10-27-2015 06:45 PM
How do you set the buffer for that? I mean i can always divide the number of samples by .75 but if i switch to another computer without the buffer issue then the issue is going to happen again.Its not a huge deal, i can just record for longer, but id like to know why HA.
10-27-2015 06:50 PM
Oh,
Definitely misread the last post. Did that and success, pretty weird.
Thank you for your help again.