Results 1 to 5 of 5

Thread: nDVR "timeshift" stop working

  1. #1

    Default nDVR "timeshift" stop working

    Hi,

    I've tryed to use this nDVR addon and recorded content for 8 days. Today url to my content like

    "http://[wowza-address]:1935/dvr/myStream/manifest.f4m?DVR"
    has stopped worked. But if I try to request specific part of content by playlist request API I can get it.

    So urls to my content like

    http://[wowza-address]:1935/dvr/myStream/manifest.f4m?DVR&wowzadvrplayliststart=60000&wowzadvrplaylistduration=300000
    works well.

    In logs wowza only tryies to create stream without publishing it.


    What can I do?

  2. #2

    Default

    First, I think you need to consider a different manner of managing large recordings-- an 8 day recording is not very scalable as the playlist/manifest sent to the player will end up being in the 100's of Kb or even megabytes. Its also not fault tolerant. If one thing happens to your recording, you could lose it all. It also means that Wowzas needs to hold the every increasing manifest information in memory instead of loading and unloading manifest for smaller recordings as they are needed.

    A better way is to make individual recordings. You can write a custom module for this or use the example HTTP Provider found here: Wowza nDVR Recording API. You can also name each individual recording.


    Regarding your specific problem-- please send your zipped up conf/ and logs and send them to support@wowza.com. Explain in detail the player you are using, the URL the player uses, the encoder you are using, and any other pertinent details. Reference this thread.

    Scott

  3. #3

    Default

    I've tried your recording API.

    and I've got a question:

    At now in development I've got only one incoming stream channel and I can view it by this url:

    http://[wowza-address]:1935/live/DD_MM.[version]/playlist.m3u8?DVR
    But if there are lot of channels how can I specify which channel to see? I mean I need to create an unique name for each timestamp of each channel? There is no quiet well... (40 channels * 31 day * multibitrate) = BIG. Which url I need to use to access to content which stores per day/per channel or something like this?

    And I've find another problem:
    I've tried to use playlist request API to set the time from which user can view content for example:
    http://[wowza-address]:1935/dvr/mySt...iststart=60000

    So I don't use wowzadvrplaylistduration option and than I get position that I need + possibility of view live content. But when I've tried to seek to the oldest position (in quicktime player on iOS) that equals wowzadvrplayliststart and returns back I've observed that audio and video very asynchronious or video continues from old position but audio gets live position.
    Last edited by xzerth; 02-08-2012 at 04:06 PM. Reason: problem not occurs I've mistake

  4. #4

    Default

    1. Yes, if you have different channels, I would name them with different names. I would come up with a scheme for them-- [name][date][bitrate]. Whatever makes sense for your situation.

    Maybe channel number or maybe a name:

    http://[wowza-address]:1935/live/MTV_DD_MM.[version]/playlist.m3u8?DVR
    Regarding your playback issue on iOS, is that always reproducible?
    If you have stopped recording to that DVR store and play it back with the same URL, does it do it?
    Can you reproduce it in a reasonable sized dvr recording (not multi-day but something in the size of minutes to a couple hours?)
    If so, zip up your conf/ and logs/ folders from when you recorded and played back, as well as the associated [install]/dvr/app/appInst/streamName,[version] folder, which is the DVR recording.
    Also, let me know the URL you use to access the store, the player you are using, etc.
    Send this to support@wowza.com and refer to this thread.
    We'll take a look.

    Scott

  5. #5

    Default

    Hi,

    1) It's not very good but it's usable and we should use it I think at least we can't sort our recordings in other ways.

    2) This problem reproduce only in multi days recordings. At now when I start record in different dirs this problem disappears so I think we can just don't worry about this. In any case I've send you confs and logs.

Similar Threads

  1. "Doneness" doesn't work in live stream (nDVR)
    By harpman in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 05-30-2012, 01:20 PM
  2. How to stop "SHoutcast" application
    By tribalhost in forum Server Administration Discussion
    Replies: 8
    Last Post: 02-15-2012, 02:32 PM

Posting Permissions

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