Recent Posts

Pages: [1] 2 3 ... 10
Discussions / Control using an Arturia Keylab Mkii 61
« Last post by jemakeyboards on May 27, 2023, 08:40:20 PM »
See attached .spp file I use to control Cakewalk from an Arturia Keylab Mkii 61.

All functions are controlled as labelled on the keyboard with the following customizations:
- GLOBAL CONTROLS: In -> Set Loop Points to Selection
- GLOBAL CONTROLS: Out -> Set Punch Points to Selection
- TRACK CONTROLS: Read -> Enable/Bypass Read Automation - couldn't find an entry for Automation Read for the selected track
- TRACK CONTROLS: Write -> Clear all automation write enables - couldn't find an entry for Automation Write for the selected track
- JOG-WHEEL: Press -> Input Echo for selected track
- JOG-WHEEL: Turn -> Scroll track view
- CHORUS: Scale track view

These mods were done mostly due to personal preference.
I have noticed some inconsistency in the Loop button lighting. 
Otherwise, everything seems to work great!
Discussions / Re: Faderport and Cakewalk by Bandlab
« Last post by randro on May 22, 2023, 09:42:26 AM »
Hi Alexey, I'm not sure what happened, maybe I didn't restart CBB after I changed Faderport mode. In any case, it is working as it should right now.
Thanks for your help again.
Discussions / Re: Faderport and Cakewalk by Bandlab
« Last post by azslow3 on May 18, 2023, 09:07:35 AM »
I can only guess what has happened.

If it has stopped working completely, normally that means Cakewalk has switched MIDI devices. That was many time bugged and fixed, but for some reason still periodically
happened. Re-inserting Surface and assigning MIDI again normally helps.

For assignments. Check what really happens when you use buttons in question. You should see MIDI event and assigned named logical control. In the overview tab you can also
see what was executed. Depending from the result I can give other tips what to check.

I have loaded the preset in the latest beta (b422) is the preset looks reasonable (Channel and Pan buttons are assigned). It can be Faderport for some reason was switched into different mode and so buttons generate different messages, but that you can recognize using mentioned method.
Discussions / Re: Faderport and Cakewalk by Bandlab
« Last post by randro on May 17, 2023, 10:31:42 PM »
Hello Alexey, I have been using my Faderport 2 using the preset you made for me since 2021 and it has worked great. Recently it stopped working completely and there was no indication for Last MIDI Event in AZ Controller GUI. I updated to version azctrl_0_5r11b419. I started to see MIDI events again and my Faderport started to work after I reloaded your preset AZ Faderport V2 0.5. The only difference now is that the "Pan" and "Channel" buttons are not working properly. Pan moves Now Time back and forth, and Channel does nothing. Is the preset you made for me compatible with this new version of AZSlow? I have included the file with your preset. Appreciate your help, Thanks
Hi Alexey

I downloaded the test version b422 and the LOCATE function is working correctly with the Fostex Tape Machine.

I also added PLAY and STOP commands (which use preset SysEx messages) and these are also working correctly, so I can PLAY, STOP and LOCATE the Fostex to follow Cakewalk.
It will be possible to add RECORD and Track REC ARM commands in the same way, all using SysEx.

By the way I use a software utility called 'Chameleon' to provide screen based MIDI buttons which sit on top of the Cakewalk GUI.  So I have a button called LOCATE to trigger the Fostex locate function.

Many thanks for taking care of this so quickly.  Let me know if you need me to make any further tests.

Best regards
BTW you can mark the last one with "loop", so you can directly observe final result (select all 3 and press "Play").
Please try b422 (test version). It has "Append now time SMPTE" in SysEx Action options. So you need 3 SYSEX Actions, one
with "Start" (put prefix "51 7F 12 18 42" there), next "Append ... SMPTE" and finally "End (and send)" with "12").
Hi Alexey

The Fostex protocol defines four frame rates using "yy" as follows:

00 = 24 frames/second
01 = 25 frames/second
10 = drop frame (no frame rate quoted)
11 = non-drop frame (no frame rate quoted)

The original official MIDI specification specifies the use of the "yy" bits as follows:

00 = 24 frames/second
01 = 25 frames/second
10 = 30 frames/second (drop frame)
11 = 30 frame/second (non-drop frame)

Whereas the entry for MIDI timecode in Wikipedia quotes:

00 = 24 frames/second
01 = 25 frames/second
10 = 29.97 frames/second (drop frame)
11 = 30 frame/second (non-drop frame)

Next I checked the actual output "yy" bits from the seven frame rates available within the Cakewalk Preferences\Project\Clock menu:

00 = 24 frames/second
00 = 23.976 frames/second
01 = 25 frame/second
10 = 29.97 frames/second (drop frame)
10 = 30 frames/second (drop frame)
11 = 29.97 frames/second (non-drop frame)
11 = 30 frames/second (non-drop frame)

So although the Cakewalk SDK supports six different frame rates, the actual MTC code output by Cakewalk uses only the two "yy" bits with no differentiation between 29.97fps and 30fps rates.  This is identical to the Fostex protocol.

Therefore my suggestion is to implement the AZ Controller 'numeric' MTC in the same way so that it compatible to what Cakewalk outputs and so also compatibility with the Fostex protocol.


Fine, I can implement that. But can you check what "yy" (so, "frame rate") means for Fostex?
Cakewalk encoding is defined there:
So they support 6 different frame rates, while you mention Fostex use 2 bits, so it supports 4.
Hi Alexey
Let me first explain the application:

I am putting together a small mobile recording setup with a Laptop PC running Cakewalk and AZ Controller, and a Fostex R8 8-track analogue tape machine which has a MIDI interface with remote control protocol mostly using SysEx messages for tape transport, record arming etc.  The Fostex can also be slave sync'd to Cakewalk using LTC timecode.  I will use this mobile setup mostly to record 'real' drums (I can only record MIDI based drums in my small home studio).

The idea is to record simultaneously to Cakewalk and the Fostex R8, and then integrate the recording with other tracks recorded in the studio.  The final mixdown will be from the R8 (and my Fostex G24S) via my Cakewalk/AZ controlled analogue mixer.

It should be easy to configure an AZ Controller preset to allow Cakewalk to remote control most R8 functions but there is one important function which is the subject of my enquiry to you.

The Fostex R8 had a 'locate to timecode' function which allows the R8 to fast spool and then stop at the received (static) timecode.  In use this means I can move the Cakewalk song pointer to the desired position (to start recording) and then request the R8 to move to the same timecode position.  However this would require a SysEx message from AZ to the following format (I will show the preset bytes in hex):

F0 51 7F 12 18 42 hr mn sc fr 12 F7

hr = hours and frame rate: 0 yy zzzzz (yy = frame rate, zzzzz = hours from 0 to 23)
mn = minutes: 00yyyyyy (yyyyy = minutes from 0 to 59)
sc = seconds: 00yyyyyy (yyyyyy = seconds from 0 to 59)
fr = frames: 000yyyyy (yyyyy = frames from 0 to 29)

I normally run LTC and MTC and 30fps and have no requirement to change this from session to session.

In the studio I take care of this locate function (for my Fostex G24S 24-track machine) as part of the mixer's PIC software but in my mobile setup (with the Fostex R8) I don't want to have the complexity of a PIC for just one remote control function.  That's why I'm asking if you think it is possible to make the static Cakewalk MTC position available, to the desired format, within AZ Controller?

Best regards

Pages: [1] 2 3 ... 10