I've just tried the app using 10.3.3 but had no success using the 1.6 and old 1.5 XML options.
The app parses the XML OK, but then reports that the source material is not supported.
It's JVC Log UHD 422 h264 150Mbps from an LS300.
Quicktime can't play the footage although FCPX has no problem with it.
So perhaps that's the problem...?
[File Attachment: IMG_9653.jpg]
[File Attachment: IMG_9654.jpg]
Hackintoshes come in a variety of sizes and styles. Personally mine are both in the room next door meaning the suite itself is completely silent. My boxes are indeed very large but have plenty of cooling, lots of HDDs/SSDs, GPUs and a big PSU of course.
It's only a bit of fun though right? If anyone wants exact metrics for a system then LuxMark and Geekbench are a good start. Both of which can be compared with other known setups as a way of checking that your system is functioning correctly.
Personally I thought I'd post my new times as it's been three years since I first did the test.
Also I think it's worth mentioning, as others have, that Sierra seems slower than El Cap.
From the very first post...
3. In Final Cut Pro X, go to 'Final Cut Pro:Preferences…' – in the Playback tab make sure 'Background Render' is off.
7. In the 'Video Codec' section choose 'H.264' (edited to add - many people have got errors with H.264, so use ProRes422 instead you you have a problem - some times are given with different flavours of ProRes, but each person usually mentions which they've used when reporting their results)
Seems pretty well explained to me!
I've recently installed a second Gigabyte R9 280x in my 5 year old Hackintosh which still serves as my main edit machine.
With a single 280x under Sierra I was getting a time of 35s using 10.2 and 34s using 10.3.
With dual 280x under Sierra I get a time of 22s using 10.2 and 21s using 10.3.
However with dual 280x under El Capitan I get a time of 17.5s using 10.2 and 17s using 10.3.
So I'll be booting to the El Capitan SSD for now, until it's performance improves.
The times I've quoted are completely un-rendered sequences, exporting ProRes 422 to the desktop
A vertical video is really simple, just create a 1080x1920 project instead of 1902x1080.
Spanning multiple screens will be more complicated though.
From memory the Sumvision doesn't have any HUD (I'm sure I wouldn't have chosen it otherwise) and it can be set to loop all or loop single. It is subject to FAT32 4GB limits.
I've supplied clients with Sumvision Micro3 media players - £30
Full HD over HDMI, small enough to be cable-tied tidily behind a TV.
They can be setup to autoplay and autoloop, and can be USB powered from any modern TV.
I love the Sloths website.
The trouble is that without a comedy soundtrack, some people might actually take this seriously.
The tone of your voice is really reassuring.
You should consider making relaxation tapes for editors still using FCP7, to listen to while they are waiting for renders to finish.
I'd think that you can simply drag the items out of the library, into the parent folder. Then relink from there.
Jen and few things I've noticed.
At my end Safari won't even play the 720p60 I've made.
But my 1080p30 version does look much better: youtu.be/RPdyLXmqYAE
I'm not seeing any difference in Firefox or Chrome playback quality.
(By the way I manually set 1080p playback each time, and don't leave it in 'auto' - I thought there was a setting for that somewhere...)
Jez, regarding the original edit, If you prefer my 1080p version then you can remake the video in 1080p30 fairly easily.
Try cutting and pasting a few minutes of the original 720p60 timeline into a 1080p30 timeline.
(To be clear, use the various individual segments of clips them the original timeline, don't just drop the master ProRes on a new timeline!)
You'll find that you need to fix a few elements, and you probably won't need to render all those slow motion sections anymore - if you originally set them to 50% they will now run at their original frame rate and don't need optical flow processing.
Also your master ProRes files can be ProRes LT, as I guess it's 8bit material?
I said PART of the problem.
And yes, we did have this discussion earlier.
7 months ago I suggested uploading a proper ProRes file.
I'll unsubscribe from this thread now.
The h264 that you put on DropBox earlier, is that what you've been uploading to YouTube?
Is that fair representation of your ProRes master?
If so, then that's your part of the problem. It's horrible.
9Mbps for 720p60 is way too low.
I think you should shoot in 60fps and edit in 30fps.
Have you tried dropping your ProRes into a 1080p25 timeline, exporting ProRes then encoding to a high bitrate x264, then uploading? I'd try if for you, but until you upload a proper master file I can't.
Hello. Please please Dropbox the ProRes master and then we can put this to bed.
I'm pretty confident that you need to master in 1080p and above 10Mbps to get to quality that you want.
The 9.5Mbps h264 that you've Dropboxed is pretty rough, and when I compare it side by side with the same file I uploaded to YT is even worse. I've tried uprezzing it to 1080p then encoding, but the fact it's already a heavily compressed h264 isn't helping.
I've just bought their MorphCut software. And some 3D Transitions.
30% off everything. I assume it's today only...
Can I suggest that you stick 20 seconds of your most active footage to wetransfer or a cloud service and share the link with us.
Export a full ProRes master and run it through Handbrake.
10Mbps at 720p should just about handle your moving water footage OK.
For my broadcast work I use PPMulatorXL which floats over the top of any app running on the Mac (including FCPX)
I position the vertical R128 meters to sit over FCPXs own meters to the right of the timeline.
The software is fed audio via an old Griffin iMic, which in turn is fed from the audio output of the edit suite via a spare mixer output. The iMic plugs back into the Mac, but the signal isn't used in the Audio preference, so there's no internal feedback problems. The same could be achieved with almost any audio interface. As long as you aren't interfering with the main system output, because that's what FCPX uses to output audio. So long as you can calibrate you system to your local standard then you'll be fine.
It is possible to fudge a software workaround using Soundflower and creating multiple audio paths inside the mac, but I find the iMic solution to be really reliable, plug and play.
When I play export ProRes masters back in Quicktime, PPMulator indicates their levels correctly too, as it works for any sound playing on the Mac.