Sample Delay VI

Currently i'm using Labview 7.1 embedded together with speedy-33.
i had my audio input to speedy-33 from my PC sound card and i wish to delay the time of my signal by let say 1sec.
I had my left signal connect to the sample delay vi then from sample delay vi to audio output.
Audio in (only one channel,left)--> sample delay --> audio output
i should heard a delay of 1sec when a audio signal i played but there is no delay.
i use two waveform graph to observe the signal before and after the sample delay vi and indeed there is a delay as the waveform are different.

The file attach has a input sin wave connected to a sample delay vi and then to a analog output.
Waveform graph were ploted before and after the delay for comparsion.
Thanks for the help.
Attachments:
Sin sample.vi ‏36 KB

Similar Messages

Avoiding phase cancellation with sample delay plug in

Hi
I had soem horns in a mix sounded flat so i used the sample delay plug in to slightly delay the right side then they sounded great , really big and sat in the mix but when witching to mono they nearly dissapear.
Is there any trix to avoid this phase cancellation when swithching to mono?

Data Stream Studio wrote:
1.-I think if you reverse polarity on 1 of the channels of your mix instead of just reversing polarity of one side of the problematic horns, you may well solve one phase issue and create a whole lot of new ones.
2.-This is a good idea, maybe there's a setting that sound as fat as the one you're using but will not phase cancel in mono.
3.-I'm not sure what audio file you'd move... could you explain?
If it's a Stereo file, split it into two mono tracks, and move on of the two up/down the timeline by a few samples, until you get the least phase combing effect.
Maybe the OP needs to go back and re-mix that song, and find the culprit horn out of the whole section... if he can...

Sample Delay - samples into millisecond delay time?

Hi guys
Hopefully a simple question and I'd love some info.
I'm mixing in 5.1 and want to simply put up a general 25 millisecond delay in the left rear channel and 35 millisecond in the right rear channel. Some room calculations for what I recorded require 25 - not 20 and 35 not 30 milliseconds...... the standard stereo Delay won't allow increments of 5 miliseconds.
I'm therefore thinking of using the SAMPLE DELAY ........ whilst I have a 24 bit 48 khz recording setting ....... is it possible that within the maximum 10000 samples I can get up to 35 milliseconds ....?
How do we make the calculation work ..... the manual says 10 centimetres mic distance is 13 samples at 44k
is it possible to get up to 35 milliseconds using this?
Many thanks
Dick

My dear Christian ....... that is just the quickest most wonderful solution to question I've ever had ..... thank you for that PERFECT answer ....... I'm a happy man!
All the very best
Dick

"fine/sample delay", mixing down live drums, esp for JustinC!

I'm curious about the "fine/sample delay" and "phase inversion" techniques briefly mentioned by JustinC in an older post regarding recording live drums. I understand using phase inversion on snare mics that are pointing up/down, but I'm not 100% sure about the fine delay adjustment. Is this actually shifting the audio to line up waveforms from mics that are different distances from the same source? I've done this with an upright bass before (F-hole mic and another a few feet away) and it seemed to get a much fatter, clearer sound. I really appreciate any tips you might have on how to pinpoint and solve the problems.

