Logic Pro Expert has this to say about Logic 10.4.5
Logic Pro | Logic Pro X 10.4.5 Looks Like a Routine Minor Update, But Contains a New Feature That Changes Everything!
Now here is the best part. The reason you will need all these additional tracks and instruments. There is a new project setting on the General Page. And this one little checkbox CHANGES EVERYTHING:
In the process of replacing spinning hard drives with SSD on our Macintosh systems.
All of the Macs are “ancient” coming from the spinning drive era.
USB3 disks have been performing at less than 100 MByte/second read and write speeds. Not adequate for doing audio work with many disk files. Overloads occur very easily.
Current tests (Blackmagic Disk Speed Test) on SanDisk Ultra 3D SSDs are very encouraging.
2013 iMac – APFS formatted – unencrypted – write at 320 Mbyte/second, read at 425 Mbyte/second.
2013 iMac – APFS formatted – encrypted – write at 240 Mbyte/second, read at 325 Mbyte/second.
My portable “system” with everything on it is encrypted. I will be using it for my studio work drive. Performance is fine for my purposes. I had moved the working files to a different machine on the network. Network disk performance was just above 100 Mbytes/second. I experienced no problems.
Eventual target is a 2TB NVMe drive on USB 3.1 protocols for the system/portable studio. Working disk will be SATA III drives. In 2TB sizes I am down to about $.10 per gigabyte.
Off-Line “tape” is still 1, 2, and 4TB spinning disks – portable – fast enough for archive – $.025 per gigabyte. Unlikely to get larger spinning disks. That would change the archiving process into a very long and difficult process.
Scripting News: Saturday, June 9, 2018
Unreal. Fourteen years ago a standard was published (ISO 8601:2004) which clearly defined how things should be. Problem is that software developers do not spend their lives re-implementing “standard” software for the rest of their lives.
ISO gave us (back in 2004) this format 20180609T221145Z
What the world wants now is this format 2018-06-09T22:11:45+00:00 (we avoid timezone abbreviations and geo-political nonsense)
I retired from the big data world in 2004, so I never would have had cause to change my preferred world – 20180609T221145Z. To tell the truth, since just before 2000-01-01 I actually preferred the “Astronomical (Julian) day number (at noon UTC): 2458279.5” which for my machines this morning worked out to 2458279.03405093.
From the wikipedia we see
November 17, 1858, 00:00:00 UT is the zero of the Modified Julian Day (MJD) equivalent to Julian day 2400000.5
and we all basically know that the VMS clock started there 😉 In earlier times (snicker) I discovered the “bad things” that would happen if one entered a proper geocentric clock offset in a TOPS-10 system – I mean, c’mon, I had it right within 200 yards. All hell broke loose in all time-based things. Wonder why it required an OS rebuild to set/change that value.
As a reminder to anyone who uses a database that I have built – 20180609 – is not a date, nor is 2018060915270001 – but it is a very fast integer index 😉 I can’t insert things in my databases faster than 10,000 per second. I learned the hard way that telescope telemetry databases surely can 😉
Ahhh, dates. I would rather slip the bass DI track by 87 samples so it lines up with the bass amp track these days.