Jump to content

Promidi

Members
  • Posts

    4,168
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Promidi

  1. Have you searched your entire hard drive for a file called Alesis.ins. That file contains an entry for the Alesis SR 16 On my machine, pretty much every version of Cakewalk (right up to CbB) comes with this file.
  2. Did this project contain any audio that you recorded or is this a MIDI and VSTi based project? If it contained recordings, then the audio folder may contain the actual audio of the recordings.
  3. That's the meaning I got from it as well. I do many MIDI only projects myself and when I am working on these projects, Cakewalk's audio engine does not run.
  4. They are more likely to if you lodge a support ticket (with steps to reproduce). https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633
  5. Have you left ripple edit on by any chance? Note: when you say "still using the same CbB", which version exactly (numerically) are you using?
  6. Midi files will only contain the MIDI data itself. Any data pertaining to specific Cakewalk features (such as their assigned track outputs) will not be saved in the MIDI file. What you need to do is save the file as a Cakewalk Project file or CWP. Unfortunately, this CWP file would not be readable by the PSR-SQ16 You will probably have to have two versions of the edited files - one on the PC as CWP files and other as MIDI files (probably back on the floppy disk).
  7. Have you done any "Daw PC" optimisations - you know.... disable power saving everywhere you can Disable C-states, speedstep snd put CPU min/max at 100%. All of that stuff
  8. According to the Cakewalk user guide, it maxes out at 16. The manual does not indicate that this can be increased.
  9. Are you able to find 64bit versions of the problematic 32bit plugins. Are you able to give Jbridge a try? https://jstuff.wordpress.com/jbridge/ Personally, I have banished all 32bit plugins from my PC and only use 64bit plugins.
  10. What you could do is write a cal script to go to the measure you wish to go to and then map a keybinding to it. (Don't use W as that is reserved and can't be used for anything else. Here is the code to go to measure 5 (but can be any measure - just change the 5 to any measure you like) (do (int measure 5) (= Now (makeTime measure 1 0)) )
  11. I have had this happen on my PCR-800 as well - this time it was the pan control sending out random CC10 events. I fixed it with a dab of electrical (non lubricating) contact cleaner in the slider... In the OPs case looks like something funky going on with the ACT drivers (or whether you use)
  12. Whoops, my bad...... I just copy and pasted the OP......
  13. For the track exhibiting this issue, open up the event list and look for "Pitch Wheel" events that occur before any notes start. For Example:
  14. Have you checked for any non zero pitch bend events in any MIDI tracks that are routed to the VSTs?. Best way to check this is to use the event list view (and maybe apply a filter using the event manager)
  15. I've given up on using drum maps for MIDI files because if I do use them, I no longer have access to NPRN parameter names (as defined in instrument definition files) via the controller lanes. Yes, I still use a hardware module. PRV with the drum piece names on the PRV keyboard is much easier for my work flow.
  16. I am suspecting the "Fit to time function" would be useful here. It can do this by adjusting the tempo but keeping the tempo changes intact.
  17. Then the CC events will be in the saved MIDI files. Even if I wanted to, I cannot deliberately make Cakewalk strip the CC events on save to MIDI file. It just never happens. Maybe you are in a parallel universe where the normal rules of physics do not apply..... Can you create a file with CC events in and save as a MIDI file and then attach it so I can have a look at what you end up with?
  18. That has never happened to me. Even if you originally used an automation lane to enter the MIDI events, the resultant MIDI will still have them in the file. If you open the MIDI file, the CC events would now be visible in the Piano Roll View or Event list view. The CC events would no longer appear in an Automation lane.
  19. Exactly which version (numerically) of Cakewalk are you running?
  20. Before making changes, File | export < this creates a backup of this specific registry key. In "edit" drop down, select the entry you wish to delete. Change "Update Registry" to "Yes" Press "Delete" - (this only appears when you Change "Update Registry" to "Yes")
  21. You have not mentioned which iteration of "Cakewalk Sonar" you're using, so I have assumed Sonar Platinum. The exact location depends on the particular iteration of "Cakewalk Sonar" you're using. The "TSSSEQ.INI" file is located in the following folder, depending on iteration (Copy and paste rather than typing it) Platinum: %appdata%\Cakewalk\SONAR Platinum Professional: %appdata%\Cakewalk\SONAR Professional Artist: %appdata%\Cakewalk\SONAR Artist Cakewalk by Bandlab (Which I recommend you start using, BTW) %appdata%\Cakewalk\Cakewalk Core Note: you might want to rename (which cakewalk closed) the file rather than deleting it.
  22. If you are using ASIO driver mode, then the Windows sound subsystem is completely bypassed. This means that any Windows sound adjustment (Including volume) has no effect on the output. This is by design.
  23. Promidi

    Cakewalk.ini

    For possible entries, see: https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=INI_Files.4.html
×
×
  • Create New...