gscam donot stream on nano,but do stream on tx2
vxgu86 opened this issue · 0 comments
gscam donot stream on nano,but do stream on tx2,
with nano, the nano and QGC all connect to the same hotspot,
for tx2, the QGC connect to tx2's hot spot.
that's the only difference, was this diff's problem?
here is the output of nano:
export GSCAM_CONFIG="v4l2src device=/dev/video0 ! tee name=t ! queue ! videoconvert ! omxh265enc ! video/x-h265, stream-format=byte-stream ! h265parse ! rtph265pay config-interl=1 ! udpsink host=192.168.43.184 port=6000 t. ! queue ! video/x-raw, width=1920, height=1080 ! videoconvert"
rosrun gscam gscam
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
[ INFO] [1570506196.474633043]: using default calibration URL
[ INFO] [1570506196.474751611]: camera calibration URL: file:///home/vx/.ros/camera_info/camera.yaml
[ INFO] [1570506196.474930634]: Unable to open camera calibration file [/home/vx/.ros/camera_info/camera.yaml]
[ WARN] [1570506196.475000723]: Camera calibration file /home/vx/.ros/camera_info/camera.yaml not found.
[ INFO] [1570506196.475090391]: Loaded camera calibration from
[ WARN] [1570506196.475998472]: No camera frame_id set, using frame "/camera_frame".
[ INFO] [1570506196.730035566]: Time offset: 1570504947.020
[ INFO] [1570506197.065613688]: Publishing stream...
[ INFO] [1570506197.066097905]: Started stream.
Framerate set to : 6 at NvxVideoEncoderSetParameterNvMMLiteOpen : Block : BlockType = 8
===== NVMEDIA: NVENC =====
NvMMLiteBlockCreate : Block : BlockType = 8
NVMEDIA: H265 : Profile : 1
and this is from my laotop:
gst-launch-1.0 udpsrc port=6000 ! application/x-rtp, encoding-name=H265,payload=96 ! rtph265depay ! h265parse ! avdec_h265 ! xvimagesink
//////////////////////////////////////////////////////////////////////////////////////////////////
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
then nothing show up.
did anyone ever encounter this problem?