msmcleod

I find that the selecting the right detection algorithm can affect the sound quality greatly. Try changing the correction algorithm and see if it makes a difference.

Wow, that's strange. It works perfectly for me on Audio FX, MIDI FX, and Instruments. I guess it's possible %APPDATA%\Cakewalk\Library\Library.db has somehow got corrupted. How.... I've no idea. However, if you come out of Cakewalk and rename Library.db to Library.db.bak, and restart Cakewalk it should recreate it. I'm guessing that this might make your properties dialog re-appear. You can always rename it back if it doesn't. CORRECTION - renaming it back doesn't restore the layout

You can use CTRL + click to select multiple plugins in the browser, then right click to assign them all to the same category. Also, the category is not just a drop down - you can type into it to create new ones.

I tried out various Fostex & Tascam 4 tracks at the time, and I've got to say the Yamaha MT1X for me beat them hands down with fidelity (this was before the MT2X came out). The choice of cassette was pretty vital too - Maxell XLII's were matched the best for the Yamaha (I see you're using those too). The guitarist I worked with would record his parts live, mixed with my sequenced drums, keyboards & bass (Alesis SR16 / Roland CM64 sequenced in Music-X on an Amiga 500) to 2 tracks. We'd then use the other 2 tracks for vocals & additional guitars. I recorded tonnes of stuff on my MT1X that way... hardly anyone believed they were done on a 4 track with no bounces!

That looks like an old MT1X. I had one of those, and later upgraded to a MT8X which ran at double the speed. The increase in fidelity was significant. And when you consider that it was using half as much of the tape width for each track, that's saying something.

Awesome - thanks Noel. I don't use the app that often (partly due to the slowness), but this will certainly make it much more usable.

Good point.

The plugin browser layout equivalent of the *.pgl files is %AppData%\Cakewalk\Library\Library.db which you can copy between your desktop & laptop.

For the most part, you don't actually need the Plugin Manager: Manual scans can be done from Preferences->VST Settings Plugin properties can accessed be via the plugin's VST2/VST3 dropdown menu The plugin layout can be changed via the plugin browser by right clicking on the plugin The only thing you really need the Plugin Manager for is excluding problem plugins, but I'm sure the CbB devs will provide an alternative way of doing this before removing the Plugin Manager.

We've been discussing this in another thread. I found this to be worse than 4.2.0. I've found that once I set my default detection algorithm in 4.2.0, it remembered it and worked fine even after rebooting the PC. In 4.2.1 however, it consistently hangs cakewalk when dragging an audio track on to a MIDI track. The workaround is to create a region FX and manually select the detection algorithm. It'll then work for the rest of the session with that project.

Yeah, I've got 4.2.020 on my main PC, and 4.2.103 on my laptop. Both versions are quicker than 4.1.1, but not as stable.

You're probably thinking of OMF.

No, it's not a big issue for me. Maybe the OP has other reasons for needing to use it.

I upgraded to 4.2.1 on my laptop yesterday. The 4.2.1 update consistently hangs Cakewalk when dragging an audio track on to a MIDI track, unless I've previously created a region FX and selected the default detection algorithm. On my main PC I'm still running 4.2.0. So far I've had to set the default once with 4.2.0, and it's remembered it ever since without issue. I'm running the Editor version, with a default of Polyphonic Sustain.

I used to use it to switch 32 bit plugins to use JBridge instead of bit-bridge, and exclude certain problem plugins. Nowadays I find it quicker to edit the registry directly.

yeah, on reflection I think Kylie is better.

Or Carlton maybe...

I've not really used overwrite mode much, I mostly use sound-on-sound or comping. As keyboard is my main instrument, for keyboard parts more often than not I'll just CTRL+Z and re-record if I'm not happy with it. For guitar, I'll use sound-on-sound in the way I've described in earlier posts. I'll keep on playing takes and pick the best one. If I don't get a good take after around 30 odd takes, I'll give up and start comping manually. Drums is my weakest instrument, so I'm more likely to use comping. I've occasionally experienced the waveform not displaying. I've not worked out what causes this yet - it might be the zoom level combined with the scroll lock setting perhaps? Maybe some-one else can enlighten us... Personally I don't pay much attention to the display, as I'm concentrating more on playing. I just keep playing in a loop until I think I've got a good take.

I've just upgraded to the latest Melodyne (4.2.1.003), and the hanging issue is still there. The issue with the default algorithm not being picked up is intermittent. Sometimes it picks it up, sometimes I have to re-select. The workaround of creating a region fx first, then dragging to a MIDI track works; but if I forget to do this first, just dragging an audio track on to a MIDI track will cause Cakewalk to hang.

Thanks for the update notification ØSkald. Detection seems to be quicker on this release. Unfortunately it still causes Cakewalk to hang when dragging an audio track on to a MIDI track, unless you create a region FX first ☹️

You can send a WM_SETREDRAW message to the control's handle to turn updates on and off: https://docs.microsoft.com/en-us/windows/desktop/gdi/wm-setredraw But yes, it would be good if that was part of the CWnd class.

This method still works for me. I don't recall having to change the registry... although I suspect I changed it in Preferences before the option disappeared. The things I need help for are less well used ones, rather than standard workflow tasks (which usually means they've not changed since SONAR), so the fact that it's out of date hasn't been an issue for me so far.

For me it takes around 4 seconds to display 324 VST 2 effects, but clicking on VST3 instruments takes 8 seconds for only 7 VSTi's. Clicking on the DirectX effects comes back almost instantly. To my mind it must be doing more than that behind the scenes. Then again, it might just be inefficient code. For example, you can see the scroll bar handle shrink as the VST2 effects populate, almost as if it's responding to WM_PAINT messages as each list item is added (rather than refreshing the GUI after the list has been populated). This wouldn't explain the 8 seconds for 7 VST3 instruments tho. For me it's not the end of the world, but it is a bit annoying when it repopulates everything every time you alter the plugin options.

What MIDI interface are you using? I've found the cheaper USB to MIDI cables are extremely problematic. The reason being is that their internal buffer size is extremely small, so if they're overloaded with MIDI data they drop notes... and for sysex, they are totally useless. Bear in mind also that at 1:1:000 any program changes, CC settings (pan, volume etc) are being sent all at once. Maybe moving the start of your song to 2:1:000 might help.

Here's a sample of the preset from my D550: Soundfont format: D50Fact-028-Pizzagogo.sf2 Sfz : PizzagogoSfz.zip Note that there's no release samples, so you'll need to set the decay accordingly.