Answers.Body: <p>After much help above it looks like its because the camera I was recording on was recording in 50i but the project I had created in fcpx was set to 60p, this was causing issues with the final result as it tried to convert 50i to 60p...</p>
  
  <p>I restarted one of the projects as 25p instead and copied in some of the source video again and a quick repeat of my normal output process (export as mov, use handbrake to convert to a reduced size mp4 for youtube upload) seems to give a much better result (I'm comparing the mp4 on my machine to youtube but there is 0 wobble and I don't think its youtube adding it in) so I think this is the solution, make sure your projects are set to the same fps as the source!</p>
  
  <p>Thanks all</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-04-04T07:51:34.477Z
Answers.LastActivityDate: 2018-04-04T07:51:34.477Z
Answers.UserDisplayName: MorkPork
Body: <p>Hoping this is the right place to ask this and that what Im asking isn't nonsense.</p>
  
  <p>I record some top down videos of board games, the camera is on a boom arm fastened in place overhead pointing down (I can't work out a better way to do that at the moment but it works for now and isn't the main issue of this question anywho...), the boards in question have a white grid on them and when I edit and produce the footage I find afterwards that the lines seem to wobble, see <a href="https://youtu.be/mvDiWCOPshU" rel="nofollow noreferrer">here</a> for an example of what I mean if you scroll to 6.47 (as a random point without things obscuring the view).</p>
  
  <p>I'm wondering what the cause might be and if I can stop it happening.</p>
  
  <p>I do have to use the distort tool in fcpx to drag out the edges and rotate things a bit as usually my camera is never centred on the board and so one end has a noticeable slant/narrowing to it as the camera is pointing at a slight angle, could that cause it and if so anyone have any tips or suggestions as to how I can ensure my camera is pointing square to the table? :/</p>
  
  <p>Cheers!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-29T21:49:08.427Z
