G.K.

Hi copy the link below and paste it into an email that you then send to your own Apple Mail account . If you receive that email in your Apple Mail App and you click on it you should be directed to the correct download page in Apple's App Store : macOS Mojave by Apple https://apps.apple.com/de/app/macos-mojave/id1398502828?l=en&mt=12 It worked for me , hope it works for you too . Best Gerd

Ouuchh ...

I remember having a similar issue , way back with a former version of Logic . My - not so elegant - solution at that time was to select the particular audio regions and use "Bounce Regions in place", onto a new AUDIO Track and new naming , remove the original region and then delete all "unused" Audiofiles in that project. ( However my audio file folder had an overall size far beyond 60GB , and the number of regions that I "bounced in place" was something around maybe 15 ... . ) Might this be an option for you in this project ? Best, Gerd

If your setup and your particular Sessions allows it , I recommend running the session in 88kHz when using UAD PlugIns . Latency is not completely gone then, but everything runs much smoother than in 44kHz .

Hi , when I remember it correctly this is not possible at all. I did this whole process with Logic4/5/6 songs when Logic9 was around. To re-create LOGIC4/5/6 songfiles it is necessary to import and save them in LOGIC 7 first ! Then , this LOGIC 7 songfile can be imported and saved in LOGIC 9 . Then , this LOGIC 9 songfile can be imported and saved in LOGIC X . During this process it is very likely that certain elements in Logic's Environment - for the case you've built some stuff in LOGIC 6's environment - are getting lost and won't work anymore . I remember that also AUDIO and INSTRUMENT Channels and certain routings didn't work also. Best, Gerd

https://support.apple.com/en-us/HT203718 New in Logic Pro X 10.4.1 Stability/Reliability Logic Pro no longer sometimes quits unexpectedly when clicking on an automation point in a project that starts before bar one. Logic Pro no longer sometimes quits unexpectedly when switching Room Types in the ChromaVerb plug-in. Logic Pro no longer quits unexpectedly when Auto Punch recording in Keep Mode with no metronome. Logic Pro no longer rarely quits unexpectedly when loading Space Designer presets created in older versions of Logic Pro. Logic Pro no longer quits unexpectedly when pressing Command–Period (.) to stop and discard an in-progress audio recording. Logic Pro no longer quits unexpectedly when opening certain projects created in earlier versions. Logic Pro no longer quits unexpectedly when loading certain Alchemy presets that were originally created in Chameleon 5000 Logic Pro no longer freezes when horizontally zooming while recording. Logic Pro no longer sometimes quits unexpectedly when creating a new project on a computer that is also running Parallels. Logic Pro no longer quits unexpectedly when a channel strip setting is loaded while the EXS editor is open with unsaved changes. Logic Pro no longer quits unexpectedly when performing Undo after packing a folder in the Tracks area. Logic Pro no longer quits unexpectedly when pressing Play after automation has been copied from one track to another. Enabling Auto Voice Split and setting Humanize to a high value in the Studio Instruments no longer sometimes causes notes to hang when Cycle Pre-Processing is enabled in the Preferences. Logic Pro no longer quits unexpectedly sometimes when changing presets in the Klopfgeist instrument plug-in. Logic Pro no longer quits unexpectedly sometimes when using a non-US keyboard to enter certain characters into the Scripter plug-in. Logic Pro no longer quits unexpectedly in certain rare cases when opening projects created in earlier versions. Undoing the creation of a Track Stack or deletion of an Aux in the Mixer no longer sometimes sets all channels to No Output and disables the Audio Engine. Logic Pro no longer sometimes becomes unresponsive after removing an instance of Space Designer from a project originally created in a previous version.

