Recent Posts

Pages: [1] 2 3 ... 10
1
Discussions / Re: Tascam FW-1884 (early prototype)
« Last post by Cedric on Today at 07:21:14 AM »
Spying: AZSlow 366 + templates 0.6

 ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Sat 24-Jun-2017 06:56:24 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT         

// STOP (nothing playing)     
 0003A86E   5  10     BF    15    7F   16  ---  CC: 21 (E-MU)         
 0003A948   5  10     BF    15    00   16  ---  CC: 21 (E-MU)         

// PLAY
 0003C3BC   5  10     BF    16    7F   16  ---  CC: 22 (E-MU)         
 0003C3FA  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 00 F7
 0003C3FA  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 16 7F F7
 0003C3FA  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 17 00 F7
 0003C46D   5  10     BF    16    00   16  ---  CC: 22 (E-MU)         

//STOP (something was playing)
As you can see already, the STOP behavior is completely different than this of the Tascam driver, see previous post.
 0003D864   5  10     BF    15    7F   16  ---  CC: 21 (E-MU)         
 0003D8A2  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 7F F7
 0003D8A3  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 16 00 F7
 0003D8A3  10   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 17 00 F7
 0003D901   5  10     BF    15    00   16  ---  CC: 21 (E-MU)         
 <=== MIDI-OX Log Closed: Sat 24-Jun-2017 06:57:06 <===


// REW & F.FWD (was stop)
Too complicated to record with midi ox
The behavior seems random

Sometimes, clicking either moves backward or forward from a measure, as it should.
Sometimes it is less
Sometimes, the move is continuous, and cannot be stopped with STOP. One have first to press PLAY, then STOP.


// SET + REW
When no loop, goes to beginning, as expected.
Too sensitive ?
Instead of going to beginning on loop (when one is define), we are 1 measure left from the beginning of the loop

// SET + F.FWD : does not work.
Note that the documentation incorrectly stated that this was SHIFT + F.FWD. See previous post
2
Control Surfaces/ACT / Re: Steinberg CMC
« Last post by azslow3 on Today at 12:17:09 AM »
Is possible work with CMC series?
AZ Controller can works with any MIDI controllers (bidirectionally). In the users guide for CMC series I see the MIDI implementation chat. If you want, I can prepare some simple preset for one particular module of your choice. Then you can decide either you want the rest or not (and what you want control inside Sonar with each module you have).

Note that AZ Controller support aggregation up to 4 devices only, not sure how 6 modules exposed to Sonar... In worse case 3 AZ Controller instances will be required (4+1+1).

Sorry to mention that, but in case you ask for test preset, I implement it, but you never test it and report back (no time... no more interest... etc), that obviously will reduce my willing to create presets for other. I mean please reserve 20 minutes of your time for testing and reporting back ("works but I think that is not what I need" is acceptable) in case you decide to continue.
3
Control Surfaces/ACT / Steinberg CMC
« Last post by freeliberty on Yesterday at 09:30:42 PM »
Is possible work with CMC series?
4
Discussions / Re: Tascam FW-1884 (early prototype)
« Last post by Cedric on June 19, 2017, 08:09:29 PM »
Here is my first spying session with MIDI OX
NOTE: THIS IS WITH THE NATIVE FW-1884 driver, not AZSLOW

 ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Mon 19-Jun-2017 19:39:10 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 
//STOP (nothing playing)
 000502F1   5  11     BF    15    7F   16  ---  CC: 21 (E-MU)         
 00050387   5  11     BF    15    00   16  ---  CC: 21 (E-MU)         
 
 
// Play
 000535C7   5  11     BF    16    7F   16  ---  CC: 22 (E-MU)         
 0005362F   5  11     BF    16    00   16  ---  CC: 22 (E-MU)         
 0005365D  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 16 7F F7
 0005365D  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 00 F7
 
 
 //STOP (something was playing)
 00057C37   5  11     BF    15    7F   16  ---  CC: 21 (E-MU)         
 00057C44  11   6     E0    00    40    1  ---  Pitch Bend           
 00057C44  11   6     B0    01    00    1  ---  CC: Modulation       
 00057C44  11   6     B0    40    00    1  ---  CC: Pedal (Sustain)   
 00057C44  11   6     B0    79    00    1  ---  CC: Reset Cntrl       
 00057C44  11   6     E1    00    40    2  ---  Pitch Bend           
 00057C45  11   6     B1    01    00    2  ---  CC: Modulation       
 00057C45  11   6     B1    40    00    2  ---  CC: Pedal (Sustain)   
 00057C45  11   6     B1    79    00    2  ---  CC: Reset Cntrl       
 00057C45  11   6     E2    00    40    3  ---  Pitch Bend           
 00057C45  11   6     B2    01    00    3  ---  CC: Modulation       
 00057C45  11   6     B2    40    00    3  ---  CC: Pedal (Sustain)   
 00057C45  11   6     B2    79    00    3  ---  CC: Reset Cntrl       
 00057C45  11   6     E3    00    40    4  ---  Pitch Bend           
 00057C45  11   6     B3    01    00    4  ---  CC: Modulation       
 00057C45  11   6     B3    40    00    4  ---  CC: Pedal (Sustain)   
 00057C45  11   6     B3    79    00    4  ---  CC: Reset Cntrl       
 00057C46  11   6     E4    00    40    5  ---  Pitch Bend           
 00057C46  11   6     B4    01    00    5  ---  CC: Modulation       
 00057C46  11   6     B4    40    00    5  ---  CC: Pedal (Sustain)   
 00057C46  11   6     B4    79    00    5  ---  CC: Reset Cntrl       
 00057C46  11   6     E5    00    40    6  ---  Pitch Bend           
 00057C46  11   6     B5    01    00    6  ---  CC: Modulation       
 00057C47  11   6     B5    40    00    6  ---  CC: Pedal (Sustain)   
 00057C47  11   6     B5    79    00    6  ---  CC: Reset Cntrl       
 00057C47  11   6     E6    00    40    7  ---  Pitch Bend           
 00057C47  11   6     B6    01    00    7  ---  CC: Modulation       
 00057C47  11   6     B6    40    00    7  ---  CC: Pedal (Sustain)   
 00057C47  11   6     B6    79    00    7  ---  CC: Reset Cntrl       
 00057C47  11   6     E7    00    40    8  ---  Pitch Bend           
 00057C47  11   6     B7    01    00    8  ---  CC: Modulation       
 00057C47  11   6     B7    40    00    8  ---  CC: Pedal (Sustain)   
 00057C47  11   6     B7    79    00    8  ---  CC: Reset Cntrl       
 00057C47  11   6     E8    00    40    9  ---  Pitch Bend           
 00057C47  11   6     B8    01    00    9  ---  CC: Modulation       
 00057C47  11   6     B8    40    00    9  ---  CC: Pedal (Sustain)   
 00057C47  11   6     B8    79    00    9  ---  CC: Reset Cntrl       
 00057C47  11   6     E9    00    40   10  ---  Pitch Bend           
 00057C48  11   6     B9    01    00   10  ---  CC: Modulation       
 00057C48  11   6     B9    40    00   10  ---  CC: Pedal (Sustain)   
 00057C48  11   6     B9    79    00   10  ---  CC: Reset Cntrl       
 00057C48  11   6     EA    00    40   11  ---  Pitch Bend           
 00057C48  11   6     BA    01    00   11  ---  CC: Modulation       
 00057C48  11   6     BA    40    00   11  ---  CC: Pedal (Sustain)   
 00057C48  11   6     BA    79    00   11  ---  CC: Reset Cntrl       
 00057C48  11   6     EB    00    40   12  ---  Pitch Bend           
 00057C48  11   6     BB    01    00   12  ---  CC: Modulation       
 00057C48  11   6     BB    40    00   12  ---  CC: Pedal (Sustain)   
 00057C48  11   6     BB    79    00   12  ---  CC: Reset Cntrl       
 00057C49  11   6     EC    00    40   13  ---  Pitch Bend           
 00057C49  11   6     BC    01    00   13  ---  CC: Modulation       
 00057C49  11   6     BC    40    00   13  ---  CC: Pedal (Sustain)   
 00057C49  11   6     BC    79    00   13  ---  CC: Reset Cntrl       
 00057C49  11   6     ED    00    40   14  ---  Pitch Bend           
 00057C49  11   6     BD    01    00   14  ---  CC: Modulation       
 00057C49  11   6     BD    40    00   14  ---  CC: Pedal (Sustain)   
 00057C49  11   6     BD    79    00   14  ---  CC: Reset Cntrl       
 00057C49  11   6     EE    00    40   15  ---  Pitch Bend           
 00057C49  11   6     BE    01    00   15  ---  CC: Modulation       
 00057C49  11   6     BE    40    00   15  ---  CC: Pedal (Sustain)   
 00057C49  11   6     BE    79    00   15  ---  CC: Reset Cntrl       
 00057C62  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 16 00 F7
 00057C62  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 7F F7
 00057C9F   5  11     BF    15    00   16  ---  CC: 21 (E-MU)         
 <=== MIDI-OX Log Closed: Mon 19-Jun-2017 19:40:09 <===

 
  ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Mon 19-Jun-2017 19:47:40 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 
