Jump to content

Export region as MIDI file - exports entire project length


wilx
 Share

Recommended Posts

Hi there,

 

I've encountered a frustrating issue with exporting regions as MIDI.

 

I've got a project which is around 40mins long with lots of 2 and 4 bar loops. I want to export these loops, individually, as MIDI files.

 

I select the region, set cycle length/locators and Export As Midi File.

 

This works, but only if I drag the resulting loops into an existing project.

 

If I drag and drop one of these MIDI loops into logic, the 2 bar loop imports, exactly as expected with no extra data.

 

If I open one of these loops from scratch in Logic, I end up with a 40minute project which is mostly empty apart from the midi loop at whatever position it was at in my original project.

 

So how can I make sure that the MIDI export only exports the region, or the locator range? I presumed exporting a region as MIDI would ignore the 34minutes of silence before the region and the 12 minutes after it, but I'm getting this annoying issue with all the exports so far.

 

The only hack I can think of is to open a new logic project, and import the MIDI files one by one, setting the project length (rather than the locator range) to be exactly the same length as the MIDIs - 2 bars for one, 4 bars for another etc. This will take a long time.

 

Is there a hidden checkbox somewhere which says "when exporting a region as a MIDI File, also include redundant information that isn't contained within that region"?

http://www.wilx.co.uk

 

iMac pro. 64GB RAM - RME babyface

Link to comment
Share on other sites

Hi.

 

A standard MIDI file isn't just a region and some notes. It includes other info too (tempo, time signature, key signature, markers, etc). If you open a MIDI file, it will bring all this info with it. To avoid this, you know the answer already: Import the MIDI files (using the command or via drag and drop).

 

I set cycle length/locators and Export As Midi File.

 

The exported MIDI file won't include anything pertaining to Logic's cycle range.

 

J.

Mac mini 2018 3.2 GHz 6-Core Intel Core i7 - 67GB RAM | macOS 11.6.1 | Logic Pro 10.7.1
MacBook Pro 15" Retina i7 2.2 GHz - 16GB RAM | macOS 10.15.7 | Logic Pro 10.6.3
Merging Hapi | Merging Anubis | RME Fireface 400 | Akai MPK49 | Nord Micro Modular

Link to comment
Share on other sites

Thanks Jordi. I'm sure when I did something similar with cubase it restricted the length of the resulting MIDI file to the length of the locator region.

 

Looks like I'll have to change the whole project length to 2 or 4 bars for each midi file and re-export one by one.

 

Sigh...

http://www.wilx.co.uk

 

iMac pro. 64GB RAM - RME babyface

Link to comment
Share on other sites

Looks like I'll have to change the whole project length to 2 or 4 bars for each midi file and re-export one by one.

 

You don't have to do that, unless you want/need to open the files instead importing them.

 

J.

Mac mini 2018 3.2 GHz 6-Core Intel Core i7 - 67GB RAM | macOS 11.6.1 | Logic Pro 10.7.1
MacBook Pro 15" Retina i7 2.2 GHz - 16GB RAM | macOS 10.15.7 | Logic Pro 10.6.3
Merging Hapi | Merging Anubis | RME Fireface 400 | Akai MPK49 | Nord Micro Modular

Link to comment
Share on other sites

  • 6 months later...

Does anyone know how to get around this? I have to export 150 four and eight-bar loops from a logic project today, and if there's no way of exporting just the selected region with no redundant space before or after, then I have to drag each individual loop into the start of a a new logic project, adjust the new project's length to 4 or 8 bars, and export again.

 

This way lies madness. Someone must have a better idea! :cry:

http://www.wilx.co.uk

 

iMac pro. 64GB RAM - RME babyface

Link to comment
Share on other sites

In Logic X,,if you cut the the region to the loop you want you can export, I just did it, and dragged midi loop into project, works fine..

The two red/brown regions. First I cut the region to what I wanted, exported that, and then dragged back in on track below.. I colored them so to make the explanation better..

165841644_midisection.jpg.2a91e29865c78f7274245e102dda80df.jpg

MacPro 2015 12 core - 64 gig of ram

OSX 11.01

Logic Pro 10.6

RME fireface 800, Genelec 8040A's

Genos, Montage,Motif XS Rack, Korg M3, Intrega 7, Falcon UVI, Kontakt, u-he, musiclab

Kontakt, UVI, U-he, Music Lab- Modartt

Kontakt and UVI libraries, U-he, Madrona Labs, Music Labs, Serum, Synthmaster, Seaboard Rise, SWAM

 

SampleTank,Falcon,UVI, A.I.R. MusicTechnologies

Link to comment
Share on other sites

Thanks for that. Unfortunately, as I said earlier these files need to be the correct length with no dead space when opened from scratch, not just dragged in to an existing project.

 

I've just finished the tedious task of re-importing all my MIDI files to a fresh logic project which I adjust to be 4 or 8 bars long for each MIDI file and re-export (all 148 of them). I'm now going to switch my computer off and hope I never have to deal with MIDI like that again...!

 

:?

http://www.wilx.co.uk

 

iMac pro. 64GB RAM - RME babyface

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...