View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000343 | JVT JM H.264/AVC reference software | encoder | public | 2014-06-17 18:24 | 2014-06-19 07:27 |
| Reporter | MohammadReza Yamaghani | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Microsoft Visual Studio 2010 | OS | Windows | OS Version | 7 |
| Product Version | JM 18.6 | ||||
| Summary | 0000343: program does not create result histogram for single yuv-image | ||||
| Description | the configuration encoder file for yuv file is: 2143.yuv width=240 and height=512 hand image size -which is one of MRI medical image of IRMA (ImageCLEFmed2009_train)- is 247 *512. I set width and height -240*512- in configuration encoder for mod 8. but It doesn't work and result in histogram. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Can you please clarify what you might be looking for. This is a video encoder and its purpose is not to generate image histograms but instead compressed image/video bitstreams. It is possible that histograms could be generated at some point for some encoding algorithms (e.g. weighted prediction, scene detection etc), but such is not necessary (and likely not even supported in this software). A histogram is not a necessary part of the encoding process and thus not supported. Furthermore, even if it was, the generation would likely be internal and not external. So what you seem to be asking is a new feature, which likely is not really needed for most users. Maybe using Matlab or your own proprietary code would be a better method to get what you want? Btw, do note that the encoder tends to also pad resolutions to multiples of 16. If any such computations were done after padding, then your results would be contaminated by the padding process (trivial information, but just good to maybe be aware of that in case you intend to add your own code to achieve this behavior). |
|
|
|
|
|
Thanks for your help in advance. As you mentioned in your note, I am using the encoder to compress and create prediction mode of yuv images, which creates 13 modes ,and then I am using the result as a histogram for my purpose. I am sorry for not being clear at my first question. I am resizing the image width and height to meet mod 8 ,that the encoder is able to work with well. but unfortunately,It doesn't work for a few images, eg. "2359.yuv" -an 264*512 image- which I attached here by. the real png-image size was 265*512, I resized it to 264*512 before use encoder. the encoder get such result : h(1,:)=[ -1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00, -1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00,-1.#IND00]; |
|
|
Which result are you using for your histogram? Which modes? Are these intra prediction modes? Keep in mind that internally there could be using submodes as well. Also there is the ipcm mode. The results are also captured in some log files such as stat_frame.dat. Did you look at that file also? You can enable that using "ReportFrameStats". Your images seem to be monochrome, have you considered converting them to 4:0:0 format (or in the worse case 4:4:4)? odd resolutions are not supported for 4:2:0. I have not looked at your yuv files to see what these are. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-06-17 18:24 | MohammadReza Yamaghani | New Issue | |
| 2014-06-17 18:24 | MohammadReza Yamaghani | File Added: 2143_png_n_yuv.zip | |
| 2014-06-17 18:56 | Alexis Michael Tourapis | Note Added: 0000612 | |
| 2014-06-19 06:29 | MohammadReza Yamaghani | File Added: 2359_yuv_png.zip | |
| 2014-06-19 06:39 | MohammadReza Yamaghani | Note Added: 0000613 | |
| 2014-06-19 06:41 | MohammadReza Yamaghani | Note Edited: 0000613 | |
| 2014-06-19 07:27 | Alexis Michael Tourapis | Note Added: 0000614 |
