Topic: TCO (hdsp) virtual sync port

The manual says that this port should appear in the sync menu of the host (Cubase SX2 in my DAW), to use the ASIO Positioning Protocol correctly.
Why I can't see it?
Actually I'm slaving the DAW through the LTC In (from multitrack deck) of the TCO, the MTC generated by a MOTU MTP (only MTC, no WordClock) through his sync port that appears in Cubase, and linking the WordClock from TCO to my Digiface.
The system seems to work properly, but sometime the MTP freeze and I have to restart Cub to get the sync again.
Probably the APP works better but without this virtual TCO port in the Cub menu the MIDI tracks goes back and forth tryng to sync unsuccesfully.
Please help.
3FRS

Re: TCO (hdsp) virtual sync port

hmmm...maybe because I was reading an old user's manual?
The last one says that there are limitations using APP with Digi/Multiface (No virtual sync port)...
Am I right?
If yes, is there a chance to get this option thru future drivers (or hardware) update?
3FRS

3

Re: TCO (hdsp) virtual sync port

Are you talking Mac? Then there is no ASIO, thus no APP. Note that MF/DF need an external wordclock connection from the TCO WC out to the MF-DF WC In, or the whole system will not work.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

PC DAW with PCIe/Digiface+TCO:
I can set TCO in the driver sync options, but there's no TCO virtual sync port in the Cubase sync settings, then I can't use APP.
The TCO generate the clock from LTC in and the WC out of TCO is connected to the DF (I can see it in the TCO tab of the driver window), but I have to use the Midi time code sync method in Cubase (generated by MOTU MTP) instead of APP.
As said before, the system seems to work correctly: I can pull up (or down) the pitch of the deck up to 1-1,5% and hear (and see in the window) the frequency clock going up and down without drifting.
But sometime the MTP freezes, the DAW stops and I have to (save at first!!) restart cubase.

Re: TCO (hdsp) virtual sync port

I try to explain in a different way: Can I use APP with a non APP MIDI Timecode sync source (MOTU MTC Syncport in my case)? Or: If I send a MTC to the DF box MIDI In, could APP works?

6

Re: TCO (hdsp) virtual sync port

It might be that this feature is missing in the latest driver. I will check.

Regards
Matthias Carstens
RME

7

Re: TCO (hdsp) virtual sync port

Seems to work. In Cubendo you just have to check 'ASIO Positioning Protocol' or 'ASIO Audio Device' as timecode source. No port selection.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

At page 8 the manual says:
"Note: The MTC signal is provided via a new (virtual) MIDI input port. This one has to be chosen
as MTC sync source in the application."
Followed by:
"7.3 Notes on using the HDSPe PCI
Since driver version 3.068 the TCO can also be used with the HDSPe PCI, and therefore with
Multiface and Digiface. The following notes and limitations apply: 
•  Only ASIO timecode (APP) is supported. Converting LTC to MTC is not supported."

Selecting APP without any MTC sync source causes (in my setup) the MIDI to wander in search of the correct time position.
I suppose that's relative to the manul's above indications.
3FRS

9

Re: TCO (hdsp) virtual sync port

You either select MTC or APP, but not both. Please provide a screenshot.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

...mmmhhh... :roll
Could you explain the procedure to place screenshots?

TY
3FRS

11

Re: TCO (hdsp) virtual sync port

http://take-a-screenshot.org/

12

Re: TCO (hdsp) virtual sync port

Hmmm, I think he meant how to upload it here. Use any file/photo/document hosting service then add the image tag in your post, with the correct url in it. There is no direct upload to our site. If that is too complicated for you just send the screenshot to us directly.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

OK...Thanks for the suggestion...

This is the way I'm actually working with:
http://s19.postimage.org/rjtyijxrz/sync_settings.jpg
The sync is really stable, but sometime the MTP crashes and I have to restart Cub to go on.

Choosing APP needs this:
http://s19.postimage.org/ybkdlemrj/APP_sync_settings.jpg
But the TCO manual says that I should have an MTC (virtual) syncport to select in the MTC sync settings field; in my setup this port does not appear, probably due to the limitations exposed before.

Both the situations use TCO as LTC to WC conversion with the driver windows settings as follow:
http://s19.postimage.org/nkwqzq94v/RME_Settings.jpg

and
http://s19.postimage.org/pqr1u8clb/RME_TCO.jpg

Is this correct or something's missing?

3FRS

14

Re: TCO (hdsp) virtual sync port

When using MIDI Timecode (first pic) what MIDI ports are shown in the MID Timecode Settings dropdown list? The choice here is wrong. You should see the two MIDI ins of the Digiface plus one HDSP MTC port. Selecting MTP AV makes no sense.

If these MIDI ports are missing then this might be an older XP machine and you ran into the 10 port entry limitation. Or have to reset all the MIDI ports within Cubase.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

I have only the two MIDI In of the DF.
There's no HDSP MTC in the drop down list; even the Window's (continuously updated SP3) hardware list doesn't show it.
I think this is the nature of the problem.
I'll try to reset the ports and see the changes; this is a very old installation and I never reset the ports.


The Midi Timepiece receives the same LTC that goes to the TCO and generate the MTC transmitted directly into the computer parallel port.
3FRS

16

Re: TCO (hdsp) virtual sync port

Can you please check the firmware version of your HDSPe card? The TCO is supported since firmware 14, current is 18.

Also in the Settings dialog, the DF MUST be set to WC in, not TCO. There is no word connection internally, that's why you have to connect the external wc cable - and select the appropriate input.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

HDSPe driver version 3.27
Hardware Revision 18
SN 22679221
TCO Revision 4 (no answer by Synthax to my request for fw updates)

Never thought about te wc connection (I've just connected...) and never tried the APP with wc in the sync source dropdown list.
I'll do it ASAP
TY
3FRS

18

Re: TCO (hdsp) virtual sync port

Revision 4 is no good - we are at 8 now. Please keep bothering them. But that doesn't explain the missing HDSP MTC port. We are checking the driver code.

Regards
Matthias Carstens
RME

Re: TCO (hdsp) virtual sync port

No way to select wc in the DF window, doing so makes the sample rate go crazy.
To sync to an external wc, I have to choose TCO in the DF and WCK in the TCO windows.
In the same way, syncing to an analog recorder, TCO in the DF and LTC in the TCO windows is the only way to go.
I've contacted Midiware here in Rome for the updated EPROM.
3FRS

Re: TCO (hdsp) virtual sync port

bump
Did you check the driver?
I'm waiting the new EPROM from Midiware.

3FRS

21

Re: TCO (hdsp) virtual sync port

The MTC port seems to be missing in the driver (it has never been in for the MF and DF). But the MTC port is not necessary for a successful ASIO Positioning Protocol synchronization.

Regards
Matthias Carstens
RME