uchristo
Forum Replies Created
-
AuthorPosts
-
I remember I had to choose AV1 for YPbPr input rather than AV3 because input from AV3 would not run through LPF and therefor I had issues. I’m unable to find the thread…. Is the limitation still present for modified OSSC running Firmware 1.x ?
Seems like this is heading in the corect direction:
Is the USB Blaster mandatory for UART or is the JTAG integrated UART compatible to “normal” uart. I’d love to hook up a ESP8266 to this port
is it possible to share the webapp (files) for self-hosting?
Any news on this one? I‘d hook an esp8266 to the uart. Having remote options in case of misconfigured sampling options (and no resulting picture) would be extremely helpful…. Or even entering the samplingrates directly….
Will we regain the possibility to name the Profiles? I‘m a bit lost at the moment because I’ve got to map the connected system to the slot id on a paper currently :-X
edit: opened an issue: https://github.com/cmcginty/ossc/issues/1
-
This reply was modified 3 years ago by
uchristo.
Indeed! The ongoing development on ossc classic is really great!
Will updating from SD-Card retain the settings or will it wipe everything?
Understood that, yes. But with current FW I‘m able to create a 1920×1080 Screen with a centered 1280×1080 (lx4ed amiga HiRes Screen 320×262) screen inside. Is the old ossc able to create the 4k-Window in theory?
Will this enable the output of a 1920x~1500 frame inside a 4k-Resolution?
There seems to be an overflow-issue with h.backporch. In UI, there‘s the ability to adjust more than 256. but internally there seems to be uint_8 in use because when increasing to a value over 254, the image jumps to the right and will vontinue to move to the left (until we reach 512 and the next overflow appears resulting in another jump to the right)
Edit: using the latest 1.01 SD-Image
-
This reply was modified 3 years, 7 months ago by
uchristo.
Hi marqs!
Are there any differences to the former uploaded beta build?BTW: I’d like to say “thank you!” for all the work your doing to keep this masterpiece of hardware up to date and support all those creepy non-standard input sources out there!
Hi Marqs,
initial message was more detailed, but forum software asked me whether I really want to submit my message…I did not need to adjust VSync Threshold. From time to time, the 288p (313-p) screen will lose sync for less than a second. But it’s not really reproduceable.
Both modes are working now!
Thanks a lot!I’ve got an old ( Scope) with 60MHz….. Has been some time since I last used it…. Should I trigger on Y from YPbPr since this includes the Sync signals or shall I trigger already on my FPGA Board? It’s a MiST based on CycloneIII
Alternatively, I could probably send you my second MiST ?
-
This reply was modified 3 years, 8 months ago by
uchristo.
installed the new build (debug version).
nios2-terminal gave me this:
Sync LPF value set to 0x0
PCM1862 found
RC data read (54 bytes)
Profile 0 data read (1916 bytes)
SetInputMode(00,00)
Input mode is RGB24
Output mode is RGB24
SetupAFE()
Reg[61] = 00
Reg[62] = 18
Reg[63] = 10
Reg[64] = 0C
Reg[65] = F0
Reg[66] = 00
Reg[67] = 3F
HDMITX_SetAVIInfoFrame: VIC=2, ColorMode=0, Aspect-Ratio=4:3, ITU709=No, ITC=No, pixelrep=0
SetAVIInfo():
CTS: 27000
### DIY VIDEO DIGITIZER / SCANCONVERTER INIT OK ###RCODE: 0x02e0, 1
### SWITCH MODE TO AV1_YPbPr ###
THS source set to 1
SOG detectedtotlines: 1381 (cur) / 0 (prev), pcnt_frame: 1048575 (cur) / 0 (prev)
Sync upLines: 1381 p
Clocks per line: 759
Hswidth: 127 Vswidth: 0 Macrovision: 0
Error: no suitable mode found, defaulting to 240pOSSC won’t change inputs after this anymore nor reflects the incoming ir-code with green led.
Non-Debug build constantly toggles between 764-p and 764-i
23.01. kHz/ 46kHz / 92kHz and 60.23Hz/120.47Hz
Non-Debug-Build will allow further input after initial selection of source.-
This reply was modified 3 years, 8 months ago by
uchristo.
-
This reply was modified 3 years ago by
-
AuthorPosts
