RndMnkIII

Hi, the Y/C module in Analogizer is include as standalone, not integrated in the MiSTer framework full pipeline, When instantiating it, it needs to be provided with the following parameters...

then the parameters are passed to the Analogizer module instance: openFPGA_Pocket_Analogizer #(.MASTER_CLK_FREQ(40_000_000)) analogizer ( ... //Video Y/C Encoder interface .PALFLAG(PALFLAG), .MULFLAG(1'b0), .CHROMA_ADD(CHROMA_ADD), .CHROMA_MULT(CHROMA_MULT), .CHROMA_PHASE_INC(CHROMA_PHASE_INC), .COLORBURST_RANGE(COLORBURST_RANGE),

If you are using a well tuned value don't need to tweak nothing using CHROMA_ADD and CHROMA_MULT

Example of interact.json file for the game In the Hunt related to Y/C settigns: { "name": "Analogizer Video Out", "id": 45, "type": "list", "enabled": true, "persist": true, "address": "0xA0000000", "defaultval":...

Hi, In the following link you can see the quality obtained with SVideo using the optimized parameter values ​​for each core together with the active Y/C adapter: https://x.com/unlovedhomie/status/1798939801485508637

Here I have left the Analogizer specifications: https://github.com/RndMnkIII/Analogizer/blob/main/specification/Analogizer_specifications.md Aqui he dejado las especificaciones de Analogizer: https://github.com/RndMnkIII/Analogizer/blob/main/specification/Especificaciones_Analogizer.md

Of course, depending on the Analogizer menu has its drawbacks, I understand that as a general rule the Analogizer settings are not going to be changed often, in any case...

By the way, reviewing the code of the Y/C module used in other cores, I have seen that a version is being used that only needs two parameters, the rest...

Hello, I have only tested the video output part, as there are several details I have put it in a Google spreadsheet for you to see. Please contact me in...

Any news about support for Analogizer?