• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 319 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

VPFE Capture driver from LSP2.10 in encodedecode demo - interlaced mode

Jinh
Expert 2315 points

I am trying to insert data (bargraph type on edge) per field on the DM365 and have questions about one-shot mode and continuous mode if it applies to the Pass-Through setting in the encodedecode demo code.  Firstly when I run fbdev_loopback demo then the original fields from the input buffer is just coipied over to the output/display buffer and my field data is kept as is and displayed but when I run the encodedecode demo and even in -p mode my second field is duplicated into my first field and I loose half my data.  From the VPFE and v4l2 documentation I can see that when the resizer and encoder is enabled this will happen - also something to do with continouos mode - but from the comments in the code in encodedecode demo and what I understand the data in passthrough mode should not change like I see it is doing now.  Please help me to resolve if there are problems with buffer handling or setting up the attributed of the mode.  In my application, derived from encodedecode, I do not wish to use the resizer or encoder and want to keep field information in place like in the fbdev_loopback demo. 

I see my bootargs is still set up for continuous mode but can I run this demo to it full functionality when it is not set up in continuous mode?  I will try and confirm that now but need answers on the theory please.

Thanks, Jinh T

  • 0
    TI__Prodigy 720 points

    I am an LSP person. The continuous mode use only one field when used with resizer and scale it up vertically 2x. So you will see duplicate data in the second field. In one shot also I guess the encode-decode demo is doing similar thing. If you don't resizer, you could capture from isif without resizer and feed the frame to fvdev device as in fbdev_loopback demo. The DVSDK developer will have answer to the encode-decode demo question.

  • 0 in reply to MDK35233
    Expert 2315 points

    I established that the problem is probably not with the mode as setting both encodedecode and fbdev_loopback demos to one-shot mode seized them from working.  Because the fbdev_loopback does not use resizer and have fields in tact, I am busy finding out how to remove resizer from encodedecode demo as it seems putting it into pass-through mode is not suffiecient.  As a newby to Linux I was hoping to be able to use API to accomplished most functionality but are busy implementing a driver in order to control kernel space level.  If you are familiar with encodedecode demo, how do I disable the resizer?  Currently having problems with my host computer but sorting it out so progress is quite slow and also going away for a week.  Hope you have some answers for me please or a DVSDK developer.

    Thanks,

    Jinh T.