Hi Rudiger,


ad 1) Red5 does not really work with MP4 files (no seeking) and it does not know about the mp4: notation. For Wowza and FMS it seems that the current notation should be right as far as I see it [1] [2]. We will use MP4 with wowza in the next semester. And it principle it works, with the current notation.

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?)

ad 2) I don't know the error message. I have not seen it yet. But I've encountered the problem that we have to press play twice. At the first press I sometimes get only the audio and at the second the video starts to play to. This is not 100% reproduceable. But we will create a patch for this.

I think I only see the complete error because I have the debugger version of the flash player on my system. I've seen the behavior you describe on a co-worker's system, where it fails silently, but clicking twice works.

    Thanks,

    Rute


Regards
Rüdiger

[1] http://www.wowza.com/forums/content.php?3-quick-start-guide
[2] http://www.adobe.com/devnet/flashmediaserver/articles/beginner_vod_fm3.html

Am 04.04.2012 19:21, schrieb Rute Santos:
Hi,

I am trying to stream an H.264 file and I am seeing two problems:

1) First, I get a 'stream not found' error. I tested with both Red5 and Flash Media server. Looking at the media package, I think that the rtmp link is generated with the "mp4:" tag misplaced (before the file name instead of before the complete path to the file): rtmp://de-dev-flash1.de-dev.harvard.edu/matterhorn-engage/e02b9b71-cac8-406d-9e30-922c559d88a4/track-3/mp4:20120403_142902_003.mp4
instead of
rtmp://de-dev-flash1.de-dev.harvard.edu/matterhorn-engage/mp4:e02b9b71-cac8-406d-9e30-922c559d88a4/track-3/20120403_142902_003.mp4 If I provide the modified rtmp link as the 'videoUrl' parameter to the engage player to override what is in the media package, the file is found but then I have the second problem below.

2) The engage player shows the error: "Error: The specified capability is not currently supported" in . If I dismiss the error and click on play again twice, the stream plays.

Has anyone experienced the same when streaming .mp4's? I couldn't find any similar bug in the jira, but I assume someone is using .mp4 streaming (?)

We have Matterhorn 1.3. I am using the ncast-mp4-segment-distribution-stream workflow to generate the mp4 file.

Thanks,

Rute Santos
Harvard DCE

_______________________________________________
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

Reply via email to