Jump to content

MarcT

Member
  • Posts

    12
  • Joined

  • Last visited

MarcT's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the feedback! I'm using an old MKII Novation launchkey - the documentation is next to nil although I found more info on their website. I don't think you can remap the CC numbers so the real trick seems to be to figure out where Logic is auto assigning the CCs - when I check controller assignments I'm not seeing any for those. Interesting enough I don't have this issue for CSSS, just CS2. I'll let you know if I figure it out. Need to upgrade midi controllers anyway so might be another solution - miss weighted keys.
  2. Hi folks - I've been running into a strange thing where when using Kontakt in Logic I'm finding that the CC's my midi controller uses (CC21-29) are missing from the options for assignments. An example is trying to assign X-Fade Velocity on Cinematic Strings 2 - I can select from full range of CC's except the exact range my midi controller uses. I'm not sure why those aren't available; also I was wondering if there is a way to change the CC's that my keyboard send to logic or if those are fixed. Logic only seems to allow reassignments in the learning mode but that doesn't work for a situation where there isn't some knob or fader to train to - which is the issue again with CS2. Anyway - thanks for the help! Tried to find a video or tutorial on this but none I could find troubleshoot this specific issue or explain enough to clarify the conflict.
  3. I'll have to explore those - thanks for sharing!
  4. Work flow is getting better - I've gotten really quick at using the nudge features for duration and pitch - as well as sorting how key commands change depending on wether score editor or step keyboard is selected. It just takes a bit more time than simpler interfaces to sort out - also using the mouse more than I would have expected - but its proving worth it for all the instruments, plugins, and effects.
  5. Sorry, tried to edit the last post to clean it up and make it a little clearer but took to long and the edit wouldn't post.
  6. Hi, I just wanted to post an update to help any others who are new to the score editor for composition. A lot of it comes down to learning what key commands functions are available within Logic X, even unassigned functions. You'll want to look at the functions for score editor, for the step input keyboard, for the play head, as well as event/region functions. The event/region functions are important because its there you'll be able to assign 'nudge' commands that will allow you to move around notes already in your score, both by pitch and location in the measure so you can make fast changes when your composing in real time. Unfortunately, some of these commands can have inadvertent effects when the score editor isn't in full window, such as, if you try to nudge a single note up a half step in pitch, Logic may adjust the entire midi region if the track editor is in view; but if score editor is in full screen then it won't. So identifying those conflicts really helps avoid them in the future. I did delete many key commands to remove conflicts (another option is to reassign which tool is prioritized for the command - I'm not sure how to do this yet). You'll also want to assign 'nudge' commands for note duration, so you can quickly change note durations to correct or experiment with rhythms in measures without have to delete and re-input values. Note input in the score editor is linked to the playhead bar, which isn't the case for some other editors, so learning to control and set controls for that bars placement without having to always rely on the mouse which is inefficient. Rather than using undo to remove any notation errors just inputed, using shirt+delete will remove the input and, importantly, move the playhead bar back so you don't have to do so manually before placing in the correct note - this is really helpful for flow. You'll want to know that shift+delete will remove the previous note. The presence of the step keyboard, and also, if it is clicked on, will change the hierarchy of key command functions; so you need to figure out what 'level' you want to be in while working and setup your commands for that level. For a while I was moving between levels and again, it was a flow killer. When the score editor is in full screen, pressing space bar will not play the tune, instead it will cause the playhead to jump an assigned value forward, so I removed that function to free up space bar as play function and then learned key command for stopping the play head. You'll also want to assign key commands for playing from start of the piece vs from the play head and functions like that so you're not wasting energy trying to move the playhead with the mouse every time you want to listen to a small section. I found a way to have it start with whatever note I clicked on and found that the easiest way to quickly review a measure or two. The last thing I'll mention is you can setup so the 'nudge' values match whatever note duration you've selected in with the step keyboard; this will again, allow to control nudge values quickly without having to reach for the mouse and go to the toolbar. I think this is a summary of the major changes I made that really helped me spend less energy trying to input my intentions and more time thinking compositionally. I alternate between using a midi keyboard for input and computer keyboard and reassigned note input so A is A, C is C, B is B, as I've had that way deeply internalized for a long time, and this did mean removing other pre-exisitng key commands, but less of a concern since I'm primarily concerned with score composition but want access to Kontakt and wider range of vsts as well as some ability to create new sounds and add reverb ect. Anyway, this is mainly for folks coming from Musescore and similar software looking for ideas on how to have a score first setup. Hope it is of some help and assurance that it is doable, just takes some hours of initial investment. Thanks all, Marc
  7. I love this technique! - it's one I sort of 'discovered' when I got stuck writing a transition or new section of an instrumental piece and was feeling overwhelmed by trying to match the earlier parts of the piece that were more developed. The simplicity made it easier to explore, hear ideas, and carry on. I think it may have actually come from hearing a bass player describe how with a single note he could change the quality of the whole band's harmony moment to moment.
  8. So I discovered more difficulties with key assignments and commands whose resolution is alluding me. I'll probably need to take a course on the score editor I thought I had successfully setup where I can transpose an note up or down half steps to edit lines, but when I do so it always transposed the entire midi region and I can't locate a way to differentiate the command for a single note from the entire midi region. Whenever the note is selected, the entire region is as well. I checked all the help sections and some web searches but couldn't locate any information that resolved the issue. I think a lot of the difficulty I'm running into resolves around how Logic Pro has internal hierarchies that aren't clear in how they are setup or how the user can modify them when multiple tools are present. I'm really gonna have to earn my wings. Anyway, thanks again for anyone who has time to field this - when I get a chance I'll sign up for some instruction. Thanks!
  9. Oh great, I had totally missed that you could assign key commands to the part box (must of been fatigue sorting through all the options)! Yes, I would love to setup key commands for changing note duration for already entered notes and moving/rearranging notes left or right - I got pitch changing setup yesterday so I can go back and tweak lines/phrases already written, and I still need to investigate how rests are handled and changed. I appreciate the insight - its easy to get lost in logics vast options, screens, and tools! I've just learned how to use exs24 for sound fonts and how to use Kontakt plugin! Take care, Marc
  10. Oh brilliant, it was that simple! I need to study up more on the link function and systems of heirarchy built in to Logic - I couldn't quiet parse the descriptions/search help on it. This also got me re-assigning keyboard shortcuts which helped a lot with ease of use/work flow for using Logic Pro as a notation based composition tool rather than focus on engineering/production. Thank you for taking the time, it means a lot, All the best, Marc
  11. Hi, I did figure out that double clicking the space outside the score in the score editor, or using the curved up arrow button will bring back the view of all the tracks: if I then click on a track within the score editor, and then click on step keyboard I can keep them all in view. As long as I don't press up arrow or down arrow it doesn't shift score view to just one track. It's not an amazing solution as I'd love to be able to shift without having to rely on the mouse to work around/avoid the issue (or clicking out of the step keyboard and then back in). I also saw that you can input notes in score editor without having clicked on the step keyboard as long as its still on the screen, but then you can no longer change note lengths using 1, 2, 3, 4, 5 ect. because instead that switches window view, so its not a great solution either. Maybe if I was able to disable window switch key binds and somehow reassign the numbers to setting note duration in the score editor without having selected the step keyboard. Just some thoughts, thanks again for any help!
  12. Hi all, I've been wanting to use the Logic Pro X score editor as a primary composing tool using step keyboard key bindings, (note input, duration, octave, velocity) but I've run into two difficulties: 1. When selected in the score editor with the step keyboard selected (to have access to all the computer keyboard inputs for placing notes, note dynamics, and values), if I shift between tracks using arrow keys, the score editor automatically hides all the tracks but the one I shifted to. I would like to be able to shift between tracks while editing/composing this way without it hiding the others automatically- it there any way I can bind to this view layer or disable this auto function? 2. When the step keyboard is clicked on, I haven't been able to find a way to play back without clicking out of the step keyboard / going back to the track editor which interrupts workflow since I do that at a really high rate to check harmonies and counterpoint. Are there any work around or solutions for this - thanks, I'm pretty new to Logic as I've always written in Musescore 3 but I'd like to dig deeper and not have export scores to logic if possible Thanks again! Marc
×
×
  • Create New...