Forum Discussion
New ContributorTone Mapping Operator IP Malfunctioning
Hi @dscully David,
Does this IP have undocumented restrictions on input resolution?
>> Yes, there is restrictions on the input resolution.
For the input width, it needs to be multiple of the pixels in parallels (PIP) and the number of internal tiles (it is fixed as 4)- So, if PIP = 4 and Number of tiles = 4, then the width needs to be multiple of 4x4 = 16
- For the given two widths you could see that condition is not met, 1944/16 = 121.5 and 3268/16=204.25
- I suggest your to try: 1952 for the first case,
- and 3280 for the second case, then if need be, you could use a clipper to put the width back to your desired width.
- For the input height, it needs to be multiple of the number of internal tiles (it is fixed as 4)
- In this case, your current values are both fine.
Regards,
Wincent_Altera
New ContributorHi Wincent,
I have discovered that part of the issue is that this core requires the Lite variant of the video protocol and I was passing the Full variant to the core. I have since fixed this by adding protocol converters on both ends of the IP.
However, I am now facing new issues related to the resolution of the incoming video.
I have four sources of 60FPS video with varying resolutions:
800x800
1944x1092
3268x1840
1920x1080
When the video source changes, I call intel_vvp_tmo_set_resolution and set the lite to full protocol converter after the IP to the same resolution.
For 800x800 and 1920x1080 resolutions the tone mapping operation appears to apply correctly.
However for 1944x1092 and 3268x1840 the IP appears to be incorrectly applying the operation.
Processing Mode 3268x1840
Bypass Mode 3268x1840
Does this IP have undocumented restrictions on input resolution? The only restriction in the documentation I see is "Video resolutions up to 8192x4320 at 60 fps or 8192x8192 at 30 fps". Does the width or height need to be a multiple of the pixels in parallel? Does the ratio of width and height matter?
Thanks,
David
Regular ContributorHi David,
Does this IP have undocumented restrictions on input resolution?
>> Are you referring to the provided design example or IP itself ?
>> if the design example, it only support
>>
The only restriction in the documentation I see is "Video resolutions up to 8192x4320 at 60 fps or 8192x8192 at 30 fps".
>> IF the TMO IP itself , the answer is YES
Does the width or height need to be a multiple of the pixels in parallel? Does the ratio of width and height matter?
>> Theoretically you need it, But to be honest I never try this implement before.
>> But based on my understanding The TMO (Tone Mapping Operator) IP core processes a set number of pixels in parallel per clock cycle, often referred to as pixels_in_parallel. For efficient hardware utilization and to avoid partial processing at the end of each row, the frame width must be evenly divisible by the pixels_in_parallel parameter.
>> You can refer to 38. Pixels in Parallel Converter IP
Regards,
Wincent_Altera
