Simultaneous acquisition of accelerometer and an encoder measurements of a rotating machinery.

I want to do a simultaneous acquisition of accelerometer and an encoder measurements of a rotating machinery.
So which National Instruments data acquisition product must be chose to do this capture.
Solved!
Go to Solution.

1st: check the voltage ranges of your encoders and accelerometers
2nd: do your accelerometers need IEPE power?
Ideas: (for accelerometers needing power and encoders with > +/-10V range)
NI USB 4432
NI USB 9232
NI CompactDAQ with 9232
other options in C series include 9234, 9229, 9215, etc.
In PXI, there is the 449x series of PXI express cards.
Do you have analysis and visualization requirements?
Take a look at these manuals:
http://digital.ni.com/manuals.nsf/websearch/5D343672A7367E6286257B9D00527B30
http://zone.ni.com/reference/en-XX/help/372416C-01/
Regards,
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

Similar Messages

Is there an existing balance and vibration monitor program for LabView for rotating machinery?

I want to test generators for ballance and vibration, and shaft critical frequency. The data is to be collected automatically and reports generated preferably with LabView. Can I buy a written program as a starting point? I know of the Sound and Vibration Toolkit, and am willing to buy it, but still prefer to start with a verified package. Currently we are using a Bently-Nevada standalone system that is limited in its capability. We are installing a new data collection system so have a lot of flexability.

Good Morning,
Yes, we can put together a written program for collecting balance and vibration data for generators. There is a new tool to be announced April 30th, that goes beyond the sound and vibration toolset for machinery monitoring. We can use LabVIEW and our Dynamic Signal Acquisition hardware to capture accelerometer data, encoder/keyphasor data, and other rotational parameters. We can provide an off-line analysis set of software as well, or report the data to any existing Computer Machine Maintenance Software (CMMS) you need us to work with.
I'd be happy to discuss this with you further.
Sincerely,
Preston Johnson
Business Development Manager
Industrial Applications
National Instruments
512-683-5444
[email protected]
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

I need an accelerometer data anaylsis vi that will give displacement from transisent data.

Sample rate = 50 kS/s
no filter
event duration 20-40 msec
700 g's max
I want it to run inside of labview.
Any suggestion?

