Please fix the "Capture Recording" feature...

Question

Ok..
Here's how "Capture Recording" (a.k.a. "Retrospective Record" in other audio applications)
is supposed to work:
The song either is or isn't playing.
You play your instrument.
You liked what you did, even though you weren't recording.
You press the "Capture Recording" button.
Your software captured what you played, even though the song wasn't playing.
And that's why Retrospective Record was asked for, and implemented in the DAW's of the world.
But in Logic, if the song is not playing, and you play something you liked,
Capture Recording just puts every note onto Bar1, Beat1 of a new track.
And there's what you wanted to "capture", every note you played, sitting at Bar1, beat1,  All at the same time. lol.
Now, I know that in this particular user group, there are many who love
to jump onto a fast response in defense of this application.
And that's ok, because I love this app also.
but the Capture Recording feature needs to be fixed.
Capture Recording (or "Retrospective Record" as Cubase calls it (they were first to implement it in 1995 btw))
works as described above in bold,  it DOES make a very VERY big difference, believe it or not.

Answer 1

I want My ES2 wrote:
Ah,, that must be because Logic stops sending Midi clock to ext. Instruments. I know Cubase continues to send MC when stopped, so its clock must continue while stopped and it bases(nu pun intended) your recording on this clock. But like i said, it must needs quite some editing afterwards since you didn't hear a click. The note must be all over the place, rhythm-wise. Cheers.
No, it has nothing to do with MIDI clock being enabled or not, it's the manner in which Logic's MIDI/Audio engine is implemented and can be traced way, way back. When Logic is not running, there is zero processing going on, this is part of Logic's intentional design and is one of the main reasons Logic is processor efficient, it also allows large instrument templates to be designed and loaded, if Logic's not running, no CPU is used. All other DAW's keep plugins partially active, you will always see CPU use. Early on when Mac's had limited graphics processing this was a big advantage, when Logic was stopped you had the full CPU to perform editing. This behavior was carried over as more powerful hardware was introduced.
The downside: Many of Logic's quirks can be traced to the fact that nothing is being processed when Logic is halted. The "System Overload" message, missed notes at the beginning of bar 1, not being able to play a song all the way through the first or second time it played.  Say you have a region at bar 40 that uses a processor heavy instrument with a couple of Waves FX plugins... a second or two before bar 40 Logic starts to fill the FX and Instrument buffers with data as the plugins become active... "System Overload". I'm guessing Logic 10 will do what recent versions of Cubase has done, offer a preference that enables either type (active, inactive) processing.
If anyone wonders why some Cubase users get on Logic's case... it's pretty much payback as Logic users use to really slam Cubase as being unprofessional because it was pirated so much it had many, many users who were completely clueless musicians/producers.
The shoe is on the other foot now, a Mac is a dongle for Logic, while Apple would rather have your $199, they're not going to gripe at pirated versions as it will sell Mac hardware... and Apple makes their money with hardware, software is merely a support group for the hardware. As anyone on this forum can see, It's Logic collecting the clueless these days.
Users don't realize how much they owe Steinberg/Cubase...
Logic's Arrange Page
Virtual Instruments
Low Latency Audio Systems
Piano Roll style editing
And that's just a few, make no mistake, Steinberg has been the innovator on a lot of the breakthroughs.
I've used Logic since version 2.1 (MIDI Only) and Cubase since version 3.