Where is De-Interlace in FCX?

Can't find de-interlace in FCX. Most of my footage is HDV and I need to DI most of it. Help.

If you have Motion 5 you can make your own de-interlace effect and publish that to use with FCP X.
If you don't have Motion the quick and dirty way is to go to Inspector (cmd-4) and select the Info tab. On the bottom left corner of the Inspector select the Settings view. There you find a Field Dominance Override selector, which you can use to de-interlace clips.

Similar Messages

Interlacing problems on graphics

I have a 1920x1080i ProRes project where I get interlacing lines on the graphics. I have screencapture video generated with iShowU and stills with text from Photoshop. Both with lines after export from FCP. Is there any way to avoid this?

In FCP, change the field dominance to None in Sequence > Settings.
Deinterlacing throws away half of your vertical resolution.
Note that a computer monitor cannot display interlaced video formats correctly. They are intended to be displayed on televisions. Depending on where the finished project is intended to be seen it might in your interest to keep the interlaced video as it is.

Loss of quality from iMovie Project to Burned DVD

Hello,
I have read some strings regarding this subject but I'm still left with questions.
I have created a photo collage set to music, in iMovie. It's 12 minutes long, and when I play it in iMovie on my computer, it looks great. All the photos are crystal clear, rich with color, and vibrant in all the right places.
I played the file in Quicktime 10.0 and it looks great.
The info in the Quicktime Inspector is
Format: H.264, 1920x1080, Millions AAC, 2 Channels, 44100 Hz
FPS: 29.97
Data Rate: 20.23 Mbit/s
Current Size: 1549x871
I burned this to a DVD using Toast Titanium (because ever since my iLife '11 upgrade my iDVD hasn't worked past startup. I can't get it to do anything at all.)
Somewhere between the Quicktime movie and the Burned DVD, the movie loses a significant amount of quality. It seems all the colors are washed out. I can see my edits on some of the photos... it looks like crap. To me it looks awful, to others it may not look as bad, but I know the difference. It looks awful.
Can someone please tell me why this is happening and how I can prevent it? All while still using iMovie through this whole process, and Toast for burning?
Thank you so much
YahYah

Hi Ziatron,
The quality workaround I proposed assumes the person starts with a progressive source material. The original poster did as I don't see how you would import true progressive source media and get interlaced artifacts at the end, especially for stills! We are not in the days of the Sony Mavica you know. What you are doing is importing interlaced video and processing it in interlace with a progressive scan workflow. The combing artifacts you saw is from the consumer algorithm that is inherent in iMovie 11. I know iMovie 6HD and FCE or FCP have better de-interlacing algorithms. You can by pass iMovie 11's weakness by treating the interlaced video through a commercial/high end de-interlace software and get better results.
As long as you are working with a progressive source media, then you are not bound by de-interlacing artifacts unless your movie was shot in it. Suffice to say, best de-interlace programs cost money and a lot of computing power. That is not something the majority of computer owners use iMovie possess. I see you have a high end Mac Pro. I also have a high end Quad PC with a high end Nvidia graphics card to utilize its hundreds of CUDA cores for vReveal to eat on. But that's not what the general public of Mac or PC owners have nor what the general public buy during Black Friday or Boxing Day in Canada either. High end Macs or high end Quad PCs go with high end video editing software where the de-interlacing and the encoding and decoding algorithms are much better than the consumer versions.
This is OBVIOUS! Better algorithms will simply slow down any mid-end Macs to mid-end PCs to a low teeny 1-5 fps processing a video clip in H.264 in very very high quality and multiple passes. This is not acceptable to the general public. Which is why, you are also seeing noise artifacts in the workflow too, because you need to first de-interlace the source media and then re-encode to H.264 which obviously adds artifacts to the source before you can use it with iMovie 11, so clearly iMovie 6HD has a clear advantage. This carries over to the final workflow. But most AVCHD material out there is compressed too!
Consumers need to be aware that there is a difference between consumer grade software and commercial grade software. Also, commercial grade software require a hefty computer to do its job reasonably well! People need to understand that just because you own a nice $900 to $1000 camcorder does not mean that your mid-end Mac can deal with it.
Getting quality is so easy. Just spend lots and lots of money on hardware to shave off 15mins to a few hours of video encoding to digital video processing, but at what end because it will never end!
I've seen a few footages floating around on Youtube that looks really good made with iMovie 11. Just keep in mind that there are always tradeoffs for reasonable rendering time vs cost of your computer package.
Message was edited by: Coolmax

Converting 24p footage to 29.97

yes, I can convert it easily by placing it in a 29.97 timeline and rendering, but there is a repeat frame every five frames.
but from the help menu, it seems there's a way to get compressor to do this without repeating the frame. I can't seem to find the menu to do it.
i know about the Nattress conversion tool, but I have the feeling I already have the tools to do it.
Thanks
Eric

Well, there's no way around it really. The most common way to do pulldown is to repeat a frame, just like you are seeing. How were you hoping that it would be done? Frame interpolation?
There is a slightly more advanced way where you can interlace the fields from the two adjacent frames into each other, but you still have to use the existing frame data. I don't know how to interlace the fields in FCS though.

MPEG-2 have to be deinterlaced?

I recently exported a project from FCP to an MPEG-2 using Compressor, looking at the file there are lines going across on certain frames because I didn't deinterlace the footage.
Is this going to look alright once I burn it to DVD?
And if it's not then does that mean I have to always deinterlace my footage when exporting to MPEG-2?
Thanks

Yes, I agree. There's no need to interlace, it should look fine on the computer screen. This is what I have just done, however I would like to know whether the same is true for outputting to a video projector where the image will be exploded quite a lot. I will know the results tomorrow so I'll post them here. My project is a very complex video animation and involves many diagonal lines of sharp contrast. (I can hear the groans!) I noticed something with my finished DVD. Well two things. When I imported the m2v file back into compressor it read it as progressive even though I hadn't as you say deinterlaced. When pausing the DVD on the computer (apple DVD player) I noticed that the image was very nice and clean with just a tiny amount of blur which looked okay, but on restarting the video I could see some artifacts (in comparison to the still image) like fuzziness where the two interlacing fields would have been, in certain parts of the image, and some subtle spidery-like arcs. I wonder if there's any way to get rid of these without compromising the image?

Where is the De-interlace in Adobe Media Encoder CS4?

How do you de-interlace video Using the Adobe Media Encoder in CS4? In CS3 there was a de-interlace check box in the video Output Tab but there is not one in CS4?
I am using 720x486 SD interlaced 29.97fps footage editing it and exporting the final product to flash flv.
Thank you!
Joe

Deinterlacing is now automatically applied if the source and the destination differ as far as their field order is concerned. In other words:
Interlaced source --> interlaced destination = no deinterlacing
Progressive source --> progressive destination = no deinterlacing
Interlaced source --> progressive destination = automatic deinterlacing
The Field Order option in the output setting determines whether deinterlacing is applied. Be sure to check the "Use Maximum Render Quality" option in the fly-out menu; it will take 4-5 times longer to render, but with better results.

Where is the De-interlace feature in the new update for Compressor?

Hi all, I use compressor for editing weddings and I ALWAYS have to use the de-interlace feature because of my settings. I can't seem to find it and I am worried because I have to give my couple their couple in 2 days! Please help!

Hi there.
There are a couple of ways.
1) In the Inspector. set fold dominance to progressive.
Or:
2) Choose any of the H.264 output settings; those will automatically de-interlace.
Russ