Sure . However , when you connect other Hardrives, Monitors etc. to this Dock : What about pops/crackles in the AudioInterface's Signal when several devices share the same single (thunderbolt-)lane thru this Dock ? This might be irrelevant in most scenarios, but no matter how powerful thunderbolt looks on paper , for AUDIO-recording I've found it is a save way to use the AUDIOINTERFACE on a single dedidcated Thunderbolt Bus. - The MacPro2013 has 6 Thunderbolt2 Ports , but there are actually only 3 seperate thunderbolt Busses. ( https://support.apple.com/en-us/HT202801 ) My current system is based on a UAD Apollo8 interface. It's connected via a thunderbolt port to the macpro . I've noticed that sometimes - out of the blue - crackles occured during recordings. Of course this might be also related to UAD Drivers , the specific mac OS , blablabla ... . But since I've been using a dedicated thunderbolt Bus for the AudioInterface and leave the second Thunderbolt port - that shares the same bus - free , no pops/crackles occured .

Hi , when I purchased a MacPro2013 I used the following cables/adapters to connect my Firewire 400 Interface ( MBoxPro2 , AVID ) and external Firewire 400 Hardrives to the Thunderbolt2 ports : 1.) Firewire 400 to Firewire 800 : Lindy FireWire 800 Cable 9-6pin 3m ( some 25.-U.S.$ )( https://www.thomann.de/gb/lindy_firewire_800_kabel_6_pol_3m_02.htm ) 2.) Firewire 800 to Thunderbolt 2 : Apple Thunderbolt to FireWire Adapter ( 29.-U.S.$ ) ( https://www.apple.com/shop/product/MD464LL/A/apple-thunderbolt-to-firewire-adapter ) This connection worked absolutely stable and without flaws . Theoretically (!) you could add here Apple's "Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter "( 49.-U.S.$ ) ( https://www.apple.com/shop/product/MMEL2AM/A/thunderbolt-3-usb-c-to-thunderbolt-2-adapter?fnode=138f4a72ff2270dd05e1b0137dd7c40cba07d7a09aeb2b3cc07a657af41e12149226bcf6c9596e952d2fc0b92e579a6bba20f19f6dc06362a3bf88065592c57204aed047d6b822a241c125edb46cea2ce12df20bfaa7a95a32c0ebe2f6cc2574d93b15d7f283084d54fbaba26b7d135b ) to build a connection for your system. Give it a try ... Best, Gerd

Me thinks , with the iMacPro-Models Apple is targeting the Augmented Reality ( not sure if this is the right term ??) Developers . Their future apps/games will be necessary to provide the must-have-content in Apples App-Store for the next generation iPhones , iPads , i-whatevers ... . Apple needs content that makes/keeps its iPhones attractive.

Logic Pro 10.3 , VCA Faders ( BUG ?? ) Hi , I've just stumbled across the following : when I open my basic setup ( large Logic session created prior to L10.3 ) that already contains 5 VCA Faders , and I try to create a new VCA Fader , Logic 10.3 selects the first listed one of my existing VCA Fader instead and offers me to re-name it . After another attempt to create a new VCA Fader Logic 10.3 completely ignores it . Can somebody check this . Maybe it is something I can get rid of by trashing my Logic Preferences , but maybe it is a bug . Best Gerd

Some ( very tiny ) news concerning Logic and the "magic" TOUCH BAR : https://9to5mac.com/2016/11/02/macbook-pro-touch-bar-logic-pro-x/

Concerning your MacPro : The cleanest and most troublefree to upgrade from OS 10.6.8 to OS 10.11.xx is to install the new OS on a new seperate harddrive. This way you can switch back to your OS Snow Leopard system anytime , just by selecting the StartupDisk of your choice .(The downside is that you have to install all your Software and PlugIns from scratch on this new OS system.) I did it this way on my older MacPro's . It is actually very helpful , because I need to be backwards compatible , and some sessions are too big / too specific for opening troublefree under a new OS and/or newer Logic version. I've arranged my systems in a way that I have two dedicated Harddrives for each OS version and their particular own Logic workspace . The samples are on dedicated Sample Only/ Read Only SSD's , which can be accessed from both OS systems . If you are in the process of upgrading your OS ( and Logic ) please also read this older post of mine : viewtopic.php?f=1&t=120527&p=624462&hilit=Gerd#p624462 Best , Gerd

Hi Sam , actually I cannot comment on making a DiskImage of OS10.6.0 . However , Apple still offers a DVD installer disk in their Webshop . Maybe it is an option for you to buy it . Link to Apple Webstore, U.K. : http://www.apple.com/uk/shop/product/MC573Z/A/mac-os-x-106-snow-leopard?fnode=0ae8a0dd7372f254bd68d754750e27a2e568134f5f975c1958d5f99960ab25c00285f5023899643789d9d276ba0dadf9cc431db32ea8ff2a92c5fdabba11a1551cb2b0f1115434f810da822ceb1686173c288f5c3f696b5c7275044f6918f1f1 Best , Gerd

Hi all , athough I only might have a conversation with myself here, I'd like to share an update concerning this issue. A scary update , indeed . While I wasn't able to successfully load my above mentioned sample setup after updating to OS X 10.11 I thought that the difference of successfully loading this setup would be getting slightly more additional RAM , maybe 4GB more or so . (Similar situations concerning RAM usage occured with former OS updates , and I could solve this through getting 4 or 8GB more RAM.) So , because I'm in the process of upgrading my complete setup , I yesterday installed a new system , a MacPro ( 2013 ; 6 Core , OS X 10.11.2 ) with 64GB RAM . Now the scary part : I couldn't load (or rebuild ) the particular VEPRO mframe that loaded without issue and enough headroom of free available System RAM under OS X 10.8.5 with 48GB System RAM . No way . While ActivityMonitor shows reasonable RAM usage in the category MEMORY USED , the number for CACHED FILES is outgrowing those numbers, which leads to the point that VEPRO will crash , because the system is running out of free RAM. OS X 10.11 is the worst system so far when working with large Orchestral Libraries . Those of you who want to update from former OS versions should be careful , otherwise they might run into the situation to not be able to open their older sessions due to this issue. ( Like in this case of Sebastian: viewtopic.php?f=1&t=122002 ) Best Gerd

Hello Sebastian , just a thought : ... does your project contain lots of samples and/or AUDIOfile snippets ? If so , can it be that you are simply running out of RAM ? The reason why I think of this is that I couldn't open my basic VEPRO metaframe filled with Orchestral Sounds after upgrading from OSX 10.8.5 to OSX 10.11 ElCapitan . While on a 48GB RAM setup this VEPRO metaframe used some 40GB of RAM when completely loaded under OS X 10.8.5 , it wouldn't load completely ( and then crash) under OSX 10.11 ElCapitan . Obviously ElCapitan is much more RAM hungry than previous OS versions. I had to rebuild this VEPRO metaframe from scratch , this time leaving out quite a number of instrument samples. Next time when launching your specific Logic Session open the app "Activity Monitor". Under the memory tab you'll find below the new categories MEMORY USED and CACHED FILES ( ... different from former versions of ACTIVITY MONITOR ...). If both numbers together get close to or equal the number of your PHYSICAL MEMORY , you are running out of memory. While VEPRO will crash in this situation , Logic might stay open but is unresponsive. As I said , just a thought. Best wishes Gerd