search

philhartung / aes67-sender

Make a soundcard input available in an AES67 network
https://aes67.app
GNU General Public License v3.0
174 stars 19 forks source link

Error Could not sync to PTP master. Aborting. #2

Open jbittner1002 opened 3 years ago

jbittner1002 commented 3 years ago

I have PTP installed and bound to the eth0.

Why am I still getting this error ?

root@x92f3371a9a4f:/usr/src/aes67-sender# ethtool -T eth0 Time stamping parameters for eth0: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) software-receive (SOF_TIMESTAMPING_RX_SOFTWARE) software-system-clock (SOF_TIMESTAMPING_SOFTWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL) ptpv1-l4-sync (HWTSTAMP_FILTER_PTP_V1_L4_SYNC) ptpv1-l4-delay-req (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ) ptpv2-l4-sync (HWTSTAMP_FILTER_PTP_V2_L4_SYNC) ptpv2-l4-delay-req (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ) ptpv2-l2-sync (HWTSTAMP_FILTER_PTP_V2_L2_SYNC) ptpv2-l2-delay-req (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ) ptpv2-event (HWTSTAMP_FILTER_PTP_V2_EVENT) ptpv2-sync (HWTSTAMP_FILTER_PTP_V2_SYNC) ptpv2-delay-req (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ) root@x92f3371a9a4f:/usr/src/aes67-sender#

s0600204 commented 3 years ago

Hi there,

Are you using linuxptp (aka ptp4l)? If so, you should know that this application disables multicast loopback in its source code. This means that applications/services running on the same host as linuxptp are unable to see the PTPv2 clock it emits if you only bind ptp4l to external facing network interfaces.

You have three solutions to this, each of which should (in theory) work:

  1. Run linuxptp on a different device on your network,
  2. Specify the loopback network interface at the same time as the external facing network interfaces,
    • (e.g. ptp4l -i eth0 -i lo)
  3. Acquire and patch the linuxptp source to enable multicast loopback on interfaces.
mormegil6 commented 10 months ago

Hello there,

I am also having an issue with the PTP synchronisation. I am running the aes67-sender on Windows 10 machine which I installed without issues. I cannot run the sender despite running the PowerShell console with privileges.

Here's the output from the terminal:

PS C:\Users\user\Downloads\aes67-sender-master> w32tm /resync
Sending resync command to local computer
The command completed successfully.
PS C:\Users\user\Downloads\aes67-sender-master> w32tm /query /status /verbose
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0435235s
Root Dispersion: 7.7877779s
ReferenceId: 0x14653909 (source IP:  20.101.57.9)
Last Successful Sync Time: 30/01/2024 10:44:33
Source: time.windows.com,0x9
Poll Interval: 10 (1024s)

Phase Offset: -0.0000291s
ClockRate: 0.0156250s
State Machine: 1 (Hold)
Time Source Flags: 0 (None)
Server Role: 0 (None)
Last Sync Error: 0 (The command completed successfully.)
Time since Last Good Sync Time: 3.4476934s

PS C:\Users\user\Downloads\aes67-sender-master> node aes67 -a ASIO --devices
10:46:04  In ASIOImpl.cpp, line 91: Windows Audio Device initialized successfully: 10:46:04  In ASIOImpl.cpp, line 92: Input Device "Microphone Array (Realtek Audio)" - 10:46:04  In ASIOImpl.cpp, line 93: Output Device "Speakers / Headphones (Realtek Audio)" - 10:46:04  In ASIOImpl.cpp, line 94: Sample Rate 48000kHz - 10:46:04  In ASIOImpl.cpp, line 95: Buffer Size 480 - 10:46:04  In ASIOImpl.cpp, line 96: Input Channels 4 - 10:46:04  In ASIOImpl.cpp, line 97: Output Channels 2
Index, Name, # of Channels
0 OCTA-CAPTURE 12
1 Realtek ASIO 2
2 ReaRoute ASIO (x64) 16
3 VB-Matrix VASIO-128 128
4 VB-Matrix VASIO-64A 64
5 VB-Matrix VASIO-64B 64
6 VB-Matrix VASIO-8 8
7 WASM 4

