On Thu, 1 Sep 2011, Ruediger Rolf wrote:
Hi Hank,
I don't think that this question only marginally Matterhorn related.
Have you tried to play the file with the JWPlayer?
Yes, plays perfectly.
Matterhorn currently does not offer MP4/H.264 encoding profiles. I guess you
only copied the files and their encoding from what your hardware already
encoded? I don't have ncast-hardware that I can check how good wowza works
with ncast mp4 files.
Yes, the files were run straight thru Matterhorn from our encoders. No
processing or compression by Matterhorn. We use Wowza for playing our files all
the time (usually with JW Player) and the resultes are excellent. No Problems.
Use of .mp4 files is critical to us because that is what our encoders generate
and conversion to .flv (which appears to create heavy loads on the workflow
servers and which becomes very time-consuming) is totally not needed when we
run the files straight through Matterhorn without any special processing.
Wowzas default codec is FLV. If the filetype is unclear you will have to
specify the application-instance:
rtmp://mycompany.com/myapplication/mp4:mycoolvideo.mov
see http://www.wowza.com/forums/content.php?217#flashRTMP
JW Player seems to figure this out and I don't have to change anything on the
server. What does Engage do in this respect? Isn't engage looking at any of the
media information from the Media-package? Media inspection seems to be
right-on:
Media
presenter/source video/mp4
presenter/delivery video/mp4
presenter/delivery video/mp4
presenter/delivery video/mp4
Matterhorns configuration currently does not support to specify the
application instance but in my short tests with wowza and my H.264 encoding
profile (see
http://opencast.jira.com/wiki/download/attachments/24445142/h264.properties?version=1&modificationDate=1305894747875)
it worked somehow, even without specifying the application-instance.
I specify the application instance for the Wowza server this way:
org.opencastproject.streaming.url=rtmp://nway.ncast.com/matterhorn-engage/streams
where "matterhorn-engage" is a directory under Wowza's "conf" directory and
contains an "Application.xml" file for the matterhorn instance.
Thus, there is always an application instance associated with any Matterhorn
streaming request. When I use JW Player to play this file it works perfectly.
With Engage it fails completely.
I don't know how important this application-instance is for Wowza, you
better ask them the question.
It's pretty important and I always use one for playback or live streaming. I
have several defined on my server for different types of streaming activities.
So I still don't understand what Engage is doing to cause this error and not
have Wowza play these files.
Hank
Am 01.09.2011 04:33, schrieb Hank Magnuski:
>
> I'm trying to get .mp4 files to play within Engage and they don't.
>
> Wowza is reporting the error below. Why does Engage think an .mp4 file is
> an .flv file?
>
> WARN server comment 2011-08-31 18:44:15 - - - - -
> 2371861.669 - - - - - - - MediaReaderFLV.open:
> Metadata appears to be bad:
> streams/ef3542a9-ed6d-4a74-80b3-267f04395413/track-2/20110402_101226_005.mp4
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
