program change and syncing issues

[droolmaster0]

Still new to Tracktion, but I'm running into some frustrating issues.

The MIDI clock implementation seems really unstable. I'm trying to sync a hardware sequencer, and I get periodic glitches - when Tracktion loops I almost always get a glitch, and often when it is not looping. There is also a tendency for the sync to go absolutely crazy - right now it's sending 32nd notes instead of 16th notes, and nothing I do has any effect, though previously if I quit Tracktion and come back it will be ok. It's certainly not the hardware sequencer - I switch to Sonar and the sync is solid.

I also have problems with undesired program changes and I am NOT recording them. Only certain vst synths seem to have an issue. The Waldorf PPG resets to program 1 (although the Tracktion display still displays the selected preset) every time I save. I have not been able to stop this from happening. I have no recorded events in the track - the ppg is being sequenced by the hardware sequencer which is most certainly not sending program change 1 - and wouldn't be sending it only when Tracktion saved anyway. I tested this again with a pretty much identical setup in Sonar, with the hardware sequencer - the PPG synth did not reset (and the sync was solid, as mentioned above). I've also had weird problems with program changes with Z3ta+. I'd suspect user error more except I've never had this issue with other software.

I'm hoping that there are solutions to this, but I'm fearing that these are issues with Tracktion 2 right now.

[valley]

The MIDI clock implementation seems really unstable.

There's a whole ongoing thread about this somwehere around here. Feel free to join in, as we are still trying to work out why things seem OK for some people and very bad for others.

I also have problems with undesired program changes and I am NOT recording them.

You can set default programs for midi inputs and clips. If you do, Tracktion will change program each time playback starts or the clip is reached. Check that any MIDI inputs you have attached to tracks have their programs set to (none).

For any clips that seem to be doing it, simpluy click the clip, and select the 'insert program chnage' and then 'remove all program changes from clip'.

[droolmaster0]

The MIDI clock implementation seems really unstable.

There's a whole ongoing thread about this somwehere around here. Feel free to join in, as we are still trying to work out why things seem OK for some people and very bad for others.

I also have problems with undesired program changes and I am NOT recording them.

You can set default programs for midi inputs and clips. If you do, Tracktion will change program each time playback starts or the clip is reached. Check that any MIDI inputs you have attached to tracks have their programs set to (none).

For any clips that seem to be doing it, simpluy click the clip, and select the 'insert program chnage' and then 'remove all program changes from clip'.

I'll have to find the thread about MIDI clock - I didn't see it. I did find a temporary solution (Bidule as VST), posted in a new thread, since I hadn't seen a response here yet.

As far as the program changes - there seems to be more going on than that. I'm not even sure that it's always a program change - but (mentioned this in the other thread) my p3 hardware sequencer was resetting to another pattern while synced to Tracktion - when I turned off MIDI clock in Tracktion and synced from Bidule, this stopped happening. the input object for the p3 has no program change selected, and there is no clip for it.

Plus, I have had program changes sent out when I never set this up to happen. When I loaded Z3ta+ for the first time, it took me awhile to realize that Tracktion was set up to send program change #23. I did not set that or record it myself. And this has happened with some other synths also. It's weird. With the Waldorf PPG, no matter what I do, when I save the edit, it resets to pgm #1. I had to add a clip with a program change so that I didn't have to toggle the Tracktion program selection every time I saved. And even then when I save it resets until the beginning of the loop...

I would suspect user error with this stuff, except that I have definitely not experienced this with other hosts. I am new to Tracktion though, so if I am missing something, I will be glad to find out about it.

[droolmaster0]

I just found the older thread about MIDI clock, and I realized that I did have Tracktion set to send to two external devices. I turned off the sync on the second one, and the clock became MUCH more stable. This has the feel of a bug to it - in any case, I am going to want to send sync to more than one device.

Even this solution didn't work completely however. When I stop Tracktion, the hardware sequencer still continues to keep playing. What is interesting is that when Bidule is hooked up as a VST, and receives its sync info from Tracktion and then sends out MIDI clock - when I stop Tracktion, the hardware sequencer stops.

[IIRs]

Strange. I did quite a bit of testing the other night with my Micro-Modular's step sequencers.. while I can confirm that looping round the markers causes a glitch (which should be fixed IMO) I couldnt cause any major problems otherwise, even when I send clock to all my MIDI ports (Midisport 2x2, Oxygen8 & UC-16). Timing got a bit shaker when I started browsing KVR at the same time, but nothing like you describe. Start & stop commands work fine btw..