parboo12

10 hours ago, pax-eterna said:

Firstly Pro channel (after the last update) now shows none of the standard Pro channel stuff, like the EQ etc, and whenever I try to load a module it crashes Sonar. Anyone else experiencing this?

 

Thanks

I think I've had this problem. I solved it by re-installing Windows and everything but I hope you don't have to do all that.

A good person from Cakewalk (I think his name was Mike)  wrote me a note with instructions, too late for me, and I can't find his instructions. I'll  continue to look for them, but it involved the Microsoft Visual C++ Redistributables.

One thing to try might be to Uninstall them all (make sure you write down exactly what you uninstalled) and install the same things from the Microsoft website ( https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads).

If it doesn't help, I would write the support and probably someone would give you a few more tips.

Let me know how you make out.

A couple of other things..make sure echo is enabled on both tracks.

And out of the box  ...middle C is the only key that works, on my system, anyway. You could try changing MIDI - Process, to Pass (top right area) and I would think that if the keyboard works, you're good. Change Pass back to Process to go back to InstaChord mode. You got to load some Presets and Press C3 along with C5 and play around pressing a low key and a high key at once.

For me, I found that the time it took me to learn this one would have been better spent on my keyboard skills!

Good luck!

Hi John. Open up 2 soft synths, InstaChord and another one (that you want to play the sound of).

At the top of InstaChord click the DropDown where it says VST2 and select enable MIDI out.

The input for InstaChord will be your keyboard instrument.

The input for your other instrument will be InstaChord (enabling MIDI out makes this possible). The output should be Master.

You'll probably have to read up a bit on how to use this, its kind of different. Good luck!

This very well could be related to the BIAS problem recently discovered by Noel and team, but clicking the track view interleave button a bunch of times on  a track with BIAS in the fx bin causes an Unhandled Exception error.

Backup advice will be heeded!

Thanks, all!

35 minutes ago, Gswitz said:

Put TH3 in the regular FX bin and enable it for midi input from the drop down at the top of the effect. Then route your midi from a midi input track to the TH3 output item. Then open the TH3 VST and use midi learn. Click the wah wah and choose learn, touch the midi controller then click ok on the midi learn. That's all you have to do.

Hey, it worked! Took a little bit of effort to find how to enable the midi input, but I finally found it.  And it works pretty good as far as I am concerned.

If I ever need a wah wah for any of my recordings I now know what to do! It beats using the mouse!

Thanks all for your info and effort.

Thanks for the info, Jim. I did uninstall both, re-installed just Cakewalk by BL to see if it would work...it didn't. I didn't delete the other folders it left, or look at the registry, though. Cakewalk techs suggested to uninstall and reinstall some Microsoft Visual C++ Redistributables, which I did, but no luck. At that point I think I had everything so screwed up, I figured I better start over. Hope I don't have the same problem again, but if I do, you might have some questions coming your way!

No, I think this one sends out data depending on where it is. It can tell if it's half open, etc.

Just was just fooling around trying to get it going to see if I could.

I got a set of Roland TD11 drums. I noticed TH3 got a bunch of midi stuff and was wondering if I could use the hi hat pedal controller for a wawa pedal, if I had to.

I had no luck, but I'm certainly no expert in this. If TH3 is not good, I got the scaled down version of TH2 too.

Anybody have detailed instructions how I would go about it, or is it possible?

Thanks.

In case anybody's interested in my solution... I got frustrated and wiped the computer clean ....again. I hope it sticks this time.

32 minutes ago, msmcleod said:

Right click->Properties on the folder, and click the Advanced button:

If you're still seeing the ProChannel on other projects, and more importantly the ProChannel modules, then its more likely your project is corrupt.

If you've had to do this more than once, I'd check and/or consider replacing your drive - it may be on it's way out... HDD's usually make strange noises before failing, but SSD's give very little warning.

Thanks Mark, for all the research and advice. Your're a great help around here! 

No, I didn't think I did any drive compression, and unfortunately it's more than my project, it's affected X3 also. I'm wondering if it's a registry problem.

Any good tests you know of to see if an SSD drive is bad.?.. it's probably still under warranty.

Hopefully you'll be rockin' out again soon, Christian!

Thanks, Noel!

3 minutes ago, msmcleod said:

Did you enable compression on your drive? If you did, this will be the issue.

