Jagged Edges w/ CS5.5, FS100 1080p30

bkmvincent

Active member
Guys, I'm pulling my hair out over this because typically I'm able to solve these stupid problems within a reasonable time, but this is just impossible. On top of my playback being god-awful and stuttery, I'm getting bad Source/Program playback in Premiere. Both look extremely jagged on edges everywhere, and as soon as I apply anything simple to the clips it can barely play. I attached a screenshot of my Program at 100% and the same clip opened in VLC player.

To clarify: My playback AND pause resolution are at FULL. MPE is ENABLED. Only unless I force a render on the timeline (going from yellow to green) is when I can get playback to be smooth. BUT the aliasing is still there.

Here are my system specs:

Windows 7 64bit
Premiere CS5.5.2
Intel i7-950
ASUS Sabertooth X58 Motherboard
12gb RAM
Nvidia GTX 570
2x250GB HD in RAID0 for my OS
2x1TB HD in RAID0 for my Footage

You have to look at the image at 100% to see what I'm talking about. My resolution is kind of large so double check!

EDIT: DVXUSER scaled the image down. This is on my server:

http://www.brandonvincent.net/images/jaggies.png

Someone please help!
 
Last edited:
OK, so after doing a little digging in some other threads on this board, I found someone else running into this problem with Premiere as well. It's interpreting the .mts files straight from the camera with an Upper Field First for some reason. When you go to the clip and choose Modify -> Interpret Footage it verifies this. This is clearly wrong and I can't figure out how to make it default to what it SHOULD be. If anyone has any idea as to changing the default interpretation of footage upon import it would be greatly appreciated...


Also, manually changing the field order gets rid of the aliasing, BUT I still have a very bad performance issue. It's not like I'm running the minimum requirements, either. There should not be any performance problems with the little I'm doing to the footage.
 
Last edited:
There's no sequence preset for 30p, so you need to change it to 29.97, Progressive (no fields). Once you do, you can save it as a permanent template.
 
Why is playback so important, set it to 1/2. The only thing that matters is the output.
Select all clips in the project window and interprete them correctly.
Maybe your pc is not configured right
why do you want 500 gig for OS?
250 is more than enough, use the other disk for export or temp files.
http://ppbm5.com/
 
Last edited:
Why is playback so important, set it to 1/2. The only thing that matters is the output.
Select all clips in the project window and interprete them correctly.
Maybe your pc is not configured right
why do you want 500 gig for OS?
250 is more than enough, use the other disk for export or temp files.
http://ppbm5.com/

I'd like to be able to watch my timeline without having to force-render it. Otherwise it's unwatchable. Setting playback to 1/2 still yields the stuttering playback. Even 1/4 is exactly the same.
You have to select the files individually to interpret the footage. I have over 200 clips for this project. I'm not going waste that much time just fixing footage that should be right to begin with. I also don't want this to happen every time.

I don't "want" my OS to be 500GB, I want my OS to be RAID0. I had two 250gb HD's left over from my previous build and put them in an array.

I already sent in my output files to PPBM5 but they've yet to be posted. I assume they will be up sometime Monday.
 
I thought CS5.5 interpreted them correctly?

The problem is the AVCHD spec. It flags all progressive footages incorrectly as interlaced. CS5.5 should be able to interpret them correctly, CS5 saw them as interlaced... People are generally really bad at noticing horrible deinterlacing artifacts so I thought this problem was fixed. :Drogar-BlackEye(DBG

It's not possible to interpret them all at once?

http://provideocoalition.com/index....g_workflow_part_7_adobe_premiere_pro_cs5.5.x/

" If you have several similar clips, you can list the bin as List, select multiple PsF clips simultaneously, and follow the same procedure with all of them at once."
 
You should be able to watch unedited footage in the timeline in full resolution. It should be a yellow line.
I think you are a bit short on seperate disks. I do not see any advantage in setting OS on a raid 0. Is this raid partioned?
 
You should be able to watch unedited footage in the timeline in full resolution. It should be a yellow line.
I think you are a bit short on seperate disks. I do not see any advantage in setting OS on a raid 0. Is this raid partioned?

What do you mean by "short on separate disks"?

Neither of my RAIDs are partitioned. And just an FYI, I have over 300GB of data on the OS drive, so separating the two 250GB drives wouldn't make sense anyway.
 
I thought CS5.5 interpreted them correctly?

The problem is the AVCHD spec. It flags all progressive footages incorrectly as interlaced. CS5.5 should be able to interpret them correctly, CS5 saw them as interlaced... People are generally really bad at noticing horrible deinterlacing artifacts so I thought this problem was fixed. :Drogar-BlackEye(DBG

It's not possible to interpret them all at once?

http://provideocoalition.com/index....g_workflow_part_7_adobe_premiere_pro_cs5.5.x/

" If you have several similar clips, you can list the bin as List, select multiple PsF clips simultaneously, and follow the same procedure with all of them at once."

The funny thing is I had CS5 and I've never run into this problem with interpreting the clips incorrectly. Now that I'm using CS5.5 it's an issue.

Thanks for the link, I had previously tried selecting all of the clips in the bin but the "Modify" option was grayed out. I Googled how to edit multiple clips for hours and am surprised I did not come across that site. Maybe I had my had my clips set up as thumbnails at the time. I will try this when I'm back in my office.
 
What do you mean by "short on separate disks"?

Neither of my RAIDs are partitioned. And just an FYI, I have over 300GB of data on the OS drive, so separating the two 250GB drives wouldn't make sense anyway.

300 gigs of data? What on earth have you installed. You cannot put anything else on your OS disk then your OS and the programms.
A 150 gig disk is usally enough as C;drive even if you have two Adobe suites installed.
 
Last edited:
300 gigs of data? What on earth have you installed. You cannot put anything else on your OS disk then your OS and the programms.
A 150 gig disk is usally enough as C;drive even if you have two Adobe suites installed.


The majority of that is software. Adobe isn't the only thing I have installed on my computer. What's installed on my OS drive isn't really the point of the thread anyway.

What I'm probably going to do is just transcode the footage to something easier to edit. I have plenty of space so that's not really a concern. Thanks.
 
My results were recently posted to the PPBM5 database. As I write this post, I'm listed as #193. My Computer ID is "BrandonsEditStation"

A link to the database is here.

Here's the details from the test if you can't see them on the database page.

Total: 293
RPI: 2.87
Disk I/O: 76
MPEG DVD: 127
H.264 BR: 83
MPE OFF: 104
MPE ON: 7
MPE GAIN: 14.9

I've since abandoned AVCHD for editing. I've found that transcoding to DNxHD is much easier to deal with. Of course it introduces larger files and more space needed, but I can deal with that considering how much easier it is to edit. If I have a SDE or something that needs to be done ASAP I'll work with the native AVCHD files. Otherwise I'll just dump them into a watch folder and let them transcode over night.
 
Back
Top