Waveform Anzeige

Premiere CC:
Habe das Problem, das AIFF und WAV Dateien (egal ob 44.1 oder 48) - die nicht von Videomedien stammen (also Musik von CDs oder sogar das Voice Over von PP selbst) ihre Waveform Anzeige nicht von alleine darstellen. Erst wenn man einzelne Stellen anspielt, erscheint dort ein Stück Waveform - man muss also quasi mehrere stellen anklicken und anspielen, damit die Waveform im Ganzen erscheint.
EIn Test mit beispielsweise einem Track im Apple Lossless Codec erschien sofort in Gänze.
Was kann das sein?

Mmh, ja, sicher irgendwas mit dem Media Cache und wie die PEK Vorschaudateien erzeugt werden, aber wirklich sinniges fällt mir dazu nicht ein. Das sollte automatisch beim Import der Dateien passieren und nur Sekunden dauern... Vielleicht mal im PPro forum auf englisch nachfragen...
Mylenium

Similar Messages

How can i display Waveform chart in a subpanel using Vi templates.

Hi All
I am new to Labview hence need some help. I am trying to develop an application which reads some data from a Wireless Sensor Network (WSN). The WSN consists of base station connected to the USB port which recieves data from other sensor nodes. The data comes in a certain format. Node name, temperature reading, humidity reading etc. I want to read the data from the serial port and based on the Node name, i want to display the information for each node in s separate window or subpanel etc. So if a new node is detected then a new window is created for that node. Since all the nodes have the same sensors on board i only need a one template. I can read the data using the serial port, parse the data to detect which node it is and also what the sensor readings are. I have created a template VI for the sensor node. I am having problems in displaying the template VIs in a subpanel. I can succesfully display a Waveform graph in the subpanel but i am having problems in displaying a waveform chart in the subpanel. I can see the actual waveform chart in the subpanel, but i cannot see the plot. Would be greatful if someone could point out what i am doing wrong here.
Many Thanks
Raza
Solved!
Go to Solution.
Attachments:
template_graph.vi ‏16 KB
graph_template.vit ‏11 KB

Hi All
I think i have solved the problem. It seems like i was running the Vi in a loop. I have taken the Run Vi outside the while lopp and this works fine. Also i need to close the reference at the end.
Raza

How can i print out the waveform chart?

hello everybody,
how can i print out the "waveform chart". can i do it just push the button. ( example; stop button is stop the program etc..)
i checked the NI examples but i can't understand. i'm new to the Labview.
pls help me.
i added the my program
look forward your reply
regards from turkey...
Message Edited by hknmkt on 05-29-2008 04:15 AM
Attachments:
29.05.2008_11.vi ‏37 KB

hi jim,
i tried the program but it's not running. When i run the program, it's print out without run the program
i added the printed file.
look forward your reply
hakan
Attachments:
error8.JPG ‏8 KB

How can I tell if an arb is currently generating a waveform? (LabView 8.5)

I have a VI which configures the load impedance of a 5421 arb card by changing the value of the property node "Load Impedance".
This only works if the arb is not generating at the time of the call to the VI.
I wish to be able to call the function when the arb is either generating, or not generating a waveform.
Is there a way I can determine whether the arb is generating a waveform so that if necessary it can be aborted, then the Load Impedance changed, then the output re-initiated?
Thanks
Alan

The fastest way to do this is to Disable the output (with enable output.vi) change the impedance and re-enable the output.
Of course if you want to wait untill a generation session is complete you will need to configure the Done event to output something you can monitor (hardware only for unknown reasons) and use that to gate your changes.
Jeff

Missing Waveform Monitors - New Install, Most Recent Premiere CC 2014

Hi,
I recently downloaded and installed Premiere Pro CC and related apps with a cloud subscription on a new Mac Pro tower. I connected by working RAIDs and opened a PPro project originated on my previous edit system, an iMac. Right away I noticed some strange behavior and key features missing when I went to color correct my footage.
With the desired timeline active in the "Editing" workspace, I used the keyboard shortcut (I also tried this with the dropdown menu) and switched the workspace to color correction. Rather than the timeline activated in the "editing" workspace, a completely different timeline in the project appeared in the "color correction" space. This occurred multiple times with seemingly every timeline, but the one I desired to correct activating in the "color correction" space.
Also, the waveform monitors are absent from both the reference and program viewer menus. I can't seem to the find them anywhere. This leaves me feeling a bit crazy, as I was operating in the most current PPro CC version on the iMac just yesterday and everything was in its place.
Thoughts on what is going on here?
Here are my system specs:
Mac Pro
Yosemite 10.10.1
Processor: 3.5 GHz 6-COre Intel Xeon E5
Memory: 32 GB 1886 MHz DDR3 ECC
Graphics: AMD FirePro D700 6144 MB
For now I suppose, I'll try uninstalling and re-installing the app. Other ideas? Anyone else experiencing this?
Lindsay

