Hi,
I am just testing the core (1.3) installation with the Wowza server and I can
confirm that the rtmp link format as below is correct, i.e.
rtmp://server/matterhorn-engage/_definst_/mp4:dir1/dir2/file.mp4
For example:
rtmp://server/matterhorn-engage/_definst_/mp4:4c00c68c-96e9-4cac-8748-9072ceb83c2f/track-2/G_Roberts_ses1_7_03_12.mp4
Following the above I did check the code produced inside the Media Player for
the same stream:
rtmp://server/matterhorn-engage/4c00c68c-96e9-4cac-8748-9072ceb83c2f/track-2/mp4:G_Roberts_ses1_7_03_12.mp4
which according to the above is in the WRONG format (?). And when supplied to
the Flash player it will generate the error message: "Stream contains no data".
By the way, I think it would be useful to add a paragraph to the Installation
of Wowza Media Server
http://opencast.jira.com/wiki/display/MHDOC/Wowza+Media+Server+3+v1.3
with the explanation of how to test working Wowza with the MH core.
Leslaw
On Apr 11, 2012, at 6:19 PM, Rute Santos wrote:
> Hi,
>
> Looking at the Wowza tutorial link below, it seems that Wowza also needs
> the "mp4:" after the application name and before the directory path in the
> rtmp link. The only difference from FMS seems to be that it requires the
> "_definst_" instance name, which FMS assumes by default if no instance is
> informed:
>
> http://www.wowza.com/forums/content.php?35#playback
>
> This is the relevant note:
>
> Note: To play content that is not at the root of the content folder you must
> add the default application instance name to the URL. For example if you have
> a file at the path [install-dir]/content/myvideos/sample.mp4, the URLs for
> the different stream technologies are:
>
> Flash player (RTMP)
> Code:
> Server: rtmp://[wowza-address]/vod
> Stream: mp4:myvideos/sample.mp4
>
> Single URL: rtmp://[wowza-address]/vod/_definst_/mp4:myvideos/sample.mp4
>
>
> Thus, an rtmp link in the form:
> rtmp://server/matterhorn-engage/_definst_/mp4:dir1/dir2/file.mp4 should work
> with both FMS and Wowza.
>
> Thanks,
>
> Rute
>
>
> On 4/9/2012 11:37 AM, Rute Santos wrote:
>>
>> Hi Ruben, Hank,
>>
>> I was looking at the Wowza documentation and it also has the concept of
>> "application" as FMS does. So, I am just wondering if Wowza accepts both
>> forms? I recall Hank said that the rtmp link is working with Wowza as is,
>> but I was wondering if he could try to use the other form and see if it
>> works too? I am curious...
>> Thanks,
>>
>> Rute
>>
>>
>> On 4/9/2012 11:33 AM, Hank Magnuski wrote:
>>>
>>> The "application" convention is certainly present in Wowza and I believe
>>> Red5 as well.
>>>
>>> Hank
>>>
>>> 2012/4/9 Rubén Pérez <[email protected]>
>>> It would be interesting to know if Wowza is effectively following the same
>>> convention. We have already have bizarre integration problems with FMS
>>> because it follows its own conventions as to the syntax of the media to
>>> stream.
>>>
>>> We would be happy to have that patch attached to the main source code,
>>> since we are FMS users ourselves, but I think we shouldn't stick to a
>>> certain notation if it's not shared by the popular streaming alternatives,
>>> too (I'm not saying it's not, just willing to get
>>> confirmation of it). I may be wrong here, but "application" seems like an
>>> internal FMS concept, which may not be share by other streaming servers. It
>>> also seems to me like an unnatural place to put the tag (I'd rather expect
>>> it to be before the filename or at the beginning of the URL), that's why
>>> I'm trying to be cautious here.
>>>
>>> Regards
>>>
>>> 2012/4/9 Tobias Wunden <[email protected]>
>>> Hi Rute,
>>>
>>> > We use FMS here with our current system to stream mp4 files and the
>>> > "mp4:" tag should come after the application name. So, if the file
>>> > resides several directory levels below e.g. dir1/dir2/file.mp4, the rtmp
>>> > link should contain "/app_name/mp4:dir1/dir2/file.mp4" and not
>>> > "app_name/dir1/dir2/mp4:file.mp4". The links you list below don't have
>>> > examples with many levels of directories. I don't know about Wowza, but I
>>> > bet it is the same :)
>>> > I have a patch for this if anyone is interested (how should I submit
>>> > it?)
>>>
>>> We are certainly interested to apply your patch if you've go this working!
>>> The correct for submitting patches is the following:
>>>
>>> 1) Open a ticket in JIRA describing your problem.
>>> 2) Us the "attach" function to attach your patch
>>>
>>> Also feel free to let the developers (on [email protected])
>>> know that you've submitted a patch and would welcome feedback and
>>> integration (optional step :-)
>>>
>>> Tobias
>>>
>>>
>>>
>>> _______________________________________________
>>> Matterhorn-users mailing list
>>> [email protected]
>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>>
>
> _______________________________________________
> Matterhorn-users mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
