Welcome, Guest
Username: Password: Remember me

TOPIC: 4K video in a 1080 timeline export in 4K

4K video in a 1080 timeline export in 4K 14 Aug 2017 00:39 #89880

  • AZDane
  • AZDane's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 3
  • Karma: 0
So I am editing 4K footage in a 1080 Timeline (Changed the project to 1080P) and so far have been exporting to 1080 end product.
But now I want the end product to be 4K, but if I select Up to 4K in compressor it still comes out as 1080P. I didn't think it mattered what the timeline was.
Do I just need to change the project to 4K before sending the movie to Compressor. Will the original 4K files be used or have these been converted to 1080P files and now I am getting an upsampled version?
When importing media I checked to leave the files in place, but when I check the projects file in the Movies folder it is pretty large (60G) so not sure if that is actually happing. I have not selected proxy.
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 14 Aug 2017 05:37 #89883

  • Tom Wolsky
  • Tom Wolsky's Avatar
  • NOW ONLINE
  • Moderator
  • Posts: 3920
  • Thank you received: 630
  • Karma: 102
You need to use a 4K project and put the 4K media in it. The 60G might the render files, or the 4K files if they can’t be left in place.
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 14 Aug 2017 06:06 #89884

  • AZDane
  • AZDane's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 3
  • Karma: 0
Ok, but does it matter that I initially created the project as a 1080P Project and then changed it to a 4K project before sending it to Compressor? Will the media come from the original 4K files or will it come from files optimized to 1080P?
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 14 Aug 2017 10:04 #89886

  • joema
  • joema's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 770
  • Thank you received: 163
  • Karma: 11
AZDane wrote:
Ok, but does it matter that I initially created the project as a 1080P Project and then changed it to a 4K project before sending it to Compressor? Will the media come from the original 4K files or will it come from files optimized to 1080P?

If you create a 4k project then copy/paste your 1080p timeline into the blank 4k timeline, all edits and effects will be preserved and it can be exported as 4k.

Alternatively you can just change the project characteristics to 4k but out of caution I'd recommend making a duplicate of the project beforehand.

The original 4k content will be used, even IF the project is 1080p. IOW if you edit original 4k media in a 1080p project, then crop/zoom into a 1080p frame, then export that as 1080p, the underlying 4k content will be used to support the crop/zoom.

The render files will be the resolution of the project -- IOW a 1080p project will use 1080p render files and 4k project will use 4k. So there can be a modest performance advantage to editing 4k material in a 1080p timeline. However it's less advantage than just using proxy, so in general I'd recommend using proxy for H264 4k, not optimized media.

Even though FCPX does "smart rendering" (on export will use existing render files if available rather than re-render the timeline), it is smart enough to not use 1080p render files if you are exporting 4k.

Also there is no such thing as 1080p optimized media for 4k content. The optimized media is built based on the original source files, not whatever project you're using. If you transcoded to optimized media then edited in a 1080p project, the source media is always 4k.
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 14 Aug 2017 11:20 #89889

  • Tom Wolsky
  • Tom Wolsky's Avatar
  • NOW ONLINE
  • Moderator
  • Posts: 3920
  • Thank you received: 630
  • Karma: 102
Thank you joema. I probably would have said No ;)
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 14 Aug 2017 15:39 #89892

  • AZDane
  • AZDane's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 3
  • Karma: 0
Thank you very much! A lot of helpful information.
joema wrote:
Alternatively you can just change the project characteristics to 4k but out of caution I'd recommend making a duplicate of the project beforehand.

So what could potentially get messed up in the process?
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 17 Aug 2017 10:49 #89943

AZDane wrote:
Ok, but does it matter that I initially created the project as a 1080P Project and then changed it to a 4K project before sending it to Compressor? Will the media come from the original 4K files or will it come from files optimized to 1080P?

It shouldn't, although, if does come out in lower res, asides from bringing it all into a new project, you could try deleting the cached and/or transcoded media.
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 17 Aug 2017 11:03 #89946

  • joema
  • joema's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 770
  • Thank you received: 163
  • Karma: 11
AZDane wrote:

So what could potentially get messed up in the process?

Nothing should ever get messed up, it's just prudent to make a project snapshot backup before you make a major change in the project.

That's not limited to when you change the project characteristics, but anytime you make a major content change, addition, or deletion, or before you try some new plugin you've never used before. Likewise before loading an event or library XML it often makes sense to duplicate the library at the Finder level to back it up. That provides an easy roll back if the XML does something unexpected.
The administrator has disabled public write access.

4K video in a 1080 timeline export in 4K 17 Aug 2017 11:04 #89947

joema wrote:
AZDane wrote:

So what could potentially get messed up in the process?

Nothing should ever get messed up, it's just prudent to make a project snapshot backup before you make a major change in the project.

That's not limited to when you change the project characteristics, but anytime you make a major content change, addition, or deletion, or before you try some new plugin you've never used before. Likewise before loading an event or library XML it often makes sense to duplicate the library at the Finder level to back it up. That provides an easy roll back if the XML does something unexpected.

Snapshot... of course, now why didn't I think of that!!
The administrator has disabled public write access.