Thank you for all of the feedback. I have tried un-installing and re-installing twice now. Once using the cleaner tool and once without. Neither has remedied the problem. I was sure to check "Remove Preferences" when performing the un-install, but when I opened a new project after the re-installation, PPro opened in the "Color Correction" workspace rather than opening in the standard editing workspace and still no scopes.
Other ideas?
I found this thread, which isn't boosting my confidence in a healthy Premiere / Mac Pro relationship, but I have seen no mention of the missing scopes issue I am experiencing. And really I haven't progressed to the point of attempting an export or render. As you well know, scopes are vital, and there's no point exporting if I can't properly polish a product.
Premiere Pro CC and the New Mac Pro (2014)

What deterimes the amount of data in a waveform from a TDS 1012 scope

Hello,
   What determines the amount of data that is in a waveform that comes out of a TDS 1012 scope? I am assuming that I will have to look at the driver vi to determine the commands sent to the scope to figure it out. I am in a situation that I need to have the y axis to have a high resolution, that results in very little data being collected from the scope.
Regards,
Kaspar
Regards,
Kaspar

Hello,
    The amount of data that comes out of the TDS 1012 scope is determined by the data start (DATaTARt)  and data stop (DATaTOP)  commands that are defined on page 58 (2-38) in the 346 page programming manual for the scope. I found of that the data start was not set to 1, which is the beginning of the data.
    I also had a very low level signal on channel that was all most unreadable by the scope that caused me to think that I was not getting all of the data.
Regards,
Kaspar
Regards,
Kaspar

Time delay between 2 waveforms

Hi,
Please bear with me while I explain what I’m trying to do :-) Basically, in the attached LabView file (“flow vis + trigger-m.vi”), I am generating 2 signals: a sinusoidal waveform (used to drive an actuator) and a square waveform (used as a TTL signal to trigger image capture on a CCD camera). Currently when I run the program using LabView 7, both signals are started simultaneously. I would like to introduce a time delay that can be manually specified in the VI, such that when the program is started (i.e. at time t0), the sinusoidal waveform also starts (i.e. at time t0) before the square waveform (i.e. at time t0 + delay time). In a practical sense, this means allowing the actuator to run for several seconds before capturing any images.
It sounds like it should be quite straightforward to do, but I’m not so sure how to progress. I have begun to modify the original VI (“flow vis + trigger-m_2.vi”, as attached), but would be much appreciative of any help or suggestions on how I can complete the VI to meet the above requirement.
Many thanks,
Mark
Attachments:
flow vis + trigger-m.vi ‏939 KB
flow vis + trigger-m_2.vi ‏895 KB

Please refer this URL for an example VI I made to solve the problem:
http://forums.ni.com/ni/board/message?board.id=170&message.id=227603
Way S.
NI-UK Applications Engineer

Creating a Time Delay Between 2 Waveforms

Hi,
Please bear with me while I explain what I’m trying to do :-) Basically, in the attached LabView file (“flow vis + trigger-m.vi”), I am generating 2 signals: a sinusoidal waveform (used to drive an actuator) and a square waveform (used as a TTL signal to trigger image capture on a CCD camera). Currently when I run the program using LabView 7, both signals are started simultaneously. I would like to introduce a time delay that can be manually specified in the VI, such that when the program is started (i.e. at time t0), the sinusoidal waveform also starts (i.e. at time t0) before the square waveform (i.e. at time t0 + delay time). In a practical sense, this means allowing the actuator to run for several seconds before capturing any images.
It sounds like it should be quite straightforward to do, but I’m not so sure how to progress. I have begun to modify the original VI (“flow vis + trigger-m_2.vi”, as attached), but would be much appreciative of any help or suggestions on how I can complete the VI to meet the above requirement.
Many thanks,
Mark
Attachments:
flow vis + trigger-m.vi ‏939 KB
flow vis + trigger-m_2.vi ‏895 KB

