I've had only limited success dumping DAW-derived patterns into the CS vi e-loader. Usually, the channel information is not retained, and sometimes the imported pattern introduced some note offsets. However, it is possible to record a multichannel pattern/arrangement onto a multichannel (Multi-A) track on the CS (using 'first note record'), copy that track to clipboard, then 'explode' it to the individual tracks. Works for me. I'm also using stepbeater VST to program drums. The midi-drag-drop imports directly into e-loader with channel information retained, with sometimes minor-but-correctable timing issues. see: http://launch.groups.yahoo.com/group/xl7/message/21175 cheers, J --- In xl7@yahoogroups.com, James Ulibarri <jamesulibarri@...> wrote: > > let the fun begin! > > > > 2011/1/30 James Ulibarri <jamesulibarri@...> > > > That's totally nuts man. ( In a good way). > > Yeah I don't mind that it does one track at a time. I think a > > multitracked file would just make things more complicated. I love how you > > said you're juggling files back and forth > > to the CS and Ableton. I love the sound of that work flow. I wonder why > > more people aren't working like this. Or maybe they are and they're just > > keeping it on the low. That's cool if they are and I respect that. I'll > > be trying this tonight. > > > > > > > > 2011/1/30 Szõnyi András <andras@...> > > > > > >> > >> > >> > >> On Sun, 30 Jan 2011, James Ulibarri wrote: > >> > >> > thanks, bro. I will try it and let you know what happens. Ableton and > >> the > >> > CS could be the deadly combination. > >> > > >> > > >> > >> There's an annoying issue with Ableton: the way it exports MIDI. > >> Ableton lets you export only ONE clip to MIDI, not the whole arrangement > >> or a whole row in the session view. With other words: no multitracks. > >> (Although it can import or open multitracked MIDI files fine.) > >> > >> If you use other (older) DAWs, like Cubase, Logic, ProTools, > >> Sonar/Cakewalk, etc... they are able to export multitrack MIDI. > >> > >> BTW I also use the Live because it's very fast and intuitive in many ways. > >> So if I want to send back edited MIDI from Ableton into the CS, > >> I synchronize them and simply play/record it. > >> > >> Andrew > >> > >> > >> > > >> > On Sun, Jan 30, 2011 at 1:33 AM, Szõnyi András <andras@...<andras%40c3.hu>> > >> wrote: > >> > > >> >> > >> >> > >> >> > >> >> > >> >>> When dumping midi files to the CS such as tracked/clocked drawn > >> >> modulation > >> >>> is omitted I am assuming.... > >> >>> I am talking about say filter cutoff at measure 2.1 to 8.4 with a > >> value > >> >> of > >> >>> like 10 to say fully open at 127 at any point within a* *sequence, > >> right > >> >>> down to beats/measures. Will these kinds of events import over to type > >> >> .mid > >> >>> files through e-loader? If not, then I think what a damn shame. And > >> what > >> >> a > >> >>> hassle to do this on the CS when it's so silky smooth on a soft > >> >> sequencer. > >> >>> FL studio, etc. I think real-time tweaks on the CS is not exact enough > >> >> for > >> >>> what I am talking about. > >> >>> > >> >> > >> >> All data of the sequence is stored in the MIDI file, > >> >> and all parameters should be seen in a DAW. > >> >> > >> >> I assume that you use Ableton Live: > >> >> in the Envelope view of a clip the modulated parameters can be edited. > >> >> Or you can select yourself any modulations by their MIDI Ctrl number. > >> >> (As I remember ususally the MIDI Ctlr number 79 and 80 mapped to the > >> >> filter cutoff and resonance of a factory patch.) > >> >> > >> >> Andrew > >> >> > >> >> > >> >> > >> > > >> > >> > > > > >
Message
Re: DAW w/ CS
2011-01-31 by stimresp
Attachments
- No local attachments were found for this message.