[Red5] 64-bit linux issue - URGENT

Sat Jan 24 13:54:27 PST 2009

Yes, the file plays fine when I place it under oFlaDemo.

Let me look into how I am determining the size of my temp-file backed file
channel.

On Sat, Jan 24, 2009 at 1:41 PM, Michael Eckhoff <mreckhof at gmail.com> wrote:

> Yes - if you're doing any sort of bitlevel manipulation, you could
> cause issues if you don't have your types correct.
>
> If you're not using C though, you may not have to worry about it.
>
> >From what you're saying, you can take the tmp file, copy it over and
> let oflaDemo serve it, and it works fine?
>
> Michael
>
> On Sat, Jan 24, 2009 at 3:34 PM, Ritu Raj Tiwari
> <rituraj.tiwari at gmail.com> wrote:
> > I am using the FlVReader written by Dominick et al and I have modified it
> to
> > use a FileChannel implementation that my caching code hands out, backed
> by
> > the latest temp file. Everything else about the FLVReader is unchanged.
> >
> > I tried the oflaDemo and it runs fine. I am at my wit's end with where
> the
> > problem might be.
> >
> > Right now I am combing trough the diff between my code and Red5's ...
> >
> > On Sat, Jan 24, 2009 at 12:55 PM, Michael Eckhoff <mreckhof at gmail.com>
> > wrote:
> >>
> >> Good. That should rule out quite a few things.
> >> Look for anyplace you might be making assumptions about the sizeof()
> >> things. May be cutting something off someplace.
> >> I would doubt a byteorder issue if you're using the same architecture
> >> unless you've intentionally messed with it someplace.
> >> Michael
> >>
> >> On Jan 24, 2009, at 2:24 PM, Ritu Raj Tiwari <rituraj.tiwari at gmail.com>
> >> wrote:
> >>
> >> Sorry, this response was for Michael
> >>
> >> On Sat, Jan 24, 2009 at 12:12 PM, Ritu Raj Tiwari
> >> <rituraj.tiwari at gmail.com> wrote:
> >>>
> >>> Mondain,
> >>> Appreciate your quick response.
> >>>
> >>> Looks like my code for writing the temp file is working. Looking at the
> >>> file through  od -x on 32 bit and 64 bit machines shows the same
> contents:
> >>> Win32:
> >>> 0000000 4c46 0156 0001 0000 0009 0000 1200 0000
> >>> 0000020 009f 0000 0000 0000 0002 6f0a 4d6e 7465
> >>> 0000040 4461 7461 0861 0000 0700 0800 7564 6172
> >>> 0000060 6974 6e6f 4000 8553 b81e eb51 0085 7705
> >>> 0000100 6469 6874 4000 0084 0000 0000 0000 6806
> >>> 0000120 6965 6867 0074 7e40 0000 0000 0000 0d00
> >>> 0000140 6976 6564 646f 7461 7261 7461 0065 0000
> >>> 0000160 0000 0000 0000 0900 7266 6d61 7265 7461
> >>> 0000200 0065 3940 0000 0000 0000 0c00 6976 6564
> >>>
> >>> Lin64:
> >>> 0000000 4c46 0156 0001 0000 0009 0000 1200 0000
> >>> 0000020 009f 0000 0000 0000 0002 6f0a 4d6e 7465
> >>> 0000040 4461 7461 0861 0000 0700 0800 7564 6172
> >>> 0000060 6974 6e6f 4000 8553 b81e eb51 0085 7705
> >>> 0000100 6469 6874 4000 0084 0000 0000 0000 6806
> >>> 0000120 6965 6867 0074 7e40 0000 0000 0000 0d00
> >>> 0000140 6976 6564 646f 7461 7261 7461 0065 0000
> >>> 0000160 0000 0000 0000 0900 7266 6d61 7265 7461
> >>> 0000200 0065 3940 0000 0000 0000 0c00 6976 6564
> >>>
> >>> This must be an issue with the FLVReader reading off of the file.
> >>>
> >>> On Sat, Jan 24, 2009 at 11:38 AM, Mondain <mondain at gmail.com> wrote:
> >>>>
> >>>> It would appear that your video files are getting corrupted, I suggest
> >>>> you find an alternative means to transfer them to your linux box; did
> you
> >>>> try a Samba share or are you pulling them via HTTP?
> >>>> Paul
> >>>>
> >>>> On Sat, Jan 24, 2009 at 11:01 AM, Ritu Raj Tiwari
> >>>> <rituraj.tiwari at gmail.com> wrote:
> >>>>>
> >>>>> Good people of this mailing list, I hate to put "urgent" in my
> message,
> >>>>> but this one was absolutely required.
> >>>>>
> >>>>> My Red5 app fetches files over the web, caches them in local temp
> files
> >>>>> and streams off of the local files. It works fine on my 32-but Win
> and Linux
> >>>>> machines but when I run the same code on my deployment machine which
> is 64
> >>>>> bit Unubtu 8.04, I see no video. My red5 logs show messages like:
> WARNING:
> >>>>> Unexpected type? -25
> >>>>>
> >>>>> I am sure this has to do with the way I am writing the temp
> >>>>> file...maybe some network byte order issue? Or bytes I should have
> zeroed
> >>>>> out before flushing the byte buffers?
> >>>>>
> >>>>> Has anyone else run into something like this that they solved?
> >>>>>
> >>>>> Thanks for reading.
> >>>>>
> >>>>> --
> >>>>> -Raj
> >>>>>
> >>>>> _______________________________________________
> >>>>> Red5 mailing list
> >>>>> Red5 at osflash.org
> >>>>> http://osflash.org/mailman/listinfo/red5_osflash.org
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> http://gregoire.org/
> >>>> http://osflash.org/red5
> >>>>
> >>>> _______________________________________________
> >>>> Red5 mailing list
> >>>> Red5 at osflash.org
> >>>> http://osflash.org/mailman/listinfo/red5_osflash.org
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> -Raj
> >>
> >>
> >>
> >> --
> >> -Raj
> >>
> >> _______________________________________________
> >> Red5 mailing list
> >> Red5 at osflash.org
> >> http://osflash.org/mailman/listinfo/red5_osflash.org
> >>
> >> _______________________________________________
> >> Red5 mailing list
> >> Red5 at osflash.org
> >> http://osflash.org/mailman/listinfo/red5_osflash.org
> >>
> >
> >
> >
> > --
> > -Raj
> >
> > _______________________________________________
> > Red5 mailing list
> > Red5 at osflash.org
> > http://osflash.org/mailman/listinfo/red5_osflash.org
> >
> >
>
> _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org
>

-- 
-Raj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://osflash.org/pipermail/red5_osflash.org/attachments/20090124/bca470b1/attachment.html>