Jump to content

Atlas007

Member
  • Posts

    13,939
  • Joined

  • Last visited

  • Days Won

    13

Atlas007 last won the day on January 6

Atlas007 had the most liked content!

Recent Profile Visitors

3,719 profile views

Atlas007's Achievements

  1. After investing so much effort and patience, I think understanding better now why you are so emotionally bound to that library... Who wouldn't be? 🥹
  2. Try this: Create a pattern (as you like or need) Save Pattern (optional) Save Template Rename that newly saved template to #default template
  3. Which (precise) Logic version(s) is(are) involved in your issue? Are both the source and destination projects have the same bit rate settings and tempo maps?
  4. Audio-Plugin-Uninstaller is free for now…
  5. IMHO, that would be beyond the scope of a single script… Consider that a same chord could belong to many different scales… Additionally, compositions often borrow notes ifnot chords to other (neighbour) scales. Some plugins/apps (such as Scaler or Captain Chords) could be useful in that endeavour.
  6. Does the problem occurs with all projects? IOW, have you tried same while using a fresh new project (not using an existing project template, nor importing (any) data from an existing one either?
  7. I too don’t like how NI turned the Kontakt GUI intp, making it even more convoluted… Speaking of bloatware, Drones appears to be a pretty big one weighing nearly half a TB; which kind of qualify as a bloaty library, no?
  8. Pretty cool indeed! Is this a Kontakt library?
  9. I personally prefer working with the automation track opened below the region’s track. That suits my compartimentation needs.
  10. There is this old Logic topic that discusses and present possible solutions that might be of interest if applicable to Mainstage… (after transforming velocity to CC data)
  11. mouse lasso to select those notes set locators : Cmd-U split at locators : Ctrl+Cmd+T Select highest notes : Shift+^ (up arrow) Delete those notes : Del Select that new region along with its adjacent ones glue them back together : J If that is something that you will have to repeat often, Steps 2 through 5 could be easily programmed in a macro app like Automator or Keyboard Maestro.
  12. That make sense. Personally, I don’t know of a way to achieve that (via a key command or a setting) at the snap of a finger. I understand that adding those automation points graphically (via the track area or the Piano Roll) becomes quite tedious as you project grows. Perhaps proceeding via the Event List editor may prove to be more straight forward.
  13. By saving the virtual instrument preset with its parameters adjusted as you like/need them to be at the beginning of the timeline would spare you from having to create the related automation points (at the beginning of the project) to set all parameters to start at the initial value that they were set when I first started recording. Same goes for all the plugins in a given patche or channelstrip setting. Then, perhaps using the same software instrument with different versions of a given patche / channelstrip setting, each on different tracks (in a stack), could be used to spare you some of that task by decreasing the number of automation point to be added, limiting those to alternate track’s Solo/Mute as needed along the time line.
  14. Tremolo and vibrato are often erroneously interchanged…
×
×
  • Create New...