// REW (was stop)
 000CB443   5  11     BF    13    7F   16  ---  Control Change       
 000CB46E  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 00 F7
 000CB46E  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 13 7F F7
 000CB4B7   5  11     BF    13    00   16  ---  Control Change       

// F.FWD (was stop)
 000CC5E8   5  11     BF    14    7F   16  ---  Control Change       
 000CC604  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 13 00 F7
 000CC604  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 14 7F F7
 000CC673   5  11     BF    14    00   16  ---  Control Change       
 <=== MIDI-OX Log Closed: Mon 19-Jun-2017 19:47:57 <===

 
 
  ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Mon 19-Jun-2017 19:49:53 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               

//REW continuously pressed for about 2s

 000EC4B2   5  11     BF    13    7F   16  ---  Control Change       
 000EC4F2  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 13 7F F7
 000EC4F2  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 14 00 F7
 000EC7DF   5  11     BF    13    00   16  ---  Control Change       
 000EC82B  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 7F F7
 000EC82B  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 13 00 F7
 
//F.FWD continuously pressed for about 2s

 000F0227   5  11     BF    14    7F   16  ---  Control Change       
 000F0278  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 00 F7
 000F0279  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 14 7F F7
 000F053E   5  11     BF    14    00   16  ---  Control Change       
 000F0566  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 15 7F F7
 000F0566  11   6     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 4E 00 12 01 14 00 F7
 000F1F8B   5  11     BF    15    7F   16  ---  CC: 21 (E-MU)         
 000F207F   5  11     BF    15    00   16  ---  CC: 21 (E-MU)         
 <=== MIDI-OX Log Closed: Mon 19-Jun-2017 19:50:30 <===

 
  ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Mon 19-Jun-2017 19:55:25 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 
// SET + REW = Jump to beginning. This also stops at the LOOP IN point if LOOP is enabled
 //
 0013F3B4   5  11     BF    1A    7F   16  ---  Control Change       
 0013F627   5  11     BF    13    7F   16  ---  Control Change       
 0013F6B2   5  11     BF    1A    00   16  ---  Control Change       
 0013F6EC   5  11     BF    13    00   16  ---  Control Change       
 <=== MIDI-OX Log Closed: Mon 19-Jun-2017 19:55:46 <===
 
 
  ===> MIDI-OX Version: 7.0.2.372
 ===> Log Opened: Mon 19-Jun-2017 20:04:22 ===>
 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
// SET + F.FWD Jump to end.
 // Note: The documentation incorrectly states that this is SHIFT + F. FWD


001C05BA   5  11     BF    1A    7F   16  ---  Control Change       
 001C06E8   5  11     BF    14    7F   16  ---  Control Change       
 001C07AD   5  11     BF    1A    00   16  ---  Control Change       
 001C07DC   5  11     BF    14    00   16  ---  Control Change       
 <=== MIDI-OX Log Closed: Mon 19-Jun-2017 20:04:34 <===
5
Discussions / Re: SysEx messages all mapping to ctrl 85
« Last post by azslow3 on June 08, 2017, 06:09:39 PM »
If there is no plug-ins of corresponding type (f.e. strip has no FX at all), focus WILL NOT BE CHANGED (I do not know how to "void" the mapping...) and stay where it was before.
That is completely understandable.  I was not sure what to do in this instance either.  Leaving at last plugin sounds good.  When I get further into a mix I will see if there are any down sides to this approach.
While looking around trying to get the ACTLearn and ACTLock working, I stumbled onto:
Compare ACT MAP == No Mapping.  I don't know what it is supposed to do, but it does sound a little like void the mapping to me..  I realise it is a query not a command.. but maybe an area to look at??
Where you have seen that?
By itself it can not do bad things, "ACT MAP" is the System State.

Quote
I have found a bug.  I can get half way to solving it, but can't seem to get all the way there:

Code: [Select]
((None)) _Solo 8 :
...
 'BtnMode:Transport' - ACT Learn Toggle
...


((None)) _Solo 9 :
...
 'BtnMode:Transport' - ACT Lock Toggle
...
Yes, sorry. Should be fixed in attached version.

Quote
I created Software States for ACTLearn and ACTLock..  With default values of No.
Proper way will required some coding first... do you really need that indication? It is normally clearly visible in the Sonar toolbar.

ACTLearn in fact has no sense, to "learn" things the first action to do is to touch control by mouse. And if the mouse is already in your hands, why not click learn button?  ;)
For confirmation, "Enter" is required. So again the mouse should be in your hands (or keyboard... or assigned on surface action...). The whole procedure required Start/Stop Sonar, AZ ACT Fix, etc. So dedicated button on surface make sense for so called "scratch" learning only, described in some blog by Craig.

ACTLock make more sense from the surface. I think I have to implement corresponding System State and than put it into preset (for feedback and logic, to select correct plug-in when ACT is unlocked). Not next 2 weeks, but remind me later.
6
Discussions / Re: SysEx messages all mapping to ctrl 85
« Last post by Linzmeister on June 08, 2017, 02:58:45 PM »
If there is no plug-ins of corresponding type (f.e. strip has no FX at all), focus WILL NOT BE CHANGED (I do not know how to "void" the mapping...) and stay where it was before.
That is completely understandable.  I was not sure what to do in this instance either.  Leaving at last plugin sounds good.  When I get further into a mix I will see if there are any down sides to this approach.
While looking around trying to get the ACTLearn and ACTLock working, I stumbled onto:
Compare ACT MAP == No Mapping.  I don't know what it is supposed to do, but it does sound a little like void the mapping to me..  I realise it is a query not a command.. but maybe an area to look at??

I have found a bug.  I can get half way to solving it, but can't seem to get all the way there:

Code: [Select]
((None)) _Solo 8 :
...
 'BtnMode:Transport' - ACT Learn Toggle
...


((None)) _Solo 9 :
...
 'BtnMode:Transport' - ACT Lock Toggle
...

I created Software States for ACTLearn and ACTLock..  With default values of No.

Code: [Select]

...
 'GlobalMode:ACT' - BtnMode == Default
 'Last action:OK' - ACT Learn Toggle
 'ACTLearn:No' 'Last action:OK' - ACTLearn -> Yes
 'ACTLearn:Yes' 'GlobalMode:ACT' 'Last action:Failed' - ACTLearn -> No
...
I was able to affect ACT Learn and LOCK in Sonar, but I messed up the feedback.  The 01V buttons were always on regardless of Learn and Lock States.  :(
7
Discussions / Re: SysEx messages all mapping to ctrl 85
« Last post by azslow3 on June 07, 2017, 09:33:39 PM »
I have actually started to mix a few songs.  I did experience a few crashes, but I can't say that they are related to the plugin or the preset.  More observation required to ascertain what is causing the crashes.
I had several kinds of Sonar crashes:
1) plug-ins... probably 90% of all crashes was inside (or coursed by) VST plug-ins
2) Sonar itself. Another 5%. Greatly reduced on X1 -> current Platinum way
3) 4.9% from Sonar crashes "inducted" by AZ Controller. Known cases are workarounded in AZ Controller code.
4) 0.1% from AZ Controller. I remember 2 critical bugs in very specific cases during lifetime of AZ Controller.

But I can solve only (4) and sometimes (3), so if you can reproduce some crash and it does not happened with AZ Controller removed, that we can nail and eliminate.
8
Discussions / Re: SysEx messages all mapping to ctrl 85
« Last post by Linzmeister on June 07, 2017, 02:39:22 PM »
Hi,
I had a suspicion I was missing a preset on a previous post, but it was good to spend some more time actually mixing instead of testing the preset now that you have given me so much functionality.

I put a part of you changes into place, bugfix in Input and Solo / ON labels.
I used only one row, for me the table with 15 columns and 3 rows looks more sane that way, but if you disagree with that I will put your "2 rows per button" description back.
Technically it is done a bit different. In other modes (currently ACT only, but who knows the future...) each button display the label (value) for itself. So in case we display on state switching,
it can be overwritten by buttons own procedure. So there are functions to convert _Ch->Text, called from appropriate place.
That looks great.  I just used 2 rows because the pre-existing information was already laid out that way..

