Re: [Live-devel] Frames are corrupted

2014-05-01 Thread Vikram Singh
Thank you ross and chris. It works !! J From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Thursday, May 01, 2014 10:57 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Frames are corrupted On May 1, 2014, at 9:5

Re: [Live-devel] Frames are corrupted

2014-05-01 Thread Ross Finlayson
On May 1, 2014, at 9:58 AM, Vikram Singh wrote: > Hi ross, > I am not able to get SPS and PPS units from the encoder. > I am using CUDA Video Encode library which has a function NVGetSPSPPS(). [...] >> >> Sorry I am not getting the detailed documentation for the function >> NVGetSPSPPS(). Ple

Re: [Live-devel] Frames are corrupted

2014-05-01 Thread Chris Richardson (WTI)
Hello, > 00 24 67 4d 40 1e f6 04 00 83 7f e0 00 80 00 62 00 00 07 d2 00 01 d4 c1 c0 00 00 27 a1 20 00 02 62 5a 17 79 70 50 00 04 68 ee 3c 80 >Total of 44 bytes. It looks like the buffer is formatted with the 16-bit length of the NAL unit, then the NAL unit data. So you can s

Re: [Live-devel] Frames are corrupted

2014-05-01 Thread Vikram Singh
ss Finlayson Sent: Tuesday, April 22, 2014 8:46 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Frames are corrupted Does this happen because I have not received SPS and PPS nal units ? Yes. If you are streaming H.264 video, then you *must* have SPS and P

Re: [Live-devel] Frames are corrupted

2014-04-22 Thread Ross Finlayson
> Does this happen because I have not received SPS and PPS nal units ? Yes. If you are streaming H.264 video, then you *must* have SPS and PPS NAL units. Either 1/ Your H.264 video source contains SPS and PPS NAL units, occurring frequently. In this case, you *should not* modify "getA

Re: [Live-devel] Frames are corrupted

2014-04-22 Thread Vikram Singh
devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Saturday, April 19, 2014 11:38 AM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Frames are corrupted -I think the issue is with fMaxSize in deliverFrame() which starts from 15 and goes to ze

Re: [Live-devel] Frames are corrupted

2014-04-18 Thread Ross Finlayson
> -I think the issue is with fMaxSize in deliverFrame() which starts > from 15 and goes to zero which should not happen. OK, your problem is that - in your implementation of the "createNewStreamSource()" virtual function - you are feeding a "LiveSourceWithx264" object into a "H264Vi

Re: [Live-devel] Frames are corrupted

2014-04-18 Thread Vikram Singh
9, 2014 12:41 AM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Frames are corrupted -I am still not able to resolve the issue. That's because you didn't apply *either* of the two possible solutions that I gave you in my earlier response!

Re: [Live-devel] Frames are corrupted

2014-04-18 Thread Ross Finlayson
> -I am still not able to resolve the issue. That's because you didn't apply *either* of the two possible solutions that I gave you in my earlier response! Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list

Re: [Live-devel] Frames are corrupted

2014-04-18 Thread Vikram Singh
Regards, Vikram Singh. From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Tuesday, April 15, 2014 8:26 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Frames are corrupted But if fFrameSize is g

Re: [Live-devel] Frames are corrupted

2014-04-15 Thread Jeff Shanab
Check Byte Alignment,Pixel format, and encoder slices. How are you encodeing them? If the frames are large, then the encoder may spit out more than one frame with the same timestamp and differnt sequence number. Nal units may be [7][8][5][5][5][1][1][1]... instead of simply [7][8][5][1][1][1]

Re: [Live-devel] Frames are corrupted

2014-04-15 Thread Ross Finlayson
> But if fFrameSize is greater than fMaxSize then I have to truncate the data. > I think this is what that is causing the corrupted frames. Yes, because if a frame has to be truncated, then the truncated data will be lost (i.e., not sent to the client). > Is there any way to get around this pro