Promidi

Manually, Note by note, effect by effect, event by event (including CCs). It's the only way, really. (yes, really).

Depends. Can you do what Shade does with what you already have? In my case, Meldaproduction Mfilter or Mturbofilter comes to mind (both of which I have).

Personally, this is how I would do it I have a 3rd Generation Focusrite 8i6. The includes a loopback input - This is a signal that is a copy of what ever is being played by the 8i6. So, in Cakewalk, I select the 8i6 as the ASIO output. In the DAW I want to record in, I select the ASIO loopback as the input. As long as sample rate, bit depth and buffer size match, this works. My real world example is playback via Cakewalk. Record the audio via OBS Studio or Izotope RX11 (everything in ASIO mode). Yes, you can have two applications accessing one ASIO device at the same time. I guess what I am trying to say is that the capabilities of your audio interface plays a part in getting this done.

Note: Requires Full Retail Version of Kontakt.

Can we please have the ability to select multiple Sysex banks in Sysex view. Currently, if we want to perform an operation (like delete, for example) on multiple Sysex banks, we have to select one at a time. Then perform the required operation on just that bank. Sometime we need to open MIDI files that have many sysex banks therein (for example, those intended for older Roland GS or Yamaha XG devices). When reworking these MIDI files for VSTi, we might want to delete these, now surplus, sysex banks. Currently, deleting many banks is quite tedious. It would be much quicker to be able to simply multi-select the Sysex banks. Then do the deletion.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html

When you use the MIDI time offset, the MIDI events themselves in the tracks do not move position. Only the actual trigger time changes in response to what ever you have entered in the MIDI time offset field. With a value of +346, the trigger time of all MIDI events will be 346 ticks after the time position at which they appear. If you enter a value of -346, the trigger time of all MIDI events will be 346 ticks before the time position at which they appear. The events themselves do not actually move as they appear.

I always do multi track copy and paste in the TV. In the PRV I mostly do single track editing. However, there are occasions where I want to do move or copy events from a single track to other tracks while in the PRV. If multiple tracks are visible in the PRV (which the non active tracks ghosted), I hold SHIFT while marque selecting the events. Hold SHIFT restricts the event selection to just the active track, even if some ghosted notes are within the marque selection window. When viewing multiple tracks in the PRV, there are also key modifiers to move and copy selected events from ghosted tracks to the active track. Holding ALT and right clicking on ghosted events moves the events to the active track. Holding CTRL + ALT and right clicking on ghosted events copies the events to the active track. Holding SHIFT while doing the above allows horizontal or vertical movement only (which ever direction is moved first) Of course, for these to function, Auto Focus needs to be deactivated (I have keybinding for this) As I say, I pretty much live in the PRV.

How do you “Disconnect PRV completely with TV” when they are both representing the same event data? Maybe I am missing something. I spend most of my time in the PRV when sequencing. I do most my copying and pasting in the PRV. For me, the pasted events always end up where they are supposed to, TV or PRV. I do use CAL scripts for a lot of my copy and pasting. I also have a CAL script that shifts the NOW cursor to the correct paste location based on how far the FROM is from the nearest measure. This is to capture any notes that might start before the measure. Note: I rarely quantise. There are those rare times when I paste a group of events to a destination, and some events already exist (especially with rhythms) - creating some duplicates. It does not happen often, but often enough to make the Unduplication CAL script useful feature to have if you need it. Sure beats manually finding duplicates.

I hope you’re right. I still would not risk it.

You might want to get that serial number off the thread.

As per title. Yes, there are CAL scripts that attempt to do this, but I have found that with these CAL scripts, some duplicate notes are missed. I believe the reason those CAL scripts miss some duplicate notes is because those CAL scripts assume the notes that occur at the same time also have consecutive index numbers. I noticed (usng the Event List Viewer) that this is not necessarily the case. For these older undup CAL scripts to work, the duplicate notes have to be right next to each other in the list as they appear in the Event List View. Until this has been implemented, I have written the attached CAL script that attempts a full unduplicate. The criteria this CAL script uses is that it delete any duplicate note that is within 30 ticks of each other that are in the same track. However, they do not have to be right next to each other in the list as they appear in the Event List View for the deletion to occur. This script also displays how many notes were deleted. I have tested this CAL script with up to 32000 notes with around 31000 of them being duplicates. Unduplicate 2025.1.CAL

I would love to see how most of them would go at writing a CAL script. Now that is not for the faint hearted....

On my rig, the Channel Tools help file “Channel_Tools.chm” file is in the same location as the dll itself.

I might be wrong on this but I believe this is a per project setting and is set in Preferences - Project - Clock > Ticks per Quarter-Note. This may be important if you have loaded older Cakewalk project or a MIDI file created with an older DAW (not only Cakewalk).

As with most CAL scripts, they work best when all the MIDI events you want to effect are in the same clip. Also, make sure your project clock is set to 960 PPG (Preferences - Project - Clock). I have rewritten these since this last post. Try these. Note: Any slight random fluctuations might be down to rounding issue with CAL itself. Compress to the right V2.CAL Compress to the left V2.CAL

However, if you open an old project or a MIDI file, the clock will be changed to that of the opened file or MIDI file. So, if you open an old project or a MIDI file and run any CAL script that includes the editing of any Event.Time parameters, you will get funky results. The resultant events will end up not appearing where you expect them to end up. I have learnt this the hard way many times.

They are indeed. Some things to point out with many CAL scripts. · For best results, bounce MIDI clips to one clip · For many to work properly, set your clock to 960 PPQ (remember, this is a per project setting). · Try not to delete events immediately after using many CAL scripts, Sonar can crash or give unpredictable results. (The panels have delete functions in them)

I have written CAL scripts for all of those functions I listed.

Remember, when you insert a MIDI track in Cakewalk, iIts MIDI channel defaults to “none”. This means the MIDI event’s MIDI Channels are used. Set the MIDI tracks to specific MID channels so that that can override the MIDI event’s MIDI Channels. In your case, set MIDI track 1 to MIDI channel 1, set MIDI track 2 to MIDI channel 2.

Reinstall Melodyne?

There's one way to find out.

I was wondering if some of the following could be added to MIDI editing. · Mirror copy forward and backward (Yes, we can so a copy + Retrograde - but a single function would be elegant) · Apply a time warp to notes and controllers (Yes, you can use the Transform tool, but this cannot be done on notes and controllers) · Vertically flip controller events with the fulcrum at the halfway point between controller values · Scale events with NOW being the anchor point. If Now outside the selection, use the central time as the anchor point. · Scale events to the left with the anchor point being the last event selected (including note duration if present) · Scale and shift controller events to occupy the duration of any selected notes. · Convert linear ramps to curves with changing event times. (Transform tool modifies event times - can cause Events to bunch up) · Shift selected controller Events so they start at the first selected note (if included in selection). I have created Studioware Panels with embedded CAL scripts to do the above (and more). However, as Studioware Panels with CAL scripts have been officially deprecated, a build in method of performing the above would be handy.

AI anything?? Lord help us.

If this was ever implemented, one criteria I am hoping for, is that we do not have to rely on any Input Echo to be enabled for the routing to stay intact. This is the way it works for a MIDI track that is routed to a synth track. My request is to allow multiple synths to be selected in the MIDI track output drop down.