Hi Mark,
I forgot that all analog waveforms generated needed to have the same number of samples in a single task. By introducing a delay into your square wave, I effectively added samples that waveform. So the same number of samples added to the square wave has to be added to your sine wave. I added code that extends the number of samples of your sine wave (# delay + square wave samples). Let me know if this works for you.
Regards
Way S.
NI UK Applications Engineer
Attachments:
flow vis + trigger-m70.vi ‏872 KB

Arbitrary waveform generation from large text file

Hello,
I'm trying to use a PXI 6733 card hooked up to a BNC 2110 in a PXI 1031-DC chassis to output arbitrary waveforms at a sample rate of 100kS/s. The types of waveforms I want to generate are generally going to be sine waves of frequencies less than 10 kHz, but they need to be very high quality signals, hence the high sample rate. Eventually, we would like to go up to as high as 200 kS/s, but for right now we just want to get it to work at the lower rate.
Someone in the department has already created for me large text files > 1GB with (9) columns of numbers representing the output voltages for the channels(there will be 6 channels outputting sine waves, 3 other channels with a periodic DC voltage. The reason for the large file is that we want a continuous signal for around 30 minutes to allow for equipment testing and configuration while the signals are being generated.
I'm supposed to use this file to generate the output voltages on the 6733 card, but I keep getting numerous errors and I've been unable to get something that works. The code, as written, currently generates an error code 200290 immediately after the buffered data is output from the card. Nothing ever seems to get enqued or dequed, and although I've read the Labview help on buffers, I'm still very confused about their operation so I'm not even sure if the buffer is working properly. I was hoping some of you could look at my code, and give me some suggestions(or sample code too!) for the best way to achieve this goal.
Thanks a lot,
Chris(new Labview user)

Chris:
For context, I've pasted in the "explain error" output from LabVIEW to refer to while we work on this. More after the code...
Error -200290 occurred at an unidentified location
Possible reason(s):
The generation has stopped to prevent the regeneration of old samples. Your application was unable to write samples to the background buffer fast enough to prevent old samples from being regenerated.
To avoid this error, you can do any of the following:
1. Increase the size of the background buffer by configuring the buffer.
2. Increase the number of samples you write each time you invoke a write operation.
3. Write samples more often.
4. Reduce the sample rate.
5. Change the data transfer mechanism from interrupts to DMA if your device supports DMA.
6. Reduce the number of applications your computer is executing concurrently.
In addition, if you do not need to write every sample that is generated, you can configure the regeneration mode to allow regeneration, and then use the Position and Offset attributes to write the desired samples.
By default, the analog output on the device does what is called regeneration. Basically, if we're outputting a repeating waveform, we can simply fill the buffer once and the DAQ device will reuse the samples, reducing load on the system. What appears to be happening is that the VI can't read samples out from the file fast enough to keep up with the DAQ card. The DAQ card is set to NOT allow regeneration, so once it empties the buffer, it stops the task since there aren't any new samples available yet.
If we go through the options, we have a few things we can try:
1. Increase background buffer size.
I don't think this is the best option. Our issue is with filling the buffer, and this requires more advanced configuration.
2. Increase the number of samples written.
This may be a better option. If we increase how many samples we commit to the buffer, we can increase the minimum time between writes in the consumer loop.
3. Write samples more often.
This probably isn't as feasible. If anything, you should probably have a short "Wait" function in the consumer loop where the DAQmx write is occurring, just to regulate loop timing and give the CPU some breathing space.
4. Reduce the sample rate.
Definitely not a feasible option for your application, so we'll just skip that one.
5. Use DMA instead of interrupts.
I'm 99.99999999% sure you're already using DMA, so we'll skip this one also.
6. Reduce the number of concurrent apps on the PC.
This is to make sure that the CPU time required to maintain good loop rates isn't being taken by, say, an antivirus scanner or something. Generally, if you don't have anything major running other than LabVIEW, you should be fine.
I think our best bet is to increase the "Samples to Write" quantity (to increase the minimum loop period), and possibly to delay the DAQmx Start Task and consumer loop until the producer loop has had a chance to build the queue up a little. That should reduce the chance that the DAQmx task will empty the system buffer and ensure that we can prime the queue with a large quantity of samples. The consumer loop will wait for elements to become available in the queue, so I have a feeling that the file read may be what is slowing the program down. Once the queue empties, we'll see the DAQmx error surface again. The only real solution is to load the file to memory farther ahead of time.
Hope that helps!
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

Trouble capturing waveform from PXI-4472

I'm really a very green newbie at this stuff, so bear with me...
I've got a PXI-4472 data acquisition board and a PXI-5411 waveform generator. I've connected the arbitrary out of the 5411 to the channel 0 in on the 4472. An external oscilloscope shows a 1v-amplitude sine wave being generated.
I created a very simple VI to show what the 4472 is capturing. It connects a NI-DAQ channel I generated to the standard "AI Acquire Waveform.vi", then out to a Waveform Chart, all within a while loop with a Stop button. Problem is, all the waveform chart seems to be showing is the running average of the waveform instead of the form itself (solid line, a tad above zero).
I can hook the 4472 input channel up to a DC-out power supply, a
nd when I vary the voltage, the waveform chart changes as well.
So my question (whew!): What's wrong here that's not allowing me to capture a waveform from the 4472 (in turn from the 5411) and display it on my waveform chart?
Thanks in advance for the help.

Never mind.... it was a sample rate problem. I upped the sample rate and it came out ok.

Triggerring PXI-4110 to measure 1 current value while HSDIO PXI-6552 generating waveform

Hi,
Some question about PXI-4110 to measure current while PXI-6552 is generating the waveform.
1. Let say, I need to measure 3 points of current values, i.e. while PXI-6552 is generating sample-1000, 2000 and 3500. On the edge of sample 1000,2000 and 3500, the PXI-6552 will send a pulse via PFI line or via PXI backplane trigger line. My question is, is it possible to trigger PXI-4110 (hardware trigger or software trigger) to measure current values at these points ?
2. Let say I need to measure the current on 0ms (start of waveform generation by PXI-6552) , 1ms, 2ms, 3ms, 4ms... and so on for 1000 points of measurement, code diagram as shown at the figure below. It is possible for the VI "niDCPower Measure Multiple" to measure exactly at 1ms, 2ms, 3ms .. ? How much time will have to spend to complete acquire 1 point of measurement by "niDCPower Measure Multiple" ?
Thanks for viewing this post. Your advice on hardware used or software method is much appreciated. Thanks in advance.
Message Edited by engwei on 02-02-2009 04:24 AM
Attachments:
[email protected] ‏46 KB

Hi engwei,
1. Unfortunately, the 4110 does not support hardware triggering. Therefore you cannot implement direct triggering through the backplane or anything like that. However, there are a couple of possible workarounds you can try:
a) Use software triggering: Say your 6552 is generating in one while loop, and your 4110 is to measure in another while loop. You can use a software syncrhonization method like notifiers to send a notification to your 4110 loop when your 6552 has generated the desired sample. This method, however, will not be very deterministic because the delay between the trigger and the response depends on your processor speed and load. Therefore, if you have other applications running in the background (like antivirus) it will increase the delay.
b) Use hardware triggering on another device: If you have another device that supports hardware triggering (like maybe an M-series multifunction DAQ module), you can configure this device to be triggered by a signal from the 6552, perform a very quick task (like a very short finite acquisition) then immediately execute the DCPower VI to perform the measurement. The trigger can be configured to be re-triggerable for multiple usage. This will most likely have a smaller time delay then the first option, but there will still be a delay (the time it takes to perform the short finite acquisiton on the M-series). Please refer to the attached screenshot for an idea of how to implement this.
2. To make your 4110 measure at specific time intervals, you can use one of the methods discussed above. As for how long it will take to acquire 1 measurement point, you may find this link helpful: http://zone.ni.com/devzone/cda/tut/p/id/7034
This article is meant for the PXI-4130 but the 4110 has the same maximum sampling rate (3 kHz) and so the section discussing the speed should apply for both devices.
Under the Software Measurement Rate section, it is stated that the default behavior of the VI is to take an average of 10 samples. This corresponds to a maximum sampling rate of 300 samples/second. However, if you configure it to not do averaging (take only 1 sample) then the maximum rate of 3000 samples/second can be achieved.
It is also important to note that your program can only achieve this maximum sampling rate if your software loop takes less time to execute than the actual physical sampling. For example, if you want to sample at 3000 samples/second, that means that taking one sample takes 1/3000 seconds or 333 microseconds. If you software execution time is less than 333 microseconds, then you can achieve this maximum rate (because the speed is limited by the hardware, not the software). However, if your software takes more than 333 microseconds to execute, then the software loop time will define the maximum sampling rate you can get, which will be lower than 3000 samples/second.
I hope this answers your question.
Best regards,
Vern Yew
Applications Engineer, NI ASEAN
Best regards,
Vern Yew
Applications Engineer
Attachments:
untitled.JPG ‏18 KB