PS C:\Users\user\Downloads\aes67-sender-master> node aes67 -v -a ASIO -d 0 -n "OCTA-CAPTURE" --address 192.168.1.123
Selected ASIO as audio api
10:46:49  In ASIOImpl.cpp, line 91: Windows Audio Device initialized successfully: 10:46:49  In ASIOImpl.cpp, line 92: Input Device "Microphone Array (Realtek Audio)" - 10:46:49  In ASIOImpl.cpp, line 93: Output Device "Speakers / Headphones (Realtek Audio)" - 10:46:49  In ASIOImpl.cpp, line 94: Sample Rate 48000kHz - 10:46:49  In ASIOImpl.cpp, line 95: Buffer Size 480 - 10:46:49  In ASIOImpl.cpp, line 96: Input Channels 4 - 10:46:49  In ASIOImpl.cpp, line 97: Output Channels 2
Selected device OCTA-CAPTURE with 12 input channels
Selected 239.69.2.240 as RTP multicast address.
Opening audio stream.
Trying to sync to PTP master.
Could not sync to PTP master. Aborting.

I tried running the above lines with two different network adapters -- the one built in my Dell Latitude laptop, and an external USB-C mini-dock, also by Dell. Sorry if this is too easy (or too complex!) to help with, but I hope you will find some time to at least give me a hint what should I do with this error :)

Renlong2020 commented 4 months ago

Hello there,

I am also having an issue with the PTP synchronisation. I am running the aes67-sender on Windows 10 machine which I installed without issues. I cannot run the sender despite running the PowerShell console with privileges.

Here's the output from the terminal:

PS C:\Users\user\Downloads\aes67-sender-master> w32tm /resync
Sending resync command to local computer
The command completed successfully.
PS C:\Users\user\Downloads\aes67-sender-master> w32tm /query /status /verbose
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0435235s
Root Dispersion: 7.7877779s
ReferenceId: 0x14653909 (source IP:  20.101.57.9)
Last Successful Sync Time: 30/01/2024 10:44:33
Source: time.windows.com,0x9
Poll Interval: 10 (1024s)

Phase Offset: -0.0000291s
ClockRate: 0.0156250s
State Machine: 1 (Hold)
Time Source Flags: 0 (None)
Server Role: 0 (None)
Last Sync Error: 0 (The command completed successfully.)
Time since Last Good Sync Time: 3.4476934s

PS C:\Users\user\Downloads\aes67-sender-master> node aes67 -a ASIO --devices
10:46:04  In ASIOImpl.cpp, line 91: Windows Audio Device initialized successfully: 10:46:04  In ASIOImpl.cpp, line 92: Input Device "Microphone Array (Realtek Audio)" - 10:46:04  In ASIOImpl.cpp, line 93: Output Device "Speakers / Headphones (Realtek Audio)" - 10:46:04  In ASIOImpl.cpp, line 94: Sample Rate 48000kHz - 10:46:04  In ASIOImpl.cpp, line 95: Buffer Size 480 - 10:46:04  In ASIOImpl.cpp, line 96: Input Channels 4 - 10:46:04  In ASIOImpl.cpp, line 97: Output Channels 2
Index, Name, # of Channels
0 OCTA-CAPTURE 12
1 Realtek ASIO 2
2 ReaRoute ASIO (x64) 16
3 VB-Matrix VASIO-128 128
4 VB-Matrix VASIO-64A 64
5 VB-Matrix VASIO-64B 64
6 VB-Matrix VASIO-8 8
7 WASM 4

PS C:\Users\user\Downloads\aes67-sender-master> node aes67 -v -a ASIO -d 0 -n "OCTA-CAPTURE" --address 192.168.1.123
Selected ASIO as audio api
10:46:49  In ASIOImpl.cpp, line 91: Windows Audio Device initialized successfully: 10:46:49  In ASIOImpl.cpp, line 92: Input Device "Microphone Array (Realtek Audio)" - 10:46:49  In ASIOImpl.cpp, line 93: Output Device "Speakers / Headphones (Realtek Audio)" - 10:46:49  In ASIOImpl.cpp, line 94: Sample Rate 48000kHz - 10:46:49  In ASIOImpl.cpp, line 95: Buffer Size 480 - 10:46:49  In ASIOImpl.cpp, line 96: Input Channels 4 - 10:46:49  In ASIOImpl.cpp, line 97: Output Channels 2
Selected device OCTA-CAPTURE with 12 input channels
Selected 239.69.2.240 as RTP multicast address.
Opening audio stream.
Trying to sync to PTP master.
Could not sync to PTP master. Aborting.

I tried running the above lines with two different network adapters -- the one built in my Dell Latitude laptop, and an external USB-C mini-dock, also by Dell. Sorry if this is too easy (or too complex!) to help with, but I hope you will find some time to at least give me a hint what should I do with this error :)

Hello, may I ask if your issue has been resolved? I have also encountered the same problem and look forward to your reply