MIDIbox SID V2 Editor
#101
Posted 27 March 2011 - 16:54
I don't know if your problem could be caused by fragmentation of the midi-data, but you could try using miditrix.
Are you running a DAW in parallel? Maybe it sets the cutoff to zero, everytime you play a note?
If your problem doesn't occur with the filter switched off (on the sammich), this might be the case.
#102
Posted 29 March 2011 - 16:38
I did not try miditrix but ain't that the same as MidiOX (virtual midi ports) ? MidiOX did not change anything.
Is the editor actually still maintained?
#103
Posted 29 March 2011 - 16:55
#105
Posted 30 March 2011 - 02:24
... so far I did all testing with a simple 44khz Cubase project but all my real project are 48 khz...
and when I start the Editor it resets 48khz to 44khz ?!
I don't understand why it triggers the sampling rate at all...
Using the laste Motu 424 drivers ...
#106
Posted 30 March 2011 - 03:50
#107
Posted 31 March 2011 - 01:24
So just to recap: Once I changed the Filter Cutoff, the next change of ANY other param stops any midi note data to the SammichSid.
The editor itself actually keeps on working. For instance, if I change the Cutoff and, say, the waveform of OSC1, it does that.
Sammich and me are very sad. Today Sammich showed a sad smilie on his LCD Display.
#108
Posted 31 March 2011 - 09:31
and use Midi-OX(or -trix) to merge those ports.
#109
Posted 31 March 2011 - 12:00
I am using Win7 64bit, a MB6582 and an M-Audio Fasttrack Ultra Midi Interface and it works fine for me, no problem changing on the cutoff within the editor.
Otoh, I had severe trouble with a different MIDI Interface (akai mpd32, their midi implementation sucks ;-))
Might be also a cable problem (e.g. too long/too noisy midi cable), although that sounds esoteric ;-).
Bye,
Peter
#110
Posted 31 March 2011 - 12:43
Rutger
ps. I'm sorry I haven't provided more support for the editor. I initially made it for my own use and then decided to share it with the community here, but with my current job as PhD candidate I don't have the time to provide much support.
#111
Posted 31 March 2011 - 19:10
But you probably noticed that I used past tense, and the reason for that is, that the problem seems to be solved.
And because I think it is always important to state how a problem was solved (and not just ask for help and silently solve the problem) here is the (not surprising) answer:
As stated earlier I used MidiOX and Miditrix in combination with MidiYoke. I tried different setups, for example the one here: http://www.ucapps.de..._manual_ed.html
I think I actually tried the right setup very early with MidiOX but it did not work because of the lack of midi defragmentation (I assume).
What did (for example) not work?
Editor:
What I mostly did , was to send the Editor Data to virtual Midi Yoke cables and from there to the Motu Device and from there to the Sammich. (and visa versa)
Daw:
Send Midi Note Data from my Keyboard to Motu In, from there to the DAW Midi Track, from there with Midi Through to the Motu Midi Out and then to the Sammich.
What did work?
Editor: Same as above.
Daw: Send Midi Note Data from my Keyboard to Motu In, from there to the Daw Midi Track, from there with Midi Trough to a third virtual Midi Yoke Cable, from there to Motu Out, from there to the Sammich.
So right now I am really happy. And of course thanks go to this helpful community. A special thank has to go out to imp. Your last post basically made me try miditrix with 3 virtual cables.
Cheers
#112
Posted 03 April 2011 - 12:15
Rutger
#113
Posted 17 June 2011 - 13:39
Not certain if this is a bug as I guess it would have been reported a while ago, but...
I use the editor to make a Multi patch. Make new sounds for the oscillators and save/transmit from the editor to the memory of my Sammich. No problems - all seems stored OK.
When I turn the Sammich back on (or just change the patch) all the sounds are screwed up. So I load up the editor, transmit the patch from the Sammich to it - still messed up. If I then click on the patch to edit it, it starts to come back to life a little and some of the sounds reach their correct settings. If I come out of the edit screen and go back into it a few times, it all eventually gets restored.
Anyone else experienced this?
#114
Posted 19 June 2011 - 20:02
Currently I've only following explanation for such an effect:
Under the assumption, that Notes are played by a sequencer at the same moment where the MBSID Editor sends patches to sammichSID, and under the assumption that you are using a SW based solution to merge the MIDI streams, it could happen that the SysEx data get corrupted during patch uploads.
Which operation system are you using, and how do you merge the MIDI streams?
(At least I can confirm that there is no problem under MacOS)
Best Regards, Thorsten.
Buy TK a Beer Disclaimer: buying TK a beer gets you absolutely nothing in return likesuchas firmware enhancements, technical advices and MIDIbox troubleshooting assistance.
#115
Posted 20 June 2011 - 03:53
#116
Posted 20 June 2011 - 11:44
I'm using XP pro with a Steinberg Midex 8 interface (which is generally pretty reliable with sysex). I've tried doing it with no notes playing, but still the same problem. I'll try another interface before we get too far into it as it could well be the problem. I seem to recall a problem with loading in the patch bank via the editor though (it was missing every few patches). It worked OK with the Mios software though. Maybe the Mios software transmits more slowly somehow?
Hmm - I'll check it out...
TK., on 19 June 2011 - 20:02, said:
Currently I've only following explanation for such an effect:
Under the assumption, that Notes are played by a sequencer at the same moment where the MBSID Editor sends patches to sammichSID, and under the assumption that you are using a SW based solution to merge the MIDI streams, it could happen that the SysEx data get corrupted during patch uploads.
Which operation system are you using, and how do you merge the MIDI streams?
(At least I can confirm that there is no problem under MacOS)
Best Regards, Thorsten.
#117
Posted 27 July 2011 - 09:49

Every thing is connected as it should be (as I would if doing sysex dumps on my elektron gear)
Cheers
This post has been edited by bhc303: 27 July 2011 - 09:50
#118
Posted 28 July 2011 - 08:00
bhc303, on 27 July 2011 - 09:49, said:
The Java MIDI API which comes with MacOS 10.6 doesn't support SysEx.
Workaround: install mmj: http://www.humatic.de/htools/mmj.htm
Best Regards, Thorsten.
Buy TK a Beer Disclaimer: buying TK a beer gets you absolutely nothing in return likesuchas firmware enhancements, technical advices and MIDIbox troubleshooting assistance.
#120
Posted 17 March 2012 - 16:21
'tini, on 18 January 2012 - 22:12, said:
Hey Tini, i don't know if you found a solution since you asked about OS X Lion, but i just found one as I had the same trouble : the editor could'nt fin any of my sound card midi port.
I just installed the mmj (Midi for Java) extension that you can find here : http://www.humatic.de/htools/mmj.htm
Simply copy the "libmmj.jnilib" et "mmj.jar" files to /Library/java/extension and the Editor should have access to your midi port. At least it work for me with an Audio Kontrol 1 soundcard.
haha just realised that Thorsten posted the link just before. So what works for OS X 10.6 is also required for 10.7
This post has been edited by Yan: 17 March 2012 - 16:20



Help


















