|
Logic Pro X is here (pg. 7)
|
View this Thread in Original format
| Looney4Clooney |
so,
anyone care to share their experience ? I mean are the still kinks , is it worth the possible PITA. Kinda paranoid changing what works. |
|
|
| cryophonik |
| quote: | Originally posted by Looney4Clooney
so,
anyone care to share their experience ? I mean are the still kinks , is it worth the possible PITA. Kinda paranoid changing what works. |
I've been using it a lot over the past few weeks and haven't run into any kinks, or any stability issues. From my limited experience with Logic 9, this seems like a step in the right direction. Of course, since I don't have a long history with Mac or Logic and I was already running everything in x64, my viewpoint is rather limited, so take it for what it's worth.
The only thing that bugs me at all about this is the Remote app for iPad. Unlike V-Control Pro which stays in awake mode when active, Remote goes to sleep after a few minutes of inactivity and then needs to be rediscovered by Logic. I haven't found a solution for it yet, but also haven't looked too far since I still tend to work mostly with V-Control Pro. Remote is very cool, though, and I'd like to see other developers make dedicated app controllers like this for their DAWs. Probably just a matter of time. |
|
|
| Lolo |
I finished a new production on it last week.
I had a few bugs, running 10.0.1, and also some things happen when enabling new features, things I wasn't used to but that have been into logic for years. Other odd behaviors such as dotted values for audio regions have almost disappeared now, which is a good thing.
So far though I had zero app crash running it.
Only because of the Vu-meters, the remote app, and an few other top features such as the midi fx and I would recommend it.
BTW I am still using logic 9 for all "opened" projects. I have no plans to ditch it. What's in 9 so far remains in 9, which is 32 bit btw.
If you have the money, have a go, really is THAT good for me. But keep your v9 in the dock as well for your older projects, at least for now. |
|
|
| DJ RANN |
| quote: | Originally posted by Lolo
I finished a new production on it last week.
I had a few bugs, running 10.0.1, and also some things happen when enabling new features, things I wasn't used to but that have been into logic for years. Other odd behaviors such as dotted values for audio regions have almost disappeared now, which is a good thing.
So far though I had zero app crash running it.
Only because of the Vu-meters, the remote app, and an few other top features such as the midi fx and I would recommend it.
BTW I am still using logic 9 for all "opened" projects. I have no plans to ditch it. What's in 9 so far remains in 9, which is 32 bit btw.
If you have the money, have a go, really is THAT good for me. But keep your v9 in the dock as well for your older projects, at least for now. |
This seems to be the general consensus and in fairness, exactly why Apple made it so you can run both at the same time on the same machine.
There are a few reported bugs but they're minor.
Here's an incomplete list:
1) The cycle function still catches a tiny bit of audio outside the cycle points.
2) Some minor issues with Euphonix controller's Eucon protocol (names of plugins not displayed when inserted via the surface, glitches for some using the transport etc)
3) Limited to max 16 threads
4) Automation still not sample precise (timing, snapping) and automation resolution not 100% accurate.
5) Cannot apply fades/gain to comp'd audio
6) Cannot use outputs 1&2 to send to hardware when using other outputs for hardware.
7) Bounce in place still not working in realtime on External Instruments or tracks with the i/o plugin.
8) All input monitoring still on one core.
9) Sending outputs from a multi out plugin (e.g. kontakt/maschine) still processes all the plugins on the auxes on one core.
10) GUI delay is not compensated so that the meters etc are in time when using heavy plugins on the master.
Other than that, it seems they fixed nearly everything else. Tbh, a lot of these were things left over from LP9 so if you're looking if it's better, it most certainly is, just that they haven't got all the requested kinks out yet. |
|
|
| echosystm |
| quote: | Originally posted by DJ RANN
3) Limited to max 16 threads
4) Automation still not sample precise (timing, snapping) and automation resolution not 100% accurate.
9) Sending outputs from a multi out plugin (e.g. kontakt/maschine) still processes all the plugins on the auxes on one core.
10) GUI delay is not compensated so that the meters etc are in time when using heavy plugins on the master.
Other than that, it seems they fixed nearly everything else.
|
Aren't these kind of a big deal though? The timing and concurrency issues in Logic and Ableton really don't seem acceptable in this day and age. I've given both a decent try over the last few months with the intention of switching over, but it has made me realise how spoiled I am with Cubase/S1. |
|
|
| meriter |
| in 10 does the automation move along with the plugins when you rearrange the order? Like for instance if you have automation data set to bypass insert 4, and you move that plugin out of slot 4 it'll end up bypassing whatever plugin happens to take its place. I can't imagine a situation where that would be useful |
|
|
| Lolo |
| quote: | Originally posted by meriter
in 10 does the automation move along with the plugins when you rearrange the order? Like for instance if you have automation data set to bypass insert 4, and you move that plugin out of slot 4 it'll end up bypassing whatever plugin happens to take its place. I can't imagine a situation where that would be useful |
when I move a plug-in here assuming it's on the same channel, the automation remains. Only the order changes |
|
|
| meriter |
| it only happens for insert bypassing I think, just wondering |
|
|
| Lolo |
| quote: | Originally posted by echosystm
Aren't these kind of a big deal though? The timing and concurrency issues in Logic and Ableton really don't seem acceptable in this day and age. I've given both a decent try over the last few months with the intention of switching over, but it has made me realise how spoiled I am with Cubase/S1. |
I don't know what the problem is here, since 8 I've had no automation timing issues, it's spot-on.
That single core issue is a general AU and Au-related architecture issue I guess, it doesn't limit to a single specific DAW. Not to speak of Cubase. It was there long before, and has its fans, which I'm not. But it runs on VST architecture, that is rock-solid as I could experience myself while doing "beta-testing" for nomad factory magma (till 1.6 it was a nightmare but they fixed it) |
|
|
| Lolo |
| quote: | Originally posted by meriter
it only happens for insert bypassing I think, just wondering |
that's because the automation level is at the channel in that specific case. But in which specific case would you automate plug-in bypassing? Can you develop? |
|
|
| Looney4Clooney |
| they took out the node distributive processing. wankers. |
|
|
| Juan Paulino |
| New 10.8.5 update came out today. Now i can finally use logic 10 and I'm Luvin itttt |
|
|
|
|