USB-6009 Analog Waveform Output

I'm trying to create an analog waveform from a USB-6009 device through one of the analog output channels. However, through the DAQ Assistant, I can only select the 1 Sample (On Demand) setting. When I test the device, I can only push a constant voltage out. If anyone has any advice on how to create an analog voltage waveform using this device, I would like to know.

>I am only a novice at LabVIEW and data acquisition in general.
I don't use Labview (I write in C++) so I can't help you with that. I try to answer questions about C/C++ and general hardware questions.
>What did you mean by software-timed waveform generation?
That's where the software driving the device sends a sample to the DAQ device, waits for the prescribed time interval, then sends the next sample. So the timing of the waveform is driven by the software, using the computer's clock, instead of by the DAQ hardware. Software-timed is less reliable and has (often) lots more jitter because of competition for CPU resources.
>Does this mean that I cannot generate a waveform that is more than 150 Hz?
It's worse than that. It means you can't generate a waveform faster than 150/N Hz, where N is the number of samples (data points) that define the waveform.
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

FPGA_cRIO build an accurate triangle waveform

Hi,
my third problem is to build an accurate triangle waveform. Which properties the signal should have, please check out the attached OneNote file "Forum_1_part 3" (in the zip file)
there is a detailed description.
Would be nice if anybody can help me there.
Thank you!
Best regards
Chris
Attachments:
Forum_1_part 3.zip ‏2297 KB
I_Stand Project v5.vi ‏71 KB

