nILS

lol @ ultra :) That's a really awesome and subtle way of saying "go to hell" :thumbsup: Oh and what's it with DJs going all arrrrr on us? :pirate:

Yay, the midibox-blue-smoke initiation ritual :frantics: The clicks you hear are digital noise, not the actual audio output. Get the SID out of it's socket, measure all voltages again(!), then measure them again, if they're correct both times, measure them again. Then upload the interconnection test from ucapps.de and see if everything works as described in the readme.txt. If that's the case plug the SID back in.

This is a close call but I think latigid on has got you beat by... erm a week ;)

Ubervoltage is a relatively reliable way to kill them. Although I've accidentally powered one with 9VAC for a while until I realised I had mixed up J1 and J2 :) This one still works as well. Voodoo.

Here's the schem of the version of the cheapo-lpt-wiggler that's a bunch of us are successfully using:

You're allergic to the only key you can play in? Suckage. :baby: Don't hit me, I'm just a baby.

Yes. A lot of stuff is possible, but just like phil has, I've done some pretty incredibly stupid things to PICs over the last years and never ever managed to actually kill one :-) They're like little tanks with lotsa legs.

It appears your buttons are constantly making and losing contact - hence the repeated messages. Do you get the same message over and over again or two different ones? Also if you shorten the pads on one button with a piece of wire, does it behave as expected?

I can't tell you if v0.2.0 will work (I'd simply assume so) but if all else fails I've got the installation files of v0.1.0 and could upload it for you.

Not sure if shipping it across half the world is worth it for an item that can be had for $4,99 including shipping in the states ;)

WTF IS WRONG WITH YOU SMITHY?! Those are some perfectly fine boobies :frantics::)

Crashes are to be expected, it's an early version and heavily under development :) There's a new version up that seems a lot stabler and even plays evil stuff like most Hubbard tunes :yes: There seem to be 2 flushing methods that yield good results. One of them works on about half of the sid files, the other on the other half :wacko: So I guess that'll have to become an option - "doesn't work, try the other one". Also the .dll behaves differently on different players. For instance Dwayne Bakewell's "Old Friends" works like a charm in ACID64 and sounds like a raped goat in sidplayw.

Whether or not there's a hardsid PCI in the system doesn't matter. What does seem to matter is the MIDI interface. So far the gm5 seems to be the only device that works like an absolute charm with my coding style ;)

That's exactly what I am missing when I am bored on the train or the likes... One day I'll make sth like that :)

M.U.L.E: I have only noticed that behaviour in sidplay1 when using "sidstation" as output device - have you accidentally selected that? ;)

I've recently been fiddling around a bit with ways to play back .sid files. What came out of it is a custom hardsid.dll that doesn't work with hardsid(4u) but with the mbSID via the ASID protocol :drool: Technically that means mbSID is now supported by all apps that support hardsid. Oh, and the sidstation as well. It's in early beta state and for those of you that feel lucky, the (constantly updated most) recect version will located here. It's been successfully tested to work with sidplayw (not sidplay2w atm), goattracker, ACID 64 Player, and my own little tracker :) WinVice support will follow once I found time see which version it expects... Any other candidates? Usage: Copy the .dll to the folder that has the .exe you want to use. When the app loads the library it creates a tray icon. Clicking that icon will let you set the MIDI out port (careful - if you don't have a midi device at all it'll prolly just crash, burn and turn off your freezer so your ice cream goes all melty). Select the one you want and check the "try to reopen..." checkbox so you don't have to select it everytime the driver gets loaded. It seemsthe driver has issues with some MIDI devices, gm5s work really well :thumbsup: The M-Audio Delta 1010LT seems to be trouble for Wilba and some EMU device for Smithy. If you have a midi device that creates problems, send it to me for testing :angel: If you try it out, please give some feedback about if and how it works for you with some info on your system (CPU, midi device, OS, software used with it). Have fun. :yes:

That's up to you to decide. Could be any button. Shift or menu come to mind. Then again, there's already menu and shift buttons. :logik:

Both will work.

12bits

Sure thing, drop me a PM of what you need ;)

Someone broked the preconfigured .asm? Uh-oh, I'll look into it right away. Actually, I should have Wilba look into it :D

Welcome aboard Astazou :D That's the spirit! :yes: You can always wire the "buttons" in a matrix which will allow you to use more than the original 128. A 16x16 matrix would allow for 256 buttons for instance. A forum search for "button matrix" or "blm" might get you some useful hints. Being a programmer I tend to think that the obvious firmware choice is to write an app yourself :) If I am not mistaken it (will?) support(s) a max of 8 DINx4 modules. The pic version does not. You'll either have to wait for a new one to appear or code it yourself - which gives you the highest flexibility anyways :) Yes and no. If you don't need the powerful CPU I'd still go with the PIC. It's smaller, easily replaced if you break sth, a bit cheaper and still powerful enough for most apps. I guess the USB port of the core32 does count as a major advantage, if you need/want USB :)