Jump to content

Mouse_SF

Member
  • Posts

    14
  • Joined

  • Last visited

About Mouse_SF

  • Birthday 01/06/1968

Personal Information

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mouse_SF's Achievements

Rookie

Rookie (2/14)

  • Dedicated Rare
  • Collaborator Rare
  • First Post Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

6

Reputation

  1. I can help you. The solution is on the first page of the "Tips & Tricks" forum right here on Logic Pro Help. Feel free to contact me directly.
  2. Here is an update with some features i neglected to show in the last video: Keep following this project here on Logic Pro Help, the one stop shop to mastering Logic on your friendly interweb. I cannot praise this site enough.
  3. APC40 Mk 1 Customized modeless Control Surface for Logic Pro with full LED feedback 11/17/23 Here’s a few more details on the above post: Outline I’ve had a goal of using my APC40 with Logic as a customizable surface for a while, and wanted the expanded functionality Ableton provides via its Remote Control Scripting. It’s a big ask. Ive been working on this for a few years now in many forms and have kind of stumbled into Wonderland. It goes without saying that this type of Modding should no be attempted unless you have a pretty good understanding of Logic. I’m a 26 year veteran user. Here is the General Outline of how this works: - The APC40 should be in Mode 1 (Ableton Live Mode, 0x41) - The APC40 inputs into Logic and is interrupted at its input in the “Cables & Ports” Environment layer, routing it to an Environment Layer called “APC40 Mods”. I use these “intercepts” frequently for many purposes. - There’s a lot going on in the APC Mods Environment layer, but the point is, after all the modifications this layer outputs to an IAC Bus named “APC/LPX Mod IAC Bus” and a few things route directly to the APC40. - I have installed a Control Surface for a Novation Launchpad Pro Mk3 with its input set to APC/LPX Mod IAC and its output set to APC LED Return IAC. It is important that you DO NOT CHANGE THESE SETTINGS. It will destroy the template. Never rebuild your Control Surfae Defaults, and back up your .cs file regularly. The CS file ONLY updates when you quit Logic. - The APC/LPX Mod IAC Bus sends all this data back into Logic, where it triggers Control Surface Assignments in the Top “No Mode” modeless assign area where all your CMD-L Learned Assignments go by default. A few commands are triggered in the LPP3 Control Surface and some LPP commands have been cleared of assignments for clean operation. - Shift + Record Enable 8 sets the Track Knobs to PAN, the knob select buttons enable AUX 1-4, and while Shifted enable AUX 5-8 on all 8 tracks in the bank - I’m also fine tuning a Function Map and onscreen display for user ease. The Grid Mapping Syntax: It took a minute to figure out a sensible data flow for the grid map - this order works The feed is an intercept of the APC LED Return IAC Bus. Separate Notes & CCs Pass only Notes 11-18, 21-28…81-88 Set for Empty, Loaded, & Selected Values Modify Queuing/Playing Ch/Values Send to LPP3 —> APC40 Grid Mapped Instrument Remove Duplicates Send to APC40 Current Status: MASTER APC40 MOD TEMPLATE ❎ Multi viewer in Mod Layer ❎ Checking Mod Layer by APC “Sectors” - Selection ❎ - Transport ❎ - Navigation ✴️ - Global ❎ - Grid ✴️ - Scenes ✴️ - Stops - MSR ❎ - Faders ❎ - Cue/QAA ❎ - TRK Knobs ❎ - DEVICE CONTROL - Shift ❎ - Add Mode Display Panel for Mods - Select to APC LPX Mod IAC? TO DO: Scene triggers need adjusting for Queue & Play States There are a couple of flaws in the grid, ch 7 map seems wonky Row & Column Banking could be tighter Inst and Plug-in “mode” (By One) Custom Bank for Smart Controls Fix Track Select/Focus Stability (Mixer Learn? Within LPP CS? Check Record Mode Feedback Isolate TRK, Device, Nav & Global by Zone EQ Controls Display Check & Update Control Diagram I’ll keep updating here as I progress for anyone who is interested in this kind of stuff. Wish me luck and Have Fun!
  4. This is a pretty complex setup, no OSCulator or anything like that. Full Navigation & Grid Feedback, Clip & Scene Launching, The Track Control Knobs can select Pan or Aux 1-8 on all 8 channels, and Shift triggers secondary functions for all controls. The APC40 feeds into an Environment Layer for custom assignments, which outputs to both the APC40 and an IAC Bus. A Faux Novation Launchpad Pro Mk3 Control Surface reads that IAC Input and outputs grid info via a second IAC bus into a custom map in the Environment. Still some programming to go, but yes this is 100% Logic Based, and transferable via .cs import and Environment Layer Import. I'll be doing a full write up soon if you are crazy enough to try something like this I can show you how. Don't tell Apple. Here's a short video and a pic of the Environment Mods:
  5. wonshu - check your syntax - you are pointing to the "Application Support" Folder, not the "Logic" folder inside of it, but you are real close
  6. The solution I’ve found for this is keeping a text file handy with your <<sudo on -s [destination][original] >> syntax. - Go to your BootDrive/Library/ApplicationSupport and Delete the folder “Logic” - Open terminal log in an paste the ln-s syntax an t enter - You are done
  7. When Building Control Surface Assignments In Logic Pro It's a good idea to remember Logic ONLY SAVES CHANGES to the Program Assignments csfile when you QUIT the PROGRAM. Go slow and and when it's working QUIT and BACKUP that .cs file IMHO You are Always better off saving that cool new plugin's default patch twice and using the CSParameter File for organizing plugin controls There is a great Utility for itcalled "Logic Parameter Order" It's simple and effective, much like backing up your <<com.apple.logic.pro.cs>> file. Also the Environment Still RULES!!
  8. Here's the proof, I'll be happy to outline the details later in this thread and at the OSCulator Forum. So many of you helped me do this I am so so grateful for LPH and all the great contributors and extra big thanks to Camille and David, of course. Now go make some music. Logic since 1997 - MIDI since 1983 - Aint nothin' but a coffin stopping me & my drum machine!!!
  9. Re-downloaded program, Library is in default location, same crash occurring. I'm perplexed (with 24 years on Logic I'm pretty sure this is a legit bug, but no word from Apple yet) Think I'm looking at going back either an OS or a program version because any workflow is super disrupted by this. I'll keep updating here. Thanks for the recs!
  10. Yes, if I create a new empty project (not from template) and add tracks it crashes on Library open.
  11. No luck there, same hard crash from any Library or Channel Strip access.
  12. Just to be clear, are these the prefs I should trash (located in ~/Library/Preferences)? com.apple.logic.pro.cs com.apple.logic.pro.LSSharedFileList.plist com.apple.logic.pro.plist com.apple.logic10.plist Thanks, I’ll try that. I’m hoping I can reload my saved version of the .cs file as I have quite a few customized control surfaces. Thanks!
  13. I'm running Logic 10.6.2 on Big Sur 11.3 on a 2017 5k iMac (18,3) and am experiencing crashes anytime I try to access either the Library or Channel Strip Settings, either via mouse or Key Command. Anybody else experiencing this bug? I notified Apple last week and have not received any response. It's killing my workflow... Thanks, Mouse
  14. I have been a Logic user since version 1, so finding new tricks doesn't happen every day for me. Here is a great one. Since Logic Pro X was released I occasionally encounter what I have coined "Blooming", when you are saving projects in Folder Mode. Like many producers, every time I work on a project I duplicate the previous days' file and append a new number, ie. Project_01, Project_02, etc. I have found that many projects will begin to dramatically increase their file size, sometimes to many GB. This should not occur in Folder mode, as the audio files are not included in the file size. If your file size exceeds 1 GB you are definitely experiencing Blooming. I have seen this in multiple studios and setups. Here is how you resolve Blooming: 1) Open your Bloomed File 2) Save as a Template (this should take a minute or 2) 3) Close the file 4) Select "New file from Template" and select the template you just saved from the Bloomed file 5) After it has opened "Save as" into the file's original folder under a new name. 6) Close the file, I usually save it again when prompted 7) Open your Project folder and check out your new skinny file. Congrats, you did it! 8) You can now safely delete the Bloomed file and the Template you created to resolve the issue. I have saved hundreds of GB using this technique. It's 100% effective, and I have been testing it for over a month. Always works. Enjoy!
×
×
  • Create New...