Jump to content

JoseC

Members
  • Content Count

    189
  • Joined

  • Last visited

Everything posted by JoseC

  1. The main problem with the Matrix, IMO, is that most people expect it to be like Ableton Live´s Session View, find out that it is not, and just never open it again, instead of trying to find out what it actually is, and what it can be used for, which is more than it seems. Just a warning: there is a bug in the Matrix where if you double click an audio clip in the Matrix, it opens the Loop Construction editor, but as soon as you do anything to it within the editor, bad things happen, like if the Matrix cell did not recognize the clip anymore and it got lost in another dimension. You can double click a midi cell, though, and it will ask you if you want to create a Step Sequencer pattern. This works, though as I said above, you need to stop play if you want to hear changes.
  2. But what you can do is use the Patch Browser for that. Right click in the midi track patch selection drop down menu and the Patch Browser appears. You can search your .ins file for the assigned instrument there, by text. If you do not have all presets with significant names, like EP, or Piano, just edit the .ins file and add a category prefix to the name, and search that. Like bas:Lowly or epi:PhaseyRhod, gpi:Steinway and so on. That way, if you search bas: you get all basses. Up and down arrows scroll the results AND select the patch too, so it is very convenient.
  3. The first "bug" is just the way the Docker works. Melodyne opens docked by default. If you want to close it, close the Docker tab.
  4. I was hoping that this update was bringing some improvement for the Matrix, but the Arranger Track is a nice surprise instead. Anyway, you can do more than it seems with the Matrix. You can drag and drop clips from tracks. You do not need to render clips, you can drag directly Instrument Track midi clips to the Matrix and they are automatically routed to their Track. With audio clips you do need to set up the loop, same as in any other program, but you can drag single shots as they are. And you can route the Matrix rows to any Console track, and use the effects there. In Ableton Live is exactly the same, you add FX in the track, not in the Session View slot. In fact, in Cakewalk you can even route several rows to the same track, something you can´t do in Live. You can create a Step Sequencer clip from a cell, and edit from there, but for some reason you need to stop the Matrix to hear the changes. Very annoying, but if you link the Matrix transport to the main transport you can manage somehow. BTW, a nice feature with the Step Sequencer is that you can experiment with the Step probability and sequence length and record the Matrix output to a track. You can leave it rolling and record multiple variations. Recording audio and midi directly would be great, but in the meantime it would be nice if they made possible to edit the Step sequencer without stopping.
  5. You actually need to do it once if you use track templates. A track template in CbB includes all its routing. Just drag it from the browser and you are done.
  6. Yes, I tested everything you suggested, with three synths, and the results are the same. I also tried lowering the buffer to 64 and it records only 10 ms early instead of 14 ms at 256, but it also cuts the first transient if recording starts on the beat. Just out of curiosity to see if midi input is affected, I was even testing with a groovebox synced to Cakewalk, recording its midi and audio outputs simultaneously. Same thing, no count in, at 256 samples both midi and audio line up within 1 or 2 ms, 10 ms after the beat, same results at 64 samples buffer. With a count in audio gets recorded 14ms ahead of the beat, against 10 ms at 64, and midi still 10 ms late in both cases. I am using a Tascam US2x2, latest drivers, ASIO, and a MOTU Midiexpress XT midi interface. I tried with three different synths with the same results. Timing offset is 0. Tried your suggestion of disabling that Config File parameter, but same results. Again, not much of an issue because a count in is not really needed, to record a midi track to audio, and if you want to line up everything you´ll need to slide the audio to compensate for the midi delay anyway.
  7. Found the culprit. The audio metronome. If I set a count in, the first beat gets cut and the rest of the track gets recorded early. If I don´t, everything gets recorded with an 8 ms delay, that equals more or less to the input latency of my interface at 256 samples, which should be normal. Funny thing is, this only happens with the count in, if I set the metronome to play while recording, but no count in, everything is normal. The midi metronome is fine. Of course I don`t need a count in to record a hardware synth from a already recorded midi track, but this seems like a bug.
  8. Since that seems to be the only possible explanation, and I do not remember at all doing so, what worries me now is what this quarantine is actually doing to my brain. 🤦‍♂️
  9. Thanks, Scook, that is what I see, but what I find confusing is that there is a Workspace called "Global Screensets", other called "Screensets", and you can check or uncheck "Screensets" in the "Show in GUI" side of the Manage Workspaces dialog. If Screensets cannot be global, what does "Global Screensets" mean?
  10. What the title says. I have a midi track to an external synth routed to my audio interface through a mixer, hit record and the audio gets recorded a bit early, about the reported output latency of my audio interface, enough to cut the first transient and offset the whole audio track. If I change the latency, the offset changes, but it always records early. Is there a way to compensate for this? Of course the workaround is to start recording a bit ahead and then slide the audio track, but I have been pulling my hair out trying to find other way and I cannot find it.
  11. I am still confused about the relationship, if any, between Workspaces and Screensets. Is there any way of having Screensets saved with a Workspace, or are they just saved by project?
  12. Just made all the routings and thought that maybe somebody could be interested. It is 4 x 4 cells with outputs to 8 Mono and 8 Stereo instrument tracks. 03 16 Cell 8 Mono 8 Stereo.cwx
  13. FWIW, history tells us that no software tool can be guaranteed to last forever. I just was remembering what happened with Logic for PC. If anything, Cakewalk has proved to be very hard to kill, and it is now better than ever,
  14. Sorry if this is too obvious, but are you sure that you really selected all the tracks before exporting the template?
  15. That option is in Cakewalk´s Preferences/project/MIDI menu. Zero Controllers When Play Stops: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x200D7 It also seems like a good idea to leave that unchecked if you are using CC11 for expression. It looks like this might be the problem with the OP.
  16. The same happens with other NI instruments for Kontakt included in Komplete 12, Ethereal Earth and Hybrid Keys. Those are the only instruments I´ve found with that problem, the rest of the instruments I have tested work fine. Anyway, unchecking the Zero controllers option solves that.
  17. I was recently observing the same thing with the NI Analog dreams instrument for Kontakt. Volume dropped significantly down after stopping the transport, but came back to normal if I reloaded the preset. Unchecking the "Zero controllers..." Option fixes that. I haven't had time to go further into this, but it seems related to CC11 or CC7. Maybe those instruments use a script that changes those values over time.
  18. That seems to be a strange limitation of the Nord Electro. https://www.norduserforum.com/nord-electro-forum-f9/electro-as-midi-keyboard-change-octave-t13385.html
  19. Octave Shift for CC29 is not a standard MIDI implementation. As bvideo said above, a hardware keyboard should send the actual note number, and not expect it to be transposed on reception. https://www.midi.org/forms/midi_chart-v2.pdf
  20. It looks like there is a midi loop somewhere.
  21. You actually can´t. You certainly can drag the track´s content, but you cannot drag the track itself.
  22. As already noted, "bounce to clips" does exactly that. And then some. It is not a workaround, it is the actual name of the feature that you are requesting. Maybe you should try it and suggest how you think it could be further improved. It keeps the new clip exactly in place, BTW.
  23. I am not at the computer now, and I do not remember whether or not you can record the MIDI output of an instrument in the same MIDI track, but what you definitely can do is recording the output to a different track. Just arm that to record and set input from the original track. Edit: Of course you need to make sure that you checked the option for sending MIDI in the VSTi.
  24. I guess that a single Global Transpose Disable button in the track would suffice.
×
×
  • Create New...