Jordi Torres

Cool. Next time maybe start by adding them to your Logic score as text from the beginning to avoid additional the additional manual work in Sibelius. Come to think of it, perhaps another options would be to export your Logic markers to MIDI from Logic as explained above, then import that in Sibelius? Cheers, J.

If your plugin is supposed to output MIDI, then you'll probably want to create an AU MIDI Effect version of it. But keep in mind that the MIDI out will reach the Instrument slot and whichever instrument plugin you have there. If you want to route the MIDI beyond that, then you'll have to go out of Logic's and back in again using IAC (through Logic External Instrument plugin), like des99 says. J.

Hi, It looks like your plugin is VST and Windows-only, so that won't work in Logic. J.

Hi globet, For that to work you need to move your audio region's anchor to where the desired transient is located (there are commands to set the anchor to transients), then you can use the Pickup clock command to move it to the playhead position. J.

Hi, You might be able to work around it by exporting a dummy MIDI region to a MIDI file with a single MIDI event at position 1 1 1 1 (the resulting file will include your global track markers), then convert the marker events to text using a tool like the shareware MidiKit and resave the file. With that done, import the file into Logic again. Now you'll have all your markers as text (Logic meta events) in a region. At this point you'll have to do at least a bit of manual work: Copy/Paste the meta events (the text "markers") from that region (from the Event List editor) to each individual instrument region as to include them in all your parts before exporting them each to MusicXML. Maybe there's a better way I'm not aware of. J.

If you mean you have a bunch or markers in Logic's global tracks, then no, those won't end up in your exported MusicXML file. Your "markers" need to be part of the score as mentioned previously. J.

Right, just like Logic when using "Plain Text" text inserted with the text tool. Markers (of any kind) are not part of the score when you export it to MusicXML, so that's not going to work. If you add your text "markers" while being on the top level in the score editor (with all parts shown), then each individual instrument part will inherit those "markers". J.

Hi @craigs, It's not quite clear how you're using BlackHole there...where's your audio coming from? Which application(s)? Is the second track using a separate BlackHole channel or set of BlackHole channels, or are you reusing the same BlackHole channel(s) as the "original" track? Which flavor of BlackHole is it? 2ch, 16ch or 64ch? J.

Hi @higuywhatsthestory, No, there's no marker support (as in Logic markers/ MIDI marker meta events) supported in MusicXML. However, there are several elements in MusicXML that could be repurposed as markers: The <rehearsal>, <words> and <credit-words> elements to name a few. For example, Plain Text added in your score in Logic with the Text tool will translate to the <words> element when exporting your score as MusicXML. Just give it a try and add some text with the text tool (Plaint Text or customized with Layout >Text Styles) and see what looks best in Sibelius. I was experimenting and ended up with <credit-words> elements after creating these in a test score: I don't have Sibelius so don't know how that would look there... J.

That used to be possible with the Chord Track feature that was removed years ago. See steps 1, 2 and 3 in this old macProVideo article: https://www.macprovideo.com/article/audio-software/create-a-quick-chord-chart-in-logic-pro If you don't mind getting this information live on playback, then you could send your MIDI chords out an IAC driver bus (which will be rerouted back to into Logic) so that they are displayed in the MIDI Activity display in Logic's LCD: J.

Yep, @Anton Yegorov, if your keyboard's still controlling a selected channel strip's fader it's because there's a MIDI Device script for your keyboard that's doing some automatic assignments behind the scenes. Check your Preferences > Control Surfaces > MIDI Controllers window and if you see your keyboard there with the "Auto" checkbox checked (first column), then's that's the reason none of our previous suggestions worked: J.

This is what I'm saying I prefer, to uncheck that box and not use Control Changes Input Filter. If a given instrument still responds to CC7 to control volume, then that would require a different approach as you suggest. J.

I vote for this option, as the first one prevents all Control Change events from reaching instruments as well as prevents all Control Change events from being recorded. J.

You can move the locators by loop length forwards an backwards(search for move locators in the Key Commands window), but the actual selection of events needs to be done with a separate command (the one @Atlas007 already mentioned, Select All Inside Locators). J.

Hi globet, As long as you don't quit Logic, your last choice will be remembered. If you just launched Logic and the selected option is not "Create new tracks" (it seems to default to "Place all files on one track"), it's easy enough to hit the C key on your computer keyboard followed by Enter. J.