Promidi

When the Whois information for a given website redacts a lot of the registrant information, I take it with a grain of salt the size of the Rock of Gibraltar

At some stage, I did end up with a corrupted installer. (when I tested with Chrome’s resume function) However, I did not know that is was corrupted when I chose the “quick clean” option during the installation. As the new versions would not install, losing all my Melda plugins was not fun. Thankfully my daily backup includes all VST2 DLL and VST3 VST3 files. (which I used to restore to previous) I can see how this can bork a Melda install....

I do not even get a completed 16.08 installer..... There is another person on the Melda forums with the same issue I am having. As a test, I downloaded the Nvidia drivers (which is even larger than melda 16.08). They came down fine. It’s definitely an issue at Media’s end.

Is anyone still having issues getting a download of 16.08 on Windows 10. I've tried 3 PCs (2 win 10, 1 win7) and a mobile device (latest brave on Android 13.) 16.07 downloads ok. 16.08 does not. I get an HTTP 416 error at around 603meg in to the download with 16.08 16.07 completes correctly.

Make sure all MIDI tracks and SITs are set to specific MIDI channels and specific MIDI controllers. Only enable MIDI outs on VSTis that you actually require for your project. Avoid OMNI.

Every single time, or can it work sometimes and not others? Note: I was able to add 3 instances of Mixbox Full, each with 4 slots filled into an existing project. The project has 3 instances of AAS Chromophone 3, 1 of AAS String Studio V3. 1 UVI (World Suite 2). 1 Massive X. 1 Arturia OP-Xa. Project played through to the end. This is on a PC configured as below.

Select the track containing the Sustain Events (CC64) Then go Menu > Edit > Select > By Filter. At the By Filter dialogue box, deselect everything (click “None”) Select controllers then set Number min and max to 64 and click OK Once you have done this, only CC64 events will remain selected. Then you can use the Event Inspector to change the MIDI Channels of those selected events.

Are you absolutely sure there are no patch/bank change MIDI events at any time stamp in any tracks in your MIDI files? Use Event List View to check this.

Is it possible that you have CC64 events in the track that are set to different MIDI channels? Each set of CC64 events on a given MIDI channel will have its own controller lane. What you might want to do is select all CC64 events in the track (Use select - by Filter), and then set those events to the same MIDI channel. You can use the Event Inspector to do this quickly. On a side note, I set MIDI tracks to specific MIDI channels. I also set RechannelMIDI=1 in the cakewalk.ini file. (also can be added in Preferences - File - Initialization File (Advanced)). This is so that when I bounce MIDI clips in a given track, all of the MIDI events of the resultant clip get their MIDI channels changed to match the MIDI channel that the MIDI track itself is set to.

Worked first time here. Have you tried from UVI directly? https://www.uvi.net/my-products#PRO376

Not a clue. Not enough information.

Same!

Model D German Concert Grand is also updated.

Hold ALT while selecting a bus. All tracks that are routed to that bus will also be selected.

I am confident that your Focusrite Scarlett Solo will solve the latency issue (as long as you use the Focusrite supplied driver). When you were using onboard audio, what you were really experiencing was “audio” latency, not “MIDI” latency. I have a configuration as per my signature and I do not have any perceivable delay between key hit on the PCR-800 and sound from any given soft synth.

Which is it? One track (“...same track”) or two tracks (“both tracks”)

You might want to consider upgrading that to a 500gig.

Run UVI Portal to update. Or log in to your UVI Account to download https://www.uvi.net/my-products#PRO399 Changelog 1.1.4 ------ - Fixed potential playback issue on first step when re-triggering sequence.

Define “small SSD boot drive”

You need to set up a MIDI track that has the Digital Piano as its input. Then you need to route that MIDI track to a VST synth. Then you need to route the audio track associated to that synth to a Bus (preferably the master bus) That bus needs to be routed to your output device Hopefully you have a USB audio interface that comes with its own native ASIO drivers. In Cakewalk, what VST synth are you routing the MIDI from the Digital Piano to? What audio interface are you using?

Not really much to g on here. Could be any one of a million things. What else have you tried so far? We need more info. See my signature for the type of information needed.

See: https://www.izotope.com/en/products/ozone/features.html#comp

When adding a send (In the inspector), while the Send Menu is up, on your PC keyboard, you can press the first letter to jump to the item you wish to select. IE, press “R” and it will jump to the first item starting with “R”. You can also bind a key combination to the “Insert Send Assistant“ - the menu there also behaves as above. (press first letter to jump)

What happens if you try this. In preferences | Audio | Configuration File try adjusting the following: EnableSetThreadIdealProcessor = False MixThreadCount = {number of cores minus 1} You might like to exit Cakewalk by Bandlab, go to the following folder and make a copy of the AUD.INI file before doing this: %appdata%\Cakewalk\Cakewalk Core

What happens if you disable C-States and speedstep (maybe called IEST - (intel enhanced speed step) in the BIOS?