A drag and drop library for midi/sysex/automation/etc would be amazing.
2 Likes
A drag and drop library for midi/sysex/automation/etc would be amazing.
@Kearley
NGL I never thought of automation when posting this, but it is a fantastic add.
By automation, do you mean midi controllers, or actual track automation?
Not my idea, I saw it posted above somewhere⌠but I was picturing track automation.
Thinking about it more, I guess Cubase would also need some kind of automation container/clip system. This would be a great time saver though.
The time savings could be huge. Clicking around in tiny mod lanes is a real ask sometimes.
I suggested something like the automation idea but for Note Expression. Just drag the curve over with a dialogue to specify the length in beats, bars or timecode.
I suggested something like the automation idea but for Note Expression. Just drag the curve over with a dialogue to specify the length in beats, bars or timecode.
@JBuck
Like this, and tbf my solution wasnât as elegant. But to be able to drag drop events of all kinds freely between the MediaBay would be golden.
It all points in the same direction really, that the MediaBayâs implementation is in a sense somewhat incomplete.
1 Like
.midiloops are great, but indeed are missing the automation lane data.
Also not being able to drag & drop to mediabay is just plain silly considering its meant to be our âgo toâ media manager.
On top of all this, i think .midiloops are not enough, where is the equivalent for audio?
Nuendo has .clippackage which can do multiple audio tracks, but they dont include insertFX XD.
Why do we always stop one short of being an amazing feature?
I would love to see a SINGLE container file like â.midiloopsâ which can work for any data in cubase,
including multiple audio, midi, instrument, group, fx tracksâŚ
With automationâŚ
XMLâs are just stupid clunky, not in a single container file and are also not accessible via medibayâŚ
1 Like
Why do we always stop one short of being an amazing feature?
There is much to agree with in your post, but this is gold.
I would love to see a SINGLE container file like â.midiloopsâ which can work for any data in cubase, including multiple audio, midi, instrument, group, fx tracks⌠With automationâŚ
A lot of the requests here are summed up in this.
BTW does anyone know if Reaperâor any other DAWâhas this?
@Martin.Jirsak or any mod/staff.
I really believe in tis idea. Why is it Cubase has no way to *easily organize parts in a library.
We can do it with samples, and composers, your program would benefit greatly from this.
Hi,
As far as I know, Nuendo can do this with Audio & MIDI Events/Parts.
1 Like
Hello Martin, thank youâ I could pay the significant upgrade cost just for this alone.
Though just to confirm, you drag drop midi parts to the media bay/library from the arrange window?
Hi,
Sorry for my delay, I have a vacationâŚ
I had a look to the Nuendo manual here and here. Unfortunately I was wrong and the Clip Package is working with the Audio material only. No MIDI Parts, sorry.
Yeah you can ctrl+alt drag to the Reaper media explorer, create folders etc.
It will also preview the MIDI on the currently active instrument track too, which is nice as you donât have to wait for it to start playing like Media bay sometimes does.
Studio One does it too, you drag to the side browser and shift key toggles between saving it as a musicloop (Which saves the instrument etc. too), or a plain .mid file.
Hopefully SB will put something like this in, as itâs nice working with just plain MIDI files as youâre not tied in to any eco system then. I think the majority of users are bringing loops in to the DAW, hence why itâs probably never been introduced?
Itâs also a bit annoying with Cubase if you want to drag a MIDI part to be the source of an MIDI FX arp, you have to drag it onto the timeline first. I donât know why that is, but would love to see both improvements added as I believe theyâre part of a similar mechanism.
1 Like
Got my vote.
A Cubase user posted a youtube video showing it in action, during the C8 era. https://youtu.be/qUgQc3KPep0?t=13s
1 Like
Itâs somewhat frustrating they, SB, actually had the feature, then thought to remove it!
I genuinely believe something like this, and as I described, would be of such great benefit to many Cubase users.
Well, itâs not like they were trying to be mean. There must have been incompatibility, or it broke something else. Itâs a deep program.
I donât suspect ill intentâ I have known of ~this, and previously wondered why. My real focus though is on any glimmer of hope of this ever happening.