TK.

Source code transfered to Wilba - in the hope to have a windows version available soon :) Best Regards, Thorsten.

It was the reason... the Makefile which is generated from resid-0.16-p2.tgz is not complete, "make install" doesn't copy the new include files + library to /usr/local/... Workaround: generate a Makefile with the resid-0.16.tgz package and use this one Best Regards, Thorsten.

After one hour of additional work, .sid tunes are replayed much better now: :) http://www.ucapps.de/tmp/sidplay2_via_midi_try2.mp3 I will clean up the code and thereafter release it as is - due to my low C++ knowledge, I don't know how to realize certain functions, e.g. passing the MIDI device via command line (currently it's hard coded), or writing the ASID routines more object oriented. Great that you want to help out, Wilba! :) Best Regards, Thorsten.

Just tried it again - it works. What is different in your setup? Or is it just the fact, that the SID volume register has only a 4bit resolution, but the editor handles it with 8bit resolution (for the V2A option - same as for resonance) Best Regards, Thorsten.

With 6581s, digital background noise is much more present than with the 6582/8580 Even with your PCB, Wilba Best Regards, Thorsten.

ok, something was wrong - I applied the .patch file over the original release, maybe this was the reason. So, it should work fine when the resid-0.16-p2.tgz package is used Best Regards, Thorsten.

Instructions for Linux users: I compiled the CVS release - under Linux the compile order is important (don't remember which directories I compiled first, but you will find this out...). It's required to execute "bootstrap" in each directory in order to generate the "configure" file - the rest works as usual. resid is not part of the CVS for some reasons - the patched version is important. On my PC, the builder/resid-builder was not compilable due to an unknown mute() function in resid-emu.cpp - I commented this out, thereafter it worked. Best Regards, Thorsten.

Did you enable the V2A option? It disables the SID volume control for good reasons (because some people are planning to control an external VCA with this option). thats an issue with the 6581... or a feature? The DC offset changes depending on the volume, filter and oscillator assignments. Believe me, I tried a lot to eliminate this click (e.g. slow fade out/in of volume), but clicking sounds were still present, so that I removed all this experimental stuff, as it only added some additional delays (up to 1 second) on patch changes, which people probably would report as a "bug" (what is a bug???) as well. Best Regards, Thorsten.

it should be this one, but if you want to ensure, just put unique values into the TMP registers (like 1, 2, 4, 8 ) and check the logic levels on the 74HC595 output pins. This test maybe takes 5 minutes, but it saves a lot of time :) Best Regards, Thorsten.

As mentioned in another thread, currently no accurate .sid file player for the ASID protocol is available anymore. Totally frustrated I hacked into the unix version of sidplay2 today, and made some experiments - with the motivation to DIY a new solution. :) Sidplay2 offers a modular API for output devices, therefore it was quite easy to forward the SID register accesses to the MIDI interface. By using the ASID protocol, data is compressed in a way which ensures no dataloss so long a .sid file is played at a C64 typical update rate of 50 Hz. However, as you can hear in this sample: http://www.ucapps.de/tmp/sidplay2_via_midi_try1.mp3 the driver still needs some work. Timings are too wacky. This is partly related to the way how I access the MIDI interface (/dev/snd/midi is accessed via write(), no special ALSA functions are used), but mainly because the sending routine is not synchronized to the 50 Hz update rate of the emulated C64 sound routine. Thats nothing which couldn't be improved. :) I'm planning to release the source code, but it will only run under Linux due to the way how the MIDI interface is accessed. However, is there somebody with Windows programming skills, who has the right tools for building sidplay2 under Windows, and who knows how to access the MIDI interface? Best Regards, Thorsten.

Absolutely cool!

Check the DEFAULT_SRM_CATHODES and DEFAULT_SRM_LEDS_DOUT settings, the overlay all other shift register assignments Best Regards, Thorsten.

Everything is done within the driver. E.g., if you would select the sid_aout or sid_aout_ng driver, all values would be forwarded to the DAC with 12bit resolution. The AOUT registers are handled the following way: AOUTx_H[7] is cleared whenever the appr. AOUT value has been updated from the sound engine. The AOUT driver has to check this bit, it has to transfer the 12bit value to the DAC, and set the bit so that the transfer won't be repeated so long the value hasn't been updated again. The lower 8bit of the AOUT value is located in AOUTx_L[7:0], the upper 4bit in AOUTx_H[3:0] The AOUT_LC driver always updates all 74HC595 registers (8 for 4 modules), whenever any AOUTx value has been changed (an individual update is not possible with chained AOUT_LC modules) As you can read in the source code, the SID_AOUT_LC_UPDATE_MACRO extracts a 12bit bitfield from aout_a, and a 4bit bitfield from aout_b. The resulting 16bit value is transfered to 2 chained 74HC595 So, all you need to do is to change the macro, so that it partitionates the bitfield as desired. Or maybe you need to write different macros for different value alignments. This means: if you want to transfer a 8bit value instead, you can get the value from AOUTx_H[3:0] and AOUTx_L[7:4]. But these bitfields into TMP1 (or TMP2), fill the remaining TMP variable with useful data, and call the SID_AOUT_LC_Load2SR routine, which will transfer TMP[12] to the AOUT_LC module Best Regards, Thorsten.