hey over-man,
I was prowling tonight and ran across your post. I don't know your reference specifically but I understand your question.
Sample delay regarding a multimic'ed source:
This is based on phase cancellation and reinforcement. It is initiated by everything in a multimic'ed environment. The times, distances, microphone choice, effects choice-it's everywhere.
The best approach for me (typically) is to get the most appropriate sound earlier on unless you can expect variables ahead of time and factor them in right away. We'll work with an example of simply getting a natural drum sound that will line up with existing tracks (bass, gtr, vox...).
1) You can set up the sound/mics as close as possible to fit the sound you're after (we'll breeze over these points not specific to your question).
2) Before destroying the sound with a handful of plugins adjust delays. Some assumptions can be made:
A: Overheads/Room Mics will typically be the reference for the reason that they are what you have least control over because they represent more sources (Drums in this case).
B: These Mics will often have the largest delay from the start for the reason that they are farthest from the source.
C: These Mics should be adjusted less than others, I would EQ them quite minimally. Solve any problems as early in the signal chain as possible and use only what you know you'll need. Do not apply FX you don't need and position mics to better suit your desired sound.
So your OHs/Rooms are as good as they can sound naturally and sit with the track as well as possible, you can now start adjusting delays/intrtoducing other elements.
The order can vary here but I tend to start with the tracks/mics which will be more prominent. I will use snare in this example.
Some useful tools before we resume: Logic's sample delay, Expert Sleepers' Latency Fixer, because Logic's Sample Delay will not predelay. Found here:
http://www.collective.co.uk/expertsleepers/latencyfixer.html
I would normally just load both of these up, I use full PDC and apply these AUs to each track-remember to turn off Software Monitoring!
Create an instance of Latency Fixer, set it to 2048 samples. You have now added 2048 samples of predelay to your track.
Create an instance of Sample Delay, set it to 2048 samples. You have now adjusted your track to play back at the original record position.
Copy both instances to each adjacent track.
So we now have Latency Fixer followed by Sample Delay on each track for the kit (not necessary for the OHs unless you want to shift everything a little, but I will often do this from the arrange by ms).
At this point you will not need to adjust Latency Fixer's settings and simply use sample delay to offset delay in either direction.
Bring the snare track up to a reasonable level (the closer you are the better). Adjust Sample Delay in either direction and you will notice the sound changes from phase cancellation/reinforcement. Certain frequencies will stand out more at different settings. It normally won't take much, we don't want it to sound like a delay. Someplace within +/- 300 samples is often best for a natural sound. It's a good idea to have a phase inverter (Gain PlugIn) handy for 2 reasons: It may sound better inverted. You can invert the phase to pronounce things you DON'T want to hear and then flip it around the right way after setting the delay to pronounce them. Volume has a huge bearing on interaction here, a good delay setting may sound bad after reducing the level 2dB so Sample Delay setting, volume and phase should all be updated as soon as possible.
By now you have noticed how adjusting the delay affects the sound, inverting the phase is an exaggerated example of this principle. Inverting the phase of two identical tracks cancels them entirely, applying fine delay to one will introduce some of the frequencies and leave some cancelled. You can hear it scan through which frequencies by adjusting the delay. With multiple sources, different mics and different distances these delays already exist. Delaying them so they match (based on distance) is not always the best sounding but try to start somplace close. After setting the delay and Volume as close as possible you should be able to get away with much less surgical types of PluggIng and ultimately have more natural sounding tracks. Will often comprise 75% of the sound (if you want natural tracks).
If there are dynamic effects you know you'll want to apply there are special considerations.
Many of Logic's "lookahead" paramaters delay the signal.
Compression/Gating, etc. (on a per track basis) will alter the volume significantly enough that if you know you want a track compressed... ahead of time you should probably set these as you would then adjust the delay.
I tend to use predelayed tracks as keys for the audible tracks, this allows you to get around the aforementioned lookahead problems and will provide you with more control over the "shape" or envelope.
Concerning phase inversion based on which head you mic: It is a generalized solution to mic setup, though not a hard and fast rule which applies in every case.
Delaying in this manner is aligning waveforms. Based on frequency you are causing some frequencies to stand out more or less since we are working with complex waveforms. Very small deviation from original position will affect higher frequencies most and as you get further away from the original postion it begins to affect mids and eventually low frequencies. Of course this is because the frequency/wavelength. Align and misalign the waveforms for your desired sound. It does require you listen very closely when setting it up but I really think the results are worth the effort. Hopefully you'll find this helpful, it's easier to hear the effect than to describe it, hopefully it is apparent once you hear it.
Finally, I don't have any Platinums. If it doesn't work better for you, don't believe it needs to. Hopefully others will chime in here so you can get some second opinions on the approach and/or general drum mixing techniques.
Cheers, J

Sample Delay

Hi,
with using ProTools there is a nice function that allows you to adjust the sample delay due to adding several plug-ins to a track.
this way you can compensate the physical micro-dealy created by the
poor/stressed DSP by processing that amount of data at the same time..
now, where can i find the same fuction here in LE?
how is ti called?
thanx

You're talking about plug-in delay compensation. It's built right into Logic (Express and Pro). You can switch its behaviour to act on All tracks, Audio Tracks and Instruments, or None in the Audio preferences (I'm not in front of Logic at the moment...can't remember the exact path).
You'll want to leave it on "Audio Tracks and Instruments" when you're tracking, and "All" when mixing. Other than that, it's automatic. No adjustments required.

