Schrijver
| screensplit
|
norakomi
msx professional
Berichten: 861 |  Geplaatst: 11 April 2005, 21:31 |
line interrupts?
|
|
Edwin
msx professional
Berichten: 594 | Geplaatst: 11 April 2005, 22:22 |
Line interrupt = screensplit. An interrupt generated after every that is displayed on the screen (also those that are not).
|
|
ro
msx guru
Berichten: 2320 | Geplaatst: 12 April 2005, 10:41 |
hmm, the TERM screensplit is a loosy one. Line interrupt is a variable interrupt (variable Y position) which is standard disabled. VBL (Vertical Blank) interrupt is at the bottom of the screen (BIOS calls #FD9F here)
ps. a screensplit is really a..euh SPLIT in the screen  LNI can be used for replay of music for that matter.. no screensplit there!
|
|
Sonic_aka_T
msx guru
Berichten: 2262 | Geplaatst: 12 April 2005, 16:40 |
I remember using the first MBWAVE driver I once had to put my program on the interrupt and have MBWAVE running as the main program! Had to split my program up into two or three parts running on line ints... Always thought that was pretty funny  |
|
[D-Tail]
msx guru
Berichten: 2994 | Geplaatst: 12 April 2005, 17:52 |
o_O
is that MBWAVE driver *THAT* slow?
O_o
|
|
ro
msx guru
Berichten: 2320 | Geplaatst: 13 April 2005, 15:24 |
no, it's tobie's programming "skills" |
|
Sonic_aka_T
msx guru
Berichten: 2262 | Geplaatst: 13 April 2005, 15:27 |
Actually, it was damn slow... I think it took somewhere in the order of 60% CPU time on Z80, which is pretty darn steep for a background tune... At first I thought I'd just EI in the MBW routine so that all my lineints would run normally... Somehow this didn't really work tho and it all became pretty unstable. In the end I decided it would just be easier to flip the whole thing around and have my main program running on the interrupt and the interrupt program as the main program ^_^
|
|
ro
msx guru
Berichten: 2320 | Geplaatst: 14 April 2005, 10:08 |
it's time I had a look at the driver.. interrupt states should never be changed in such a piece of code (atleast be "re"set) although there are lotsa channels to be set ofcourse (depends on tune??) MB uses STATIC channel numbers not?
It's the same in Oracle, altho the channel numbers are variable(!)
When using a tune with, oh, 32 channels the driver's getting pretty steep indeed.. in Z80 itsa drag! (thaz why most ppl experience Oracle as being a SLOW program.. nope, it's the total channels u use (and remember every channel has it's own fx settings.. so that slows it down too). initialy set to 24 iirc)
so, how about flexible wave channels eh?
|
|
|
|
|
