TTS-1 program changes in X2 don't work; but work in X1?

2012/11/24 21:39:38

swamptooth

double checked all vsti's and they work ok. yeah dxi problem.

2012/11/24 22:14:41

SuperG

swamptooth

just tried tts-1 with my oxy49 keyboard in both x2 and x1. same thing you're getting. program changes work in x1 not in x2. inserted a load of program changes in the project and had arpeggiator running with automation and they all worked fine. looks like a routing question. i also opened the midi track in prv and let it play and x2 DID NOT crash or experience any abnormal issues. played as expected.

It's is possible there may be some differences - in my case the project started by opening a pre-existing midi file (later saved as a .cwp). I'm not sure if my problem would carry over or not to tracks originally authored (or recorded) within Sonar - I'll have to look into that.

2012/11/25 04:53:47

Bristol_Jonesey

Well now, I just tried to replicate this and every attempt to insert TTS-1 results in an instant fatal crash of Sonar, right back to the desktop

Seems like I've got 1 or 2 problems as the Pentagon is also acting weird

2012/11/25 11:41:10

SuperG

Just to haul it out once again - here's a video demonstration of my issue with the PRV, FWIW.

http://forum.cakewalk.com...px?m=2714509&high=

2012/11/25 13:25:10

arachnaut

SuperG

swamptooth

just tried tts-1 with my oxy49 keyboard in both x2 and x1. same thing you're getting. program changes work in x1 not in x2. inserted a load of program changes in the project and had arpeggiator running with automation and they all worked fine. looks like a routing question. i also opened the midi track in prv and let it play and x2 DID NOT crash or experience any abnormal issues. played as expected.

It's is possible there may be some differences - in my case the project started by opening a pre-existing midi file (later saved as a .cwp). I'm not sure if my problem would carry over or not to tracks originally authored (or recorded) within Sonar - I'll have to look into that.

To be clear - there is no problem using TTS-1 on recorded MIDI files or tracks recorded/played-back from real-time -it's only on the real-time auditioning/monitoring during recording. Somehow, the program change messages aren't sent to the DXi synth.

2012/11/25 13:40:12

swamptooth

arachnaut

SuperG

swamptooth

just tried tts-1 with my oxy49 keyboard in both x2 and x1. same thing you're getting. program changes work in x1 not in x2. inserted a load of program changes in the project and had arpeggiator running with automation and they all worked fine. looks like a routing question. i also opened the midi track in prv and let it play and x2 DID NOT crash or experience any abnormal issues. played as expected.

It's is possible there may be some differences - in my case the project started by opening a pre-existing midi file (later saved as a .cwp). I'm not sure if my problem would carry over or not to tracks originally authored (or recorded) within Sonar - I'll have to look into that.

To be clear - there is no problem using TTS-1 on recorded MIDI files or tracks recorded/played-back from real-time -it's only on the real-time auditioning/monitoring during recording. Somehow, the program change messages aren't sent to the DXi synth.

precisely.

2012/11/25 13:42:32

arachnaut

By the way, if you are looking for a DX -> VST interface here is a good, free, tool:

http://xlutop.com/buzz/zip/dxshell_v1.0.4b.zip
Put in your VST path and after you scan VSTs it will appear as a folder with your DXi entries. It will also show audio and midi dx effects as VST audio effect.

2012/11/25 14:36:08

swamptooth

damn wish exposed mfx parameters for automation. :(

2012/11/26 09:19:23

arachnaut

I submitted this: CWBRN-13184

TTS-1 program changes in X2 don't work; but work in X1?

Use My Existing Forum Account

Use My Social Media Account