Hello Markus Ketterl,
Thank you for your answer.
I already edited /opt/matterhorn/felix/conf/config.properties as follows:
org.opencastproject.streaming.url=rtmp://139.6.65.240/matterhorn-engage
org.opencastproject.streaming.directory=${org.opencastproject.storage.dir}/streams
I didn't change the streaming dir, because through the link, I think it
is already pointing to the right directory:
org.opencastproject.storage.dir=/opt/matterhorn/felix/work/opencast
root@pips03:~# ls -al /opt/matterhorn/red5/webapps/matterhorn/
..
lrwxrwxrwx 1 root root 43 6. Jun 15:26 streams ->
/opt/matterhorn/felix/work/opencast/streams
Also, I didn't edit
/opt/matterhorn/felix/conf/workflows/compose-distribute-publish.xml,
because the following already existed:
<!-- Distribute to download server -->
..
<operation
id="distribute-streaming"
fail-on-error="true"
if="${org.opencastproject.streaming.url}"
exception-handler-workflow="error"
description="Distributing to streaming server">
<configurations>
<configuration key="source-tags">engage,-publish</configuration>
<configuration key="target-tags">publish</configuration>
</configurations>
</operation>
I don't quite understand how this is connected with the engage media
module. I thought the way, if you have the URL to access directly the
RTMP-stream, you could play that stream through a website-integrated
flash or a separate video player.
In addition, on the testing server, the URL for the engage media module
seems to be
http://139.6.65.240:8080/engage/ui/embed.html?id=fc252959-44f7-43ad-b61d-fdfe602c1821
But as to my primary post, the URL to directly play the Red5-stream in,
let's say
http://www.wimpyplayer.com/products/wimpy_standalone_flv_player.html as
VLC seems not to be working, is:
rtmp://139.6.65.240/matterhorn-engage/fc252959-44f7-43ad-b61d-fdfe602c1821/65598c20-11be-4dca-8ad0-ca15c2ee2ff4/matterhorn_1_1_0_install_video_addendum.flv
So I do need that track id, don't I?
Greeting, [email protected]
Am 07.06.2011 19:43, schrieb Markus Ketterl:
> Hi,
> track is the reference to the 'mediaitem'.
> Like:
> <track ref="track:d1edaf64-3873-4f64-b31f-38cfa62273f4"
> type="presenter/delivery"
> id="track-25"><mimetype>video/x-flv</mimetype><tags><tag>engage</tag><tag>low-quality</tag><tag>publish</tag></tags><url>rtmp://yourserver/matterhorn-engage/841/d1edaf64-3873-4f64-b31f-38cfa62273f4/dozent.flv</url><checksum
>
> type="md5">f4e2590c193dd644758131d101e21498</checksum><duration>6059416</duration><audio
> id="audio-1"><device/><encoder type="MPEG
> Audio"/><channels>2</channels><bitrate>64000.0</bitrate></audio><video
> id="video-1"><device/><encoder
> type="H.263"/><bitrate>195312.0</bitrate><framerate>12.0</framerate><resolution>300x240</resolution></video></track>
>
> There is no need to search for track id. If you use the "distribute to
> streaming server operation" in your workflow definition you should end up
> with valid urls.
> Engage will select the right rtmp links.
>
> If you set the right streaming.url in your config.properties plus also add
> the distribute-to-streaming operation in your workflow you should be good to
> go.
> Hope this helps.
>
> Greetings from Osnabrück
> Markus
>
>
>> Hello Ladies and Gentlemen,
>>
>> According to the Matterhorn documentation, the URL for streaming a
>> recording should be:
>>
>> rtmp://10.0.1.2/matterhorn-engage/<id>/track/<filename>.flv
>>
>> Information through upload recording:
>>
>> General
>> start 2011-06-05T22:00:00Z
>> id fc252959-44f7-43ad-b61d-fdfe602c1821
>> duration 553090
>> title test123_3
>>
>> First try, failure:
>>
>> rtmp://139.6.65.240/matterhorn-engage/fc252959-44f7-43ad-b61d-fdfe602c1821/track/test123_3.flv
>>
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action connect
>> [INFO] [NioProcessor-1] org.red5.server.net.rtmp.RTMPHandler -
>> Connecting to: [WebScope@21aac775 Depth = 1, Path = '/default', Name =
>> 'matterhorn-engage']
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action createStream
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action play
>> [INFO] [NioProcessor-1] org.red5.server.stream.ProviderService - File
>> was null or did not exist:
>> fc252959-44f7-43ad-b61d-fdfe602c1821/track/test123_3.flv
>>
>> Looked content up, found it here:
>>
>> root@pips03:/opt/matterhorn/felix/work/opencast/streams/fc252959-44f7-43ad-b61d-fdfe602c1821/65598c20-11be-4dca-8ad0-ca15c2ee2ff4#
>> ls -al
>> insgesamt 41876
>> drwxr-xr-x 2 root root 4096 6. Jun 16:42 .
>> drwxr-xr-x 3 root root 4096 6. Jun 16:41 ..
>> -rw-r--r-- 1 root root 42806050 6. Jun 16:41
>> matterhorn_1_1_0_install_video_addendum.flv
>> -rw-r--r-- 1 root root 12885 6. Jun 16:42
>> matterhorn_1_1_0_install_video_addendum.flv.meta
>>
>> Second try, failure:
>>
>> rtmp://139.6.65.240/matterhorn-engage/fc252959-44f7-43ad-b61d-fdfe602c1821/track/matterhorn_1_1_0_install_video_addendum.flv
>>
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action connect
>> [INFO] [NioProcessor-1] org.red5.server.net.rtmp.RTMPHandler -
>> Connecting to: [WebScope@21aac775 Depth = 1, Path = '/default', Name =
>> 'matterhorn-engage']
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action createStream
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action play
>> [INFO] [NioProcessor-1] org.red5.server.stream.ProviderService - File
>> was null or did not exist:
>> fc252959-44f7-43ad-b61d-fdfe602c1821/track/matterhorn_1_1_0_install_video_addendum.flv
>>
>> Third try, success:
>>
>> rtmp://139.6.65.240/matterhorn-engage/fc252959-44f7-43ad-b61d-fdfe602c1821/65598c20-11be-4dca-8ad0-ca15c2ee2ff4/matterhorn_1_1_0_install_video_addendum.flv
>>
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action connect
>> [INFO] [NioProcessor-1] org.red5.server.net.rtmp.RTMPHandler -
>> Connecting to: [WebScope@2c79cd09 Depth = 1, Path = '/default', Name =
>> 'matterhorn-engage']
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action createStream
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action play
>> [INFO] [NioProcessor-1]
>> org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action seek
>>
>> But: how to get that "second id", shown in the path above? When I upload
>> a recording for example, the general information gives me only the
>> "<id>" mentioned in documentation. I could not find information about
>> "track". And, in production you should not be searching for files on the
>> server to get the right URL.
>>
>> Thank you in advance,
>> Greeting, [email protected]
>>
>> _______________________________________________
>> Matterhorn mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>
>>
>> To unsubscribe please email
>> [email protected]
>> _______________________________________________
>>
>
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/community
>
>
> To unsubscribe please email
> [email protected]
> _______________________________________________
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
