- Posts: 119
- Thank you received: 0
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Fully Loaded imac dropping frames during multicam editing (Using proxies)
I have a brand new fully load imac so I don't know what it is dropping frames
-27" iMac (5K Retina, late 2015)
-OSX 10.11.5 (El Capitan)
-4 GHz Intel Core i7
-3TB Fusion Drive
-32 GB RAM (4 8GB 1600 MHz DDR3 modules)
-Graphics Card: AMD Radeon R9 M395X 4096 MB
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
3 TB
7200RPM HDD
Connected via Thunderbolt 2
Write speed 199 MB/s
Read speed 207 MB/s
...Will that work better than my built in fusion drive to fix my issue?
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
- nils.dettmann
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 13
Please Log in to join the conversation.
nils.dettmann wrote: You probably already tried to set the playback to "performance" instead of "quality"?!
Yes I already tried that, In fact when you switch to proxy it doesn't even allow you to choose better performance or quality because proxy is automatically lower quality but better performance
Please Log in to join the conversation.
mgmartino wrote: I am editing a music video and I have 6 different angles...
Is this 1080p or 4k?
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
mgmartino wrote: I have a Lacie d2
…
Write speed 199 MB/s
Read speed 207 MB/s
…
This is a superb drive - but imagine, what's going on, when you use it for Multicam:
For a MC, FCPX demands all streams simultanously.
So, poor read/write-head inside that box, has to quiver between six different places on the platter, search it, find it, lock to it, change track, and again.....
I'm using a near-specs-bottom setup (MacMini, i5, 16GB) - but several mechanical drives = no stutter.
Please Log in to join the conversation.
Please Log in to join the conversation.
joema wrote:
mgmartino wrote: I am editing a music video and I have 6 different angles...
Is this 1080p or 4k?
1080p
Please Log in to join the conversation.
Karsten Schlüter wrote:
mgmartino wrote: I have a Lacie d2
…
Write speed 199 MB/s
Read speed 207 MB/s
…
This is a superb drive - but imagine, what's going on, when you use it for Multicam:
For a MC, FCPX demands all streams simultanously.
So, poor read/write-head inside that box, has to quiver between six different places on the platter, search it, find it, lock to it, change track, and again.....
I'm using a near-specs-bottom setup (MacMini, i5, 16GB) - but several mechanical drives = no stutter.
I might not be understanding the terminology of "mechanical drivers" but how is your computer able to run a 6 angle multicam clip with no stutter with much lower specs than mine?
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
mgmartino wrote: ...
I might not be understanding the terminology of "mechanical drivers" but how is your computer able to run a 6 angle multicam clip with no stutter with much lower specs than mine?
sorry, 'drives' .... ok, that superflouos 'r' made my reply completey undecipherable ...
read again my description what your single mechanical drive has to accomplish.
now, spread your 6 sources onto 6 individual platters (just in case: means 'drives') - ... = my method.
And 'mechanical', 'cause a hdd utilizes basically the same techniqué as a record player from 1920. Unlike SSDs, I'm using too two ext. SSD as media-drives.
(although double-checked, text can contain spells&grammars)
Please Log in to join the conversation.
- nils.dettmann
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 13
Interesting concept but some more organisational work.
I hope this isn´t two far OT but it´s interesting how every article, test and review is concentrating on the throughput of storage and rarely talks about seek times.
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
nils.dettmann wrote: So with multicam shoots you are putting every angle on a different drive?
Interesting concept but some more organisational work....
hmm, not really, depends on the formats in use:
I have to transfer from cam/card anyhow, then in FCPX 'leave files in place'. That easy.
me lazy to search myself:
you'll find an older post of mine "4k 4xMulticam on Macmini"… no real use, more a stunt, but fun to show APr on Windows users... :evil:
As mentioned, I'm on a very low spec system (and an even lower budget, it's hobby!).
I'm less interested in abstract speed-tests, prefer the 'real life' numbers. (such as BruceX)
And my 70€ platters don't deliver that fast, not speaking of the connection speed, but 'from platter to screen'
BM Diskspeed tells me ~70mbps for my 2.5" drives, ~120mbps for my software raid0, and ~420mbps for my ext.SSDs => without limiting mechanics, my method of 'MultiCam/MultiDrives' isn't needed anymore.
btw: I use a diff. drive for exports too ... same story here, intHDD is for OS&app, cache, sources and export on separte media.
On a lame Mac like mine, smart media management gives noticeable improvements... :woohoo:
Please Log in to join the conversation.
mgmartino wrote: ...I might not be understanding the terminology of "mechanical drivers" but how is your computer able to run a 6 angle multicam clip with no stutter with much lower specs than mine?
As Karsten said, speed degrades a lot due to conflicting concurrent I/O streams. You have six streams of 1080p proxy media, which are each 1/2 the linear resolution and 1/4 the total resolution per frame of the original content. So instead of H264 frames of 1920 x 1080, each frame is lower-compression ProRes at 960 x 540.
Combining the lower proxy resolution with the lower compression ProRes encoding, this produces files very roughly 1/2 the size, which equates to roughly 1/2 the I/O rate of the original files.
An additional major savings is lower CPU burden from not decoding the highly compressed H264 format, even though your Mac does have Quick Sync decoding assistance. So using proxy vs H264 reduces both I/O load and CPU load, which is why it's so advantageous.
If you have ever copied a group of files between hard drives, it is obvious it's faster to do them sequentially than in parallel. Copying six files in parallel will be far slower than doing them in sequence, because the HDD must rapidly seek between each one. There may also be adverse buffering issues, or "cache thrashing" on both drive level and by the file system buffer. This can cause a drastic exponential degradation in I/O performance.
A six-angle multicam is essentially copying six files at once. Having all that content on a system boot drive (even if Fusion) will probably not yield good performance. They need to be on a fast external drive, series of drives or RAID array capable of supporting that I/O rate.
Note if your media is on an external drive but the library (containing your proxy files) is on your boot drive, it will do most of the I/O to the library so having the external drive will not benefit greatly. You can move the library to the external drive.
People sometimes overstate the importance of I/O, as if that will solve anything. However this is likely not one of those cases. With large multicam projects, I/O is very important, and more than aggregate transfer rate is needed -- I/O operations per second in a random seek workload is important.
Please Log in to join the conversation.
- Daniel Rutledge
-
- Offline
- Premium Member
-
- Those that know don't tell, and those that tell don't know.
Please Log in to join the conversation.
One way to test this is fully render the timeline of the multicam project, then try to scrub forward and backward in the timeline. If it is fast then but slow with an unrendered timeline, the problem may be the CPU/GPU load, not I/O.
Please Log in to join the conversation.
- nils.dettmann
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 13
One factor is also the datarate of the sources at least in non-proxy-mode.
Please Log in to join the conversation.


