Baffling TTS-1 problem

[smckee]

I see that others on the forum have had problems with TTS-1, but unless I've missed it--and apologies if I have--I have not seen anything quite like what I'm experiencing,   so I thought it made sense to start a new topic. 

I'm having the following problem with TTS-1:  When I press a key on my midi keyboard, I'll get a note as usual, but when I release the key, I'll hear that note repeated at a lower volume, then the note sustains indefinitely.  The midi information is recorded properly and plays back properly.  It's just the actual real-time playing of the TTS-1 that is wonky.  It does this with both my keyboard and CbBL's virtual keyboard.

Here's the real weird part:  I have a project in which TTS-1 is working normaly.  When I compare all the settings in this project with one in which the TTS-1 is wonky, I find they are identical.  I've painstakingly comparing everything--even parameters that should have nothing to do with midi.  I've looked at the midi data in the clips, and nothing is showing up differently in one project's clips compared to the other.  

I've updated both CbBL and Windows 10 a few times since this started happening.  I've deleted and reinstalled TTS-1.  I've checked the Microsoft website and my DXi software is up to date.   I've been back and forth with CbBL support and so far haven't gotten any helpful feedback.  

Does anybody have any idea what I'm overlooking?  Thanks for any input.

[abacab]

I'd start with adding your computer and audio interface specs. And any additional info about your Cakewalk and system configuration that could help someone to reproduce this issue.

 

[smckee]

Well, I've stumbled upon a strange fix.   I tried to "rebuild" one of my songs that was exhibiting the bad TTS-1 behaviour.  After a lot of experimenting, I stumbled upon this:

1. Duplicate track #1; in the pop-up, check the Event and Effects box, but uncheck the Properties box.

2. Delete the original track.

3. Save the project.  

Now all the tracks behave.  This does not work if I start by duplicating any track other than the first.  Also I have to delete the original track first before I start to mess with the project, otherwise, the TTS-1 won't behave.    I crashed the project once, but saving it right away seems to make it stable.

So unchecking the Properties box is a surely a clue...  I tried changing track properties first instead of duplicating the track, but no changes I made affected the TTS-1. 

Even though I don't know what caused this problem, or why my fix works, I'll tentatively call this one "solved".   

Thanks. 

Edited February 6, 2020 by smckee

[abacab]

Well the only clue that I see is that by deleting the track properties of the original track you have cleared the issue.

That implies that something in the original track properties was causing your issue.

Glad you got it solved, but am curious, how exactly did you create the original track?

[smckee]

10 hours ago, abacab said:

That implies that something in the original track properties was causing your issue.

Glad you got it solved, but am curious, how exactly did you create the original track?

Well, the broken project I chose to focus on was created in Sonar a while back, but it--and other older projects--were working perfectly in CbBL for a long while before things got weird.  I would always just insert the TTS-1, assign midi outputs to it and record midi via my midi keyboard.   I have yet to check all of my more recent CbBL projects to see if any of those are acting up.   Do you know of any "hidden" track properties?  I can't find anything in the track inspector of working TTS-1 tracks that is different from the non-working ones.   It's also odd that duplicating (minus track properties) the first track fixes all of them,  and that it only works with the first track of any given project.  Also, if I try playing the TTS-1 after duplicating track #1 but before deleting it,  the TTS-1 goes wonky, and won't fix even after I've deleted that track.   I'd be curious to know what's going on, but as long as my fix is permanent (time will tell) I'm good to go.

[abacab]

10 minutes ago, smckee said:

Well, the broken project I chose to focus on was created in Sonar a while back, but it--and other older projects--were working perfectly in CbBL for a long while before things got weird.  I would always just insert the TTS-1, assign midi outputs to it and record midi via my midi keyboard.   I have yet to check all of my more recent CbBL projects to see if any of those are acting up.   Do you know of any "hidden" track properties?  I can't find anything in the track inspector of working TTS-1 tracks that is different from the non-working ones.   It's also odd that duplicating (minus track properties) the first track fixes all of them,  and that it only works with the first track of any given project.  Also, if I try playing the TTS-1 after duplicating track #1 but before deleting it,  the TTS-1 goes wonky, and won't fix even after I've deleted that track.   I'd be curious to know what's going on, but as long as my fix is permanent (time will tell) I'm good to go.

I don't have any specific knowledge of track properties, "hidden" or otherwise. And I have never seen this happen before. Just commenting that your observations were indicating that might be a good place to look.

I would shoot an email to support if you think it's worthwhile for the devs to look into it, as is maybe a case of a subtle change in one of the recent Cakewalk updates: support@cakewalk.com

[davet]

Yup, I've had the same experience with TTS-1 in old Sonar 8.5.3 projects. The old project created in Sonar plays fine in Cakewalk/Bandlab.  My solution is a template created in Sonar that I've added TTS to. That template is used for new projects in Cakewalk. So far it works fine.

[David Baay]

Arpeggiator inadvertently enabled on the track?

[smckee]

9 hours ago, David Baay said:

Arpeggiator inadvertently enabled on the track?

I had the same thought, but it wasn't.  I can't find anything different anywhere compared to the TTS-1 tracks in projects that work.  I wonder if it is something in the way that Sonar saved the tracks--some bit of code that was added to track properties.   Then something changed in a CbBL and it didn't play well with that bit.  ( I know squat about code, so I'm not sure that that even makes sense.)

Edited February 8, 2020 by smckee

[smckee]

9 hours ago, davet said:

Yup, I've had the same experience with TTS-1 in old Sonar 8.5.3 projects. The old project created in Sonar plays fine in Cakewalk/Bandlab.  My solution is a template created in Sonar that I've added TTS to. That template is used for new projects in Cakewalk. So far it works fine.

Thanks for that tip!  I still have Sonar on an old computer, so that may come in handy.   I think I've got my problem licked though (knock on wood).  If you have any old projects that still act up, I'd be curious to know if my track duplicating procedure fixes them.   It's a quick and easy thing to try.   I wonder if it would also fix other kinds of TTS-1 problems people have been reporting.  Hopefully all the screwing around I went through helps out somebody.

[Krister Fruberg]

 

On 2/6/2020 at 12:24 PM, smckee said:

Well, I've stumbled upon a strange fix.   I tried to "rebuild" one of my songs that was exhibiting the bad TTS-1 behaviour.  After a lot of experimenting, I stumbled upon this:

1. Duplicate track #1; in the pop-up, check the Event and Effects box, but uncheck the Properties box.

2. Delete the original track.

3. Save the project.  

Now all the tracks behave.  This does not work if I start by duplicating any track other than the first.  Also I have to delete the original track first before I start to mess with the project, otherwise, the TTS-1 won't behave.    I crashed the project once, but saving it right away seems to make it stable.

So unchecking the Properties box is a surely a clue...  I tried changing track properties first instead of duplicating the track, but no changes I made affected the TTS-1. 

Even though I don't know what caused this problem, or why my fix works, I'll tentatively call this one "solved".   

Thanks. 

Many thanks for your fix solution. I was almost going crazy trying to find the reason for this problem.  But I can now confirm that your fix to duplicate track 1 without Properties and then delete first track worked fine also for me. I will now sort this problem in category "Don't bother about the root cause - just find a way around".  ?