Luma Touch Support Forums

Welcome to the Luma Touch community forums, a great place to get help and share ideas with other users. The registration code can be found by emailing support@luma-touch.com.
It is currently Sat Dec 04, 2021 7:11 am

All times are UTC-07:00


To contact us directly, please use our support page at https://luma-touch.com/support.

LumaFusion 3.0.9 is now available in the App Store


Post new topic  Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Wed Sep 22, 2021 7:35 pm 
Offline
Apprentice
Apprentice

Joined: Thu Aug 19, 2021 9:18 am
Posts: 50
Hi.

I’m not sure where the most appropriate place is on the forum for posting suggestions but maybe someone from LumaTouch will see this post anyway.

I’ve noticed some odd things when exporting ProRes that someone may find useful.

When exporting a timeline with ProRes source media, a single clip for example. When matching the source, timeline/project and export settings, the exported file is a different size.

The estimated export sizes are a lot lower, almost a quarter, of what the export will be. The final export sizes could be quite a surprise for someone bit budgeting based on the estimate in the exporter. Also, does the exporter use these estimations itself to calculate space needed for the destination medium. If so, this could cause an issue of exceeding the destinations free space and could cause a ‘disk full’ error, which can also lead to other issues.

When in the export options there are export parameters that are available for selection that won’t effect the export. It maybe an idea to blank out unrelated export settings once the variation of ProRes has been selected, bit rate as an example, that may confuse a user who maybe a little unfamiliar with ProRes. Reordering the hierarchical structure of the export parameters may make this procedure a bit easier to understand. Starting with codec and container could also make it easier to follow an output’s parameters and path.

It may also be an idea for export suggestions for things such as alpha channel, if the exporter is capable of alphas with ProRes exports. A suggestion for ‘Transparency’ like there is for H.265 may be useful.

The ability to smart export/render ProRes would also help speed up an export when source and timeline attributes match the export. Even if this was only applied to non-destructive segments of an edit it could help speed up the output. At present the export times are quite high.

I’ve already asked before about the video buffer but didn’t get any response. How does it work in LumaFusion? Bypassing this when exporting could help speed up the output where appropriate.

Cheers,
Dave.


Top
   
PostPosted: Thu Sep 23, 2021 1:26 am 
Offline
Adept
Adept
User avatar

Joined: Mon Oct 05, 2020 9:43 am
Posts: 101
One thing that I have considered - it's kinda relevant to your post as it's in the dialogue before export. When a project is exported as a Lumafusion package, when exporting trimmed does it properly trim the ProRes, or (like it does to WAV, grrr) transcode to a compressed format?

I'm happy to experience these updates through other people's eyes for now... It's still gonna be a while before I complete this massive project and update to iPadOS 15.

_________________
www.youtube.com/mevi
Lumafusion on 2020 iPad Pro (with FCPXML export)
Davinci Resolve Studio on M1 MBP
Windows laptop for emergencies


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 2 posts ] 

All times are UTC-07:00


Who is online

Users browsing this forum: Bing [Bot] and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited