I understand it now ;)
I have uploaded your preset version with initialization added.
 
EDIT: second typo within last 3 days... the first one was a broadcast that huge computer center is going into downtime (while the meaning had to be that it does NOT going to have downtime )

azslow3
Not I understand it ;)
I have uploaded your preset version with initialization added.

Thanks.  I'll grab it now.  We'll know something over the next few days.

Jimbo21
Every time I boot my computer the faderport "write" button is lit up. With it lit up, if I open Sonar the fader on the faderport will move back and forth quickly and like others here have mentioned, the project won't complete loading until I move the fader by hand.
 
But if I press the "write" button to where it is not lit up before opening Sonar, the project loads just fine and faderport works great.
 
i know it's not exactly what you've experienced, but maybe someone else is having this problem.

Jim, thanks for this info. I just gave it a try but no cigar. It is amazing how the same product and driver works differently on different systems. There must be a common denominator somewhere.

FYI guys.  The init logic that I'm testing for A is working so far.  I'll keep you posted.

BobF

azslow3

BobF

azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.

A - I have downloaded and installed this preset and turned WAI tracking back on.

Sorry, but I do have not understood that statement. "WAI tracking" option exists in the original (Presonus) plug-in only. And AZController can not be used in parallel with it...
So, have you tried this preset with AZController only, after power cycling Faderport, so bringing it in position where it was not recognized before?
 

  Quick question ... can you post the changes you made to implement this INIT function?  I would like to add this to my already existing and modified AZ preset.

* One software state, "Initialize" with "Pending" (default) and "Done".
* One system hardware control "Init", with logical control attached.
* The logical control has single action, "Monitor" "Initialize" state
* In that monitor I check the state of "Initialize", and for "Pending" send 2 SysEx messages, then change the state into "Done".
 
If you publish you current preset (on my forum), I will apply the change (can save you some time, I need ~1minute to do this).
 

This is where I had disabled WAI

 
I'll try to export my preset and post at your forum ...

When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

Mosvalve
When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

At the moment we are in "testing" phase with the change, so please download http://www.azslow.com/index.php?action=downloads;sa=downfile&id=28 0.5r3b342.
Build-in preset has no initialization yet, get moded versions from http://www.azslow.com/ind...topic=163.0;attach=436 and install it with Cakewalk Plug-in Manager in Sonar Utilities menu. Open AZ Controller panel and select "Faderport with init" preset (in the left top corner).
 
Possible cause of different initial behavior I have asked you to test in your previous thread: Faderport has "mode" and it can be switched on the device. The documentation is silent either selected mode will be persistent and which modes exists, they just describe how to switch it into Ableton compatible mode.
 
Watercouse (the user with which I have created the preset) had it in "some" mode, I mean we have created the preset in mode he had. So he had no problem with initialization.
 
What we are testing now are 2 SysEx which original Presonus plug-in sends to Faderport, my guess is that one of these SysExes is the mode switcher.
 

Mosvalve

BobF

azslow3

BobF

azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.

A - I have downloaded and installed this preset and turned WAI tracking back on.

Sorry, but I do have not understood that statement. "WAI tracking" option exists in the original (Presonus) plug-in only. And AZController can not be used in parallel with it...
So, have you tried this preset with AZController only, after power cycling Faderport, so bringing it in position where it was not recognized before?
 

  Quick question ... can you post the changes you made to implement this INIT function?  I would like to add this to my already existing and modified AZ preset.

* One software state, "Initialize" with "Pending" (default) and "Done".
* One system hardware control "Init", with logical control attached.
* The logical control has single action, "Monitor" "Initialize" state
* In that monitor I check the state of "Initialize", and for "Pending" send 2 SysEx messages, then change the state into "Done".
 
If you publish you current preset (on my forum), I will apply the change (can save you some time, I need ~1minute to do this).
 

This is where I had disabled WAI

 
I'll try to export my preset and post at your forum ...

When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

Widen the columns.  The A is the first part of ACT, the N is actually part of the W in WAI

azslow3

Mosvalve
When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

At the moment we are in "testing" phase with the change, so please download http://www.azslow.com/index.php?action=downloads;sa=downfile&id=28 0.5r3b342.
Build-in preset has no initialization yet, get moded versions from http://www.azslow.com/ind...topic=163.0;attach=436 and install it with Cakewalk Plug-in Manager in Sonar Utilities menu. Open AZ Controller panel and select "Faderport with init" preset (in the left top corner).
 
Possible cause of different initial behavior I have asked you to test in your previous thread: Faderport has "mode" and it can be switched on the device. The documentation is silent either selected mode will be persistent and which modes exists, they just describe how to switch it into Ableton compatible mode.
 
Watercouse (the user with which I have created the preset) had it in "some" mode, I mean we have created the preset in mode he had. So he had no problem with initialization.
 
What we are testing now are 2 SysEx which original Presonus plug-in sends to Faderport, my guess is that one of these SysExes is the mode switcher.
 

Good news and bad news.  The good news is that the FP initialized fine thru several reboots without problems.
 
That bad news is that from a full power-off shutdown, the FP comes up with [Write] lit and fails to initialize by starting SONAR.  Starting Reaper gets it going, then it works fine with SONAR again.
 
Toggling [Write] off doesn't help.

I have found Ardour source for FaderPort! I will implement proper initialization tomorrow (there is "are you there?" -> "Yes I am... " -> "Use native mode please" conversation, not a problem to put that into the preset once it is known what to send and expect...).

Great news, A
 
PM me your shipping address.  I'll send you ... something