Damn, was gonna make a joke with the pointy m poking through an ay chip with some splatter, but gimp botched the render.

Anyway, I like kinda like the pointy things, they look a bit like a chip pins, no?

Yeah, I'd vote for #2. Or #1, but then with a shorter dash. Perhaps also flipped vertically and maintaining the 2px spacing from the rest of the chars.

edit: uhhmm, like this perhaps?

http://irrlichtproject.de/transfer/1bitforum5.gif

Arrrghh... and I just persuaded PROTODOME to remove the dash/spacing.

Excellent, thanks a lot mate. I think #2 looks best.

Yes, awesome. Just one last thing, I think the "m" still looks a bit heavy/solid compared to the rest. Do you think that could be helped somehow? I tried breaking up the horizontal line with another triangle but that looked rather silly.

Oh yes, looking sweet! I'd like to suggest a few tweaks to improve the readability though. What do you think about making it read "1bitforum", ie. something like this:

idea

Not so happy with the "1" yet, though. Perhaps it should also be more solid, like the "u" and "m"?

707

(11 replies, posted in General Discussion)

Aww yis, ZX Spectrum Orchestra! They are pretty big nowadays with their follow-up project: http://www.modifiedtoyorchestra.com

708

(2 replies, posted in Sinclair)

Can't help with that, sorry. I have a WinXP install just for running Beepola and some legacy tools yikes Other than that, blaming pulseaudio would have been my first response as well big_smile

It should be possible to increase the buffer size through ALSA. Looked it up a while ago when somebody was having troubles with something on cm.org, but forgot all about it. Worth doing some digging in that direction though.

That's a very reasonable concern wink However, I believe we're on a version that proved to be, uh, not so successful, and was quickly replaced with another one. 1.4.4 on the other hand hasn't been updated in over half a year, so I assume it should be reasonably stable.

710

(135 replies, posted in Sinclair)

Did you manage to solve the aliasing problem that comes with this approach, and if yes, what was your solution? I'm thinking to use a simple low-pass filter like the one I described earlier, not sure if that'll work out though.

Hmm, I wonder why smart phone view is broken. We're running a slightly newer PunBB version than the old forum, but surely that shouldn't break things? Well, come to think of it, there are a some things that are broken in this version (bbcode in lists, for example). I should poke d0x10 about upgrading again...

712

(130 replies, posted in Sinclair)

Aye, that's good news, too!
So... will you make us a Pokey+GTIA sound driver, so we can rock the "standard" MSX compo, too? big_smile

713

(130 replies, posted in Sinclair)

De:coded 2016 will have a beeper compo, yay!
http://decoded.org.ua/en/demoscene-compos/

714

(21 replies, posted in Sinclair)

Got it, thanks!

Yes, 126 step limit is indeed quite a hassle. However I recall Chris mentioning that it would be rather complicated to fix this issue, which is why he hasn't done so until now I guess.

Dunno about WyzTracker. Since it runs AYemul at it's core it should in theory be possible. But many (especially newer) beeper engines may not fit in well with the current instrument/fx editing approach, since beeper routines are generally not frame-based (unlike AY routines).

715

(5 replies, posted in General Discussion)

Well, I'm a huge fan of 1tracker, so I certainly don't mind big_smile

I'd be interested in your instrument handling logic in any case. Perhaps Shiru and/or ccowley could even be convinced to add this kind of functionality to their editors.

Yes, the request is still very much open! Also, a complete forum styling would be even better.

Personally, I would very much like a "simplistic but elegant" black-and-white design. It doesn't necessarily need to be very retro, as some things discussed on here are pretty un-retro. But oh well, anything is better than what we currently have, I guess...

Btw finally changed the forum header text to something more concise. Hope you guys are ok with that smile

717

(21 replies, posted in Sinclair)

Thanks, awesome! Uhhm... what do those asterisks in your table mean?
Also, how about a meta patcher tool for Beepola that allows you to set your own configurations for note tables, speed values? That would basically open up a whole new range of possibilities for people who are into drone music, microtonal stuff etc...

718

(5 replies, posted in General Discussion)

Hi mate, welcome back to the 1bit-forum smile

Nice examples! I think some people would indeed appreciate a proper xm21tm converter. It's not even terribly difficult to do. Check Shiru's engine packages or my github (for example this for some C++ resp. Perl examples of how to read out XM data. Also, I believe this is the most accurate XM file format specification. If you're interested let me know and I'll post a walkthrough in the tutorial thread.

Yo, nice jammin' smile Also, envy at that nice burgundy colored 82 STATS wink

720

(21 replies, posted in Sinclair)

Great to have these mods available as patches. Thanks a lot, mate.

721

(14 replies, posted in Sinclair)

So does that mean the gfx iteration actually varies in length? I always thought the timing fluctuations from memory contention would be too much of a nuisance.

722

(21 replies, posted in Sinclair)

Good job, thanks Frank!

723

(14 replies, posted in Sinclair)

Yeah, I noticed you can lower the rate a lot with the "combined pin pulse" approach. I would have assumed you'd be interlacing music and gfx iterations one by one though Good to know that dropping one out of several sound frames works, too. I'd be curious about how you keep the timing of the gfx frame stable (ie dealing with contention) while still syncing properly, too. I assume syncing is done in software, not via an ISR? Well, guess I'll have to dig into this with a disassembler, then wink

724

(25 replies, posted in Sinclair)

Looks pretty damn stylish. Too bad it's "just" another FPGA box, but yeah, with that design even I am tempted wink

725

(65 replies, posted in Sinclair)

Ahahaha, now I remember. Yes, it's a pity that the spam stopper plugin can't be configured in a more flexible way. Just recently we were hit by quite an onslaught of spammers signing up (they had figured out the answer to the old question somehow), so removing the questions are unfortunately, uh, out of the question at the moment.