Christoph Gelfand
Forum Replies Created
-
I should add that I had it playing for 10 minutes this morning using 30p footage played back at 59.94i and then all of a sudden it dropped out. Very strange. Tested same cables with AJA T-Tap and no issues…
-
I set that setting to 29.97- should I set to 30? Either way it doesn’t play back progressive- only Interlaced. For whatever reason those settings don’t translate to the settings offered in FCP.
-
In theory this should work, but in practice it actually doesn’t. Is there anything I need to set in the System Prefs of the Blackmagic setup? Their tech support couldn’t help me and basically said if you don’t see a 30p option then it doesn’t exist.
As it is 59.94i does not output properly. I also have the AJA T-Tap and associated software installed- could this cause a conflict?
-
I apologize, I must be staring too deeply into my monitor. After further review, the FCP X titles look far superior upon export than the PSDs. Lesson learned, I suppose…
Thank you!
-
I don’t know what you mean by Pixel size or PAR? If titles simply don’t look good in FCP X there must be an issue…why would the native title function in FCP X also output problematic text?
-
Here’s a still from the timeline. This looks the same whether I use FCP X titles or Photoshop titles. The project is 1080p 29.97. The titles for this project were all exported PSD files. They were repositioned using the Transform function is FCP X but they look the same with no transform parameters set.
-
I did not scale the image but I did move it around the frame to center it- could that be the issue? Will post a grab tomorrow morning.
-
I really don’t think it’s a Matrox issue since I still see the issue on the Quicktime outputs. I also attempted to use text I produced in FCP, but no difference. I have to use Helevetica since I am trying to match the same standard font the client used prior to hiring me.
-
How do I move this to the other forum that you suggested?
-
It was set to Better Quality. Isn’t that just a preview function? This issue occurs in the finished QT output as well…
