Sample rate (X_Value) is wrong

On one particular PC i recorded:
X_Value
0
1.000122
2.000243
3.000365
4.000486
5.000608
6.00073
7.000851
8.000973
on every other PC i recorded:
X_Value
0
1
2
3
4
5
6
7
8
Just have a simple timed while(1000ms) loop around a "Write To Measurement File"
Is it time for another new PC?

OK, this is not helpful at all. Please attach the raw lvm file from each computer, not after opening and saving in excel. Too many middlemen!
(A lvm file is NOT an excel file, so forcing it to open in excel might be somewhat unpredictable.)
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • Wrong sampling rate from Sound Input Read VI on Dell Latitude E6510

    Hi,
    When I
    receive data from the sound card with the Sound Input Read VI, the actual
    sampling rate is not equal to the sampling rate set in the Sound Input
    Configure VI. I estimate the sampling ratio by dividing the number of samples received
    by the difference between the first and the last t0 from Sound Input Read. For
    example, if the sampling rate is set to 7000 S/s, the actual sampling rate is
    around 6900 S/s. If the sampling rate is set to 7050 S/s, the actual sampling
    rate is around 7200.
    This problem appears when the
    code is run on my Dell Latitude E6510 machine. When I run the
    same code on my Lenovo ThinkPad, the sampling rate is correct.
    The Labview application I
    am developing is to be used to acquire data synchronously from several sources,
    including the sound card input. It is therefore important that the sampling rate
    is correct.
    If anybody has any idea
    about what may cause this problem, and a way to fix it, I would be grateful.
    Ole

    It has been a trend the last years that sound card only support some sampling rates, not a range. You should refer to your sound card manual for this kind of information.  You should also be aware of that the NI sound interface is junk, and they do care about it either. Use the WaveIO interface instead See the link. But I am quite sure your problem is related to the sound card hardware not some NI driver issue
    http://www.zeitnitz.de/Christian/waveio
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Help please? Logic playing back wrong sample rate

    So I created a new session and recorded a new song that I have already done some work to this song and have had no problems whatsoever.  Last night I went to open this song and work on it some more and when I pressed play the song started playing back very slowly.  This session was recorded at 88.2k and I am getting a Logic error message that says sample rate 44.1k is recognized however my audio interface  (a Metric Halo 2882 +DSP 2d unit) is set correctly to 88.2k.  I look at my bin and all the files are correct, my preferences are all correctly set at 88.2k but Logic is playing the song at about half speed!!
    What happened??  I have a couple projects going and I need to get this fixed..  Anyone??
      Thank you in advance!!
      DDD
    Mac Book Pro Dual Core, OSX 10.6.8, Logic 9.1.5 (do not want to upgrade Logic to 9.1.6 I tried that and it was a BAD experience so Im sticking with 9.1.5), Metric Halo MIO Console 5.4

    Sounds to me that your best bet is to use a utility like SoundHack (http://music.ucsd.edu/~tre/soft//SH893.hqx) to change the audio file headers. What you want is to flag the files as 48k, not do any sample rate conversion--they should play back natively at 48k. The only SRC you'll need to do is if you actually do want the files to end up as 44.1k at some point. (In your case, I don't think Logic is converting the sample rate in real time, by the way--what it's doing is playing back the files with a clock setting of 48k, which only sounds right because they've been mis-labeled.)
    Either way, you should fix the file headers now, I think. And even if your final product needs to be 44.1k, since your files are quite clearly at 48k now, I'd do all the necessary editing and processing at 48k, then convert to 44.1k as the final step. And until the SRC in Logic is improved (Apple ?), maybe use some other app to convert to 44.1k in the end. Peak gets high marks--not sure what else out there sounds good and doesn't cost a mint.
    Best luck!
    James
    [email protected]

  • How can I ensure that the audio sample rate of my capture preset matches?

    Hi
    1. I have found that none of my ten projects has sound, although audio meters & settings moves up & down.
    Simultaniously, canvas displays that In: Not Set- & Out Not Set. Below those reads: Video V1: 00:03:42;13 Audio A1: 00:03:42;13 A2: 00:42;13. These happen on the images of all my ten projects when the playhead stops in timeline
    2. In Viewer the In & Out sets show a thin red line connecting them.
    I never had this problem before. A/V of all projects were doing just fine till last night.
    I wonder if these issues are interrelated, or if I may have clicked something wrongly that has triggered this, which I don't remember now.
    I would appreciate it if you could kindly address this problem and help me to resolve the isssue. Thank you. Faruk.

    The red line indicates the audio must be rendered. This may be caused by several things but your playback settings may be set too high for your system to handle. You may have too many audio tracks for your computer to play in realtime.
    Select one of the audio files in the timeline, get properties, not the audio format and sampling rate.
    Now got to Sequence>Settings and determine if the settings match your audio settings.
    Your online help system can guide you through adjusting your system settings, user settings and sequence settings.
    bogiesan

  • How can I find out the audio sampling rate of BetacamSP tape?

    Hi guys
    I'm trying to digitize BetacamSP tape. But I'm afraid if I might choose wrong setting...
    This tape is from very long time ago so we don't know which audio sampling rate we recorded with..
    How can I find out the audio sampling rate of this BetacamSP tape?
    Thanks:)

    The sampling rate is set by the Sony DVMCDA2 you are using, when the conversion is made from the analog input to the digital (DV) output. You should be outputting standard DV which is 16bit 48khz audio.
    Assuming you are in the US, your Easy Setup for FCP should be DV-NTSC, and then open the Log and Capture Pane and set the Capture Settings Device Control to Non-Controlable Device and you should be good to go.
    You will have to roll the deck manually and start and end your capture manually.
    You can download a user manual for the DVMCDA2 by clicking here.
    MtD

  • Parallel port sample rate

    Hi,
    I`m desperately in need of your help.
    For my school project, I`m trying to write a labview code in order to acquire air pressure data by using 8-bit analog digital converter via parallel port. Although my signal frequency very low -100 Hz-I think  I experience sampling rate problem. I  want to put sample rate and frequency data in my code but  how can I put it in my code?I `m giving square waveform via function generator which I need to see it on my graph in Labview. But there is something wrong in my signal in waveform chart. You can see screenshot and code attached.  . Also there are some noises and amplitude is not stable . How can I fix this?
    Would you please have a look at to my code and tell me how can I set sample rate and frequency?
    Attachments:
    CAN1.VI ‏21 KB

    Hi LW-s
    There isn't really a way to set the sampling rate for these VIs. You will have to use software timing. The only way to do this is with 'wait' functions inside your loop. You can also implement some logic to smooth/adjust your waveforms.  For a square wave the logic is pretty simple. If the input value is above a threshold store it as the max and if it is below the threshold store it as the min. (See the example below). For sine waves this is a bit more difficult and if I were you I would probably try to implement some sort of averaging. 
    Best Regards,
    Chris J
    Message Edited by ChrisJ on 08-23-2005 05:31 PM
    Attachments:
    example.JPG ‏86 KB

  • Finder - audio file info - bitrate, sample rate, etc

    Is there a way to find out what bit rate and sample rate an audio file is without opening it in QT and then CMD+I from there?
    I don't see detailed info when I get information from Finder. Is a script or anything that will allow me to find this info quickly in Finder?

    juhani h. wrote:
    Works fine here, too. But make sure you´ve ticked the box "Convert audiofile...etc", like M-Dan pointed out.
    I tested it and if unchecked the imported file plays at the wrong speed. Amusing at first, but potentionally disastrous.
    /J
    Does NOT work in repeated tests on my system, and yes, the 'convert audiofile' box is ticked. Wouldn't report it as a bug if it wasn't....
    This almost ruined a session of mine and cost me a deadline, but luckily I caught the SNAFU in time and converted the files individually.
    Very odd though to hear that it works on some users' systems. How can this be a system specific bug? Are you sure you're dragging files in from the Finder to your arrange page? And Logic converts them? Are we talking 48k files being converted to 44? Or vice versa (44 to 48)?
    In my case, it was a 48k session and Logic failed to convert the 44k files I had mistakenly been sent.
    Since I've noticed other weirdness (like malfunctioning Apple Loops) at 48k, I still think Logic is less than bullet proof at different sampling rates. Just a hunch though.
    T

  • FCP 6 with M-audio fastrack pro and sample rates

    hello, having a weird problem in FCP 6.02 under OS X 10.4.11 on a MacPro where if i record a voiceover through my m-audio fastrack at 48khz, which matches the sequence and project settings, it comes back at the wrong sample rate (plays back higher pitch), but if i record it at 44.1 it sounds right. any ideas on this?
    thanks in advance
    david

    Perhaps the M-Audio is still recording at 44.1, and FCP is set to convert the audio to 48k, but is unable to resample as it would with an analog source. I would try to access the control panel for the M-Audio box and see if you can get it to force its sample rate to 48k outside of FCP. If so, you can probably get FCP to record correctly at 48k. If not, you might be better off just letting it record in 44.1, and maybe batch exporting later to upconvert.
    Hope this helps -
    Max Average

  • Counter Problem at low sampling rate

    What I am trying to do is to count the input from the camera and generate the number of pulses depending on the delay and interval. At the rate of 33ms the program works perfectly but if the sampling rate is 150ms it generates 2 pulses at a time. Is there a better solution to my problem ? Am I doing anything wrong ? Is it a problem with the loop timing or acquisition timing? I have attached the program. What puzzles me is that it doesnt work if the rate is lower! Please HELP.
    Thanks 
    p.s. I am very new to LabView so please excuse my ignorance.
    Attachments:
    CoolSnap.vi ‏142 KB

    Hello sha33,
    Thank you for getting back to me with more information. After looking through your code once more, I believe I have found the issue. Since this application is timed entirely in software, it is based on how quickly your operating system can run the program, and thus cycle through loop iterations. Since you have no Timing VIs in the program, this loop is running as fast as possible. Now, in the 33 ms case, you are getting a TTL edge a lot faster, so the DAQ assistant is updating its count faster as well. Lets say hypothetically that your loop is iterating at 60 ms. This means that every time you run through the loop your DAQ assistant will read the updated count value, and since you are counting every 33 ms, your count value will have updated.
    Now let's look at your 150 ms TTL signal. This is significantly longer than the 33 ms signal in the previous case. Lets say hypothetically your loop is running on average at 60 ms again. This time, your edge will come in and the counter will increment, generating a pulse with the second DAQ assistant accordingly. Now your loop will run through again 60 ms later but your next edge on the 150 ms signal is still around 80-90 ms away. This means that your DAQ assistant will return the same count value as the last iteration, and once again a pulse will be generated.
    Obviously the numbers I used for the loop iteration timing are hypothetical and entirely dependent on the operating system and its resources (i.e. it will run slower with an MP3 or Movie playing in the background). My suggestion would be to use a timing VI such as Wait Until Next ms Multiple to clock your loops more consistently. The goal would be to make sure that your loop is repeating faster than your counter is updating. Alternatively, you could account for the possibility of no counter input in your overall application to prevent a false positive.
    Let me know if I can clarify any of the above information, or if you have any additional questions related to this issue.
    Regards,
    Chris Behnke
    Sr. RF Engineer
    High Frequency Measurements

  • High sampling rate is not accurate

    Dear alls,
    Any one know why the time loop is not accurate at defined period at the RealTime Trace Viewer ? In figure of VI, I set the period for the time loop is 250 us, but when I analyze in Real time Trace Viewer, it shows the real period time about 676 us. That means my data acquisition will be sampled in wrong sampling rate.
    Could you give me some explane, please? And how can I solve this problem? I tested this code with MyRIO board.
    Best Regards,
    Kien 

    crossrulz wrote:
    Why do you have a wait in your timed loop?  The point of the Timed Loop is to state the loop rate.
     ??? Bigger problems than that!  Why do you have any timing other that the TASK timing? And really, The task timing is most likely the loop rate.
    Can you post your actual VI?  I suspect something else is happening here that we cannot see (configurations, channels used, etc).
    And a snip of the Task needs posting

  • MyRIO aggregate sample rate

    Hi Forums,
    Quick question, the myRIO AI sample rate is 500kS/s aggregate on the MXP connectors (A and B).
    My current thoughts are that connecting to inputs on AI0-AI3 on MXP connector A, would give me 125kS/s per channel, therefore ~ 62.5kHz bandwidth (please correct me if I'm wrong).
    What I'm trying to work out, is whether the 500kS/s gets split between the total inputs shared between MXP A & MXP B; or is it 500kS/s aggregate per connector? I.e. If I split my inputs to AI0-AI1 on MXP A; and AI0-AI1 on MXP B, would I be able to increase my sample rate per channel?
    Kind thanks,
    Tori
    Tori
    Student
    Solved!
    Go to Solution.

     Hey Tori,
    Here is a thread on a similar question: http://forums.ni.com/t5/Academic-Hardware-Products-ELVIS/Question-about-myRio-Hardware-ADC-DAC/td-p/...
    Any I think my answer in that thread (copied below) should answer your question:
    The best way to think about the myRIO hardware is as if it has two ports the MSP and MXP (don't distinguish between A and B on the MXP connectors).
    The MSP AI, MXP AI, and Audio In (ie all the AI) share the same ADC.
    The MSP AO and Audio Out each have their own DAC but share an SPI line.
    The MXP AO has its own DAC and has its own SPI line
    Let us know if you have additional questions!
    -Sam K
    LabVIEW Hacker
    Join / Follow the LabVIEW Hacker Group on google+

  • Captures footage w too fast speed and strange audio (sample rate)

    I'm capturing NTSC video via small JVC camera. however the captured clip views much faster and audio is interrupting. I also get the message that my sample rate on source tape do not match capture presets. I've checked all the audio/video settings and can't figure out what's wrong. Also, on the camera screen it shows 12Bit - and I am not sure what it means.
    Footage is shot on Panasonic PD150, should be 29.97 frame per sec. Does anyone has any idea what I should be looking at?
    In the past I've captured the footage from the same tape and it captured normal. But it was a different workstation. Please help!

    A couple of things that you can try:
    Do you have a tape that is pretty much full and is designated on the cassette shell as a 60 minute tape? Fast Forward it to the end, you should not get more than 62 minutes showing on the timer. If it shows more, it was recorded in Long Play mode and has 12 Bit audio.
    When you change the Capture Preset to 32 kHz, it will still be 16 bit as you have already seen. It won't stop the sampling mismatch error message -just dismiss it. But your audio will probably still be usable. Give it a try on a short section.
    Your camera may have a problem, its not unheard of. Try a different camera if you have the possibility. Some cameras simply will not work well with tapes recorded on a different manufacturers camera.

  • Optical digital input (S/PDIF) problem (sampling rates)

    I have a huge problem with my 2009 iMac's digital input that I didn't run into on my older MacBook running the same OS (10.6.x), and it's driving me nuts!
    Basically, I'm trying to record a digital feed from an ADC hooked up between my hand-built tube amps/turntable and my iMac, with the goal being the transfer of some of my LP records to 48/24 LPCM for archiving and editing. The ADC's output rate is fixed at 48000Hz and cannot be changed. My iMac, however, refuses to lock on to the device rate, instead forcing 44.1kHz in the audio/midi setup. In fact, I can't get it to do anything but 44.1kHz on anything I plug in (even my DAC's passthrough) despite the fact that I need to use 48kHz. The audio is correct for a few seconds, then forces back to the wrong rate again. No matter how many times I try, the computer insists on using the wrong sampling rate, which has rendered impossible any hope of using my iMac as an audio recorder.
    I've tried setting up an aggregate device, but to no avail. Nothing I do seems to work, and since the problem is with Core Audio, any program used to catch the audio records gibberish. Is there a way to force Core Audio to use 48kHz in the terminal? It's not like the computer can't do it, as I get about 2 or 3 seconds of correct audio when changing the sampling rate manually. I just can't get it to stick!

    Seeing the exact same thing here. External digital source is 48kHz, and this Mac Pro Desktop will only stay on that setting very temporarily (for about .10 or .15 seconds) then it reverts back to 44.1kHz. Even if I don't have a signal or even a Toslink cable plugged in to the input.
    (I'm surprised you are getting 2 or 3 seconds of correct audio, when I'm getting about 1/10th that before it reverts back to the wrong sample rate. Maybe related to a buffer size option somewhere?)
    I have tried every known option to reset or re-configure this, and even to the point of creating a new user, resetting PRAM, resetting SMC, etc. I was going to try upgrading to 10.6, thinking maybe it was a 10.5.x problem, but now I'm not sure that will help.
    Had I the choice to set the setting to be 48kHz and lock it in, it should stay on that setting - (even if the chance exists that what I'm getting is not correct.)
    More often than not, I know what I'm doing more than Mac OS does, and I want to force it to do what it needs to.
    There really needs to be a "do it because I told you so" option for most of the Mac audio configuration system. This automatic "the hardware decided to do something for you" stuff is absolutely horrid for a system that is marketed as "Pro". A real "Pro" system would let me edit the configuration once, with the tool (text editor hopefully) of my choice, rather than attempting (and failing) to automate things.
    +1 for another instance of this being "a huge problem" and "it's driving me nuts!"

  • Why Audition CC don't show sample rate correctly?

    Hi
    Using Audition CC on Mac OS X with Mackie 1220, 12-channel premium analog mixer with integrated 24-bit/96kHz Onyx FireWire I/O (Quality is amazing!)
    Need to record on mono a horrible old tape recording with voice only to "hero"'s repairing audio and configure the best sample rate for recording.
    My preferences Audio Hardware on Audition are:
    Device Class: CoreAudio
    Default Input: Onyx Firewire (0025)
    Default Output:  Onyx Firewire (0025)
    Clock Source: Device
    I/O Buffer size 512 Samples
    Sample Rate: 96000 Hz
    Question 1: Expert said do not use more than 48000 Hz for recording voice only and use mono. Humans can't listen more than 20000 Hz... well... My recording on 96000 Hz is better than 48000 Hz and I'm not Superman... and can hear better difference with 96000 Hz recording. Don't know why.
    Question 2: Why after selecting Audio Hardware preferences to 96000 Hz after recording the File Panel said my track is 48000 Hz Mono 32 (Float)? My hardware can record at 96000 Hz and preferences is set correcty at that Bit Depth then WHY don't appears 96000Hz on File Panel after recording and instead appears 48000Hz?
    Question 3: Don't understand the differences of my 24-bit/96kHz Onyx FireWire I/O and 32 bit (Float) of Audition. If I record using 24 Bits (Maximum bit depth of my hardware) why appears 32 bit (Float)? My recording are 24 Bits or 32 Bits?
    Thanks :-)
    Tom

    CS6 has a serious issue with saving files correctly. The program is asuming that 48kHz is the maximum you will be using and in my case it saved a 96kHz recording with a 48kHz internal header. The file size is consistent with all my previous 24/96 recordings and it sounds just fine interpreted correctly - but played an octave low in frequency and tempo it really sucks unless you are a Blue Whale..
    I can play it "interpreted" as a 192kHz file just fine, and it now sounds 100% right, but I cannot save it correctly. I have yet to find out how to recover because when I use "convert Sample Type" it saves it with the same mistake - the wrong sample rate off by the same ratio again.
    It is a program flaw - so at this point you cannot record with sample rates higher than 48kHz in CS6 and depend on your file being OK.
    Tom the reason you can tell the difference between sample rates is that your hearing has two dimensions, frequency and timing, I sure hope you can't hear the bats at night but I expect that you can tell a good drummer from a bad drummer. In addition there is also the issue (dimension) of bit-depth - instrument decay and acoustic space occupies the time space between notes and if it is not sampled at the right time and place or rounded off to the nearest digital digit you have a problem.
    You all know that some humans have perfect pitch and others dont, this gives you some indication how much we each differ. Some people have even learned to use echolocation; the best know cases being blind people because they are not supposed to be able to find their way and know where they are. You can learn underlying concepts of this little discussed aspect of human hearing here and hit the university libraries for the rest. http://en.wikipedia.org/wiki/Human_echolocationhttp://
    SteveG's comment are only true in one of the three dimensions - frequency range. We all hear about the same for starters anyway.
    The second dimension, timing, is what provides spatial information. Coarse sampling effects this as well. My most recent experience was when transcribing some old casette tapes - when I experimented with FLAC and WMA lossless I found that they din NOT downsample well. Spatial information was significantly deminished be that aucoustic or studio work. Needless to say this surprised me because I was auming that I could drop the samplerate to 48kHz as soon I was done editing and save a lot of drive space. For now I made some excellent 48kHz/24 bit mp3s (320) because they altered the sound the least.
    Now you know some additional reasons why older guys like me who have lost the high end and a lot of decibel as well can still tell the difference:we have good sense of timing.
    Anyway - I need to learn how to edit my files to reset the sample frequency header - real fast. I just recorder a fabulous Madrigal group for 2 hours and my files are lost in the vortex.

  • Core audio and sample rate conversion

    I would like to know how to take manual control over core audio regarding sample rate destruct... er conversion. First - I know the workarounds - simply closing the audio player of choice, resetting the external hardware and relaunching the audio player of choice.
    setup:
    I run external converters with an external sample rate clock source. No problems or issues here. I keep my music collection segregated by SR (96k, 88.2k, 48k, 44.1k) as I ALWAYS listen through external converters.
    The annoyance is when one forgets to keep track of core audio and inadvertently ends up listen to a piece of music sample rate destructed. You know - walk up to music server computer, forget that you had DAC set to 44.1k for last music played, put on 96k source, SRC takes over and you don't notice the artifacts and distortion for a few songs. No one wants that! Don't get me wrong - it's a convenient feature and the amateur user would be sunk without it.
    What I want is an indicator that will tell when SRC is turned on and further, what the input and output sample rates are (as far as core audio is able to determine from the hardware anyway). In my world this would have been a check box in a preference setting. Perhaps someone has written a script or app for this? Command line instruction?
    Thanks

    Start with http://developer.apple.com/documentation/MusicAudio/Conceptual/CoreAudioOverview /Introduction/Introduction.html and direct further queries to the developer forums under OS X Technologies.

Maybe you are looking for