Jump to content

Tayto

Member
  • Posts

    100
  • Joined

  • Last visited

Recent Profile Visitors

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

Tayto's Achievements

  1. Ok I see what you mean: actually dragging controller icon down to a new row in Control Surfaces setup. Sorry about that, I'm using these alternately and not together as a group: basic stuff… Thanks very much
  2. Thanks do you mean "Mix Group"? I can see "Plug-in parameter Page" in Control Surfaces setup shifts by 16 alright but I have the Mackie powered off…
  3. Hi. Apparent bug when using x-touch mini controller in Mackie mode where it doesn't see all parameter pages: Using Mackie monitor in MIDI Tools, plugin parameters apparently start on page 2 and skip every other one (although it just reports e.g. "2 pages" where normally would 4). This includes Channel EQ mode where normally MCU shows 4 pages (2 bands per page) while x-touch mini only has 2 (again the equivalent of MCU pages 2 and 4). Have reported. Anyone else seen this? Thanks
  4. …indeed, and as it is there are already loads of layout presets for over 8 parameters e.g. 'Electric drums 12' has 12 rotary encoders and 6 switches etc…… thanks
  5. Thanks for replying. Yeah I know what you mean but still, it would be cool to have access to custom core controls of different plugins and just have to page between them - this crucially for live performance fx parameter control rather than a mixing situation where indeed, I take your point…
  6. Hi. Would be amazing to both extend the amount of parameters available in smart controls and for the Mackie control protocol to be able to page through them: Smart controls mode currently limited to 8 parameters in Mackie control. Smart Controls could potentially allow for doing away with having to write custom CSParameterOrder.plist altogether e.g. for plugins with twenty pages of weirdly ordered parameters etc. I've sent this on to feedback. Please think about doing the same if you agree 🙏 : https://www.apple.com/feedback/logic-pro.html Thanks [Logic Pro v10.8.1]
  7. ...working great with x-touch mini. Amazing how obscure this is....and it's free...
  8. Hi. Just to share, anyone interested in using mini controllers in mcu mode: amazing utility mentioned here: …just assign some cursors and you can page through parameters/slots with the help of an onscreen Mackie display. Very cool…
  9. Great idea! Managed to set a controller assignment for flip mode ('swap' mode) and it works. Now have access to unlimited sends with onscreen visual guidance on an x-touch mini controller that only has 8 encoders and no channel faders…Super cool!
  10. Hi. Would be great to have a control surfaces preferences option for "sends on faders" to switch control from channel faders to control the currently selected sends on faders thus allowing simple basic controllers such as x-touch mini to have access to multiple sends with visual feedback i.e. not 'flying blind'. Thanks (Logic Pro v10.8.1)
  11. Sorry if that wasn't clear, I wrote it up here to then include the post link when reporting to apple so as to be better able to describe issue with images etc.…if that's ok with the moderators… Yeah I'm saying that this is a redundant implementation and probably a legacy from some discontinued incomplete paradigm and that it should know channel/voice. It clashes with the usual paradigm for stave/voice designation - it's redundant and serves only to create the problem - see also the slurs. Independent notes have no such problem as they can be channelized as normal. Obviously I don't expect developers to pay any attention to this but just thought might be interesting to make note of. Thanks for responding … It's a classic Logic score situation where a feature is almost very cool and in fact better than other scoring software except for the fact that it's flawed. Polyphonic staves with staff styles using '-Full' rests very cool with below environment setup for proper polyphony: Would be nice to clean up the explode polyphony feature is all. thanks
  12. Posting this to report to apple: Unnecessary problematic behaviour where Meta objects in polyphonic staves attach to ‘staff’ instead of voice. These are a pain in ‘explode polyphony’ where they incorrectly reappear in every exploded stave. Unnecessary 'staff' designation anyway as midi channel already defines voice in poly staves? exploded view:
  13. …easier still I see that you can get the same fix without region splitting by just inserting a user barline which is cool… (edit: previously I mistakenly said user 'rest')
×
×
  • Create New...