You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, First of all thank you for such a great plugin, But I have been using command post for the last couple of years and just since I have updated to FCPX 10.8.1 I can no longer Batch export active timeline. A year or to ago I had a similar problem with command post just failing but has been woking just fine for the last year or so with FCPX 10.7.1 and actually an older version of command post 1.4.24 but I just started using FCPX 18.1 3 days ago and got the cannot switch back to FCPX error so I updated to the latest command post and same thing. If I try to export more than 2-3 clips it happens every single time.
I use your app on daily basis and really am going to suffer with out it working and actually do not even know any other way to bath export clips other than the making compound clip "trick" but I need to export at least 60-100 clips and usually do it with command post in batches.
Thank you so much if you have any suggestions I might be able to try or if you all are aware of this problem.
By the way I am on Ventura 13.6.4, could that maybe be part of the problem? DO I need to update to Sonoma for any reason?
I will do what ever it takes LOL I really need to get this working!!
Thank you very much
The text was updated successfully, but these errors were encountered:
Thanks, but I do not use Frame.io I love Command post and will patiently wait to see if you can work this out...
I appreciate it.
Command post is hands down the best!
Can you all please try an address this or maybe give a reason as to why this may happen? Why would it fail to switch back to FCPX while exporting the time line clips?
Thanks
Normally it's because Final Cut Pro is struggling with too many exports on slower computers. I'm guessing you'd run into the same issue if you tried to do things manually.
Normally it's because Final Cut Pro is struggling with too many exports on slower computers. I'm guessing you'd run into the same issue if you tried to do things manually.
NO, not the problem bc I have a Studio Max M2 with plenty of Power my friend
I'm having a somewhat similar issue with Batch Export, though on FCPX 11. My hardware is also quite adequate, being an M2 Ultra, 64GB RAM and plenty of space on the SSD.
Batch export starts fine and seems to successfully queue up 4-5 clips for export. After that, it seems to slow down substantially. It doesn't look as though there's any renders happening. It seems as though Commandpost itself is simply stuck. Eventually, it queues up another clip for rendering. But for more than 4-5 clips it's nearly unusable. I have to give it an hour to export 30-40 clips.
Hey there, First of all thank you for such a great plugin, But I have been using command post for the last couple of years and just since I have updated to FCPX 10.8.1 I can no longer Batch export active timeline. A year or to ago I had a similar problem with command post just failing but has been woking just fine for the last year or so with FCPX 10.7.1 and actually an older version of command post 1.4.24 but I just started using FCPX 18.1 3 days ago and got the cannot switch back to FCPX error so I updated to the latest command post and same thing. If I try to export more than 2-3 clips it happens every single time.
I use your app on daily basis and really am going to suffer with out it working and actually do not even know any other way to bath export clips other than the making compound clip "trick" but I need to export at least 60-100 clips and usually do it with command post in batches.
Thank you so much if you have any suggestions I might be able to try or if you all are aware of this problem.
By the way I am on Ventura 13.6.4, could that maybe be part of the problem? DO I need to update to Sonoma for any reason?
I will do what ever it takes LOL I really need to get this working!!
Thank you very much
The text was updated successfully, but these errors were encountered: