Jump to content

Promidi

Members
  • Posts

    4,416
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Promidi

  1. Promidi

    Headphones output?

    Not sure of your set up, but does your Motu M4 have multiple outputs, one of them being what your HD 600 headphones is connected to. If so, is that output selected in Preferences - Audio - Devices. Might want to give it a friendly name like “headphones” or something like that. Then you can create a bus that is routed to that output. I am not sure if I am on the right track (no pun intended)... but I have a similar set up here with a 3rd generation Focusrite 8i6 (without the Sonarworks Reference)
  2. Yes, but what about track settings, synth settings, FX, and sends, inputs, MIDI Channels (if applicable)?
  3. This I have to concur with. (Same goes for timings, but that's a story for another thread) If the velocities are varying a bit too much , I do a compression of the values. My Studioware panels has a slider for this as well.
  4. As per title. The “Cut Track”, “Copy Track” and “Paste Track” option could be presented in the right click Track menu (just above “Delete Track”) This would make it sleeker and easier to copy and paste a track to another project. Currently, we have to save a Track Template, and then copy the track data to the clipboard. Then we have to insert the Track Template in the destination project. Then paste the track data from the clipboard to the new track.
  5. I am not sure how feasible this would be, but as per title. Maybe even include the option to include track automation data. If this were possible, then MIDI Track Templates could also include synth initialisation event, like volume, pan, filter , resonance, etc. It would also be a more efficient way to transfer tracks (including data) from one project to another.
  6. You could zero them all with the transform tool first, then raise them to the value you want them to me. Personally, to set velocities to the same value, I just use one of my Studioware panels that lets you set all selected velocities to the value set by a vertical slider...... It's reasons like this that I wish the bakers would bring back Studioware panel creation in Sonar 2025.
  7. Which OS? Is it fully patched (updated)? Are you using a VPN? Have you turned off your antivirus? How exactly are you installing Cakewalk by Bandlab? (If you’re trying with Bandlab Assistant then stop! Download the Cakewalk installer from this link https://downloads.bandlab.com/cakewalk/setup/CakewalkSetup.exe What else have you tried so far?
  8. Transform tool, Cal Scripts or line tool over the velocities.
  9. .....and enter lyrics that are synced to the notes..... (my only use for the staff view for 30 years)
  10. Are the MIDI Channels of the MIDI track of all those instruments tracks set to a MIDI Channel other than “None” What VSTis are you using? A little more information goes a long way. I do this all the time, never had an issue.
  11. I am so glad I do all my MIDI editing in the PRV.
  12. Can we please have the following editing options for automation lanes. · include a Transform Tool similar to what we have for Controller Lanes in the PRV. · Flip vertically. · Flip horizontally. · Scale vertically (Anchor being the centre between the highest and the lowest). · Scale horizontally (Choice of anchor being the first or the last node - or hold CNTL the use centre as anchor). · Edit the contour of the curvature of non jump nodes - or drag a linear up or down to convert to curve.
  13. In Sonar 2025, MIDI Chase includes Aftertouch Events. In CbB, MIDI Chase does not includes Aftertouch Events.
  14. A CAL script would not be able to do this. There are no CAL script commands to export data other than to save as a MIDI file. @sadicusI would export to MIDI, then use GNMIDI to convert the file to ASCII text.
  15. Promidi

    General error on save

    Please define “a usb controller”. Probably need other information as well - like is this “usb controller” also configured as a control surface?
  16. Promidi

    Audio to MIDI

    Manually, Note by note, effect by effect, event by event (including CCs). It's the only way, really. (yes, really).
  17. 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).
  18. 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.
  19. Note: Requires Full Retail Version of Kontakt.
  20. 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.
  21. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html
  22. 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.
  23. 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.
  24. 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.
  25. I hope you’re right. I still would not risk it.
×
×
  • Create New...