Curt,
I happened to be interested in this problem for some time to monitor
vibrations in rotating machinery with order track and a mix of eddy
probes, velocity sensors and..accelerometers. In order to compare
vibrations from eddy probes and those of seismic sensors, I had to
doubly integrate the acc responses--> your wish .
.. I guess you have only one channel and fairly fast card and not doing
it continuously in real-time but as one-shot transient analysis possibly
with pretriggering.
You have to doubly integrate the accelerometer signal with some AC
filtering and acquire the response above 100 KHz (2 X bandwidth of your
acc). That is easy to do: use integration vi from the library with an AC
filter (IIR takes much less time but FIR have a linear phase lag and do
n
ot distort the time signal but simply shifts it.
If you use 2 channels, beware that the integration vi is not reentrant,
but I guess it is no issue for you since you assume that the
acceleration is quasi zero before the shock transient. Of course you are
bound to miss the low-frequency contents of your acc response anfd thus
may miss some of the real displacement. That's physics and has nothing
to do either Labview or data processing.
If you are busy with Labview and S&V problems, contact me at
[email protected] after Tuesday.
Gérard
38curt wrote:
> Sample rate = 50 kS/s
> no filter
> event duration 20-40 msec
> 700 g's max
> I want it to run inside of labview.
> Any suggestion?

Problems installing Bridge and Media Encoder in CS6

I recently installed Creative Suite CS6 Design & Web Premium. I had previously installed the CS5 version and had not un-installed it. Everything except Acrobat appeared to install correctly. When I opened Photoshop CS6 (64-bit) I noticed that it used the CS5 version Bridge. I went into Bridge and unchecked the open at start box, closed Bridge and Photoshop and re-opened Photoshop CS6 (64-bit). When I tried to lunch Bridge from Photoshop the following message appeared in the Desktop> panel : Waiting for Bridge CS6..." Bridge CS6 did not appear despite waiting for several minutes. I then pressed the Start button and went into the Programs listing. Under the Adobe CS6 group I found all of the applications (other than Acrobat) but Bridge CS6 (64-bit), Bridge CS6, and Media Encoder each had generic icons rather than the expected relevant Adobe icons. I tried to load each of the three by clicking on the icon. In each instance the following message appeared:
The version of this file is not compatible with the version of Windows you are running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program and then contact the software publisher.
My system is a Gateway FX6802. I am running Windows 7 Home Premium version 6.1.7601, Service Pack 1, Build 7601. The system has 9 GB of memory. I ran CS5 on the system and did not experience any difficulty with Bridge.

Thanks. Being the impatient sort (inspite of the problems that can create) I only did a partial uninstall with the cleaner tool, taking out the three items that were not working. Initially that seemed not to work. As I had other non-Adobe projects to take care of I put it out of mind. I even let an updatee package do its wonders. Today I used Photoshop for a quick project. I clicked on the Launch Bridge button and lo and behold the proper icon showed up and Bridge loaded. After finishing my project I closed down Photoshop and Bridge and then went through updating once more. The other problem I was having was with Acrobat. I finally traced the problem to a bad installation of Acrobat 9 at the CS4 level. (Shows you how much I use Acrobat.) I used the cleaner tool to clean up the remnants of CS4. After that Acrobat X installed quite nicely. At this point everything seems to be working as it should. Thanks for your help.

Premiere pro and media encoder CC problem

Hi guys,
I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
This is the error report, please help:
Process:
Adobe Media Encoder CC [946]
Path:
/Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:
com.adobe.ame.application
Version:
7.2.0.43 (7.2.0)
Code Type:
X86-64 (Native)
Parent Process: launchd [136]
User ID:
501
Date/Time:
2014-02-10 08:44:28.001 +0100
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
1264 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 24 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
7E711766-8C55-00D3-811F-852F73421407
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9483c212 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff8d74ab24 pthread_kill + 90
2   libsystem_c.dylib
0x00007fff8d78ef61 abort + 143
3   libc++abi.dylib
0x00007fff96ff79eb abort_message + 257
4   libc++abi.dylib
0x00007fff96ff539a default_terminate() + 28
5   libobjc.A.dylib
0x00007fff8f49d887 _objc_terminate() + 111
6   libc++abi.dylib
0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib
0x00007fff96ff5424 std::terminate() + 16
8   libc++abi.dylib
0x00007fff96ff658b __cxa_throw + 111
9   com.adobe.dvacore.framework
0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework
0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework
0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 com.adobe.ame.application
0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
13 com.adobe.ame.application
0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework
0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 com.adobe.ame.application
0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
16 com.adobe.ame.application
0x0000000100056a38 main + 424
17 com.adobe.ame.application
0x0000000100003f74 start + 52
==========================
Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

Hi mawe81,
Thanks for posting on Adobe forums,
Please follow this document http://adobe.ly/1f2EHCg
and let us know if this fix your issue or not.
Regards,
Sandeep

Does anyone know if/how to rotate a video clip? I shot it so that it is sideways on my computer screen and I cant figure out how to rotate it.

Does anyone know if/how to rotate a video clip in iphoto? I shot it so that it plays sideways on my computer and I cannot figure out how to rotate it. Thanks.

You can't do that in iPhoto. You'll need a video editor like iMovie for the job.
Regards
TD

Saving image in windows 8.1 using stream and bitmap encoder id

Hi
var renderTargetBitmap = new RenderTargetBitmap();
await renderTargetBitmap.Render(myElementTree);
var pixels = await renderTargetBitmap.GetPixelsAsync();
var picker = new FileSavePicker();
// Picker setup
var file = await picker.PickSaveFileAsync();
// File validation
using (var stream = await file.OpenAsync(FileAccessMode.ReadWrite))
var encoder = await
BitmapEncoder.CreateAsync(BitmapEncoder.BmpEncoderId, stream);
encoder.SetPixelData(BitmapPixelFormat.Rgba8, 100, 0, 96, 96,
await renderTargetBitmap.GetPixelsAsync());
await encoder.FlushAsync();
I have already used the code snippet. Could you please tell me how to save UIElement tree by having the stream and bitmap encoder id as input?
Thanks
Satheesh

Here you go. Set up the file picker and call our CaptureElementToFile function. In this case it's passing the page to capture the whole screen:
FileSavePicker picker = new FileSavePicker();
picker.SuggestedStartLocation = PickerLocationId.PicturesLibrary;
picker.SuggestedFileName = "capture.bmp";
picker.FileTypeChoices.Add("Bitmap File",new List<string>() { ".bmp" });
StorageFile file = await picker.PickSaveFileAsync();
CaptureElementToFile(this, file);
And here's CaptureElementToFile. The BitmapEncoder needs to know information about the size and shape of the pixel buffer and it needs to have the pixels as an Array. If you want to encode to a different size you can include a BitmapTransform.
async void CaptureElementToFile(UIElement element, StorageFile file)
RenderTargetBitmap renderTargetBitmap = new RenderTargetBitmap();
await renderTargetBitmap.RenderAsync(element);
IBuffer pixelBuffer = await renderTargetBitmap.GetPixelsAsync();
DisplayInformation dispInfo = DisplayInformation.GetForCurrentView();
using (var stream = await file.OpenAsync(FileAccessMode.ReadWrite))
var encoder = await BitmapEncoder.CreateAsync(BitmapEncoder.BmpEncoderId, stream);
encoder.SetPixelData(BitmapPixelFormat.Rgba8, BitmapAlphaMode.Straight,
(uint)renderTargetBitmap.PixelWidth,
(uint)renderTargetBitmap.PixelHeight,
dispInfo.LogicalDpi,dispInfo.LogicalDpi,
pixelBuffer.ToArray());
await encoder.FlushAsync();
--Rob

Using Premiere CC and Media Encoder CC at the same time

Is this possible? Doesn't seem to be. Media Encoder bails on every job as soon as you try to render anything in Premiere. I guess they don't play nice together, which is surprising. I was hoping that Media Encoder would pause and wait for Premiere to finish a render. Instead it dies on every render job, creating 0 size video files... while making a sheep bleating sound.
Is this a GPU issue? I have 2 nVidia cards, a 770GTX and 560GTX. (Windows 8.1, 16gb RAM, 3770k CPU)

As soon as I initiate a render in Premiere, Media Encoder bleats, and all subsequent render jobs bleat and produce 0 size video output files... even if I quit the Premiere render before Media Encoder reaches some of those render jobs.
I suspect this is a GPU sharing issue.... but can't be certain.
What do you mean by new install? Did I install it (AME or Premiere) recently? No. I've had Creative Cloud on my machine for almost a year, and both Premiere and Media Encoder have been updated periodically.
To my knowledge they have never worked together, but I only started using the queue feature within Premiere recently, so I haven't used AME until recently.

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

Premiere and Media Encoder - h264 corrupted encode

Hello all
I'm writing here since I simply cannot find a solution to my problem, recently out of a sudden my adobe premiere and Media encoder have been giving me corrupt h264 encodes, the files apparently encode but adobe does not put them in a container. The .m4v file is unplayable and the same goes for the audio file; here is a sample from MediaInfo:
No matter what sequence or project I try to encode with h264 this happens while I can encode to any other extension/codec with no problems. While using the same project file and the same source files on another computer the encodes finishes without a problem. Even a simple timelapse with just JPEG pictures on the timeline results in this problem. I have no idea what to do but I simply cannot encode with anything else so any help is appreciated (P.S. the 4k resolution here is a timelapse, most encodes I try to do are 1080p @ 25fps, since most people bump at this resolution 1st)
I'm running Adobe Premiere Pro CS6 (6.0.5) updated to the latest on Windows 7 64bit.

Hello all
I'm writing here since I simply cannot find a solution to my problem, recently out of a sudden my adobe premiere and Media encoder have been giving me corrupt h264 encodes, the files apparently encode but adobe does not put them in a container. The .m4v file is unplayable and the same goes for the audio file; here is a sample from MediaInfo:
No matter what sequence or project I try to encode with h264 this happens while I can encode to any other extension/codec with no problems. While using the same project file and the same source files on another computer the encodes finishes without a problem. Even a simple timelapse with just JPEG pictures on the timeline results in this problem. I have no idea what to do but I simply cannot encode with anything else so any help is appreciated (P.S. the 4k resolution here is a timelapse, most encodes I try to do are 1080p @ 25fps, since most people bump at this resolution 1st)
I'm running Adobe Premiere Pro CS6 (6.0.5) updated to the latest on Windows 7 64bit.

Upgraded to CC 2014 and Media Encoder doesn't work now.

Using a mac with mavericks, all updated. Upgraded to Premiere Pro CC 2014 and Media Encoder CC 2014. But when I want to launch it... it won't open.
Help?

JUST FOR MAC USERS - Some 10.9.3 links
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
-Mac 10.9.3 and CS6 https://forums.adobe.com/thread/1480238

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov Prores 422HQ 1080P                         22 Minutes
to .mov H.264 1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov Prores 422HQ 1080P                             13 Minutes
to .mov H.264 1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Latest Premiere and Media encoder CC update shuts down

Latest Premiere and Media encoder CC update shuts down when you load saved file or try to export to media encoder.
I tried restarting after update, next is to revert to previous version.

Every time I've try to export from Premiere Media Encoder gives me this error message that says: Installation error - please ensure this product have been installed properly.
I can't find a way to only reinstall media encoder from CC
It was working fine before the last Premeire update.

Adobe Premiere and Media Encoder crash on Export

Hi
I Run Premiere CC and media encoder on a 2011 27in iMac with 12GB RAM. Until recently everything exported fine. But now when I either do an export from within Premiere or queue via Media Encoder it crashes halfway through. I've tried reinstalling both to no avail. Any idea to why this could be happening and how can I fix it? I'm running Yosemite.
Cheers

Hi
I Run Premiere CC and media encoder on a 2011 27in iMac with 12GB RAM. Until recently everything exported fine. But now when I either do an export from within Premiere or queue via Media Encoder it crashes halfway through. I've tried reinstalling both to no avail. Any idea to why this could be happening and how can I fix it? I'm running Yosemite.
Cheers

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

Simultaneo​us acquisitio​n of accelerome​ter and an encoder measuremen​ts of a rotating machinery.

Similar Messages

Maybe you are looking for

Simultaneous acquisition of accelerometer and an encoder measurements of a rotating machinery.