Jump to content

billp

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

6 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So far that's proven to be a black hole.
  2. I'm not sure what the proper protocol is for getting this issue resolved. As I expected Win update had no effect. I have several minidumps (and many more "poof it's gone" experiences) all pointing to Cakewalk.exe, all address exceptions. These seem to be occurring under a variety of circumstances, but very frequently copy/pasting midi in PRV, the latest when I had just opened the project, selected, copied and pasted. Although I've had my share of blowups over the last 20+ years, this has reached a new level. My machine specs are in the original post. I would really appreciate it if someone could point me in the right direction.
  3. Thanks Mark. It's been awaiting restart since early today. I'll give that a try.
  4. Recently I've been plagued with address exceptions (c0000005d). They occur mainly in Cakewalk.exe but occasionally in the kernel. There is no particular sequence of events or project that causes them. They usually occur after a period of midi editing in the PRV. Since the crashes are happening so often, I've set the ErrorDetectionLevel to 7 and have been able to capture a few mini dumps when CbB doesn't just disappear, which also happens. Does anyone have any suggestions on where I might look for self-induced problems? Here's some background: Projects usually have 3-4 instances of Kontakt with a few VI's in each, between 10-20 midi tracks on average. CbB normally uses about half or two thirds of my 32GB of memory and maxes out at about 15-20% CPU per task manager when the projects play. I'm up to date on Windows updates, drivers, and firmware. Memory has been checked and is sound. Latency monitor has no complaints Specs: A nice little machine built by Jim Roseberry Windows 10 Pro x64 Version 10.0.19042 Build 19042 Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz, 8 Core(s), 16 Logical Processor(s) 32GB RAM RME Babyface Pro @2048 buffer size
  5. I'm using it successfully. Did you try using both the VST2 and VST3 versions? You may need to go to preferences > VST settings and uncheck "Hide related VST2 plug-ins" in order to see both.
  6. I get the same result as OP. When focus in PRV is on a single track and no track is selected in track view, and I select a single midi note in one track in PRV, Shift+Alt+F6 selects all tracks, including audio and instrument tracks, and any notes, audio, and other events to end of all tracks.
  7. billp

    change vst path

    Open the plugin manager from the Utilities menu Click Options button Add the new path to the path list Click the Re-scan existing plugins checkbox Click OK Click the Scan VST Plugins button
  8. Since no one has replied yet, here's an off-the-wall possibility. If you are creating the new project from a template and the template, by some quirk, happened to have an offset in "Time+", you could experience this. I don't think the offset affects recording, only playback.
  9. I could see how disabling the tempo could be useful if the entire work is midi, originally played to or entered against a fixed tempo, say 100bpm, and properly aligned (beats/measures). If tempo changes are subsequently introduced to simulate rubato, fermati or ritards, for example, you could conceivably disable the tempo map and the piece would play at the initial tempo straight through still properly aligned and you wouldn't have to contend with subtle tempo changes while playing. I do manual tempo programming, since all my tracks are midi. Sometimes it would be handy to disable it.
  10. I've used it but not in the way that you propose, but I believe it will work. You can establish the low and high range of values on the input and output sides separately for selected CC numbers, in your case CC7 for both input and output. The entire range of the incoming and outgoing values will be limited to the specified ranges. It proportionalizes the incoming range. For example if you allow the full range on input 0-127 and then constrain the output range to 0-80, setting the input to 31 (25%) would produce an output of approximately 20 (25% of 80). You also need to disable the option (checkbox) to send the original value. Otherwise you get both. This option is used when you translate the incoming CC, which this plugin also supports. I've also found the Port Diagnostic tool very helpful, also on the Ten Crazy site. It allows you to see the midi traffic. I'd put it after the CCMap.
  11. If I understand what you want to do, the "CCMap" midi plugin from TenCrazy might work for you. It allows you to set the range of values that a selected CC will produce. It also allows you to translate the CC (e.g., change CC1 to CC11), although I don't think you need this feature. Here's the link to his page of plugins. They're safe...I've used them for several years: https://tencrazy.com/gadgets/mfx/
  12. Yes it has been a problem since I returned to CbB. It's only an issue when the inspector is on a buss and I select a track using the PRV track pane. It's not an issue in track or console view.
×
×
  • Create New...