Jump to content

PandaRiot

Member
  • Posts

    40
  • Joined

  • Last visited

PandaRiot's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. So you don't think its referencing some preference files within Logic similar to how you can edit the order of plugin parameters orders by editing the CSParameterOrder.plist ?
  2. Hello all, I have searched the forum and can't seem to find an answer to this. Here's the scenario....When I want to add a new plugin via the Mackie Control I get a big scrollable list of plugins I can choose from. Great, but is there a way to customize what order they appear in? They aren't showing up in alphabetical order, category or by manufacture. For example The I/O is first, Fat EQ is second, I have read through Mackie and Logic Manuals to no avail. p.s. I saw some threads mentioning customizing the parameter order of a particular plugin, but what I'm looking for is a way to customize the overall plugin selection list when adding a new insert. Any help would be greatly appreciated!
  3. My workaround for this is to just have all the stacks expanded. Its only when a track stack is collapsed that the issue occurs
  4. So strange, I'm double checking things in Logic 10.2.0 and its works fine. 10.2.1 not so much
  5. Weird one here, for some reason the Key Command for Close Project is unresponsive in Logic 10.2.1 Mine is set to the default Option +Command + W. Can Anyone confirm? All other key commands I've tried seem to be working.
  6. Just wanted to add this seems to be happening with Summing Stack sand Folders as well when dragging a MIDI or Audio File. To reproduce, add 2 or more tracks to either a Summing Stack or Folder Stack. If you have an Audio or MIDi track below that Stack and try to drag its position, the track flies up to the Summing Stack or Folder Stack...everytime
  7. OK, problem is also still happening even when just choosing File>New (bypassing templates altogether. Also tested with Audio Interface and Built in- Inputs and Outputs. Problem happens to both. Besides the Logic Pro preference file I previously mentioned, is there a CoreAudio Preference file or reset I could do?
  8. Not sure I understand, by factory template I mean "empty project". Is there something more basic than that?
  9. Having a issue recently that when I create a new audio track, via the + button or a key command, the last settings are not retained. For example, lets say I click on new tracks, set the input to 8, check Library, uncheck Record Enable and then click ok. The issue arrises the next time I attempt to add a new track, the audio dialogue is not retaining any of those previous selections. For some reason, its always defaulting to something else. It hasn't always been like this, up until about a week ago previous new track audio setting we're retained. I haven't done any recent updates on the OS or on Logic recently so I know its not that What I've done so far.... I've attempted to reset preferences via the menu of " initialize all except.." and also just delete the com.apple.logic10.plist all together. Nether ones of these did the trick. Created a new user, loaded up Logic Pro X and the new audio track preferences were being retained as expected. Any insight on this would be appreciated.
  10. This might be obvious, but holding down option while clicking a Stack disclosure triangle will expand or collapse all track stacks.
  11. I run a 2008 MBP. Just swap out the internal HD and put in a good SSD. Upgrade the RAM to 8 gigs and its awesome. Running Logic Pro X in 10.9 and its golden!
  12. no, you can't hide them on other patches, which is the same issue I'm talking about. If the controls are purely there for mapping the software to the hardware and you don't necessarily need to see them on your display i tend to shrink them as small as they can go while in the edit window.
  13. But, not really Although there are many Smart Control templates, they are all geared towards displaying dials or faders. What I was specifically looking to achieve is to have totally custom displays per patch. Imagine it this way... Patch A) deals only with 2 Loopback devices and 1 Playback device Now to use these properly we're going to need to see those control buttons (record, play, reverse, clear) and also those waveform displays (of Loopback and Playback) properly. We'd want them to take up most of the screen so in a split second we can see exactly whats happening. Now switch to Patch B) which is only using keyboards and some effects..even though they might not be active, you still have all those GUI elements from Patch A taking up the screen. So what ends up happening is you have to make everything smaller as way to balance out your overall screen controls In an actual live situation the Smart Controls just don't cut it. You need to be able to glance at the screen and in less then a second see what you need to see. I think they work well in Logic X as a way to quickly control and map/automate, but with Mainstage they don't translate as well.
  14. Seems to be working pretty well so far. Some things I have noticed... Pressing Record functions and Record and Play Pressing Record for the 2nd time does not close the loop correctly, there's a lag (this is with all sync, and snapping off) BUT Pressing Play does close the loop correctly and continues playing. Reverse is instant and solid. To sum it up here's my workflow Press Record to start Press Play to stop recording and close the loop correctly Press Record again to overdub etc Working with various hardware loopers throughout the years they all seem to have a different workflow for starting and stoping a recording. Some use the Record button to start and stop recording initially, some function more like MainStage's Looper where as you have a Record button to start and Play to close the loop. I'm fine with that
×
×
  • Create New...