Where is "Feather" in FCX?

You know in FinalCut7 where you go to crop and feather was one of the options at the bottom… Where is feather in Final Cut 10?

Use one of the masks.
Russ

HDV 1080i to Standard def DVD "Ken Stone" method- interlace problems, help!

Greetings,
I am on a tight deadline to produce a standard def DVD for an art exhibit, from HDV material that was imported and edited natively in FCP 7 as 1080i. I used the "Ken Stone" method of exporting the 10 minute sequence using QT conversion, as a pro res 422 HQ quicktime movie, then I took it into compressor 3.5 to make a Mpeg-2 file for a standard def DVD.
The problem is that the video that came out of compressor, when simulated in DVD SP 3.5 (and also when burned on DVD) has weird "interlaced" looking edges whenever there is movement in the video. It is a figure against a black background, and whenever the figure moves back and forth against the black background, the edges of the figure show interlaced-looking lines. The rest of the video where there is slow movement looks fine. BTW, motion was set to "Best" in compressor.
What am I doing wrong? was there something not mentioned in Stone's walk-thru, having to do with de-interlacing, or something I have missed? Is there a better way to produce a standard def DVD from HDV 1080i material?
Thank you so much for your help. I am down to the wire on this one...
AKJ

exporting the 10 minute sequence using QT conversion, as a pro res 422 HQ quicktime movie...
You are adding an unneeded compression cycle for a start. Export with QuickTime Conversion always recompresses your footage, even when you use the same settings as your Timeline.
Export to QuickTime with Current Settings, Self Contained will give you a Master file that is identical to what you edited.
weird "interlaced" looking edges whenever there is movement in the video...
If your source material is interlaced it will look odd on a computer monitor. It will display correctly on a TV set.
having to do with de-interlacing, or something I have missed?
Deinterlacing will throw away half of the vertical resolution. Bye bye HD. No good can come of that, right?
What is your intended delivery format? Does the method that you are currently using to view the material compare with how the end product will be seen?

