https://www.wowza.com/docs/how-to-use-apple-quicktime-broadcaster-with-wowza-media-server-rtsp-rtp
Post the section of the logs that shows the publishing of the stream and the attempt to play the stream. Be sure you have the capitalization correct. The guide suggests a stream name of myStream.sdp. Your comments suggest you are using mystream.sdp.
Charlie
Hi,
I have been trying to use the VBrick Encoder box which has almost same publishing mechanism like quicktime broadcaster…(Unicast over TCP)
box is pushing stream successfully, but I can’t playback the stream. Wowza access log shows following line
2010-01-01 18:56:37 CST comment server INFO 200 - defaultVHost home directory: C:\Program Files\Wowza Media Systems\Wowza Media Server 2 Preview 9 - - - 1.456 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:38 CST vhost-start vhost INFO 200 defaultVHost - - - - 1.954 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:38 CST comment vhost INFO 200 defaultVHost Bind attempt ([any]:1935) - - - 2.023 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:38 CST comment vhost INFO 200 defaultVHost Bind successful ([any]:1935) - - - 2.025 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:38 CST comment vhost INFO 200 defaultVHost Bind attempt ([any]:8086) - - - 2.028 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:38 CST comment vhost INFO 200 defaultVHost Bind successful ([any]:8086) - - - 2.029 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:54 CST app-start application INFO 200 definst vboss/definst - - - 18.078 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:54 CST connect rtsp INFO 200 197939473 - defaultVHost vboss definst 18.155 [any] 1935 rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp 76.168.247.219 rtsp - - 197939473 0 0 - - - - - - - - - - - - - rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp -
2010-01-01 18:56:54 CST announce rtsp INFO 200 197939473 - defaultVHost vboss definst 18.165 [any] 1935 rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp 76.168.247.219 rtsp - - 197939473 0 0 - - - - - - - - - - - - - rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp -
2010-01-01 18:56:54 CST comment server WARN 200 - RTSPCore.setup: track missing: trackid=111 - - - 18.291 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:54 CST comment server WARN 200 - RTSPCore.setup: track missing: trackid=112 - - - 18.351 - - - - - - - - - - - - - - - - - - - - - - - - -
2010-01-01 18:56:54 CST publish rtsp INFO 200 197939473 - defaultVHost vboss definst 18.413 [any] 1935 rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp 76.168.247.219 rtsp - - 197939473 0 0 - - - - - - - - - - - - - rtsp://[any]:1935rtsp://67.192.80.14/vboss/myStream.sdp -
2010-01-01 18:59:17 CST connect-pending session INFO 100 127.0.0.1 - defaultVHost vboss definst 0.024 [any] 1935 rtmp://localhost/vboss 127.0.0.1 rtmp unknown WIN 10,0,22,87 1930838160 3324 3073 - - - - - - - - - - - - - rtmp://localhost/vboss -
2010-01-01 18:59:17 CST connect session INFO 200 127.0.0.1 - defaultVHost vboss definst 0.026 [any] 1935 rtmp://localhost/vboss 127.0.0.1 rtmp unknown WIN 10,0,22,87 1930838160 3324 3073 - - - - - - - - - - - - - rtmp://localhost/vboss -
The error log file has following lines of error :
WARN server comment 2010-01-01 18:56:54 - - - - - 18.291 - - - - - - - RTSPCore.setup: track missing: trackid=111
WARN server comment 2010-01-01 18:56:54 - - - - - 18.351 - - - - - - - RTSPCore.setup: track missing: trackid=112
Not sure…what am I missing here…
I followed all the steps mentioned,
Thanks,
nirav.
if this does not work with iphone/ipod why we have to follow it?
can we use the same but with flash media encoder? will it works?
what would be the best encoder for iphone/ipod/ipad and what configuration should be used?
i have:
-
Wowza 2.1.2
-
wirecast 3.8
-
flashmedia encoder 3
-
Quicktime broadcaster
which will work best for iphone/ipod/ipad?
my Application.xml:
digest
none
senderreport
12000
*
But playing is still required to enter username and password.
How to configure to use rtsp protocol playing, do not need to enter account and password. That is, do not need to configure the “[install-dir] / conf / publish.password” this document.
Either:
-
In QT Broadcaster select the Broadcast over TCP option
-
In Wowza config file [install-dir]/conf/Server.xml change the RTP/DatagramStartingPort to a value such as 10000
Charlie
That should work. Do you see any warning/errors in the Wowza log files regarding the video/audio format?
Charlie
There is something here that is not right. I will try to look at this and post back. Could be a week or so.
Charlie
I took a quick look at it worked for me on Windows but not Mac. Here is exactly what I tried. I had to modify the settings a bit because my Mac is a bit older:
Video source: iSight Camera
Telestream Wirecast: 3.5.8 (latest shipping version)
Settings:
Transport was the same (RTSP/RTP over TCP)
Video:
H.264/Baseline/Color
480x360/30fps/60 frames-per-key/900Kbps
Audio:
MPEG-4/16-bit/stereo
Wowza 2.1.2.04 (download here - carefully read the included README for extra instructions)
Windows QuickTime version 7.6.8:
Played great for me using both RTSP/RTP over UDP and RTSP/RTP tunneling. I tried it on two different machine.
Mac QuickTime version 10.0 (114)
I got the Max Headroom effect. What is interesting is that the option to switch to RTSP/RTP tunneling no longer exists. So it is tough to rule out UDP packet loss. I did see some artifacts that looked like packet loss. I tried lowering the frame size and bit rate and still had the same problem. So it does seem like it is most likely not packet loss. Also, VLC on the same machine using RTSP/RTP over UDP worked fine.
Other interesting observations:
-
On Windows I had to turn off the DirectX acceleration to get video to play.
-
On the Mac when I opened the inspector it did not show the correct video frame dimensions.
It sure points to a problem with QuickTime 10.x on Mac. I don’t have Darwin setup so that I can test side by side.
Charlie
Looking at this more, there is something that is just not right. Still working on it.
Charlie
I figured it out. It was a problem on our end. I will post a patch here that fixes the problem ASAP. We were formatting the RTP packets incorrectly when a frame contained multiple NAL units.
Charlie
The fix is in Wowza Media Server 2.1.2 patch5 or greater:
IMPORTANT!!!
Several core components have been updraded to newer versions. Before
applying this patch, delete the following files from your Wowza Media Server
installation:
[install-dir]/lib/bcprov-ext-jdk15-143.jar
[install-dir]/lib/commons-lang-2.4.jar
[install-dir]/lib/log4j-1.2.15.jar
Charlie
In QuickTime Broadcaster be sure to choose H.264 as the video format. You must have chosen H.263 which will generate these errors.
Charlie
I think you can start at higher number:
m=video 6980 RTP/AVP 97
Using Broadcast over TCP, do you try adding Application.xml /MediaCaster Property:
<Property>
<Name>forceInterleaved</Name>
<Value>true</Value>
<Type>Boolean</Type>
</Property>
Richard
Can you take screenshots of the encoder screens, provide the QuickTime broadcaster version number and zip up /conf and /logs and send to support@wowza.com
Richard
Also, include a reference to you post.
Richard
Try setting the Application.xml /RTP /Authentication /PublishMethod to “none”
Richard
If the Application.xml /RTP /Authentication /PlayMethod is “none”, as you have above, the player should not ask for username and password. Double check that.
Richard