By pressing the "Menu" button, the SID registers will be initialized with the selected patch parameters. Once you restart ASID, the sequence continuous to play, but with the wrong sound settings, as the very first SysEx stream is corrupted (this can be monitored with MIDI-Ox). When you select a different patch (e.g. A059: A Stormy Day), you won't probably hear any sound until the ADSR registers are rewritten with new data. Good idea, I will add this. In long term, I'm also planning to implement the F2A flag within the ASID parser - but such a feature has a low priority. Best Regards, Thorsten.

Sidenote: there isn't really an performance impact when using 4bit mode Best Regards, Thorsten.

Please upload the application with MIOS Studio beta7_5 or higher -> http://www.midibox.org/forum/index.php?topic=7238.0 Best Regards, Thorsten.

I came to the decision, that it doesn't really make sense to provide an optional compile switch for 4bit/8bit editing of the resonance parameter - now it's always edited with 8bit resolution (in V1 it was always edited with 7bit resolution, and nobody complaint...) The change is available in beta7 (-> http://www.midibox.org/forum/index.php?topic=9457.0) Best Regards, Thorsten.

Beta7 now offers integrated SID player support - but there is an issue with Windows XP! :-( o integrated support for ASID protocol, which has been originally developed for the SIDstation to replay .sid files. (see also http://www.midibox.org/forum/index.php?topic=2038.0) Only the master core (Device ID 00) will play SID tunes! Nice visual effect: the LED matrix of the CS shows three animated meters whenever a gate flag of an oscillator is set. SID player mode is automatically enabled once an ASID stream is received. It can be exit by stopping the player on the PC, and pressing the MENU button Unfortunately it turned out, that there is currently no SID player available which can replay .sid files properly via MIDI. - SIDplay (http://www.d.kth.se/~d93-alo/c64/spw/sidplayw.html) Perfect integration, but plays tunes too fast under WinXP. Works fine under Win95/Win98/WinME. Not tested under Vista - ASID (http://www.sidstation.com/sidsupport.php) Crashes under WinXP once the tune should be played - ASID XP (http://www.sidstation.com/files/asid_xp_1.0.zip) Tunes played correctly, but the MIDI stream is corrupted at the very beginning when the player is started. Accordingly the sounds are not properly initialized. Workaround: start a tune with SIDplay (for proper sound initialisation), thereafter play it with ASID XP [/code] Best Regards, Thorsten.

Hallo, eins kann ich schonmal vorweg sagen: die SW MIDI In/Out Routine musste ich aus der MBFM entfernen, da sie zuviel Platz verbraucht. Und Flash Speicher ist auf dem PIC18F452 rar... vielleicht kommt ja irgendwann einmal eine PIC18F4685 Version nach - doch sicherlich nicht dieses Jahr ;-) Trafo: dieses Problem kommte mit der alten Schaltung auftreten. Wichtig ist, dass nur ein einziger Gleichrichter verwendet wird. Naehere Infos gibt es hier: http://www.midibox.org/dokuwiki/doku.php?id=bipolar_12v_psu Gruss, Thorsten.

Just type "ratsnest" into the command window to see the ground connections. Best Regards, Thorsten.

It's very silent on the JSynthLib mailing list since years Best Regards, Thorsten.

This means that you have to chain two 32 step tracks. By doing so, each pattern can store 2 * 64 step tracks, means that you need to run two patterns in parallel. Up to four patterns can be played. In general there are 16 32step tracks which can run in parallel, there are different event modes which allow you to play a single note from a track, or multiple notes, or note+CC, or multiple CCs, etc.... this is explained in the user manual. More than 16 encoders cannot be used. And it isn't easy to realize different hardware layouts. Mostly some PIC assembly programming experience is required. Best Regards, Thorsten.

The AOUT driver gets 8 x 12bit values, and you don't need to change the patch structure just to add some additional controls. So long the F2A option is not enabled, you can control the AOUT values individually within the EXT menu, and if you prefer F2A, you are also able to disable or change the channel assignments within the setup_*.asm file. You can for example disable the assignments for the right SID very easily, so that the channels are free accessible from the modulation matrix when the F2A option is enabled. When it is not enabled, the channels are free accessible anyhow. First AOUT value is in AOUT0_[LH], second in AOUT1_[LH], third in AOUT2_[LH], etc... In a later version I'm planning to add an optional 8bit resonance support for external filters. It's already prepared (8bit are stored within the patch structure), just only a compile switch needs to be added which changes the max value and mapping of the CS menu entry for resonance. Best Regards, Thorsten.

Upload is working now For anybody who isn't in the "frequent writer" group, but wants to upload new files quickly: just go into the chat and ask for help. Best Regards, Thorsten.

Hi Rutger, the MBSID V2 feedback thread is not intended for discussing general hardware issues - if everybody would do this, the oversight would get lost even more. 1: Unfortunately I'm not an expert in solving grounding problems - I would have to see the circuit and would have to do some experiments in order to find out the root cause. Maybe somebody else has an idea Encoders: the "speed mode" (acceleration factor) is automatically selected depending on the resolution. On higher resolutions, values will be incremented faster depending on the encoder speed. The idea is, that you are still able to sweep over the whole value range with a single turn (press SHIFT button in addition), but that you can also finetune parameters when moving the encoder slowly. With lower resolutions (especially for 4bit resonance), the acceleration has no effect I don't know about an issue with a resonance limit check - it's handled like any other menu parameter, and it works since years. Did you already try another encoder? E.g., swap it with a one which is working? Best Regards, Thorsten.