AVCHD interlaced sequence export to progressive (h.264) with Premiere Pro CS5.

Hi !
I have searched everywhere on the web (and this forum) for an appropriate answer.
Here is the problem :
I have used AVCHD (upperfields first / square pixels / 1080i30(i60)) footages to make a movie.
The primary sequence settings are correct :
AVCHD 1080i30(i60) square pixels
The files play fine in Premiere, and the montage was flawless in high 1080i quality.
I have exported 5 seconds of the movie into raw "AVI Microsoft uncompressed" files, so I can import them in "After Effects" to had some texts and graphics. When done, I re-imported them into the Premiere's sequence. (same AVI uncompressed format).
Playback works fine. The movie looks great and flawless, and has no interlacing artifact.
HOWEVER : When I want to export this sequence into a MPEG H.264 progressive final file, there is some gerkiness on the parts where the "AVI" files were added.
It looks as if it had been interlaced, when the rest of the movie looks ok.
When I'm in the exporting window, I can see the "Source" and "Output" display.
"Source" looks fine and "Output" looks gerky.
I have tried to create a new progressive sequence, into which I imported my main AVCHD sequence (with some progressive footages in it). To no avail !... I had heard that this could work but it's not.
I looked in the "Output" window while trying all the possible codec formats (and field orders), to no avail.
UNTIL !! I checked the key : "Make Sequence settings match" that is on top of the exporting window.
The image in the "Output" window became clear. However, all the settings below the checked key were now locked.
Producing a file with this format (it seems it is a MPEG2 / upperfield first, the same format that is used for Preview files) can render a file that has all it's field and image quality aligned.
By unchecking the "Make sequence match" key, I was able to create my own settings of MPEG2 "upperfield" that still interpretes the movie correctly.
But it's not the MPEG H.264 progressive file that I want. I have to re-render it with a third party software to get a H.264(p) out of a MPEG2(i).
Is there something I should check or try to be able to export my movie in H.264 directly ?
Thank you!

FAQ: What information should I provide when asking a question on this forum?

Mac-mini "detect displays" where is the individual model's DDC info stored?

