Logic pro x update is out
- Banned
- 1376 posts since 23 Jun, 2007 from france
the only DAW which can't run anymore in El Capitan, while all last other DAWs can !
An Apple soft which can't run on a Apple computer that not Logical, planned obsolescence.
I will not change my old Imac because of the bad reputation of the quality of the latest Apple computers.
Is it worth the expensive price ?
An Apple soft which can't run on a Apple computer that not Logical, planned obsolescence.
I will not change my old Imac because of the bad reputation of the quality of the latest Apple computers.
Is it worth the expensive price ?
- KVRAF
- 2032 posts since 15 Mar, 2002 from Seattle, WA - USA
I stuck with Sierra for over 2 years after a mediocre experience with High Sierra. Thankfully tools like Carbon Copy Cloner or SuperDuper make testing out a new operating system quite painless, so I could easily revert back. Mojave won me over though and has been very smooth so far. Unlike with High Sierra I haven't run into any compatibility or performance issues. Another reason to consider upgrading to Mojave is because of rumors suggesting it might be the last version of macOS to run 32-bit applications natively at full performance. I don't know much about OS development, but this could be a serious issue for people still using older software with no hope of future upgrades.
- KVRAF
- 35295 posts since 14 Sep, 2002 from In teh net
I've been reluctant to install HS and Mohave though as they break compatibility with some apps I use such as TotalFinder, and even make installing RME drivers more challenging.
- KVRian
- 983 posts since 23 Apr, 2003
You can cable specific instrument outs to specific AU instruments in the MIDI environment (and always could do so). Just create a physical out object in the "Mixer" layer, and then cable the microscopic little triangles next to the instrument ports to the respective instrument tracks. You also need to delete the cable between the "sum output" and the sequencer input - otherwise, everything will be merged again.machinesworking wrote: ↑Sat Dec 08, 2018 6:27 am OK so nope. AU instruments still can only be addressed by MIDI channel, no ability to assign a specific MIDI controller to them. It's a weird thing that almost every DAW has some part of it that just reeks of legacy code? I'm Guess I'm in the minority here, wanting have the Roli Seaboard assigned to say Cypher 2, while the AKAI MPK88 here is playing a Kontakt library etc.
The environment is very much legacy code, but pretty powerful for MIDI manipulation. Step sequencers, arpeggiators, splitters - it's all there, and has been there for ages (even in the Emagic days). However, it's very clumsy to use, especially on today's big screens.
I definitely agree with you that a much more streamlined environment for cabling instruments and channels would be a god send (and esp. one that doesn't feature 5 pixel wide triangles that need to be cabled to other 5 pixel wide triangles).
- KVRian
- 983 posts since 23 Apr, 2003
Mojave runs very smooth on my machine, a recent MacBook Pro, much better than the latest OS IMHO. This also reduced fan activity and other annoying issues (that seemed to be specific to the new MacBook Pros and High Sierra). I think it's pretty safe to update now, as the initial incompatibility issues are mostly ironed out.dupont wrote: ↑Sat Dec 08, 2018 9:44 am the only DAW which can't run anymore in El Capitan, while all last other DAWs can !
An Apple soft which can't run on a Apple computer that not Logical, planned obsolescence.
I will not change my old Imac because of the bad reputation of the quality of the latest Apple computers.
Is it worth the expensive price ?
However, I would always check the web regarding audio interface/driver issues for my setup, and whether my specific machine is powerful enough to run the new OS. And I would also do a backup, so that I can revert to the previous situation without issues...
But again, my personal experiences with Mojave have been great (i.e. painless). So yes, for me, the upgrade of MacBook and OS was definitely worth it.
- KVRAF
- 25446 posts since 3 Feb, 2005 from in the wilds
Minority maybe... but not alone. That is the single worst thing about Logic.machinesworking wrote: ↑Sat Dec 08, 2018 6:27 am OK so nope. AU instruments still can only be addressed by MIDI channel, no ability to assign a specific MIDI controller to them. It's a weird thing that almost every DAW has some part of it that just reeks of legacy code? I'm Guess I'm in the minority here, wanting have the Roli Seaboard assigned to say Cypher 2, while the AKAI MPK88 here is playing a Kontakt library etc.
- KVRAF
- 25446 posts since 3 Feb, 2005 from in the wilds
I just bought a new Mac Mini and installing the RME driver was the same as it has always been... click install, done...
- Banned
- 1376 posts since 23 Jun, 2007 from france
My imac is too old for Logic and Sierra !tq wrote: ↑Sat Dec 08, 2018 12:13 pmMojave runs very smooth on my machine, a recent MacBook Pro, much better than the latest OS IMHO. This also reduced fan activity and other annoying issues (that seemed to be specific to the new MacBook Pros and High Sierra). I think it's pretty safe to update now, as the initial incompatibility issues are mostly ironed out.dupont wrote: ↑Sat Dec 08, 2018 9:44 am the only DAW which can't run anymore in El Capitan, while all last other DAWs can !
An Apple soft which can't run on a Apple computer that not Logical, planned obsolescence.
I will not change my old Imac because of the bad reputation of the quality of the latest Apple computers.
Is it worth the expensive price ?
However, I would always check the web regarding audio interface/driver issues for my setup, and whether my specific machine is powerful enough to run the new OS. And I would also do a backup, so that I can revert to the previous situation without issues...
But again, my personal experiences with Mojave have been great (i.e. painless). So yes, for me, the upgrade of MacBook and OS was definitely worth it.
- KVRAF
- 35295 posts since 14 Sep, 2002 from In teh net
Can't see anything new, not specific inputs for controllers and more usable ability to assign CC which is what I was hoping for.machinesworking wrote: ↑Sat Dec 08, 2018 1:19 am So has anyone played with the new per port settings? I'm curious as to whether you can now assign a specific controller to a specific AU instrument now or if it's still per channel only? They didn't specifically mention AU instruments in the "what's new" section... just this, sounds like it might be possible now??MIDI data is kinda vague though, as in it could just be for CC's etc.There are now preferences to filter MIDI data on a port-by-port basis.
- KVRAF
- 2744 posts since 5 Dec, 2003 from Harlan's World
Do you know if there is a tutorial showing that last part about the «sum output»?tq wrote: ↑Sat Dec 08, 2018 11:54 am You can cable specific instrument outs to specific AU instruments in the MIDI environment (and always could do so). Just create a physical out object in the "Mixer" layer, and then cable the microscopic little triangles next to the instrument ports to the respective instrument tracks. You also need to delete the cable between the "sum output" and the sequencer input - otherwise, everything will be merged again.
My Soundcloud Too many pieces of music finish far too long after the end. - Stravinsky
-
- KVRian
- 605 posts since 31 Aug, 2012
But its very logical gui its the most.I.enjoyed creating patches with it.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 6214 posts since 15 Aug, 2003 from seattle
Yeah I do recall being able to do that in the Environment back in the day when Logic was my main DAW, but to be honest that's a lot of busy work when the other DAWs I use all do it no issue.tq wrote: ↑Sat Dec 08, 2018 11:54 amYou can cable specific instrument outs to specific AU instruments in the MIDI environment (and always could do so). Just create a physical out object in the "Mixer" layer, and then cable the microscopic little triangles next to the instrument ports to the respective instrument tracks. You also need to delete the cable between the "sum output" and the sequencer input - otherwise, everything will be merged again.machinesworking wrote: ↑Sat Dec 08, 2018 6:27 am OK so nope. AU instruments still can only be addressed by MIDI channel, no ability to assign a specific MIDI controller to them. It's a weird thing that almost every DAW has some part of it that just reeks of legacy code? I'm Guess I'm in the minority here, wanting have the Roli Seaboard assigned to say Cypher 2, while the AKAI MPK88 here is playing a Kontakt library etc.
The environment is very much legacy code, but pretty powerful for MIDI manipulation. Step sequencers, arpeggiators, splitters - it's all there, and has been there for ages (even in the Emagic days). However, it's very clumsy to use, especially on today's big screens.
I definitely agree with you that a much more streamlined environment for cabling instruments and channels would be a god send (and esp. one that doesn't feature 5 pixel wide triangles that need to be cabled to other 5 pixel wide triangles).
- KVRAF
- 25446 posts since 3 Feb, 2005 from in the wilds
So far so good. I wanted a dedicated audio computer. Plus with the Macbook Pro, the fan came on too much and of course the fan is right there. I have the Mac Mini under the desk. So far the fan is not noticeable if it is coming on at all yet.