Jump to content

JoseC

Members
  • Posts

    310
  • Joined

  • Last visited

Posts posted by JoseC

  1. On 1/15/2021 at 12:04 PM, Ken Fraser said:

    Hello again

    I have bought a s/h Alesis SR-16 and I have connected to my PC via MIDI, so if anyone has the knowledge and patience of how to activate the .ins file I would be grateful!

     

    Once you have the Alesis connected via MIDI, you need to assign the .ins definition file to the port and channel(s)it is attached to. Go to Preferences>Midi>Instruments, click on the Define button, and it will open the "Define Instruments and Names" dialog. Click the Import button, and navigate to find the Alesis.ins file. Import that, close the dialog and now in the Instruments right column you should be able to find your Alesis. Link it to its port and channel in the left column, and you are set.   

    Now when you open the Patch and Bank selectors in any MIDI track with output to that port and channel(s),  your  instrument´s patches should appear listed, the drum names should appear in the PRV, if available in the .ins file, and the CC numbers will also appear in the PRV assigned to the actual controller names.

  2. On 13 de noviembre de 2020 at 6:08 PM, S. Christian Collins said:

    My feature request is to be able to choose a default MIDI input device that will be applied to all newly created instrument tracks. Perhaps this option could be added to Preferences -> MIDI -> Devices as an additional column in the MIDI input list. This feature is present in Mixcraft and Studio One, and it makes life a lot easier with my complex MIDI setup.

    When creating an instrument track, Cakewalk defaults to "Omni" and pulls MIDI data from all enabled MIDI input devices. This can be a problem in some advanced setups where you don't want MIDI recorded from a certain device most of the time, but you need it to be available for certain tracks in the project. In my case, I route various velocity and MIDI CC transformations to different virtual MIDI cables/channels for use with specific plugin configurations. Having to manually change the MIDI input device for every single instrument track I create seems unnecessarily cumbersome.

    For reference, here is Mixcraft's MIDI device preferences:

    Mixcraft_midi_devices.png.00912b57509518ee3b618502be4b4e18.png

    By default, Mixcraft's default MIDI input device is set to "All MIDI Devices", but you can see here I have set it to "Midi Through Port-0". Note: this screenshot was taken in Wine, which is why it looks like Windows 2000, haha.

    I can not check now, but I think that this might be saved with a track template. I tend to insert instruments with track templates, so they come with their color, icons and even favourite presets.

  3. 1 hour ago, Bruno de Souza Lino said:

    By default you can only have one plugin window open. If you want to keep the window up, you have to pin it.

    As @scook says above, that behavior can be changed. Anyway, if I understood correctly, the OP complains about the FX windows closing every time he starts or stops the transport, not only VST but Pro Channel FX as well. 

  4. 11 hours ago, Hans Sepp said:

    That's too bad. Maybe the developers can perceive it as a feature request.

    The same goes for the "groove clip looping" so that you only see bars that are looped and not all of them. And as a small improvement, it should be noted that if you change the bar, the looped ones don't take over. It is only adopted when you draw the loop again.loop.gif.d926cf4bdb0e07ed4f62c4a4df703275.gif

    EDIT:

    Cakealk is a great DAW, the Pro channel is awesome, the VST3 support and also the 32bit VST support are a huge strength. But without the clip and the loop feature, I unfortunately have to continue doing my arrangement live in Ableton and then do a stamp export and then do the mixing and mastering in Cakewalk.
    With these 2 features, Cakewalk would be the perfect DAW for everyone. For those who record a whole band or an orchestra and also for those who want to do EDM or HipHop on the PC.

    If you want to see clip borders clearly in the PRV you can if you change the clip´s background color. That shows in the PRV. If you are using Tungsten, clip´s default background color is about the same as the PRV background, that is why you cannot see it. What you can not do at the moment is hiding the other clips.

    Your problem with looped clips is a matter of design. In CbB you can roll a groove clip across a few bars and edit some bars without changing all the repetitions. That is very useful if you want to make variations. If you want to change all of them you need to do what you show in your animation, that BTW can be done faster if you hit CTL-L to unloop it and then again to loop it ,  and then roll it out again. Not a big deal for me, but of course to each their own.

    If you do not want to do that, you have other option, that is using linked clips. Linked clips will reflect any change that you make in one of them, and you do not need to have them one after the other, not even in the same track.

     

  5. 5 hours ago, Leon SonicTerrorist Erasmus said:

    Loop points for the intro. Loop points for the 1st verse. A loop setting for the 1st chorus. etc. I don't want to do this in a arranger.

     

     That is exactly what the Arranger Track is for. What is wrong with it?

    • Like 1
  6. I cannot reproduce that. Plugins stay open here until I close them, no matter what I do. Same with Pro Channel FX. Maybe you could describe step by step what you do, including your screens setup, if you open the Console View docked, floating in the same monitor, or in a second monitor.

  7. Personally what I find confusing is not seeing what is beyond the clip boundaries in the editor. I much prefer things as they are in CbB, where I do not need to create a midi container and all I have to do is to add notes to the track. Anyway, I get what you mean, maybe a "Show only selected clips" option could be added to the View menu in the PRV.

  8. 5 hours ago, Maestro said:

    Cakewalk has always done this on any of my PCs.  So, unless it's a default setting that can be turned off - but not labeled such that it is obvious to me, and please let me know if that is the case - that's just how the software behaves.

    ACIDized Loops are BWF, IIRC, so importing at timeline position where it waws saved is going to happen if you have that option enabled.  That is a more trivial issue to fix (or deal with).  Creating dozens of markers, however, is a royal PITA.

    I did it by simply dragging the loop into the arranger from Windows File Explorer.  It's 100% reproducible.

    Well, I have never seen that and I have been using Cakewalk since Pro Audio 9. Anyway, I am intrigued. I don't really use to drag loops from the Windows Explorer, but rather from Cakewalk's browser. I am away for the weekend now, so I cannot check that. Does it do the same if you drag from the browser?

     

  9. 10 hours ago, Bill Campbell said:

    The ability to bind controller events or midi notes to CBB functions.   So like if my keyboard controller sends a midi controller 12 message when I hit the 'Play' button I should be able to 'bind' that to the 'Play' functionality in Cakewalk.  With this also the ability to create and save maps for a given controller would allow the community here to create and trade controller maps here.

    This would solve a great number of the 'controller' based issues I see posted here.

    That is what ACT is for,

  10. How did you do that? Those markers on the timeline are not stretch markers, just regular timeline markers. I have never seen that dragging a loop to the arranger creates a marker, much less name it. No wonder that they do not move with the audio. Dragging either acidized or Rex files clips here does not do anything of the sort.

    BTW, they should import where you want them if you set your snap accordingly.

  11. 3 hours ago, Kirby said:

    I’m looking at the right click menu, I only see the relevant options “one-shot trigger” and “trigger resolution”. I’m on version 2020.11 if it helps. Is it maybe a custom scripted feature that I can add?

    edit: the trigger resolution menu does have a ‘follow global’ feature, but that’s for the time that a button press will snap to, and not the Global Latch setting. 

    Edit 2: I’m an idiot, I see the tiny buttons on the audio clip that override Global Latch and Global Loop! Is there any way to override the retrigger mode as well? Or can I set a midi learn code somewhere to stop a row that’s playing?

     

     

    All the global buttons (Latch, Loop, Retrigger..) are midi learnable. Right click on them. Do notice also that in Cakewalk, "scenes" would be columns, not rows. Their header buttons are also learnable.

    • Like 2
×
×
  • Create New...