Sample Delay bug

Does has anyone else noticed that Sample Delay doesn't remember its setting when a project is closed ? Or is this just a problem with my system ?
1) Insert a Sample Delay plug-in on any track and set the delay value to anything other than zero
2) Save your project, close it, re-open it
3) Check the delay value--it's reset to zero
Happens every time I close the project. Bummer.
James
[email protected]

To get rid of the playing through the channel strip thing, control-click (or right click) - it may be a long click, I don't remember - on the speaker/play icon in the sample editor and you have the option to listen through the pre-listen channel.

Triggered dig. input, 1.st sample delay?

I find the "Start & Stop Trig Input.vi" useful, and want to use it in an application where I sample the state of five photo detectors. When a vehicle passes a detector, I want to time stamp the sample. I collect the samples in an array, and search the array after the acquisition ends. Sample index devided with sample rate is then the time. The problem is that I get a varying time offset from the start trigger (sample 0) to my time stamps. If I wire a bit directly to the trigger pin, I get a time difference from about 10ms to several hundred ms between the trigger and that bit. My DAQ is a DIO-32HS.
Gunnar

Hi Gunnar,
Let me make sure I understand you correctly. You are trying to perform pattern input at a specific rate and you want to be able to timestamp your inputs. You notice that when you apply a rising edge signal to both, the trigger and a bit, there is an acquisition difference of 10ms-100ms. What type of trigger are you using? Is it a pattern match? What is your sampling rate?
Are you using the control "pts after stop trigger"? Does your delay correspond to this number of points divided by your frequency? What I would try using is a simple "Buffered Pattern Input-Trig.vi" from the shipping examples with LabVIEW and connect your trigger to one of the bit lines. I've tested it on my PCI-6534 and I see my signal as the first data point in my arra
y. Anyway, let me know what specifics you are dealing with and I might be able to help you out. Have a good day.
Ron
Applications Engineer
National Instruments

Sample delay from software to hardware

Hi,
I am interested to find out the time it takes for a sample generated in LabView until it hits "the air" (channel output) of one of your DAC cards? I couldn't find any data on this in the different product specifications nor in the forums.
Thank you very much,
Thomas Schmmid

Hello tschmid. The time that a value takes to appear at the analog output of a DAQ board can be divided into 2 distinct parts. The first part is the time it takes to get from the software to the buffer on the DAQ board. The second part is the time it takes to progress through the buffer on the DAQ board to the output. The first part is nondeterministic since there is no way to benchmark this process, but should be very quick since all the software does is send the output value to the board. The second part can be found in the user's manual of a specific DAQ device under "Maximum update rate" for analog output channels. For example, assuming one channel is being used, the PCI-6251 has a maximum update rate of 2.8 MS/second. Thus, if you have a clear buffer, it will take this second part 1/2.8M seconds to execute. If the buffer contains 99 values before your desired output, the second part will take 1*100/2.8M seconds since 100 values have to be written to the output in order to see that value that was just written to the board from software. There is a way to ensure that your onboard memory doesn't slow down this process too much. There is a property node in DAQmx called AO.DataXferReqCond which allows you to chose one of the three following options: "On Board Memory Empty," "On Board Memory Half Full or Less," or "On Board Memory Less than Full." Choosing the "On Board Memory Empty" option will allow a more responsive output assuring that the current value written from software will be seen on the board's output quickly, but it will limit the achievable update rate. However, if you are concerned with seeing one value appear on the board in the shortest amount of time, "On Board Memory Empty" is your best option. I hope this helps and if you have any additional questions, I would be happy to address them. Have a great day!
Brian F
Applications Engineer
National Instruments

Delay plug-in usage

I am recording live through 2 mics. I need to introduce a delay on one mic of 25 ms (millisecond). Do I use the stereo delay plug-in or the sample delay? and how do I set it to 25 ms?
I am new to this and using Logic Express
Thanx in advance.

Either would work fine, I'd go for the sample delay. To work out how many samples per millisecond is pretty easy. If you're working at 44.1khz, the thats 44.1 samples per millisecond, 96 per ms for 96khz and so on.
1102.5 samples = 25ms at 44.1khz
Hope this helps.

Can I move audio in logic by the sample in the sample editor to compensate

