Robert Whitaker

19 hours ago, David Baay said:

Sounds like an interface driver issue that the port is getting closed on stop.  What interface, and what driver mode?

It's a PreSonus Studio 26c using ASIO.

18 hours ago, David Baay said:

Hmmm... yeah, forgot about that thread.  I would respectfully suggest it might be time to return that thing, and get an interface from a more reputable manufacturer.

It's not the MIDI driver or device. The problem exists with no MIDI device connected or driver selected.

3 hours ago, Chuck E Baby said:

Another thread he does mention he is using Windows 10

And using ASIO4ALL  Probably have better luck with WASAPI

 

That's not the problem. I removed the ASIO4ALL driver. I'm now using the ASIO driver for the device - PreSonus Studio 26c.

18 hours ago, Chuck E Baby said:

I believe this... MIDIPLUS S-Engine

No, It's it not that. Removed that device and the driver isn't even seen by Cakewalk anymore.

1 hour ago, Chuck E Baby said:

Depending on how you are monitoring, this is okay to have input echo on. I know personally I have it on each time I record audio tracks because I am monitoring Amp Sims, FX, guitar signals, exc as I record each pass. What I quoted from you above, is normal working situations for most of us.

Yeah I know it is okay, under many circumstances to have input echo on, in fact, I discovered this after my initial post. However, this seems like a workaround. Without input echo on, one would expect that, if the track is armed, it should accept input without having to dis-arm and re-arm. I'm new to CbB but previous version of Sonar did not exhibit this behavior.

Thanks for your help.

On 9/15/2019 at 3:27 AM, Chuck E Baby said:

Are you referring to the Input echo button or the record button itself ? and are you using "Comping" mode to record multiple takes per track ?

It does not matter if I am in comp mode or not. Here is a step-by-step.

I arm a track (the armed for recording button lights up).

I press record and the transport activates.

I press stop and the take is successfully recorded (the armed for recording button for that track is still it up) but the VU meter now indicates it is not receiving input from the instrument.

I press record and the transport activates.

I press stop but now nothing is recorded (the armed for recording button for that track is still it up).

Only if I un-arm the track and re-arm it between takes will it record each time.

IF I TURN ON INPUT ECHO FOR THE TRACK IT WILL CONTINUE TO RECORD EACH TAKE WITHOUT HAVING TO CYCLE THE ARMED FOR RECORDING BUTTON.

When I arm a track for recording in Cakewalk, I can record without issue. As soon as the transport is stopped, I need to un-arm and re-arm the track before it will record again. The indicator button still indicates the track is armed but it receives no input.

I don't want to have to cycle the arming of a record track for each take. Is there some setting I am missing?

43 minutes ago, Robert Bone said:

I went round and round with trying to figure out why Cakewalk or Sonar would not accept midi data from an external USB midi controller, and it turned out to because a friend of mine had accidentally unplugged my USB-connected audio interface, and after I immediately threatened him with bodily harm, he had plugged it back in to a different USB port on the back of the computer.

It took me forever to figure out this had happened, because the midi controller was plugged into a USB on the front of the computer, so I knew IT had not been moved, but it didn't occur to me that he had used a different USB port in the back of the computer for reconnecting the audio interface.

I know you are dealing with midi output - but am wondering if this sort of thing might have happened to you, because Windows internally renumbers USB devices - not by name, so even if the name of the device is the same, in Cakewalk Preferences Midi Devices, it might be known to Windows internally by a different identifier.

Try going into Device Manager in Windows, under Sound, Video, and Game Controllers, then clicking on View and checking the box for showing hidden devices, and see if there is a faint icon on a 2nd entry for your midi device.  If there IS, then it was plugged in, at some point, to a different USB port.  Plugging your midi device into where it was previously connected might help it work again.

Bob Bone

 

Cakewalk is interacting with the USB device in that it accepts input from it and output if I power cycle it as described above after launching Cakewalk. It's a new laptop and I have always used the same USB port for the device. Thanks for the tip though.

I found an inconvenient workaround to get it to work...

- Launch Cakewalk.
- Power cycle the midi device.
- Open Edit/Preferences/Midi Devices, deselect the midi device and select the Wavetable Synth. Apply.
- Open Edit/Preferences/Midi Devices, select the midi device, deselect the Wavetable Synth. Apply.

At this point IT WORKS. I can open and close multiple projects and everything works. If I close and re-open Cakewalk it reverts to non-working again. I must complete the steps above to get it to work again.

So why is Cakewalk killing the sound at startup? Why must I go though the steps above to restore it?

1 hour ago, CJ Jacobson said:

Try de-selecting the Microsoft GS Wavetable and that may solve your issue

Try a different USB cable & What external hardware sound modules are you outputting to? 

I have deselected the Wavetable Synth. The hardware module is a MIDIPLUS S-Engine.

6 hours ago, David Baay said:

I'm using a GM demo file as a test as I can see the VU meters in the tracks responding, so velocities are okay, and I can see the Midi Input/output activity on the task bar indicating activity.

All midi files and Cakewalk projects exhibit this behavior, even if I create a new project.

I have disabled the Wavetable Synth and have it deselected everywhere.

Here is the most telling symptom: I can put the midi device in drum mode where it generates midi signals internally. It works fine until I launch Cakewalk which kill all volume even the though the midi device continues to generate signals. Even once I exit Cakewalk the sound is still muted. In order to get the sound back, I have to power cycle the midi device. When in Drum mode Cakewalk records the midi output from the device perfectly put I cannot hear it while it's recording nor when it's played back.

It seems clear that Cakewalk is sending some sort of signal to the device that is killing the audio output from the device because everything else behaves as expected.

No matter what I do I cannot get CbB to output to a USB midi device (MIDIPLUS S-Engine). All the proper outputs are selected but I simply cannot get any sound. Sending the the Microsoft GS Wavetable Synth works perfectly. I can get output to the USB midi device via other midi players. This is infuriating. When playing in Cakewalk, Windows indicates midi output activity but no signal is reaching the device. I'm not new to this. I've been using Cakewalk/Sonar since the DOS version. Any clues?

I think I have this one solved.

I had to install Asio4All driver. The default audio driver was causing the problem.

I've been using Cakewalk/Sonar since the DOS version however, I cannot get Cakewalk by BandLab to run on Windows 10. When I open the program, the blue circle cursor just spins. I cannot start or start even a simple midi sequence. I can open menus (with a slight delay). I uninstalled all my antivirus, disabled the plugins. Nothing. No error message. I just cannot get it to work. Has anyone else experienced anything similar?