Terry Kelley

I got a reply from the Munt developer: Munt VSTi supports MidiProgramNames feature set (getMidiProgramName, getCurrentMidiProgram functions) to send program names to hosts. But the host also has to support this mechanism. This is the only standard mechanism defined by VST 2.4 specification for sending program names to hosts. Unfortunately very few host supports this. The only one known by me is Cubase ... If there is something that can be done here should I move it to Feedback Loop? Or should I drop it.

Thanks Mark, that is what I suspected and appreciate you clearing it up.

If you have a VST that only shows 0 ...127 for the patch name on the midi track, is there a way to rename those numbers (or assign them) to patch names? I was playing with the Define in Midi Instruments Preferences and while I can create a list, I don't see where I could point the VST to use that list rather than the numbers. The VST is the Munt MT-32. The VST shows the names on it's properties screen but the patch in the midi track is always a number. Any input appreciated.

I have two SSD. The OS and all apps are on C. All music files, installers, docs, etc. are on D. I periodically do an image backup of C to D and also do a backup of D to an external drive. From that I can recover pretty much everything if one of the three die. I do agree that SSD's have a nasty habit of just stopping rather than complaining first.

Then I’m not from where I said!

Interestingly I watched the clock speeds and the noise started before the clock showed a change but I assume it was a delayed readout. For fun I swapped in an i7 and for the same temps I can drop the block to 64 but there is still too much delay so in the end it really didn’t solve the problem. The workaround is minor. Again, this isn’t the right machine for the job. But it’s fun trying!

One minor mod to an 8560p is to remove the RFI screen mesh over the bottom vents. Those restrict the air intake. I think at this point I am well outside the forums scope. Hopefully this information helps reinforce the need to clean fans and heatsink and the impact of block size on CPU temps.

I wanted to add some addition information. This is more relevant to laptops as DAWs vs desktops with large fans. Cleaning my heat sinks and fans on my laptop really helped keep the CPU from going into speed limitations but I would still get the occasional static and the temps would go north of 70C. But not all of the time. I was wondering if some setting was causing a problem with the CPU load since I mess with them a lot. The issue was the block size for the interface. With small sizes to keep the latency down (like 32/64/128) the CPU could easily keep up but the cooling couldn’t. Raising the block size to 256 or larger dropped the temps 10C minimum. The cooling just couldn’t keep up with the demand on the CPU. I added a fan under the air inlet and it worked fine but that’s not practical. One thing that doesn’t help either is the ambient temperature in the room is nearly 80F (yeah, I’m mixing units.) When it’s cooler here, the CPU cooling can keep up better. CPU heatsink compound is fine and not the issue. I have set the fan to 100% and it’s just not enough. 128 is right on the edge but the delay forces me to kill the effects or look-ahead. So at this point I just leave the block size at 256 and turn off all effects or look-ahead when I am recording. No noticeable delay on Midi and the CPU stays down in the 50C range. I have some pretty large midi/audio tracks and it keeps up fine. This laptop clearly isn’t the right tool for a DAW and someday I will go to something with cooling more in line with my needs. 😀 The laptop is an HP 8560p with an i5-2540M processor and 16gb of ram. The 8560p isn’t known for its excessive cooling! 😁 Awats

West central California near San Luis Obispo.

Thanks David, I agree that zooming out gives a rough approximation but it's still pretty busy. I've gotten used to the way it is but I was wondering if there was a setting that would collapse the clips similar to the old main screen on CfW. The old main screen allowed you to easily grab events without worrying about any grouping. I've made a couple of adjustments in View/Display that helps. Awats

It would be nice if we could get away from the overall black/gray background. It does appear unchangeable at this point.

Is there a way to get CbB to show the measure with events using dots the way the old TT Cakewalk for Windows did in the main screen? It was easy to see clear where events were. It made cut/paste very easy. Maybe I just don't see it in CbB? I know, "Go back to Windows 95 you infidel!!"

I'm running 1903 and have a couple of things that could have potentially need reactivation but so far everything works. Not a peep.

I like my Presonus M7 but I do have both M57 and M58's I can use. I can't sing so it doesn't really matter! I do prefer the sound of the M7 for my (lack of) voice.

I was thinking you could add two master buses, one with reverb and one with echo. The echo could feel the reverb. That way you can have reverb with and without echo. This assumes you want the reverb to be same either way.

I'm very glad they changed to this.

Whenever I need something unique I either add it to the track or set up a new feed/send into the main bus. I often have tracks thest have their own delay and reverb too.

I re-read your comment. I didn't try that. I'll check it out and see if a bounce will bring up the editor but I suspect I'll have to create a region. I'll let you know. Thanks for the suggestion!

I use them but only for my legacy MT32/D110 stuff from the 1900’s. Go Cakewalk for DOS!

Ah, that's interesting. I my case, the existing VV clips wouldn't open the editor. I have to create another clip to get it to open if I saved the song with Cronus disabled. . It's all working now either way. Minor glitch..

No worries. I'll bet it is better. I've seen the advertisement in CbB! I've used VV a lot and wanted to get it going. If I can afford Melodyne at some point I might consider it.

Right. So far there is a V-Vocal clip there that is pitch corrected but I can't edit it. The only thing I can do is select the region again which creates another clip and edit that. But it's a small price to pay.

Hi Scook, Yes, I have older versions so I have some options, but I can't go in and delete the V-Vocal clips - they ARE the clips now. Even though they are marked V-Vocal, they aren't. Not really a big deal now. I can go in and make any corrections I need. I am not sure why Cronus x32 was needed. I don't think I changed more than one thing at a time. I might remove it again and see what happens since I now understand why some do and don't work. Thanks!

Soanr or CbB? In CbB, I see it occasionally too. How long do you wait? But I've waited and saw it close in about a minute without intervention. No idea what is happening.

This involves Cronus (from outer space.) I have V1.5.1.0. Somewhere along the line I recall Cronus giving me issues so I did a shift-Open, removed it and re-saved. Bad move. Cronus is needed for V-Vocal. I don't see a way to add it back in after removing it. It shows in the DX folder in the Plug-in Manager but it isn't selectable to add as an effect. I do recall it showing up with parenthesis in the FX for a track (Cronus) when I started having trouble. Any file that was saved before I unloaded Cronus works. What I discovered, right or wrong is that I needed to install x32 V-Vocal in the Program Files (x86)/Cakewalk/Shared DXi folder. Why, I don't know. There is an x64 version in the Program Files location. I haven't tried hiding it to see what happened. Too scared, can't move. Any file where I saved it without letting Cronus load but using V-Vocal won't let me just click on the V-Vocal clip and open the editor, but I can create a region again and the editor pops up. I'll have to redo the pitch corrections but this time I will save them to a clip. Lesson learned, I am just not sure what it is. Something is afoot at the Circle-K. Side Note: I am going to try and re-register the DLLs.