Comments.Text: That is an odd, trippy artifact! Is it only noticable on the YouTube upload? Or do you see it when previewing the export file? In the editor? On the source material? My initial thought is it is a compression artifact and if it wasn't perfectly square to the frame or you change coded settings, it wouldn't happen. But where in the chain it becomes noticable might hint at something else
Comments.UserDisplayName: Michael Liebman
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-30T07:01:54.663Z
Comments.Text: No I see it even worse when viewing it in fcpx when editing (but I don't have optimized/proxy files when editing for space reasons) it does appear much less pronounced in the initial mov file I export from fcpx but then moreso once I've converted it in handbrake to a more manageable mp4 (but then it is dropping from 90gb to 250mb so maybe thats my problem )
Comments.UserDisplayName: MorkPork
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-30T15:39:25.923Z
Comments.Text: Any time you increase compression or go through codec cycles, compression artifacts will get worse. You can try exporting directly to an mp4 to make it less noticable. But to prevent it entirely... What camera/recorder are you using?
Comments.UserDisplayName: Michael Liebman
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-30T18:08:27.067Z
Comments.Text: Im using a pretty naff little camera, its high def but its just a panasonic hs60, which is small and compact enough for what we need/can afford.  I had tried exporting directly to mp4 before but it takes soooo long from fcpx (6+ hours ) whereas exporting in mov first from fcpx then converting via handbrake was much quicker
Comments.UserDisplayName: MorkPork
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-31T10:57:20.447Z
Comments.Text: It's not interlaced is it? Some early HD cameras shot 1080i, and this looks a lot like the ancient nemesis of thin horizontal lines, the interlacing artefact. You could try running it through a de-interlacer.
Comments.UserDisplayName: stib
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-31T11:05:20.967Z
Comments.Text: I checked online, it says full hd so I assume not interlaced 
Comments.UserDisplayName: MorkPork
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-31T12:20:48.903Z
Comments.Text: Full HD just meant 1080i vs. 720p in some of that really marketing material. I hadn't thought about deinterlacing. That's a good suggestion to try.
Comments.UserDisplayName: Michael Liebman
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-03T20:09:09.843Z
Comments.Text: How do I de-interlace?  Is there a way to tell if the source is interlaced before I do anything with it?
Comments.UserDisplayName: MorkPork
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-03T20:14:02.813Z
Comments.Text: I found this link to the user guide, searching it shows up 1080 but mentions 1920 x 1080/50i, what would the i mean?  the link is http://panasonic.ae/en/manuals/HDC-HS60.pdf
Comments.UserDisplayName: MorkPork
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-04T06:55:26.797Z
Comments.Text: Aha I think I might know what this all means now, 50i means its shot in interlaced so when creating the project in FCPX I should set the project to be 25p, I had it set to 60p  which could be the problem there, am going to attempt to edit the project settings and reproduce the video to see if it makes a difference, cheers all!
Comments.UserDisplayName: MorkPork
Tags: <fcpx>
Title: Wobbly lines on static camera videos
UserDisplayName: MorkPork
ThreadText: # Wobbly lines on static camera videos
  
  (Asked by: username_0 on 2018-03-29)
  
  Hoping this is the right place to ask this and that what Im asking isn't nonsense.
  
  I record some top down videos of board games, the camera is on a boom arm fastened in place overhead pointing down (I can't work out a better way to do that at the moment but it works for now and isn't the main issue of this question anywho...), the boards in question have a white grid on them and when I edit and produce the footage I find afterwards that the lines seem to wobble, see [here](https://youtu.be/mvDiWCOPshU) for an example of what I mean if you scroll to 6.47 (as a random point without things obscuring the view).
  
  I'm wondering what the cause might be and if I can stop it happening.
  
  I do have to use the distort tool in fcpx to drag out the edges and rotate things a bit as usually my camera is never centred on the board and so one end has a noticeable slant/narrowing to it as the camera is pointing at a slight angle, could that cause it and if so anyone have any tips or suggestions as to how I can ensure my camera is pointing square to the table? :/
  
  Cheers!
  
  **Tags:** fcpx
  
  > **Comments:**
  > **username_1**: That is an odd, trippy artifact! Is it only noticable on the YouTube upload? Or do you see it when previewing the export file? In the editor? On the source material? My initial thought is it is a compression artifact and if it wasn't perfectly square to the frame or you change coded settings, it wouldn't happen. But where in the chain it becomes noticable might hint at something else  
  > **username_0**: No I see it even worse when viewing it in fcpx when editing (but I don't have optimized/proxy files when editing for space reasons) it does appear much less pronounced in the initial mov file I export from fcpx but then moreso once I've converted it in handbrake to a more manageable mp4 (but then it is dropping from 90gb to 250mb so maybe thats my problem )  
  > **username_1**: Any time you increase compression or go through codec cycles, compression artifacts will get worse. You can try exporting directly to an mp4 to make it less noticable. But to prevent it entirely... What camera/recorder are you using?  
  > **username_0**: Im using a pretty naff little camera, its high def but its just a panasonic hs60, which is small and compact enough for what we need/can afford.  I had tried exporting directly to mp4 before but it takes soooo long from fcpx (6+ hours ) whereas exporting in mov first from fcpx then converting via handbrake was much quicker  
  > **username_2**: It's not interlaced is it? Some early HD cameras shot 1080i, and this looks a lot like the ancient nemesis of thin horizontal lines, the interlacing artefact. You could try running it through a de-interlacer.  
  > **username_0**: I checked online, it says full hd so I assume not interlaced   
  > **username_1**: Full HD just meant 1080i vs. 720p in some of that really marketing material. I hadn't thought about deinterlacing. That's a good suggestion to try.  
  > **username_0**: How do I de-interlace?  Is there a way to tell if the source is interlaced before I do anything with it?  
  > **username_0**: I found this link to the user guide, searching it shows up 1080 but mentions 1920 x 1080/50i, what would the i mean?  the link is http://panasonic.ae/en/manuals/HDC-HS60.pdf  
  > **username_0**: Aha I think I might know what this all means now, 50i means its shot in interlaced so when creating the project in FCPX I should set the project to be 25p, I had it set to 60p  which could be the problem there, am going to attempt to edit the project settings and reproduce the video to see if it makes a difference, cheers all!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-04-04. Score: 2 | Accepted answer
  
  After much help above it looks like its because the camera I was recording on was recording in 50i but the project I had created in fcpx was set to 60p, this was causing issues with the final result as it tried to convert 50i to 60p...
  
  I restarted one of the projects as 25p instead and copied in some of the source video again and a quick repeat of my normal output process (export as mov, use handbrake to convert to a reduced size mp4 for youtube upload) seems to give a much better result (I'm comparing the mp4 on my machine to youtube but there is 0 wobble and I don't think its youtube adding it in) so I think this is the solution, make sure your projects are set to the same fps as the source!
  
  Thanks all
  
  
  ---
  
  