Quick and...
Maybe it gives you an idea, so have fun
Christian

How do I use adaptive LMS filter with waveforms?

In the attached image file and VI, I am reading a .lvm file which contains abdominal ECG (AECG). AECG contains both maternal and fetal ECGs i.e. MECG and FECG respectively. I'm trying to input AECG and MECG to the LMS FIR filter so that I can get FECG as the error signal, e(n). In my VI, e(n) is coming out as a 16-Bit Double but I want it to come out as a waveform. How do I go about it?
NOTE: Since this forum doesn't allow uploading .lvm files, I have share in Google Drive here. You can use this file to run the attached VI.
Attachments:
AECG_NI.vi ‏38 KB

Step 1. Dont use the express VI. It makes assumptions about the data that don't appear to be valid.
Mike...
PS: The lvm is just a text file. Change the file extension to txt and upload away.
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Is there a better way to re-render audio waveforms (after changing media files)?

I'm shooting documentary footage on RED cameras at 6K resolution. That generates a large amount of media. The RDC format records R3D media files in 4GB chunks, which is actually relatively short compared to my hours-long media captures. I've discovered that it's very handy to simply delete the R3D files from the RDC folder in cases where nothing is actually happening at that moment. Since each R3D media file is timecode stamped, these actually stay in sync with my master audio track. And Premiere Pro sensibly places gray diagonal bars where the underlying R3D files are missing. All good.
What's not good is that Premiere Pro confuses itself about the starting point of the PEK files. Instead of simply greying out the part of the audio waveforms that are missing due to the missing media, it shifts the *waveform* to start at the location of the first R3D clip that is present, which is wrong. If I clean the cache, quit the project, restart the project, and let it rebuild the cache, the audio waveform is correctly drawn.
An ideal fix for this problem would be for Premiere Pro to recognize that if it re-links media it should re-render the audio PEK file. An OK work-around would be to make it easy to just re-render the PEK file for a given media clip.

A slightly quicker way to do what you described for an images is to select 'Duplicate version' instead of 'New version from Master' and then 'Remove adjustments' from version 1. This will leave you with the first version as the 'before' and the second version as the 'after' without having to use L&S.
If you need to do this for 108 images, it might be quicker to do the following:
Export Masters for all 108 images.
Reimport these into a new project (called 'before', for example)
You will then have a new project with the 'before' images and your original project with the 'after' images. You could then build an album to group all of these together. When you've finished with the 'before' & 'after' images (build your web gallery or emailed them or whatever), simply delete the 'before' project.
Regards,
Steve
Message was edited by: Stephen Ives

Waveform Anzeige

Similar Messages

Maybe you are looking for