This seems to be a common response. "Logic already has feature X, you just have jump though a few hoops to get there".
In most threads I've seen recently, it's the other way round. Beat Mapping (reclocking), audio quantizing, key command based audio editing often need fewer steps than what people list as 'quick and easy' in other DAWs. How do you, for instance, Beat Map a composition in PT? The beauty of how reclocking, quantizing etc is done in Logic is that it's done the same way for audio and MIDI - so one doesn't need to relearn everything. The only disadvantage of this is that these things are implemented is such a transparent way that some users don't even know that the features exist! :-)
But maybe Tap Tempo needs several steps? I haven't used it for ages. I even forgot that Logic has such an option anymore, because I never need it. AFAIR, all you need to do is to record a tap tempo track and click the Beats Form Region button.
There used to be another solution as well, where one simply clicked the tap tempo Key Command. I don't know if that is around anymore.
Apocalypse, how is it done again?
ETA - never mind, I found it. Click the Sync button and press the Tap Tempo key command (Shift-T). Adjust these parameters if needed.
__________________
Apple - please bring back the focus on *creating* music in Logic! The need for great songs is much bigger than the need for great sounds!
I haven't used it for ages. I even forgot that Logic has such an option anymore, because I never need it.
And the reason for this is that manually tapping tempo isn't a good way to get accurate results - it's much better to use Beat Mapping (for audio or MIDI). Compare the Beat Mapping workflow with Identify Beat in other DAWs... :-)))
So many people complaining about Logic to crash. Mine crashes too, but once or twice in a month. I can run a whole day without any issues. And if it crashes, I just need to restart Logic, no restart of the Mac.
I wonder what you guys are doing
Pushing it harder than you probably.
I use a ton of plug-ins.
I'd like to see Ableton style macros, and unlimited no. of plugins on a bus/track. 15 or whatever there is now is too limiting.
It has clip gain in the inspector. But, you can't draw in a volume curve like PT or DP You can only raise or lower the gain of the entire region.
Sent from my iPad using Tapatalk
__________________
Dave recordla.com www.myspace.com/dbwproductions
Logic 9.1.8, DP 7.24, PT 10.3.2, Reaper 4x, Apogee Symphony, professional 4room studio great for songwriters and producers.
And the reason for this is that manually tapping tempo isn't a good way to get accurate results - it's much better to use Beat Mapping (for audio or MIDI). Compare the Beat Mapping workflow with Identify Beat in other DAWs... :-)))
beat mapping in logic is a good idea but implemented poorly.
It is only usable in corner cases.
e.g you can only beat map the hole song, what about swapping in some section to a fixed tempo or vice versa?
In most use cases I needs is to pick up the tempo of a demo track, which then is used to record the session. I would like to beat map the track, but then go through and fix the tempo for some section. Here and there tempo needs to be modified.
Beat mapping <-> tempo map swaps should be possible like signature changes.
Or we need a beat map to tempo map conversion function, ...
Anyway, the current beat mapping pisses me off, it could be so much more useful.
e.g you can only beat map the hole song, what about swapping in some section to a fixed tempo or vice versa?
You can beat map only one note if you so wish.
Quote:
what about swapping in some section to a fixed tempo
Beat mapping isn't about adjusting a section to a fixed tempo, it's about the opposite: adjusting the grid and project tempo to the tempo of the recorded material. Remember that Beat Mapping does the opposite of "Beat detective" in PT. It's two entirely different features.
The BM user interface is the same for audio and MIDI, except that if you need to beat map to a position in you audio material which doesn't have a transient, you need to hold down Control and Shift.
The PT solution for doing what is done in that video above is to press Command I and then type in some numerical value for each and every transient or MIDI note or transient you want to reclock, isn't it? That's a workflow which hasn't changed since Identify Beat was introduced in PT, probably around version 1 or 2.
The only other DAW I'm aware of which have had something as useful as Logic's Beat Mapping (but there's a lot I don't know about other DAWs!) was Opcode's Vision.
What, specifically, would you want to change in Beat Mapping?
Dual Mono tracks (nice for choosing boom and lavalier without the need for busses)
-Bigger windows, or bigger text, or something like that. I sometimes have a hard time seeing what the hell I'm working on. I think maybe resizeable windows might be just the fix for that.
-An arpeggiator.
-Offline audioprocessing with 3rd party plugins
-better grid implementation with audio regions
-more effective audio editting tools and clear implementation of destructive vs non-destructive.
Seems that they need to do two different version of the DAW
When compared to Cubase 6, I really feel that the GUI seems outdated and much less pleasant to work with.
Maybe they could implement some kind of skin, which user could change? There could be current not so dark version and darker? Not sure how it could work then though...
You can do this now..select region > open list>view>Event position and length in smpte units
Quote:
Originally Posted by reflixtinian
Show time length from selected audio files
Dual Mono tracks (nice for choosing boom and lavalier without the need for busses)
Yeah agree, but you don´t need to use busses for this, Duplicate the track and audio region, and choose what side you want by clicking the "circles" at the bottom of the channel strip. (Left,Right,Stereo,Mono or surround is possible)
Quote:
Originally Posted by reflixtinian
-Bigger windows, or bigger text, or something like that. I sometimes have a hard time seeing what the hell I'm working on. I think maybe resizeable windows might be just the fix for that.
You can choose size of Plug in windows in preferences if that is what you mean.
Quote:
Originally Posted by reflixtinian
-An arpeggiator.
There is an arpeggiator in the environment thats not to tricky to set up.
Quote:
Originally Posted by reflixtinian
-Offline audioprocessing with 3rd party plugins
YES! BIP works fine, but it could be less steps involved when doing simple Offline Fx processing
Quote:
Originally Posted by reflixtinian
-better grid implementation with audio regions
YES, it´s a little vague what you want, but I would for example want grid lines to be visible thru regions even when not in flex mod(optional ofc)
Quote:
Originally Posted by reflixtinian
-more effective audio editting tools and clear implementation of destructive vs non-destructive.
More effective, better etc is what we all want, but I find the TOOLS to be very effective in arrange window, now we just need to be able to do what we do in the sample editor in the arrange window, and make the waveform not look like s***
Quote:
Originally Posted by reflixtinian
- better calibrated level meters
Yes, make them latency compensated at all times pls
we just need to be able to do what we do in the sample editor in the arrange window
Here are some benefits of the current solution (having a sample editor at the bottom of the arrange page):
Access to a dozens of dedicated sample edit key commands, like eg "audition next/previous slice" (called "Selection Start and End to Next/Previous Transient and Play" in Logic language).
Two zoom levels/view options at the same time: small region overview, and detailed zoom in the SE.
Access to dozens of menu option dedicated to sample editing.
Clarity re. the destructiveness of it all: if you do something in the sample editor, you actually edit the sample (destructively – if you ignore the many Undo and extra backup options of course).
This way, you can for instance click on a number of regions in Arrange with the SE open, and see each of them in a large zoom, in a dedicated window without having to zoon in/out on the Arrange region.
I'm not against having an option to do this stuff in Arrange as well, but are there many benefits, really?
Quote:
better sounding time stretch, pitch algorithms
PS - The Flex algorithms already are way better than the old destructive algos, and in the ballpark of the 3rd part Radius and Pitch'N' Time plugins, which you can use for destructive time stretching in Arrange too.
Pushing it harder than you probably.
I use a ton of plug-ins.
I'd like to see Ableton style macros, and unlimited no. of plugins on a bus/track. 15 or whatever there is now is too limiting.
Really? I mean, really? You need more than 15 plugins on a bus? That sounds completely insane to me. Maybe what comes into that bus isn't what it should be if you feel the urge to murder it to that extent.......only a thought.
What I hope they include is a protocol that will enable to keep apps on an iPad or iPhone in perfect sync with the master program (Logic) but while able to use the specific benefits of the app involved.
For example: I want to create patterns in DM-1 and arrange them into a song. But as soon as I hit the play or record button in Logic, the DM-1 starts too. This all over Wifi (of course)..
Full touch screen implementation for use with touch screen monitors so that one can move more than one fader at a time. Perhaps some modification to the standard Multitouch config in the OS that treats Logic a bit differently from the rest of the programs on the system.
That would be very cool. There are decent 22" 1080p monitors that would make great control surfaces if Logic 10 and OSX 10.8 would ship with proper drivers. That alone would be worth an upgrade from 9 to 10!
I've never had Logic 9 crash, and I've been using it since it came out. I've had it stop play back and tell me that my computer needs more power, but that was on very big projects. I've also had weird clicks and pops with huge projects, but I think that still has to do with needing more power. Restarting the project made them go away.
Is it true that Logic can only use a max of 4GB of RAM, no matter how much RAM one as installed??
I've never had Logic 9 crash, and I've been using it since it came out. I've had it stop play back and tell me that my computer needs more power, but that was on very big projects. I've also had weird clicks and pops with huge projects, but I think that still has to do with needing more power. Restarting the project made them go away.
Is it true that Logic can only use a max of 4GB of RAM, no matter how much RAM one as installed??
I believe that was true for 32bit environment with 64bit you can address all RAM.
try leaving it open overnight - sometimes ok, sometimes not - very annoying
Not my experience. Latest crash in Logic was more than a year ago and due to a third party plugin (I suspect). It's permanently opened, on a project or another. Last reboot was 3 months ago.
Really? I mean, really? You need more than 15 plugins on a bus? That sounds completely insane to me. Maybe what comes into that bus isn't what it should be if you feel the urge to murder it to that extent.......only a thought.
I would also like to mention that due to the way Logic process tracks 15 inserts on one track is not a good idea, hell the Logic manual even mentions this. Besides if you really need that many inserts why not just create another bus and keep adding inserts, you can do that as many times as you want and is the recommended method (according to Apple) to continue the chain.
If you aren't aware, Logic has issues with multicore performance. If I'm not mistaken it processes one track per core/thread basically the more inserts you put on one track, you will more likely encounter performance issues. However if you bus the output to a bus and continue the chain you can more evenly distribute the multi-core workload.
I usually notice that people who use a lot of effects (like 15 inserts) are usually Reason users who are used to going overboard with the effects and inserts to get the sound they want. Other DAW users just get better sounding/more powerful plugins to begin with. Its just a shift in thinking that they have to do.
I noticed when I switched to SSD as my boot drive, problems started to pop up after some time.
Yes, I mostly leave Logic open over night. Problems like, keyboard would stop working, Logic crashes, lots of other strange things going on.
Someone noticed me that SSD never should be filled with 90% of data, which was true in my case. When doing tests the SSD seemed to be OK though. Anyway I'm now back to a 'spinning disk' and all problems have disappeared.
To me Logic doesn´t need anything function-wise, it has got all I need except flex-pitch, but I´ve got melodyne so that´s a non-issue.
What I want for the dev´s of Logic to look in to is how audio playback is working with the program´s GUI and your interactions. This may sound vague, but somehow every audio related thing you do feels somewhat shakey and not bang on rock solid. It is very seldom something that affects the finished product ie produced song, but it´s a feeling I´ve got from working with other DAW´s that are really snappy.
Some examples: Make a fade, it takes a relatively long time before it gets active.
Move cycle(loop range), same here, Logic keeps going on in the previous cycle range for ages before it gets the new.
Select loads of regions and move or copy them, have a coffee and Logic will be done by you´ve finished it.
Sometimes you cant cut audio regions where you want, even if snap settings are correct, you might need to make a new file etc to get it right.
Moving regions around is pretty slow, not as effortless as it should, you cant just grab it and throw it somewhere else in the same movement..you need to grab it, wait a split second and then you are able to move it..might sound trivial, but if you do thousands of these moves everyday it adds up..
rant over, I love Logic and think it´s phenomenal, but these things needs to be looked at IMHO
No boot drive should be filled over 90% SSD or not. IMHO 80% should be the limit anyway.
Absolutely, but when you have a lot of Apple equipment all kinds of back ups and stuff are written to the boot disk. Stuff that's kind of hard to get rid of or hard to keep away from your boot drive. I decided not to bother anymore and use a 'giant' spinning disc.
I believe that aliases usually aren't a very food idea when speed is important. People who have problems with long load/scan time for EXS usually have lots of aliases in their Sampler Instrument folder.
I use Libraries including EXS samples outside my boot drive linked through alias with no issues . Besides as soon as you load a preset and save the project the samples are saved to the project folder. So it's not a big issue at all.
New Reply 
Facebook
Twitter
LinkedIn
:-)))