The files within the C:\Program Files\Cakewalk\Shared Utilities\Internal folder must be uncompressed for the ProChannel modules to show up (assuming you've installed Cakewalk to the default location).

 

 

No, not knowingly, anyway. Is there a way to check?

I've lost my prochannel. Anyone ever have this happen?

Actually this is the second time it's happened in the past few months. The first time I just wiped my hard disk clean and reinstalled Windows 10 and Cakewalk (on top of Sonar X3).

Now it's happened again and I hope I dont have to go through all that. Already I uninstalled  Cakewalk and reinstalled it...no go. Sonar X3 acts the same way, so it must be something Windows related. I also tried the reset plugins.

If I try to add a module Cakewalk will crash..Fatal Error mfc140u.dll

I sent a mini dump to Cakewalk techs.

Any one have any ideas or a solution?

Using Focusrite Scarlet 18i8 with an i7-8700 with 16gig. I would think its a pretty clean computer, too, I generally keep it off the internet, except for updates.

Thanks for any help.

No one else can reproduce this? 

I can do it all the time on 2 different computers, 2 different interfaces.

You have to follow the above instruction EXACTLY, (that involves NOT having BIAS in your template). Has anyone tried the above instructions and had no problem?

And its not a very good error to have, you kind of want to rely on having your track being recorded by your DAW.

I have had this bug for quite a while and mentioned it before, along with others.

I have BIAS FX Std, BIAS Amp LE, and BIAS Amp2 LE.

It's pretty easy to reproduce. Just create a simple track template. From the New Project start with an empty project and add an audio track. Set your instrument input, and save it as a track template.

Start a new project, using your new template. Add any BIAS to the effects of your track and record a few bars. The wave graphics show and everything seems to be recording  normal. Hit stop and the recording has disappeared. Record it again and it's probably all right. It seems to be only the first time.
It doesn't seem to do this if you just start off with an empty project and add the audio track and BIAS, and if you save BIAS in your template you are probably OK too. So it's something different about the template track.

I am using a Focusrite Scarlet 2nd gen 18i8 with an i7-8700 16g, and also have used an A10 AMD 8g with the same results. Focusrite driver, Cakewalk, Windows 10 and BIAS all up to date. I think this problem has been around for a while, too. Sonar X3 acts the same way.
 

Quote

 

1 hour ago, Noel Borthwick said:

13 hours ago, msmcleod said:

I've just spent the last hour messing around with various settings.

One post on the Avid forum suggested it was Intel Turbo Boost causing it, but disabling it in the BIOS makes no difference for me.

I can usually make this happen reliably by quickly stopping/starting the transport repeatedly. It'll happen around 1 out of 5 times doing this when my usual ASIO buffer setting of 64. When it's set to 32, I get it 2 out of 3 times. Obviously in normal use, it's a lot less frequent than this - I quite often use a buffer setting of 32 for recording piano, and I can go several hours with it happening only once or twice in normal use.

However, I failed to get the motor-boating with a buffer of 128 or higher.

So I think the answer is to use a larger ASIO buffer, and if necessary use the PDC button when tracking. If you really need to use a lower buffer, then just accept the buzz might come along now and again.

[Edit] - It's worth mentioning I've only ever heard of this happening with the Scarlett interfaces. I certainly don't get this with any of my other interfaces.

 

Thanks Mark and Noel for your info and work. I appreciate that!

FWIW I noticed on page 305 of the Reference Manual about the Audio Engine Button. It says you may have better performance by shutting it off each time you press Play because there's usually some processing that's left over to take care of. I wonder if something goes bad in there from time to time.

There's been several threads in the forum about this.  I have nothing that would reproduce this, but if I'm using Cakewalk for an hour or two I consider myself lucky if it hasn't happened. It happens when you hit Play or Record. It just stops and buzzes until you hit Play again or Reset. It can be very annoying. Especially if the volume is up. Thanks for the info about the wrapper, Mark. I am hoping Cakewalk will fix it before I have to resort to other things!

Sometimes its bad enough and so frequent that I have to restart Cakewalk. I haven't seen it happen with anything else, but to be fair, I use Cakewalk most of the time. Hope you guys can figure it out!

Thanks.

Unfortunately, the buzz, or motorboat situation with the play transport is still happening.

I am using a Focusrite 18i8 2nd gen with a i7 8700, 16 gig, all drivers updated. Buzz has been with me for about 6 months now, I think.