Jump to content

Channel10

Member
  • Posts

    72
  • Joined

  • Last visited

Channel10's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I played back a white noise sample trough the filter of EXS24 set at 12 dB low-pass. I added some resonance so I could easier spot the cut-off frequency. These are the cut-off values in Hz I found. 10.0% : 30 Hz 20.0% : 60 Hz 30.0% : 130 Hz 40.0% : 210 Hz 50.0% : 490 Hz 60.0% : 1000 Hz 70.0% : 2000 Hz 80.0% : 4100 Hz 90.0% : 9200 Hz 100.0% : 14000 Hz I could also use the band-pass filter for this measurement, that might give more accurate values. However I did not do that.
  2. Now I think I miss something. I was not thinking about the difference between track or region automation. I was thinking about the difference between midi-cc data for controlling synth or mixer parameters versus automation data for controlling parameters. With the current behavior there is not a big difference between them, is it? In fact, what was the reason for implementing automation (for over 15 years Logic has it, I know) in Logic? What I appreciate about midi-cc data is that it is plain/easy/raw. But with the current implementation in Logic it is not so easy anymore.
  3. Good you mention this. However . . . I thought we had automation for that?!
  4. Sorry, events, I delete them in the event editor btw. Removing pan events from the step editor works fine.
  5. The behavior in the case the "Additional behavior" button is on is really strange. Deleting events just does not seem to work as expected. I keep on deleting events but it still says 149 events.
  6. In the screenshot below you can see (midi) pan values for the region called "Strange". Why do the pan values displayed in the Step editor not correspond to the pan values in the Event list? In the Event list there are 20 midi pan values, in the Step editor there are much much more.
  7. Too many times I accidentally press one of the numeric keys (the ones lined up on top of my keyboard below the F1 ... F12 keys) when I am in the mixer (to be more precise, the mixer attached to the bottom of the main window) or in the main window and everything is "shuffled up" after that. How can I disable these numeric keys and only using them for entering values? I looked at all the assigned shortcuts in the Key Commands window but didn't find anything of which I suspect to be the reason for this inwanted behavior. thanks
  8. Yes that makes sense. Thank you. btw: are you, as Logic veteran, surprised by this?
  9. Hmm, can't recreate it either. However I am sure it happened. Never mind.
  10. Can anyone confirm this bug: When I copy paste a configuration from one Echo to an Echo in another project it doesn't properly paste the "wet" value. The "wet" value will be set to 100%. Logic Pro X 10.2.0
  11. Didn't think about it, thanks. Made another mistake: the send channel the analyzer is on should be mono of course. However if you do everything right then it is still a tough job.
  12. Channel10, regarding you goal "1.", I both second David's recommendations, but be aware that, if what you are interested in is actually mostly the differences between the two synths outputs, and if you want to both ear and see where these differences sit in the frequency spectrum, there's also another way (which will work both for stereo or mono synth signals). 1/ Stack your two synth tracks into a track stack (or, if you do not want to stack them, route both of them to the same bus). 2/ On one (but only one of the two synth channels, insert a Gain plug-in as the very last position, leave gain at 0dB and balance at 0% and select the "phase invert" button(s) (both buttons if it's a stereo channel). 3/ Insert your Channel EQ analyzer on the summing track (or the bus Aux). By inverting the phase of one of the two synths, summing them will only let differences come through. You can hear them, and the Analyzer will show what frequency range and amplitude they feature. No need for panning if you implement this approach. It is of course more appropriate if both synths signals have a lot of commonalities, and only fairly subtle differences, in which case it is more efficient to focus only on the differences, than to compare the two full signals. On the other hand, if both synths signals are very different, this approach won't be very informative because the difference between the two will be huge and all over the place. Hi Arnoud, thank you for the suggestion, however even if signals are very close (two sawtooths from 2 different synths for example) it doesn't seem to work: http://i66.tinypic.com/2l97hqh.png
  13. No, you're not. In Logic Pro X, when you pan a stereo signal, the pan knob acts as a balance knob: pan the signal left and what you're really doing is lowering the level of the right channel. Pan hard left and you're effectively muting the right channel. You are 100% right. This holds for the balance button at the Gain plugin and for the pan button at the mixer as well. Must have overlooked something when I was testing it.
  14. But in that case you are summing the right channel from synth A with the left channel from synth A, aren't you? I am not sure if I want to do that.
×
×
  • Create New...