I wanted a final say on wether or not I can move audio with sample accurate percision by moving the anchor in the sample editor with update in arrange page turned off. i just need a verification of this.
Thanks guys

yes you can and should use the sample editor to make
such compensations. you do this by aligning the
anchor point to the sample or part of the wave form
that you want to correspond to a beat or subdivision
(ideally) though of course it can be any point you
want it to.
if you use 'pickup clock; move object or event to
SPL' KC the anchor point will jump to the SPL.
Philip K is right though; if your entire track is out
by the same amount that you can measure you could use
the sample delay (though of course that will only
delay it not move it forward in time). but you won't
see the waveforms align themselves to the beat
meaning you would have to be aware that that track
has been compensated for.
on balance i would edit with the sample editor.
I was thinking that you could delay the rest
of your tracks by however many samples thus
aligning by compensating everything else though
in real world situations I don't know how practical
this would be. I keep forgetting that you can measure
how many samples you select in the sample editor even
if you cannot see them individually. So I will defer
to the voice of experience on this. If Rohan would use
the Sample editor, then I would tend to agree

How do I create a fade effect w/ a sample?

Hi...
I'm trying to get a certain effect but have yet to stumble across a good way to get the effect.
I want to make a sample repeat until fade... In other words, I want it to play the sample and then loop 3 or 4 times until it fades into nothingness. For some reason I have a feeling there is a few ways to get to this type of sound...
What is the best way? An FX Plugin, Loop/Sample Editor, Inside the DAW itself? Maybe another way?
I'd like to get some tips on how to accomplish this effect... Let me know if I'm not explaining the type of sound I'm looking for properly... But it's basically an echo to fade effect used quite commonly... I just don't know the best way to achieve it.
Thanks!

Ok, follow me on this one.
Create an Instrument track, load the EXS24 Sampler in the instrument slot. Load any drum kit. (note: this could be a one-shot sample on an audio track as well)
Next... load the Stereo Delay into an INSERT.
If you play a snare drum sound are you hearing the ping-pong echo effect. (I know that's not what you're going for, this is just a test.)
pancenter-
p.s. if you loaded the "Sample Delay" plugin, it won't work that's a different type of delay related to timing.
ps.II I suggest trying the tape delay, experiment and become familiar with the controls, also, check out presets on all of the plugs.

Logic 7.01: UAD-1, delay compensation

First question is this. If I would be using anything besides 7.01 that would fix all my problems regarding plugin delay...right?
Second question if I remain with 7.01 and when using UAD-1 card, If I use 2 UAD plugs on track 1 do I need to apply a UAD-1 sample delay plugin set to two samples for every other track in my song that does not have a UAD plug?
While I am at, does the PDC in 7.01 only work for tracks and not busses?
I know this is the approach for Pro Tools LE, didn't know if it was the same for Logic 7.01
Thanks

Hi
Full implacation of PDC is not a Logic feature ! what we have is an antiquated version of PDC, we have had a fix to PDC in 7.1 ( as an after thought to a much requested feature ) the next Logic paid for upgraded is expected to included the full program re-write that is neaded for Full PDC, but in Apples defence Logic 7.1 does go someway to fixing the the problems you are incurring with UAD, at the moment Logic is playing catch up but I'm sure it will roll some eye's with the next release ( maybe we'll get some of Studiovision pro's fully working features )
TTFN
Subcoustic
G5 2Ghz DP 4 Gig Ram Mac OS X (10.4.3) Magma 4x Uad's Powercore Pci & Firewire, Mackie Onyx 1640 firewire
G5 2Ghz DP 4 Gig Ram Mac OS X (10.4.8) Motu2408III & 24io Magma 4x Uad's Powercore Pci & Firewire, Mackie Onyx 1640 firewire
G5 2Ghz DP 4 Gig Ram Mac OS X (10.4.3) Motu 2408III & 24i0 GenX96 Magma 4x Uad's Powercore Pci & Firewire, Mackie Onyx 1640 firewire

I/O Buffer Size Causes Bounce Delay

