Results 1 to 4 of 4

Thread: problem in liverepeateredge using '#' character

  1. #1
    Join Date
    May 2010
    Posts
    5

    Default problem in liverepeateredge using '#' character

    Hi,

    do you know if there are any limitation on stream name characters using liverepeater-edge?

    If I use the character '#' in the stream name, the edge try to retrieve a stream name truncated from the origin

    example:

    When I play "stream#1" this is renamed in "stream" in the request to the origin.

    Do you know if there is a workaround or patch? My version now is 3.5.2.

    Thanks,

    Davide

  2. #2
    Join Date
    May 2013
    Posts
    680

    Default

    Hello Davide,

    The liverepeater system will try and decode the stream name. So if you were to enter the stream name with its urlencoded representation it should play back. So from your player, something like:

    rtmp://[wowza-ip]:1935/live/stream%231
    Would be stream#1.

    Thanks,

    Matt

  3. #3
    Join Date
    May 2010
    Posts
    5

    Default

    Hi Matt,

    it works fine.

    Thanks for the quick support,

    Davide

  4. #4
    Join Date
    May 2013
    Posts
    680

    Default

    You're welcome.

Similar Threads

  1. Broken character encoding in closed captions on iOS8
    By dosercz in forum Closed Captioning
    Replies: 9
    Last Post: 04-13-2015, 02:05 AM
  2. Replies: 1
    Last Post: 05-22-2014, 02:10 PM
  3. mediacache problems character encoding
    By MARY2006 in forum Video On Demand Streaming Discussion
    Replies: 2
    Last Post: 02-13-2013, 03:12 PM
  4. different character set supported?
    By seongbae in forum Wowza Streaming Engine in the Cloud
    Replies: 1
    Last Post: 09-01-2009, 03:40 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •