|
Post by Skylar MSGC on Jun 13, 2017 9:18:49 GMT -7
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:21:08 GMT -7
DougGranger LSU : I am just running ffmpeg version 3.3.1 (64bit), in that build that should be correct ffmpeg -i rtsp://192.168.1.3:8554/ -c copy -f rtp_mpegts rtp://localhost:4000 -c copy -f flv - | ffmpeg -f flv -i - -c copy -f flv rtmp://media.stream.live:1935/live/[RTMPKEYHERE] Is that similar to what you are using? No. this is the command string i was using.... ffmpeg -i rtsp://192.168.1.3:8554/ -c copy -f flv - | ffmpeg -f flv -i - -c copy -f rtp://localhost:4000 -c copy -f flv rtmp://media.stream.live:1935/live/(KEY) You have this posted in another post in the Streaming Clarification post.
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:23:06 GMT -7
It does not matter it still breaks. I think it does not like my key at all. I can't get either version to work. DougGranger LSU : I am just running ffmpeg version 3.3.1 (64bit), in that build that should be correct ffmpeg -i rtsp://192.168.1.3:8554/ -c copy -f rtp_mpegts rtp://localhost:4000 -c copy -f flv - | ffmpeg -f flv -i - -c copy -f flv rtmp://media.stream.live:1935/live/[RTMPKEYHERE] Is that similar to what you are using? No. this is the command string i was using.... ffmpeg -i rtsp://192.168.1.3:8554/ -c copy -f flv - | ffmpeg -f flv -i - -c copy -f rtp://localhost:4000 -c copy -f flv rtmp://media.stream.live:1935/live/(KEY) You have this posted in another post in the Streaming Clarification post.
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:24:22 GMT -7
Skylar, can you also get us the spreadsheet that has the streaming links? The one i have does not have the O column.
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:29:43 GMT -7
It seems like my problems have to do with my key. When i use one of my other keys everything works fine and i am able to stream.
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:40:26 GMT -7
I believe i have my key problem fixed. The spreadsheet has my key wrong. there are too many characters at the end of my key. For some reason there is a dgrang at the end. Removing that fixed my one issue. I must have pasted something in the line. I can now stream using the proper key. Still cant watch the feed on the stream site, but everything else seems to be working locally.
|
|
|
Post by Skylar MSGC on Jun 13, 2017 9:40:49 GMT -7
|
|
|
Post by DougGranger LSU on Jun 13, 2017 9:48:32 GMT -7
I sent an email to Keith at stream.live and asked about that same thing. This is what he sent me back, this should have all the rows in it now. perfect. thank you. everything is awesome
|
|
|
Post by Skylar MSGC on Jun 13, 2017 10:17:26 GMT -7
When you are looking at streameclipse.live you can view all of the current streams. You may need to zoom out to see a video toolbar on the right. I have my zoom at 90% to be able to see the videos on the right.
|
|
|
Post by Skylar MSGC on Jun 13, 2017 10:41:37 GMT -7
Just as an update this is the command that you should be using to view the stream. The first post in this thread has been update to have this command also
ffmpeg -i rtsp://192.168.1.3:8554/ -c copy -f flv - | ffmpeg -f flv -i - -c copy -f rtp_mpegts rtp://localhost:4000 -c copy -f flv rtmp://media.stream.live:1935/live/[RTMPKEYHERE]
|
|
|
Post by deniseund on Jun 14, 2017 15:19:32 GMT -7
We are on our university's wifi and are manually setting the static ip to 192.168.1.2 and the subnet mask to 255.255.255.0. Should we be on some other network? Even when we connect everything and turn the video payload on (and both ubiquiti modems are getting a good signal) the pc is unable to locate the pi- when we type ipconfig we only see the pc, and when we try to ping the pi, we get no results.
|
|
|
Post by Skylar MSGC on Jun 14, 2017 15:36:05 GMT -7
Would you be able too post a screenshot of your ipconfig results. If you have your ethernet connection set as a static IP and your wifi as dhcp (automatically picking up the network information) you should be able to ping the RPi and google.com on the same laptop.
|
|
|
Post by deniseund on Jun 14, 2017 18:05:58 GMT -7
We have the ethernet connection set to a static IP and the wifi is also dhcp but we are unable to locate the pi. It appears that we are having a number of different problems: 1. The ethernet driver for the ground station laptop was not working and will not recognize any ethernet cord, So we switched to a different laptop to see if we could talk to the pi, and we were initially able to see it, when the sd has the OS (2017-06-09-eclipse-pi.img) written as specified in video "Streaming to Stream: Video Payload Pi Code Update (Flashing SD card with video Pi updates)" using release 2017-06-09 from github.com/MSU-BOREALIS/VideoStreaming. 2.When the sd card has 2017-06-09-eclipse-pi.img written on it, we were first able to connect to pi using putty but we can not see "Ubiquiti_Pi_Code" directory on the pi as mentioned in the document "Video Payload 7.19.2016.pdf", why is it so? 3. Then we tried to write the rfd image file on the sd card (already having the 2017-06-09-eclipse-pi.img file on it) and try to connect to the pi using putty but we are unable to do so. Queries: Q1. Which OS image is supposed to be on the video sd card? If its "2017-06-09-eclipse-pi.img", then why is the directory "Ubiquiti_Pi_Code" missing? Q2. Even if "ipconfig" command shows the LAN connection for 192.168.1.2, Why is it giving network connection error when we try to connect to pi using putty? Q3. Has anyone else had issues with their ground station pc not recognizing ethernet? We believe it might have something to do with the windows 10 OS but are not sure. putty screenshot:
|
|
|
Post by DougGranger LSU on Jun 15, 2017 7:58:16 GMT -7
We have the ethernet connection set to a static IP and the wifi is also dhcp but we are unable to locate the pi. It appears that we are having a number of different problems: 1. The ethernet driver for the ground station laptop was not working and will not recognize any ethernet cord, So we switched to a different laptop to see if we could talk to the pi, and we were initially able to see it, when the sd has the OS (2017-06-09-eclipse-pi.img) written as specified in video "Streaming to Stream: Video Payload Pi Code Update (Flashing SD card with video Pi updates)" using release 2017-06-09 from github.com/MSU-BOREALIS/VideoStreaming. 2.When the sd card has 2017-06-09-eclipse-pi.img written on it, we were first able to connect to pi using putty but we can not see "Ubiquiti_Pi_Code" directory on the pi as mentioned in the document "Video Payload 7.19.2016.pdf", why is it so? 3. Then we tried to write the rfd image file on the sd card (already having the 2017-06-09-eclipse-pi.img file on it) and try to connect to the pi using putty but we are unable to do so. Queries: Q1. Which OS image is supposed to be on the video sd card? If its "2017-06-09-eclipse-pi.img", then why is the directory "Ubiquiti_Pi_Code" missing? Q2. Even if "ipconfig" command shows the LAN connection for 192.168.1.2, Why is it giving network connection error when we try to connect to pi using putty? Q3. Has anyone else had issues with their ground station pc not recognizing ethernet? We believe it might have something to do with the windows 10 OS but are not sure. putty screenshot: Q1 Answer: There is no Ubiquiti_Pi_Code folder in the new release version. I can not remember the exact name now, but it is a folder inside the /home/pi/ directory tree. Network issues: i will come back to look at it. have a meeting right now
|
|
|
Post by nzarilla on Jun 16, 2017 10:32:43 GMT -7
We have the ethernet connection set to a static IP and the wifi is also dhcp but we are unable to locate the pi. It appears that we are having a number of different problems: 1. The ethernet driver for the ground station laptop was not working and will not recognize any ethernet cord, So we switched to a different laptop to see if we could talk to the pi, and we were initially able to see it, when the sd has the OS (2017-06-09-eclipse-pi.img) written as specified in video "Streaming to Stream: Video Payload Pi Code Update (Flashing SD card with video Pi updates)" using release 2017-06-09 from github.com/MSU-BOREALIS/VideoStreaming. 2.When the sd card has 2017-06-09-eclipse-pi.img written on it, we were first able to connect to pi using putty but we can not see "Ubiquiti_Pi_Code" directory on the pi as mentioned in the document "Video Payload 7.19.2016.pdf", why is it so? 3. Then we tried to write the rfd image file on the sd card (already having the 2017-06-09-eclipse-pi.img file on it) and try to connect to the pi using putty but we are unable to do so. Queries: Q1. Which OS image is supposed to be on the video sd card? If its "2017-06-09-eclipse-pi.img", then why is the directory "Ubiquiti_Pi_Code" missing? Q2. Even if "ipconfig" command shows the LAN connection for 192.168.1.2, Why is it giving network connection error when we try to connect to pi using putty? Q3. Has anyone else had issues with their ground station pc not recognizing ethernet? We believe it might have something to do with the windows 10 OS but are not sure. putty screenshot: Q1 Answer: There is no Ubiquiti_Pi_Code folder in the new release version. I can not remember the exact name now, but it is a folder inside the /home/pi/ directory tree. Network issues: i will come back to look at it. have a meeting right now For Q1, the streaming code is in /home/pi/bin/python/auto_record; For Q2, we also had a number of issues getting the Pi to connect through SSH, however after letting it just sit for around 10 minutes and trying again it worked. I don't know if that was a fluke, or if it just needed some time to refresh the connection after all of the hardware was powered on.
|
|