Messages posted by ilander001

Thanks Shadowman for your reply. I looked up duffuse interreflection, found examples and description, and I do not believe that is what it is.

I am posting examples. The best one is the tree leaves. The camera has a slow shutter speed so a drop of rain shows up as a column. But the point I am trying to make is the tree leaves directly behind this rain drop are considerably brighter or better illuminated than the rest of the leaves on the same tree.

The rain drop is just a few inches from the camera while the tree is about 30 feet away. For some reason the rain drop is mangifying or intensifying the camera's flash.

To me it's "backlighting" because what is in back of the raindrop is lit. Or the term highlight could be used as when a person uses a flourescent magic marker to highlight text in a book. But I believe both of these terms are inappropriate.

I'm guessing there must be a term for this.

I'm creating a documentary and I am searching for the correct term to use to describe a lighting effect. I'm thinking highlight or backlight, but when I look them up they have different meanings than what is actually happening.

Here's the situation: When a translucent object is in front of the camera, much of what is behind it can be seen by the camera. An example would be a raindrop falling close to the lens. The objects behind the raindrop may be distorted or blurred, but nonetheless if it is a tree, it is still obviously recognizable as a tree.

In a nighttime situation when a flash is used, the part of the object behind the raindrop is brighter than the rest of it. In essence, the combination of the raindrop and the flash are highlighting the small portion of the tree that is directly behind the raindrop.

So my question is: What is the correct term to use when the scenery directly behind a translucent object has brighter illumination than the surrounding scenery.

Actually AVC H.264 are the first ones I tried after reading your advice. I'll try to shorten the story, but one of my cameras output file is realy odd. Windows 7 reads it's properties as an avi file. PD13 reads the file as being AVC H.264. The frameshots program will not process it and break it down into individual frame stills, but it will process avi files from other camera brands. Windows and the frameshots say this particular video is exactly 58 seconds and 0 milliseconds long. PD13 says it's 57.28 seconds long. All files from this brand of camera are like this, something about them is non-standard or corrupt.

Now this frameshots program will process this camera brands file if I run it through Movie Maker 2.6 or the newer Windows or PD13 as an avi file, however the framerate is 29.97 which throws the timing off for my project.

What I confirmed last night was that the properties read by PD13 is the correct reading for this file. This camera does output AVC H.264 files. So I had to try something else, and XAVC S worked, it gave me 30 fps and the frameshots program did it's job.

I'm working with wildlife night infrared cameras. Another oddity many of them do when creating a video is to make a frame, repeat this frame 1 or two times, then create a new frame, repeat it, and on and on. In other words, a 30 fps video will only have 10 new frames per second while having 20 repeats. In essence they are only 10 fps videos. The jerkyness of objects motion is sometimes quite obvious. This situation gives me headaches in the timing department.

If you're not bored or LMAO I'll continue. What I'm doing is clocking objects in motion to find their speed. An object passes by two known points on a surveyed plot where I know the exact distance, then I can caclulate it's speed by noting the exact frames it passes by both points and subtract the first frame milliseconds from the second frame and calculate the speed. Now I often use two or more cameras, which means their timeing has got to be syncronized down to the frame. It's an absolute nightmare trying to do this with an oddball 29.97 fps, but can be done, but creates timing errors.

So to boil it all down, what I'm using PD13 to do is to correct the corruptness of a certain brand of camera files so another program will accept it and so I can use those files to time objects in motion.

Later on I will use PD13 to create a documentary of my project.

Again, your advice really saved my day.

tomasc, needless to say, I'm new to this and I'm lost with your advice. Sorry.

optodata, OK, I understood your advice. I experimented with various output formats and found XAVC S to match what you are discussing as well as put out acceptable quality. I created a custom profile. At the video tab of this custom profile I selected "Frame Rate" of "30". I double checked this setting by going to "Details" for this custom profile and it said the frame rate was 30. Also, under Preferences, the frame rate was set to 30 fps NTSC and the drop frame time code was set to "no".

I ran it and now PD13 says the properties of the new output file is 30 fps.

I ran this file through a program where whole number fps is required in order to break it down into frameshot png files that are consistent with the orginal file and it worked like it should.

Thanks, I'll get back if there is a problem, but I don't think there will be.

What I find confusing is this will not work for avi files, which I guess really does not matter since xavc s is so much better quality. I've had a tech support ticket waiting for a response for a few days now. If they answer maybe I can find out why.

Again, thanks.

Carl, Thank you for your reply and the png file that shows exactly how to set the preferences.

However that is exactly what I have tried. I have had the frame rate set to "30 FPS (NTSC)" and the "Use drop frame timecode:" set to "No".

The properties of the avi file fresh off the camera show it to be 30 fps. After being processed through PD13 it shows 29 fps.

I also get the "Timeline Frame Rate Conflict" message stating what I've added is 30 fps which does not match the General preferences setting of 29.97 fps.

For some reason it is not working for me.

My system is Win7 64 bit. I had the computer built around the specs a CyberLink sales guy said was needed to get optimum performance out of PD13.

I have a project that requires a frame rate of exactly 30 fps. When I process a film clip through PD13 the end product is 29.97 fps, even though I have the 30 fps option selected.

I have attempted to find the solution in the manual and online. My current understanding is that changing the drop frame timecode setting will get exact whole number frame rates.

Here's an example of what I've tried. A camera put out an exact 58 second video at 30 frames per second. When processed through PD13 with the "Use drop frame timecode" option set for "yes" or "no" I get the same results either way with the output product properties as being 29 fps and a length of 57 seconds.

File sizes are also identical.

Can anyone please tell me what I'm doing wrong, or maybe it's not possible for PD13 to give exact frame rates??

Thanks.