MBHP TV (preview)
#21
Posted 03 September 2003 - 18:40
Best Regards, Thorsten.
#22
Posted 03 September 2003 - 19:13
#23
Posted 04 September 2003 - 03:25
Some words to the improved resolution: I haven't taken into account that storing so much characters per line also costs too much RAM. Another problem is the "tblrd" instruction which takes 2 cycles instead of one - very bad for "balanced code" (a requirement for proper graphics).
So a compromise would be an alternative mode with 40x25 ROM characters, and maybe another alternative mode which allows to split the screen in two halfs for a big and a small font. Let's check it next weekend ;-)
Best Regards, Thorsten.
#24
Posted 04 September 2003 - 15:04
Wouldn't it be possible to make additional 'external' RAM?
#25
Posted 04 September 2003 - 23:22
External RAM requires a completely different "core module" concept for an external bus interface. The realization is easy, but the circuit would be too complex for beginners (due to the increased number of connections) and much more expensive! It would limit the number of free PIC pins so that they would have to be replaced by multiplexers and latches, attached on the bus.
Since the effort for myself would be to high to support two different concepts, I will stay by the current solution and try to live with the limitations, hoping that Microchip releases new compatible derivatives with even more internal RAM in the next years.
However, external RAM won't help here, the access times are at least 10 cycles (possibly more, depends on the hardware design), this would result to a resolution of maybe 32x64 pixels ;-)
Expected resolution with internal memory (by using ROM fonts, I will try it this weekend): 300xYYY pixels (YYY only limited by the number of scanlines of your TV) -maybe more
For comparison the possible resolution if more internal RAM would be available: ca 580xYYY
But most TVs wouldn't be able to display it properly...
Best Regards, Thorsten.
#26
Posted 05 September 2003 - 00:10
yeahyeahyeah !!! coooool
Having displayed the 64 pots on one row!
*giggling mode off*
coooool... its getting better and better (and more bad for my purse) ;D
#27
Posted 05 September 2003 - 01:47
I just have evaluated what I said - good results - here two quick hacks:
40x25

56x25

In reality it looks better, the resolution of my digicam reduces the quality, and it's especially a rectangle frame on my TV and not a trapezoid ;-)
56x25 characters are the absolute maximum (concerning speed, memory, realtime behaviour)
Best Regards, Thorsten.
#28
Posted 05 September 2003 - 07:37
What's the story with ROM fonts? How are they used? I'd love to do menus using the character set, like in those old DOS apps... But I would rather lots of blocks and lines and special characters, than both uppercase and lowercase alphanumeric characters... Having the whole alphabet there twice seems such a waste, those characters could be musical notes, or bar graphs or menu icons etc... Can the character sets be changed? (R.O.M. implies 'no', I guess)
Could say two (or 3 or four etc) MBHPTV modules be used on one tv screen by somehow offsetting the sizes and positions of the images and mixing them? This could be seriously cool, and a (kinda clunky) way to increase resolution... Say you could have 4 cores, each displaying on one corner of the screen...
Too many ideas! Too many questions!! I'm gonna explode!
#29
Posted 05 September 2003 - 12:01
for the multiple core way.... mmm I think it may be hard to synchronized...
#30
Posted 05 September 2003 - 12:46
Every character set which consists of 256 characters allocates 2k, so you could store 8 different sets in flash and assign it to different scanline sections.
A synchronization between multiple cores isn't realistic for this application. Main reason: the "goto" instruction which is required to poll a flag or a signal takes two cycles. This results to a 1-cycle error which will be visible on screen (jittering scanlines).
It was a challenge to solve the jitter problem in the existing code - fortunately I found a solution which compensates the error (-> H_SYNC macro)
For external, asynchronous signals a deterministic compensation isn't possible.
Best Regards, Thorsten.
#31
Posted 05 September 2003 - 18:15
bye ;)
#32 Guest_ordneren_*
Posted 29 September 2003 - 13:30
With... uhm, say a charactherset for animated knobs, for displaying the position of the encoders.
I could do such a set i figure, i used to do a lot of pixel graphics on my trusty old amiga and in DPIIe on pc ;D
What's the format? Where are the tools? :)
- thorsten
#33
Posted 29 September 2003 - 13:40
Speaking PIC !!!!
you load some ".wav" (without header) into a 24c256.....
and the PIC (with a simple resistor network DAC) outs your audio file !!!!
so nice !
I imagine a speaking "On TV" mega Mios BOX !!!!!!!!
I can scan the whole schematics ......
#34
Posted 30 September 2003 - 01:09
which magazine?
#35
Posted 30 September 2003 - 03:14
i'll put it online this nite !
#37
Posted 02 October 2003 - 03:32
;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
#38
Posted 02 October 2003 - 03:35
ordneren: just wait for the next release (after my holidays), it will make clear how to create customized/animated fonts. In the meantime you could already play with the script in the utils directory, but it requires a paint program which supports the .xpm format (support for the windows-specific .bmp format is planned for the future)
Best Regards, Thorsten.
#40
Posted 02 October 2003 - 17:44
OK, lets get all this together:
We do have:
A TV connected, with whatever animated fonts on it, playing some .wav file ("MBHP ruuuuuuulz"), some flashing LEDs, some moving Motorfaders, flickering LCDs (naturally dozens of those), a few SIDs in that box ............ a yeah, and we control the whole studio over MIDI.
... ... ... 8) gonna be a looooong soldering session.



Help

