Hi All,
Came across a really frustrating problem here. I've got a pretty sizable project I'm trying to finish up. I'm about to send it to someone else to mix, so I'm bouncing out a few of the tracks that contain instruments that the mixer doesn't have. Unfortunately, everything I bounce is coming out delayed, depending on the I/O buffer size. Just to verify this, I bounced out a clip with the buffer set to 128 and one with the buffer at 1024, both with the click left on. Sure enough, the 1024 is pretty significantly delayed from the click, whereas the 128 is pretty much right on it.
I'm using some inserts across the project, but really nothing significant. All instruments, vocals, etc. are being bussed to aux tracks for grouping and then all of the group tracks are being sent to a master bus track which is going out the stereo out. I don't have any processors on the master bus or stereo out, and PDC is set to "all".
Anyone else experiencing this? More importantly, does anyone have a solution? I'd really rather not have to figure out the sample delay and shift everything.

I would think it has more to do with the Fast Track Pro than your computer or Logic. Does the FTP have drivers or is it system compliant? (plug it in and it just works)
All things considered that's a very inexpensive interface.
Please don't take this next bit personally... Unless you have a pristine listening environment and top of the line equipment... recording at 96kHz is not really a wise decision. Recording at 24-bit will have a much greater impact than the sample rate.
Here's what happens at 96kHz.
The files recorded are twice the size of files recorded at 48kHz.
A 96kHz / 24-bit stereo file is approx 35 Megs a minute, add to that effects running at 96kHz and is fairly easy to over load an iMac or Laptop type machine.. a MacPro will fare a little better, depending on the audio hardware.
Effects like Space Designer and some of the top line AU-instruments s-u-c--k CPU cycles as well.
What I think you're seeing is an overload of the bus system, why it happens at higher buffer levels is anyone's guess, most would say it's the iffy M-Audio drivers.
pancenter-

How to use my external processor effects?

I have a lexicon processor and I want to know how to use it with logic.
Thanks
g5 ma' os Mac OS X (10.4.4)

