Terry Kelley

"Calling someone out" is generally taken as a challenge and in a negative light. It's just one of those perceptions. "Calling out" is pointing something out. Welcome to English - the most dysfunctional language in the 8 planet alliance!

I have to run at 2048 during playback/mixing but during recording I turn off the effects (FX button). I turn them back on when finished recording. Turning off PDC (just below the FX button) also appears to affect the delay too but it's subtle so I am not so sure. IT doesn't hurt anything during recording. Switching the buffer while in CbB periodically makes my audio engine freak out so I prefer to leave it alone. I assume it's something with Presonus. I asked for a feature /switch in CbB to automatically turn off FX during recording and flip it back when done. I don't expect it to be implemented but I think enough of us have to turn them off to stop the delay so it would be convenient (but not critical.) As an aside, check your processor/GPU cooling. I had a problem with things starting out fine but crackles and pops would creeping in after a few minutes. Turns out my fan and heat sinks were dirty/dusty. I clean them once a week now and it solved that particular problem.

I wonder if this is why I have this same problem. I use automation a lot. I too find that the midi track volume will and won't work. I never understood why.

That method is common for analog inputs but for midi, it won’t solve the delay. I have to turn off all effects and PDC to kill the delay. There are ways to reduce it but not to zero without killing the effects ... at least for me.

Pitch Proof is good and there is GSnap.

Do you have an effect on your main out set to a low output volume? Like the LP64 Multiband?

I use this feature especially on drums EZ Drummer where I want the effects on one sound different from another. Same for the TTS-1. Otherwise I select the first synth out and it all goes to a single stereo output.

That's how I do it. I can add various controller stuff over the top of the midi notes. I use it a lot for pitch bend and Leslie speed. However I use automation write/read for a lot of effects like echo, delay, reverb, etc.

I constantly have to kill the process via Task Manager to get it to start again.

Tried that too. It will scream through the export in seconds creating short empty waves or with a few spikes. I can select all, select none, select some, doesn't matter. Sometimes I can just do it again and it will work but more often than not I have to close CW and do it again. That always works. Others have mentioned the same issue. On the other hand, I had to export several specific waves from a file and it never missed a beat.

I don't need it fast, I need it to work consistently. The various suggested tweaks to various values didn't work. It fails maybe a 1/4 of the time so it's only an annoyance. I do use a ton of plug-ins so I am not surprised it takes a bit to render and export. I do have the BounceBuffer set to 30. I'll try raising it and see what happens. Thanks!

Faster than the length of the song but a minute or so for a 4 minute song is about what I see, assuming it works. Occasionally it will do it in 10 seconds and the file is empty. I have to restart Cakewalk to get it to work.

Good thing I have no talent.

And now on to the airing of grievances and feats of strength!

Sorry Noel but TTS is being a brat. It taunts me ...

Or pin it when it’s open to keep it open. It’s a pushpin icon on the top right of the Plugin window. I like that they close automatically now and use the pin to keep specific ones open.

I chose bad wording. I didn't mean there are known issues you are working on but rather you are working to solve CbB issues specifically and some are quirks from Sonar. However, our issues with the TTS-1 plug in is an example were a CbB problem project will work in Sonar. I now have three other people that have confirmed it. And once a project is created with a crashing TTS-1, it appears nothing will fix it. I am clear that your team doesn't have access to the source code for TTS-1 which is why support declines to address tickets. It's just a really weird and frustrating issue. That said, while I started with CW back with Greg's DOS version, I am using a totally free program that blows away everything from the past. Every dime I spent has been returned to me with CbB. It is far more stable than the past versions (like Sonar). I am truly grateful to the team for this. Free and works great. But I still want to roll up a newspaper and beat TTS-1 about the head and shoulders until it gets in line. And Merry Christmas to everyone here and the Bandlab team!

For me, I have to run my Presonus iTwo box at 2048 to avoid crackles but also disable all effects (FX) when I record to stop the delay. On a side note, make sure your CPU isn’t overheating and slowing down. I use a laptop and was getting crackles as it warmed up. The heatsink and fan were pretty dirty. Drove me nuts for a bit. There are many CPU temp apps out there and it’s worth checking.

I wonder why ...

This is one of several things that work in Sonar but have issues in CbB. But they are working through them.

Well, well. Sonar 8 plays the file fine. What does this tell me? Not a d&^% thing! Update - The file crashes on my buddy's CbB and works on his Sonar 8. There you have it.

For $15, I'll tolerate it. But back to the TTS.

Reading about this. Sounds interesting. And no iLok! Well, after saying it doesn't use iLok, it does.

Still working on this. There appears to be nothing I can remove or change to make TTS not crash on it's first note. I've removed all effects and all other synths. I've messed with as many settings as I can. I know the config file contains many more but not all are intuitive on what they do. But this makes me think (similar to Mdiemer) that it's something inherent in the project now. The crash is a memory access violation. The TTS-1 dll is either sitting somewhere it shouldn't or Cakewalk is accessing memory it shouldn't thinking the TTS is there. As long as no notes are triggered, everything is fine. File lock? Maybe some other app sees the TTS and is locking it? I'm just guessing. I will start from scratch building a new project to see if I can get it to crash at some point. Where's Codeview when I need it! Yes, I know, don't say it. Edit1: Freezing the TTS will make it crash. No notes needed.

I did check out Project Scope and noticed the problem project shows a Matrix Data track and a No Name track as 22 and 23. My project has no 22 or 23. I don't know if this means anything. The instant TTS has to play a note it crashes. 022 Matrix Data Track MIDI 023 [no name - track nn] MIDI