Is there any cache needing to be cleared when doing a lot of midi takes?
Or do they disappear from the project as you click "x" on a layer?
It's so weird, I think, that midi is handled so differently than audio.
More than 50% of a project is midi most of the time.
It is also neglected when coming to import/export formats like OMF/AAF etc.
It's bascially StudioOne import of track archives from Cubase that differ that do midi too.
It's 35 years since first midi standard was created and still neglected as the black sheep of the family.
My guess is that it’s because the midi data is treated as ‘control’ data (like automation and EQ/dynamics settings). It is stored in the .song file, edited in the .song file, and deleted from the .song file when you delete it. There’s no cache involved so there’s also no cache to be cleared
And yes, midi is old like the abacus. Still accurate, but old
Since midi is not sound it takes up little space.
You can save bars of midi as midi files in the browser and pull them into any song, or get them from any song with song data import. I've stored them in layers in new song templates.
Drum programs know how to take care of midi. They have advanced browsers for organizing and finding the right midi for your song.
I don't use any pre-recorded libraries of midi at all - so not about that for me.
Or reusing between projects.
Just puzzled over the fact no daws let you get organized in the same way regarding the midi clips you have in project as for audio.
"Here is the pool of all your clips in your project"
"- ehhhummm, but midi clips, sorry"
which for me is at least half of what is there.
And no attention to transferring from/to other daws regarding midi either.
Exception is StudioOne import from Cubase track archives that do midi as well.
I also managed from Reaper doing EDL-files and you can select midi clips and tell it to be files on disk instead - then I could at the time import those straight up to Samplitude. In samp there are no separate track types so a file reference is just pulled in as is.
Midi clips could just as well be a proprietary format, need not be mid-files at all - just that you can see the full range in project in the Pool.
Just thought there might be a good reason for this that I overlooked, but guess not then.
You can stay organized by dropping the initial midi files in the song’s Media folder. But keep in mind that these are just a starting point for your song. Once you import them in the song then the original files are not referenced anymore (unlike audio material). Any changes you make to the midi tracks in your song are not reflected in the initial files.
SwitchBack wroteYou can stay organized by dropping the initial midi files in the song’s Media folder. But keep in mind that these are just a starting point for your song. Once you import them in the song then the original files are not referenced anymore (unlike audio material). Any changes you make to the midi tracks in your song are not reflected in the initial files.
I'll keep that in mind, thank you.
This might be what you're looking for, haven't tried them but sounds like you can store midi in them.
A Music Loop consists of everything required to recreate a musical performance, including the virtual instrument preset, multichannel FX chain presets for the virtual instrument outputs, the music-performance file, and an audio loop. Music Loops can be dragged in from the Browser, just like a MIDI file, but they are much more powerful in that they can re-create the exact setup used to make the original performance.
To create a Music Loop, drag any Instrument Part into the Browser. You can see a pop-up display indicating whether you are exporting a Music Loop or a MIDI file. By default, Music Loop is selected. To change this selection, press [Alt]/[Option] on the keyboard. Once exported, you can see the .musicloop file in the Browser.
Of course you can see regular midi files in the browser, have you tried saving midi tracks as .mid files? I've did that some but it's been a while and I can't remember if they want to start a new song or something when you try and import them. Definitely can't audition them in the browser.
Maybe you can audition a musicloop in the browser because it includes an audio loop.
I tried using music loops once in v2.x of StudioOne as track template, but did not work that well. You had to "fool" system with a short midi clip of some sort. Never understood what that was for.
Now we have decent import song data at least - works for me.
It's more about getting overview as for audio used, kind of.
Everything midi in project beside audio stuff.
Users browsing this forum: No registered users and 18 guests