problems with wavetable and jsynthlib!

MIDIbox SID
1

Hi!

i began playin again with my SID.

i have installed the JSynthLib-0.20.0_midibox_mod1.jar.zip (found on thorsten site)

it seems to me that the “Update wavetable” function is not working…

i have checked also with midiox: i sent the midi data from Jsynth to midiox and, while all (well, i have not checked them all…) the other parameters output sysex data, when i press the “update wavetable” button nothing happens…

i tried also older Jsynth verions (i recall the button was working), but - i don’t know why - they are no wroking now… even if all my midi equipment is off they continues to say “midi driver is flipping out” and they don’t start…

any suggestion?

thanks!

2

Hi Matteo,

the wavetable is always sent when you open the edit window. Thereafter updates are only sent on changes.

So, did you change a line in the wavetable?

Note that it will also be updated automatically when the cursor changes the line - in this case an “update wavetable” has also no effect (since it is not required anymore)

“Update wavetable” is only useful if you made a change in a line, and don’t want to move the cursor to another line…

Best Regards, Thorsten.

3

yes…

i modify the wavetable and then press “Update”…nothing happens…neither do when i change the line

BUT

as you suggested, if i close the patch (saving the changing) and then reload it, the wavetable is updated.

the situation is indeed very strange…

the sid is receiveng sysex since all the other parameters are working…

may it be an old java version?

i will try to download the latest version (don’t remember which  one i have…)

thanks!

4

It always makes sense to use the latest version, but not the official one which is available at jsynthlib.org (because in this version the SID SysEx structure is wrong), but the one from my website.

It could also be related to the infamous Java MIDI bug, which appears when Java communicates with some special MIDI interfaces (my own interfaces are also affected).

Workaround: install MIDI Yoke from www.midiox.com, use MIDI-Ox to forward MIDI Yoke 1 to the output port of your interface. Configure JSynthLib, so that it sends all MIDI data to MIDI Yoke 1 instead of  directly to the output. This helps

Best Regards, Thorsten.

5

nope…

i have installed the lates java runtime environment, but the problem perist!

i have also tried 2 different soundcards: creamware pulsar and soundblaster live… nothing!

the wavetable is not update… the only way to send the parameters is to close the patch and reload it…  ??? ???

the last hope is to try something like huby loopback device or midijoke

6

I’m sure that it will work with MIDI Yoke, because I’ve tested this on many computers in the meantime

Best Regards, Thorsten.

7

UNBELIEVABLE…

I did countless test… but still the damn wavetable cannot be edited by jsynth!!!

i reinstalled SID 1.7a MIOS with a small custom change regarding the led out (J5 enabled) and the 6580 filter

i installed midijoke as suggested.

i installed lates java version

i’m using the jsynth release found on your site (JSynthLib-0.20.0_midibox_mod1.jar)

so i think everything should be OK…

first step:

i edit the parameters with jsynth, and using midijoke the sysex are monitored in midiOX. midiOX pass the sysex to the SID via the soudncard ( i can choose between 2 soudcard, neither one works…)

everything is OK. the SID is correclty receiving all the parameters edited, BUT NOT THE WAVETABLE ONES!! the only way to update the wavetable is, as said, to save the patch, exit, and reload the patch.

second step

i connect the SID MIDI IN cable to the SID MIDI OUT cable thank to a midi female-female plug.

i sent sysex to the sid in with jsynth, and with midiox i monitor what is actually arriving at the sid.

all the sysex message correctly pass thru all the cables.

(this mean: i send a sysex message with jsynth; the sysex goes out with the soundcard midi out, it arrives to the midiplug and it is sent immediately back to soundcard midi input. the stream is OK)

just to make a simple test, i enter this wavetable sequence in jsynth (starting from a blank patch)

STEP 00 PLAY +02 +00 +00

STEP 01 PLAY +03 +00 +00

STEP 02 END +00 +00 +00

and this are the sysex strings that arrive to the SID.

F0 00 00 7E 46 0F 01 01 02 F7

F0 00 00 7E 46 0F 01 04 01 F7

F0 00 00 7E 46 0F 01 05 03 F7

F0 00 00 7E 46 0F 01 08 03 F7

nevertheless, no modifications are made to the wavetable sequence… the wavetable parameter seem the only one which are not edited.

last question: what is the last parameter found in the wavetable menu P# after the CC1, CC2, CC3 parameters?

my P#1 is set to 1

i suppose it is related to the patch, but i can’t figure out what is the use…

thanks again!

8

Hi Matteo,

F0 00 00 7E 46 0F 01 01 02 F7

The “46 0F” tells me, that the wavetable changes are sent to the SID with device ID 0F, is the your intention? Wouldn’t it be better to select device ID 00? Note that it has to be edited under Window->Preferences->Synth Driver (last column of the driver overview), and as well in the CFG menu of your MBSID.

last question: what is the last parameter found in the wavetable menu P# after the CC1, CC2, CC3 parameters? my P#1 is set to 1

This is a special feature, which allows you to change to a wavetable of another patch without changing the sound parameters of the current patch. It’s the same like CC#12 - it’s especially useful if you’ve prepared some nice note sequences (or arpeggiator textures), and if you want to select a new one on-the-fly

Best Regards, Thorsten.

9

Hi Matteo,

The “46 0F” tells me, that the wavetable changes are sent to the SID with device ID 0F, is the your intention? Wouldn’t it be better to select device ID 00? Note that it has to be edited under Window->Preferences->Synth Driver (last column of the driver overview), and as well in the CFG menu of your MBSID.

well, yes maybe this is the topic…

i will try soon…

but meanwhile i still don’t understand why the other parameters are working… :slight_smile:

thanks a lot anyway!

i’ll report tomorrow!

10

GOT IT!!!  ;D

but i think there is a bug!!!   :-\

preamble: my SID is assigned to CC16, while its device ID is 00

if i ping with

F0 00 00 7E 46 00 0F F7

i obtain

F0 00 00 7E 46 00 0F F7

so the device number is 00

in the jsynth windows, i set 16 as channel and 01 as device (01 is the only way to make it edit the parameters…)

the problem is that, when you work with the wavetable, jsynth is using the CHANNEL and NOT the DEVICE ID to build the string!!!

i think that the other parameter transmission is held in a different way, so that the sysex string construction is different, and it works.

this is the reason why you saw “0F” as device ID.. it is the channel!! (16 DEC = 0F HEX)… even thought my ID channel was set to 01!

another proof: if i change the channel to 1 i’m able to change the wavetable parameters ONLY (the only one that it seems to NOT change is the #1 parameter of first step (step 00). the other seems to work…

so, finally i think i understood the situation… :slight_smile:

maybe your sid has both channel and ID set to 01, so this bug is not evident… :slight_smile:

i set to the Channel to 16 becuse the SID is connected with midithru to a korg 01RW!

anyway… i hope that my explanation is correct!

thanks for your efforts!

matteo

11

Hi Matteo,

thanks for pointing this out! I also think that this is a bug and I will check if there is an easy workaround for the SID editor. Biggest problem is, that the core library doesn’t allow to access the MIDI channel and device ID directly from each object. If I don’t find a solution, I will ask the core developers for help, but this may take some time…

Best Regards, Thorsten.

12

at least we succeeded!! :slight_smile:

i remember, however, that latest jsynth versions worked… so maybe it’s possible!

thanks, anyway!

13

Hi Matteo,

I found out, that in the meantime it’s possible to access getDeviceID() instead of getMIDIChannel() - the new release can be found here: http://www.ucapps.de/jsynthlib.html

Best Regards, Thorsten.