I hope this info can help you.
The main Problem is that Logic don't have an delay compensation plugin like in nuendo or cubase "external FX"
Here is the info to compensate the delay coused by the D/A and A/D converters:
6.30 How do I set-up record / playback / monitoring delay?
Subject: Record delay vs send/return using external effect units
You'd think that with modern multichannel audio interfaces and a modern, professional audio sequencer like Logic, this would be a piece of cake, right? It turns out that there are a number of potential traps, all to do with Logic's highly inadequate record delay compensation. What follows is a run through of the general setup procedure, using my RME Multiface.
Basic Record/Playback delay Setup
Set up a 4/4 audio click track (trim the sample starts so they are right on the beats). Use real audio, not a software instrument. Rerecord the main outs to a new track via a hardware loopback cable (i.e. cable your audiocard's outputs into its inputs). Measure the clicks with reference to bars/beats in the Sample Editor - the clicks should be (but may not be) recorded right on the beat.
If the audio driver has a record delay parameter in samples, use that to adjust. If not - use the ASIO Buffer delay "IN" for coarse adjustment (multiples of buffer). Leave the ASIO Buffer delay "OUT" at zero. Use the main driver playback delay for final fine adjustment (samples). Do NOT use the Arrange window's delay parameter - it's in ticks and thus tempo-dependent!
So if you are playing in time with a prerecorded track, your playing is recorded in the correct position to preserve your exact timing on playback.
The use of the playback delay to compensate is not ideal, as it will mess with the playback timing vs displayed position of any audio - this has an adverse effect on fine editing, and MIDI-to-audio sync - but Logic unfortunately does not provide a sample-accurate record delay adjustment, and has not done so since version 3.5...
Effect Return/Record Setup
You definitely want to avoid monitoring external FX returns through Logic if at all possible, since that would add 2x the audio buffer worth of latency to the return, which will adversely mess with the sound of any time-based effects (i.e. just about everything). So, monitor your external FX returns at source, or through direct hardware monitoring - in my case that's through RME TotalMix routed to the main outs for (near) zero latency.
You probably want to be able to record the external FX outputs into Logic (to free up the FX for other uses) and have it play back exactly as it was monitored, right?
Using your 4/4 audio click track, panned left, send to an external delay (approx 1/2 beat, single repeat). Pan the delay return R at source and monitor as above. Rerecord the main outs to new track via a hardware loopback cable. Measure the number of samples from a click to its delay in the Sample Editor
Now record the delay return signal to a new track. Playback just the audio click panned left & the recorded delay panned right. Rerecord the main outs to new track via hardware loopback cable. Measure the number of samples from click to delay in Sample Edit.
Both measurements must be the same for accurate recording of FX returns, but it's likely they won't be, probably because the playback delay has been messed with. Compensate by inserting a sample delay on the FX return Input Objects in Logic. Since you're not monitoring the FX returns through Logic anyway, the input delay will be recorded but not monitored (in 5.2+, but if you use an earlier version you're hosed since effects are not recorded).
Record the delay return again, play it back with the click, rerecord the outputs and measure again. Adjust the input sample delay until the recorded-&-played-back delay position is identical to the monitored delay.
Live Input Monitoring/Recording
For accurate timing, monitor any live inputs at source or through direct hardware monitoring (TotalMix), the same as for FX returns. When recorded, playback timing will be accurate. Sends from live inputs to external FX can also be applied in at source or in TotalMix. No problem.
Live Input Monitoring Through Logic
Here's where the problem starts. If you also plan to monitor some live inputs through Logic - to add Logic FX, or to control & automate the live inputs, or to add live inputs to a bounce, etc - then you'll be monitoring the live inputs with a latency of 2x the audio buffer size (or more if applied processing induces further delays). Therefore when you record a live input, on playback it will be early by that amount, since the record/playback delay is set up to compensate for zero-latency monitoring. What you heard live is not what you get on playback.
There's no set-&-forget way around this, since Logic won't let you apply a sample delay to an input without the delay also being applied to the input's monitor output from Logic. So using the same input delay trick you applied to recording the FX returns won't work - you'll wind up monitoring with even more delay, which will need yet more input compensation, and so on. You can't use the record/playback delay to compensate, because that would screw up the recording of source-monitored material.
You could conceivably monitor everything through Logic at all times, and use a single record/playback delay to compensate for all of it (with the editing & MIDI-to-audio sync shortcomings discussed, but on a larger scale as considerably more compensation is required), but that will screw with the sound of any time-based external FX as noted above.
So assuming you stick with source-monitoring the external FX returns, there are 2 options for correct playback timing of any recorded tracks that were monitored through Logic while recording:
1 - Output all such tracks to a bus, and place a Sample delay on that bus to compensate. This will correct the playback you hear, but it won't correct the bad positioning of the audio.
2 - Physically move the recorded audio later to compensate. Uh-oh - Logic's Arrange window is not sample-accurate. And it's not possible to move a newly recorded audio region later in the Sample Editor without adding samples to the start of the file, which is a tedious process if you've just recorded a number of tracks. You'll just have to get it as close as you can in the Arrange - bear in mind that ticks are tempo dependent, so you have to calculate the number of ticks based on the current song tempo (let's not even begin to discuss Audio vs tempo changes in Logic), or use the smallest SMPTE nudge available. No fun at all.
If anyone has any other suggestions, I'm all ears...
So what about OS-X?
In Logic under OS X, the CoreAudio driver setup panel doesn't have any record/playback delay setup. If you're optimistic, you might interpret that as an indication that it's all done automatically by CoreAudio and the driver. But given Emagic's history in this area, what's the bet it's currently a big fat inaccurate mess? Rumblings from the Mobile i/o list seem to indicate this...
G5 dual 2,5 Mac OS X (10.4.4)

Blank Windows ...?

Hey you guys, what do think of this: When I bring up any of several screens - System Performance, Sample Delay, etc. - I get no info in the window! the window comes up, in the case of Systen Performance, say, and has the appropriate labels on the bottom. However, there are no vertical graphs showing usage. Similarly, the Sample Delay has most of the right headings, but no information as to how much I'm delaying either side.
Several restarts, trashed prefs, etc. Only new thing is an updated BFD.
What gives?

Saying "the only new thing I added is..." could be a dead give-away as to why you're having new problems. You've changed your system, and you can't assume that adding a plug-in will have no effect on your system's performance.
My advice is this: un-install BFD (all components), trash your prefs, load up an old song (from before you had BFD) and see if the problem appears. If not, then install BFD again. Load up that song, play around with BFD, see if the problem re-occurs. If so, you can be pretty darn certain that BFD is causing the problem. Then the problem-solving questions should be addressed to the people at the company that makes BFD.

Sample Delay VI

Similar Messages

Maybe you are looking for