scook

Region FXs read the raw data from the clip. Melodyne in a track or clip FX rack require the data be transferred into the plug-in. Any processing that occurs before the Melodyne plug-in is ignored after the transfer. Once transfered into the plug-in, the audio originates from the plug-in and not the audio clip(s).

Something to consider Opening a MIDI file sets the project tempo to the tempo data in the MIDI file. Importing a MIDI file strips tempo data as the program loads the data into the project; the imported MIDI data will run at the project tempo.

To me the wav files look too small so there appears to be a problem with how the audio files are being created. They may even be text files containing error messages. I have seen BandLab Assistant create error messages instead of the files expected when trying to download CbB. The name was correct for the installer but the file was a 1KB XML error message.

Just remember EA2 only does File > Open for .midi. There is post EA2 fix for import.

Or move the VST3 plug-in out of the scan path if you still want to hide other VST2 plug-ins that have working VST3 versions.

I can find no reference to a Sonar 8 Home Studio. The last numbered Home Studio version appears to be 7. Can't say for sure because I only worked with the XL, Producer and Platinum series. There was a SONAR 8 Studio. It was never available as a download. There was an upgrade download available for SONAR 8.5 but it required SONAR 8 be installed before using the upgrade installer. AFAIK, X1 was the first full version of SONAR available for download. The oldest version of SONAR I have installed is X2 and that plug-in was discontinued by that time. So, I do not have it installed. Pretty sure the Cakewalk tuner was a 32/64bit DX plug-in. If the projects were created using a 32bit version of SONAR, the tuner will not load in CbB. There are a variety of tuner plug-ins free and paid. There is a tuner in TH3 which is bundled with CbB. As mentioned above MeldaProduction offers a free one. GVST is another source for a free tuner.

The Pentagon problem is strictly a registry issue. The program was never modified to allow for security changes made in Vista.

All MeldaProduction plugins have been updated to 14.07. It is an important update which comes up with several improvements, new features and fixes. The update is free as always and you can install it simply by downloading and using the newest installer from our download page. List of changes for effects List of Changes for MSoundFactory List of changes for MPowerSynth List of changes for MDrummer

It appears the only operation that works with .midi files is File > Open. All of the import methods fail with the "Cannot fine or open file" error.

Try calling up the HUD with the shortcut "T"

Click the mouse wheel in the clip/track and change the edit filter in the HUD

If Pentagon is visible to CbB there is no need to mess with regsvr32. The plug-in is registered. This happens with all bundled DX plug-ins at install time. The typical problem with Pentagon occurs when trying to add it to a project The fix is to give Users "Full Control" in HKEY_LOCAL_MACHINE\SOFTWARE\rgc:audio Software\Dxi\Pentagon I as shown in image above There is no need to mess with anything else. Alternately running CbB as administrator works too but changing the one entry in the registry is all that is really needed. The last regsvr32 error seems to indicate the command may have been issued with no quotes around a path containing spaces. Like regsvr32 /u c:\program files\somepath\somefile.dll instead of regsvr32 /u "c:\program files\somepath\somefile.dll" Command line tools use spaces to parse input. To minimize these types of errors, I like to use regsvr32 in the folder containing the dll. But again. the usual solution to getting Pentagon working has nothing to do with regsvr32. That part is done properly at install time unless one receives the DLL/OCX error during install mentioned in the thread below.

There is an easy fix for this. It is a permissions issue. Right-click on HKEY_LOCAL_MACHINE\SOFTWARE\rgc:audio Software\Dxi\Pentagon I and give Users "Full Control" like this -

Here are a couple of alternatives to using the automation parameter menu. Using the plug-in UI - enable write automation, start the transport and manipulate the plug-in control to automate, stop the transport and clean up the unneeded notes. Using Assign Envelope - create an automation envelope for the first available parameter. It does not even have to be related to the plug-in. It could be volume or pan. Then right click on the envelope line and select Assign Envelope from the context menu. Select the plug-in and use the dialog to pick the value to automate. Even a long list of parameters is easier to scroll though in this dialog.

That is the first version with ARA2 support. It appears they do not update the site with every release since the first supported version.

Reads more like Melodyne is being loaded in the clip FX rack instead of using it as a Region FX. When using Meodyne as a Region FX the "A" in the image above points to RFX instead of FX.

Both may be unregistered using regsvr32 I am curious though, what is the problem with Pentagon I?

If you elect to use a MIDI input device (including the virtual keyboard) you need to make sure the notes being played are in the range of the instrument. A much longer thread on this subject was referenced in my reply to your original thread too.

This fallacy is so old it has a Latin name.

no

Cakewalk provides an option to "Enable MIDI Output" IF the plug-in has the feature. Many synths and most FXs do not send/generate MIDI data.

When using the same audio device for Cakewalk and Windows make sure both are set to the same sample rate and do not use WASAPI Exclusive driver mode if you want to share the device when Cakewalk is running.