Thanks again Mattias. Regarding your answer D I didn't get if you need the LTC from PT/MW to go to the normal SSL CPU TC reader card or if the parallel data interface on the Z8 takes care of this?
I will tackle my clients setup sometime in the near future but in the meantime I have written the below to get feedback from all users with any experience in this and also try to collect scattered info for future reference:
Best modern Motionworker setup:What is the best way to set up the MW up in a modern workflow? The design and manuals (referring to “Motion worker system v5 technical manual” and “Motion worker system v5 operators manual”) are from the nineties and do not take into account the modern DAW workflows.
Objectives:X: I believe we all want Pro Tools to be the master supplying the LTC/SMPTE so it doesn't need to chase to incoming SMPTE creating jitter and other digital artefacts when varying the wordclock to stick in sync. This is mentioned in the Konnektor documentation.
Y: We would like to have control of the pro tools timeline from both within pro tools, the ssl transport keys and the the ssl cpu (goto commands etc) like the Konnektor / SSL Virtual Tape Machine (ref: horizonsound on this forum) provides.
Z: The use of the Motionworker instead of a Konnektor / SSL Virtual Tape Machine provides the additional benefits of having one or more synchroniser (Lynx II, Adams-Smith, Audio Kinetics etc) controlling reel to reel tape decks chasing the DAW.
Possible solution:The best solution I could think up and that I havn’t got even close to running yet:
1: Pro Tools provides the master LTC/SMPTE either using an Avid Sync i/o if you use earlier versions than Pro Tools HD 11 or Avid Sync HD or an audio track with a LTC/SMPTE file. This goes to the MW JR14 Machine A in (hot pin 9, cold pin 22, gnd pin 10). Or should it simply be MTC generated from Pro Tools to MW midi in and mw option
2: Pro tools takes in machine commands somehow… midi MMC from Motionworker Serial port B Midi out set to mw option 11=Au Automation (MMC) (mw tech man 13-3) and mw option13=31 and mw option 14=B.B maybe? But this Automation option might not contain standard MMC? Pro Tools will respond to MMC if you enable “MIDI Machine Control Remote (Slave)” (ID important? 127) without being online as well as it is always sending out mmc referring to the Konnektor user guide .
3: Pro tools sends machine commands to Motionworker Midi in (enable mw option 10 but only stop and play commands supported in mw?).
4: SSL CPU Z8 pcb is connected to MW port JR7 with 26pin IDC to 25Pin Dsub female cable S88E for parallel data (not longer than 4 meters refering to recycled audio ssl computer pdf).
5: A dsub 25 male/female cable connected from the SSL s29e (at the console patch) to MW JR5.
(6: do we need to send LTC to the SSL CPU Timecode reader input or is the timecode to SSL provided over the Z8 paralelle data interface?)
References:Pro Tools Reference guide 2020.3 Chapter 59: MachineControl
https://resources.avid.com/SupportFiles/PT/Pro_Tools_Reference_Guide_2020.3.pdfKonnektor user guide which is not available on the internet.
I think the motion worker manuals are not scanned yet anywhere on the internet, right?
The Computer Rack - Recycled Audiowww.recycledaudio.co.uk › computerconfiguration
Please shoot back any feedback about these thoughts and let me know if I am just plain crazy
Is the only way to get to my objectives to have a Konnektor / SSL Virtual Tape Machine and then try to connect directly from Pro Tools to synchroniser over sony 9pin for example?
Thanks a lot for reading to the bottom of this post! Have a nice day
Best regards,
Uffe