If there is no plug-ins of corresponding type (f.e. strip has no FX at all), focus WILL NOT BE CHANGED (I do not know how to "void" the mapping...) and stay where it was before.
That is completely understandable.  I was not sure what to do in this instance either.  Leaving at last plugin sounds good.  When I get further into a mix I will see if there are any down sides to this approach.


Next/Previous and Plug-in type buttons are inactive in EQ/Comp mode.
Plug-in type buttons LEDs indicate current type when in Selectable mode. No from them light in EQ/Comp modes (as the indication they are inactive).

Next/Prev should be circular.
That is perfect!.  Indicates and circular navigation within a channel..  Very nicely done.

PS I have tried 2 approaches to focus PC/FX. I have found "direct" approach buggy in X2. There is "side effect" from the second method, Sonar is shortly "reseting" ACT context when switching between strips, especially if PC module had the focus (probably since PC Gui for corresponding strip is changed to the new strip... so till new context is set there is no context). It can happened that faders with move a little "in wrong direction" when switching strips in ACT mode (during Sonar switching to "no context -> value 0" and then to "new context -> target value"). If that is the case, I can try to disable motors for short time. So let me know if i should try to do that.
No, I don't see any fader  movements that seem out of place.  I think that the motors take longer to respond than the MIDI messages take to transmit.

I have actually started to mix a few songs.  I did experience a few crashes, but I can't say that they are related to the plugin or the preset.  More observation required to ascertain what is causing the crashes.
9
Discussions / Re: SysEx messages all mapping to ctrl 85
« Last post by azslow3 on June 06, 2017, 06:07:38 PM »
I hope that I have understood your idea right, and so the implementation attempt.
Please install b366, it has "find last plug-in" addition required for "previous" button to work.

So, it should (I could easily introduce some bug here) function with 3 ACT submodes:
- EQ Page 1 - focus ProChannel EQ of current strip
- Comp Page 1 - focus ProChannel Comp of current strip
- EQ/Comp other pages - focus selectable plug-in type and number for current strip (except Synth).

In all 3 modes, except selectable Synth, preset tries to focus corresponding plug-in/PC Module for Current strip. Also it follows current strip changes (from surface and mouse).
In selectable mode, if corresponding plug-in/module could not be found (f.e. wen strip has less FXes), preset tries to focus the first plug-in/module (in the strip).
If there is no plug-ins of corresponding type (f.e. strip has no FX at all), focus WILL NOT BE CHANGED (I do not know how to "void" the mapping...) and stay where it was before.

Next/Previous and Plug-in type buttons are inactive in EQ/Comp mode.
Plug-in type buttons LEDs indicate current type when in Selectable mode. No from them light in EQ/Comp modes (as the indication they are inactive).

Next/Prev should be circular.

PS I have tried 2 approaches to focus PC/FX. I have found "direct" approach buggy in X2. There is "side effect" from the second method, Sonar is shortly "reseting" ACT context when switching between strips, especially if PC module had the focus (probably since PC Gui for corresponding strip is changed to the new strip... so till new context is set there is no context). It can happened that faders with move a little "in wrong direction" when switching strips in ACT mode (during Sonar switching to "no context -> value 0" and then to "new context -> target value"). If that is the case, I can try to disable motors for short time. So let me know if i should try to do that.
10
Discussions / Re: Tascam FW-1884 (early prototype)
« Last post by Cedric on June 03, 2017, 04:08:42 PM »
(continued)

+ CTRL + MUTE of track: Toggle Archive track
+ READ toggle automation playback

Effects

+ The effects buttons (GAIN, FREQ, Q, HIGH, HI-MID, LOW-MID, LOW) all work with the prochannel Quadcurve equalizer module. Which is great.

? Just wondering, can a control surface detect which windows is on top ? If so, it could perhaps auto adapt to other eq plugins such as the L-Phase Equalizer or an EQ 10 from Waves for example ? Thus way we could control another 4 bands with pressing twice quickly HIGH, HI-MID, LOW-MID or LOW

Nudge
- None of the Nudge > Nudge < key combination works
If possible SHIFT CTRL Nudge > would close a plugin windows and / or 'windows that are in the console
Ditto for the cycling through the Windows

LATCH
+ Press the LATCH key to turn offset mode on/off.

Could you make it so that SHIFT + LATCH toggles one of the 3 automation write modes of the selected track: Touch, Default, Overwrite.

CTRL + LATCH could be Time base toggle: Musical or absolute





Pages: [1] 2 3 ... 10