Getting diffrent Page faders to work.

[Charged]

Hey there nice people of the avolites community.
If recently bought an Titan one along with an behringer bcf 2000. I use osimidi now with it, and i want to get the Motor fader to work. Before any 1 says this is an osimidi issue, hold on a minute. The Motor faders actually work. They synchronize with the Actions on the faders. I want it to get working now, that i can use the diffrent pages and have diffrent values for euch fader on a Page, so osimidi can use the motorfaders more efficently/faster like an audio Mixer with diffrent pages. Does any one know a setting for something like this? Please letzten me know! Best regards: Charged

[Gregory]

I should probably point out that OsiMIDI is not offically supported as stated here:

Osimidi does not use an official interface to Titan; not only do we recommend against users using it, we provide no support for it as it could cause instability in Titan up to and including application crashes.

Users wanting MIDI input using any Windows DirectX MIDI device (including USB MIDI and Network MIDI devices) can use these on all hardware from the newly-released T2 upwards in Titan V12.0.

That said I believe the setting you are looking for is Playback Paging in User Settings which you should probably set to Never Hold if you want to fire multiple playbacks on the same fader.

[Charged]

Hmm yes, thats kind of what i wanted. I ment that the faders basically update their position in avolites, so those (in picture) go up .

Basically when i do what you told me, just the value goes up. Not the faders. Is that possible?

[Charged]

Oh wait i just read the other post. Does the moving faders upwards work when i buy an avokey, (basically upgrade to v12)? Or does that require an T2 (which i am definetly not going to buy)

[Gregory]

I'm not sure if this is what you mean but in the version 14.0 release notes is the following:

Titan Go restore fader position on page change:
When changing page in Titan Go the faders will now move to reflect the level of different active playbacks on the same handle (where relevant).

In versions prior to this Titan would not attempt to match the on-screen fader position to the level of the playback, they effectively acted like non-motorized faders.

[Charged]

This issue has been resolved, after buying an avokey and upgrading to v18