SOLVED: "Mixdown aborted... pins are not connected"?

Hi folks-

I'm now getting this error from SONAR when I try to freeze an FL Studio Multi DXi synth:

"Mixdown aborted. The operation cannot be performed because the pins are not connected."

Does anyone know what this error means and what to do about it? Which pins aren't connected to what? And this just after I said on another thread how great this works! Honest, it works great when it does!

The mixdown seems to proceed normally (the waveforms gets roughly drawn), but at the end they're deleted and I get this message.

It works absolutely fine with the single FLS DXi synth version freezing to a single track.

I ran a forum search and came up with a couple threads which mentioned this error, but I haven't seen an explanation for it. I tried deleting AUD.INI and re-installed the FLS plug-in, but neither had any effect. I've re-booted a few times, too.

I'm running SONAR SE 5.0.1 with FLS 6.0.8 and the latest version of the FLS DXi .dll.

To troubleshoot, I started with a completely empty SONAR project and a very simple FLS project. I added just enough MIDI data in SONAR to get FLS to play back. I made sure that all of the inputs and outputs in SONAR and FLS are valid.

I've done this before with no complications, so I'm stumped. I've also tried it in SONAR 4.0.4, and I get the same error.

Thanks in advance for any suggestions.

-Susan

Hi 20x7-

Change gears. Bounce instead of freeze.

Also, try switching 64bit on/off.

Thanks, but there's not really anything to Bounce! In other words, I can't select a MIDI track in SONAR and a FLS Audio track that exactly correspond. The tracks are all complete in FLS, and when I did this before, I just selected the Freeze option in the Synth Rack view and it worked fine. I got separate Audio tracks for each FLS Mixer output. The only way I can avoid SONAR's "pins are not connected" error now is if I use the single FLS synth and output to one track.

I've never had 64-bit on, but I'll try that next.

What does "the pins are not connected" mean, anyway?

Thanks-

-Susan

Hi Geoff-

Well, that's about the only mention I've seen of this specific error, and I do have multiple monitors, so...

But then again, I really don't think that's it. I can try going with one monitor, of course, but then again, it's a SONAR-generated error, so they must have some idea what causes it, since they trapped it.

I logged a TS request; we'll see what happens.

Thanks!

-Susan

Everything that glazfolk said and...

Other like terms you can Google: directx directsound graphs pins filters.

I don't think they are going to be of much help.

Sorry,
20x7

I've run into this error before, but only with avi video files and never with Sonar. My suggestion, although its really just a guess, is if you are using WDM/KS drivers to switch to ASIO or the reverse if you are already currently running ASIO. My suspicion is it has something to do with the windows audio stack.

I've received this error when working with dxi's and vsti's once. Very frustrating. The answer for me was to delete the aud.ini file and let sonar rebuild it. Give it a shot.

ORIGINAL: Susan G

Hi all-

I get the same thing with the ASIO driver, and I had already tried deleting AUD.INI, but thanks for the suggestions.

Freezing works fine with the multi-VST version, but I much prefer using the DXi. I'll have to dig up the project I know it worked in & see if it still works & what if anything was different. Image-Line will be testing it tomorrow, too.

CW Tech support suggested raising the latency and I/O buffer and unchecking Fast Bounce. I still get the error. If anyone here could try it I'd be most grateful!

Thanks again-

-Susan

Hi Susan,

Ran into the same problem a while back - CTS advised me to raise the DiskRECBuffers or something like that to 512
They also indicated that my sample rate 88.2 might have had something to do with it - In the end I think my file got corrupted somehow because when I copied and pasted the audio files into a new project it finally worked - May not help you but worth a try - Good Luck

Very pleased to hear this, Susan .... now I hope that you'll have learnt your lesson and in future be scrupulously careful to keep your pins connected at all times.

Best,
Geoff

thanks for the update follow-up resolution susan
Glad to hear you are back in working order