I have a dilemna- I just bought a new 20" NEC LCD screen that has all sorts of bells and whistles. It's 1600 x 1050 native, and has DVI, analog VGA, YUV, compostie, and RF inputs. It is supposed to have a scalar that supports a multitude of resolutions including 1920 x 1080i.
I bought it for a system of which has (2) mini-macs through a DVI KVM. I had one mini-mac successfully read the DDC info from the montior, and it provides a wide range of supported resolutions (including 1600 x 1050). All resolutions listed are progressive (no interlaced options)
When I switched my KVM to the 2nd mini-mac it was stuck in 1024 x 768, and that was the highest res that the display preferences gave me (probably because that's what it read off the DDC of the KVM switch?). When I hit the "detect displays" button, it proceeded to update the list of supported resolutions, but a very bizzarre thing happened: It did the opposite of the first mini-mac, and only listed "interlaced" video resolutions (with the exception of 1280 x 720p and 640 x 480p). The list was all 'broadcast-style" resolutions.
The profile for this montior on this mini-mac is now stuck in this mode, and I cannot get the desired 1600 x 1050 resolution that is native to the monitor. I've tried everything I could think of including ditching plists, clearing the PRAM, tricking the mini-mac, etc....
It's almost as if a mini-mac stores a registry of the monitor's DDC information onto the video card 'permanently' the first time, and never allows to re-read the DDC info again???
Does anyone know how to clear this registry?
The other clue to this whole thing is that the monitor has an option where you can set the DVI IN to either "DVI-PC" or "DVI-HD". The fussy mini-mac displays nothing in "DVI-PC" mode, and the behaving mini-mac displays in both modes. It's possible that the monitor was in "DVI-HD" when I hit the "detect displays" button on the fussy mini-mac.
Any help would be greatly appreciated.

Wow, I wish I had your set up to play with. I could probably learn a lot from it
When DDC is read by the Mac, and when users make resolution settings based on it, the resultant settings are stored in a file called com.apple.windowserver.plist. There is one such file in /Library/Preferences but there may also be occurances of it for each user account on machines set up for multiple users AFAIK. They are plain text files so you can actually read them with TextEdit or other text editors.
The simplest thing to do might be to copy the file from the mini giving the desired behavior and use it to replace the file on the mini with the bad behavior. I don't think there is any machine specific info in the file, so I believe the file should be portable in this manner. On the other hand, this may not work because when you restart the misbehaving mini it might regenerate a "bad" windowserver.plist file again and replace the one you just copied over. Although I don't think that will be the case. Can't hurt to try. You might want to keep the older pref file around and rename it to "preferences.old". There is a procedure outlined here that is similar although it is based on doing everyting from starting into console mode:
http://docs.info.apple.com/article.html?artnum=106464
As for why one mini is reading EDID one way and the other reads altogether something else, that's a really good question and one that I hope you are able to track down the answer to and report your findings back here. It could provide a lot of insight into other types of problems people have reported on this forum. Perhaps it relates to the DVI-PC or DVI-HD setting you refered to, but I have never known any other display that actively changed its EDID. EDID is always fixed I thought. Good luck and let us know how things turn out.

Xorg.conf Where are you?

Hi,
I installed Arch (third time) and Iam not able to find xorg,conf. I installed Arch from full cd. In /etc/X11/ are these directories only: fs rstart sessions twm xdm xinit xsm
Does anybody know where I can find the X config (using XORG7)

Here is: (located in /etc/X11/xorg.conf - created by hwd -x)
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" ""
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "vesa"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x800" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1280x800" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection

PSE 11 de-interlace

How can you de-interlace a photo from video in PSE11 it was always possible in all versions until now (tried copying pluggin from PSE 10 but did not work)

First off thank you for replying.
I am using Windows 8 Pro 32bit.
I concur with your adobe comment, I am in fact wondering why I updated.
I copied the file "de-interlace EL.8bf" into the "plug-ins folder" which is, by the way empty, also tried "Required\Plug-Ins\Filters" which is where I see they are now
The error I got on both ocassions was "The proceedure entry point HandleWindowFont could not be located in thr DLL" PSE 11 opened but no filter was found in any menu.
I have downloaded and tried the Smart de-interlacer as you suggested thanks and it works for me, thanks.
Dennis

Why does progressive footage look interlace?

I shot using 30p with a panisonic dvx100, at 120 shutter speed, with auto irus. While importing, the footage looked great (imported using Adobe pro). Using Adobe pro. the footage looks interlace. Why and how do I fix this problem. I heard that de-interlace reduces the quality but the fact is I should'nt have to, since the footage was shot in progressive. If you know the answer I can really use you're help.

Which version of the software are you using: CS3 or earlier, or CS4? No version includes a pre-built preset for working with DV 30p footage. In CS3 and earlier, you have to set up a custom project, whereas in CS4, you setup a custom sequence. In either case, when you create a new project (<CS3) or sequence (CS4), click the General tab, and change the Field dropdown to "No Fields (Progressive Scan)". You don't need to change anything else, unless, for example, you're working with widescreen footage--change those parameters if necessary. When you're done, save this as a new DV 30p preset.
Now, you may also need to interpret your 30p footage as progressive--I'm not quite sure how 30p capture works in PPro. Select your clips in the bin, and go to File > Interpret Footage. From the pop-up that appears, under Field Order, select Conform To: No Field (Progressive Scan). As I said, I'm not sure if Premiere knows on capture how to interpret 30p footage or not, so this may not be necessary.

24p DVX footage Lower Even field dominance interlacing?

I've captured DVX 24p (not 24pA) footage. When I check Item properties for a clip FCP shows Lower (Even) under Field Dominance? Shouldn't it be Progressive or is it because 24p was captured using a 29.97 timeline in FCP as opposed to 24pA.
I am seeing horizontal lines during motion when played back on DVD? Is that interlacing? Where did I go wrong.

Look, you really need to wrap your head around 24p, 30p, 24pA and 30i.
Interlace is not an ugly issue. It is a benefit. Interlacing normal on broadcast television. Your TV scans down and back up for each frame... alternating lines. When you shoot 24p on the DVX it puts it to tape where for every 3 frames of progressive it combines FOUR frames to give you TWO additional combined (interlaced) frames. So.. there are 6 sets of 5 frames per 1 second giving you 30 frames per second. If you take those 3 progressive frames by themselves 3x6 is 24 frames per second.
You OBVIOUSLY want to final out to 29.97 or 30 fps so you'll need those extra 2x6 frames to get you to 30!! If you wanted to final out to 29.97 AND you wanted progressive frames for EVERY frame you should have shot 30p mode.
Now... when are they ugly? When you are standing still on a frame. When are they unnecessary? When you plan to show them on a computer or progressive monitor. Remember, even when shooting progressive and playing it on a TV you will STILL have the TV doing interlaced scans... the only difference is the down scan is taken from the same point in time as the up scan.
Plus... you don't capture TO a sequence... you capture the video and edit it IN a sequence. You can still capture the footage in 24p at 29.97 and remove those 2x6 extra frames and edit in a 23.98 sequence.
Do some reading. It will only help.
CaptM

Where is De-Interlace in FCX?

Similar Messages

Maybe you are looking for