Denial

I have viznuts code rewritten, fully commented. I manually tracked values through the code and tbh I'm more confused now than I was before but it works. I wrote a basic routine to test it with all voices and waves. I have a small bug somewhere in the code but I will post it as soon as I get it buffe...

Noizer wrote: ↑Fri Jul 16, 2021 10:10 am I gave a hint some time ago, if you really want to find out then use $900D instead.
BR

What part are you hinting to?

here are the test routines that i have been playing around with. Both only use 1 wave form on the high voice. I have only tested them in vice so far. This one all 16 bits of the wave form. It is somewhat consistent but not 100% *=$a000 lo = $900a mid = lo+1 hi = lo+2 noise = lo+3 vol = lo+4 off = $7...

So... what's it supposed to do ? When I run the subroutine, it makes a tone, but it sounds exactly like a normal VIC-20 tone, regardless of the shift register value...? I'm doing all this on real hardware. I have not yet tested his code since I can't assemble it. Now that I understand all of the el...

So !byte $xx would be the same as byte $xx in cbm org studio?

I've been studying his actual code right now and I'm staring to understand it. This leads me to a few more questions. If the 900c requires a drop every 4 cycles and 900b 8 then how does his loop with 16 cycles achieving this achieve this? l0: lda #$7f ; 2 aso TMP ; 5 asl tmp; a = [tmp] OR $7f axs $9...

Why not use a simple on/off switch? That looks exactly like what the shift register is, a sequenced on/off switch. Different patterns yield different results. Yes, but if it is not intended in the design of the chip to be able to alter the shift register and the pattern is simple 1010etc. pattern t...

I've been working on routines for producing Viznuts pwp waveforms. I can't seem to make a complete sense out of his code but i've been building my own code based of off his theory. I have gotten test demos to work ( so far I've only tested $900c) but I have a few questions. Here's the original code ...

Here is the command line output from the above listed code. ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x64-mingw32] C:\Users\Rylis>"D:\RUBY_VICXX\var_test.rb" .................................................................................................... var test start adress=824 ...

So, hp is a pointer to a floating point number, and it's used as an argument to external functions that deal with a FAC? That's quite nice. I like the idea of sort of abstracting away various functions. It sort of blurs the lines between assembly and a higher level language, but you'll eventually w...

That's neat! So the methods work sort of like inline functions in C++. More complex methods--which you might not want inlined to conserve memory--can generate a 6502 subroutine on first usage, and then set an address to indicate to subsequent calls that the subroutine has been generated. I'll be in...

I've been working in floating point conversion for an assembler that I am writing in Ruby. Examining the routines on this page helped me greatly. Thank you Mike and Nippur 77. Here is my converter as a Ruby method. =begin title ; CBM FLOAT CONVERTER language ; RUBY format ; METHOD author ; RYAN LIST...

I now have Kernal calls, petscii codes, color pokes and some key memory locations programed in. While researching I found that the Vic and the C64 have the same opcode a kernal calls values. With that here is a demonstration of the same code running on both machines (in emulation.) Hello World 2 req...

That is exactly correct. The idea is that an assembler written within another language instead of with one would be able to take advantage of the functions of that language to make generating code easier. I can use methods and loops to generate blocks of code and data. I cant use complex formulas, v...

Very satisfying and surprisingly enjoyable to write.