From the original SynthMaker forum (2004–2014), with its members’ names and dates.
meurondb ·
I am having a problem with with the String to SysEx out. The string is not converted to SysEx according MIDI-OX, but into a random assortment of other MIDI messages, such as pitch bends, CCs, Realtime clocks, empty SysEx messages, and just undefined messages. No matter how I configure the schematic, I get the same results. Can someone help me on this.
infuzion ·
meurondb wrote: Can someone help me on this.
Not without an OSM. If you're having an output problem, you should post in the Help forum first, since it is very possible your fault, not SM's.
meurondb ·
I pretty sure its a bug due to the fact that it is not just my schematic that is having issues, but every schematic I have seen that outputs system exclusive. I not sure if it has something to do with String to SysEx converter primitive or a problem with FL Studio.
rl ·
Testing your schematic using MIDI OX everything seems to work well on my system. Maybe you have a MIDI driver issue or a MIDI loop?
meurondb ·
I'm wondering if it could have to do with the fact that its the FL Studio plugin. I know that FL does not have native SysEx support. Could this also pose a problem? Btw, this my set-up. If anyone sees a problem, let me know: -Windows 7 Ultimate 64-bit edition -Pentium D 3.20GHz processor (oced to 4.0GHz) -M-Audio Delta 1010LT sound card -Novation Remote 25 throu7gh USB -Korg R3 through USB -Juno 106 through M-Audio 1010LT MIDI OUT port -FL Studio 9.1 (Have also tested on FL Studio 9.5 Beta) -FL Synthmaker
rl ·
meurondb wrote: ... I know that FL does not have native SysEx support. Could this also pose a problem? ...
as long as the SM plugin directly connects to the instruments Midi interfaces (bypassing FL's midi channels) there should be no problem.
Tzarls ·
You could try your schematic with your OC settings turned off - in other words, with your system not overcloked.
meurondb ·
Every time I try to bypass FL Studio's Ports, I get a Access Violation error.
rl ·
are the Midi devices opened by FL itself? Unfortunately Midi ports can be opened only once in windows. Try to close them on the FL Midi Settings page
AngularMomentum ·
meurondb wrote: Every time I try to bypass FL Studio's Ports, I get a Access Violation error.
You get this error when FL already opened these ports. You have to disable them first in the system properties of FL Studio. I built this schematic and tested it and it works for me.
meurondb ·
Maybe this is just me, but shouldn't I be allowed to route the information through the FL ports. I know this is not a problem with the schematic, and for the record it did work when I disabled the port in FL Studio, but then I can't control it without editing it to take Input from FL Studio and passing the info through the port opened by Synthmaker. This is a problem for me because it makes whatever midi channel unusable because it will always route to the Juno. This makes the port system a mute point and draws FL Studio's sequencing ability down to 16 channels. If I wanted this, I would have just used my MC-909 as a sequencer. This is just an overall bug in the FL Studio synthmaker. I have also been informed by the Image-Line team that this problem will be fixed, so thank you all for the help.
trogluddite ·
As a workaround for you in the meantime, you might like to try LoopBe. It's a virtual multi-client driver for windows - the only one I've seen which is Win7 and 64bit compatible. It's freeware for personal use. You would route it somethng like this... Your SM plugin's SysEx output and the FL MIDI output for the Juno get sent to the LoopBe driver which acts as a MIDI merger. Then you need to take the output from LoopBe and send it to your soundcard's physical output (which you need to disable in FL)- Here's a little SM .exe that should do that, but you may be able to find a virtual MIDI cable app on the net that is better.
AngularMomentum ·
The problem then is that you have to send notes from FL to the synths as well, something the Roland dashboard doesn't do because there is no FL Voice to MIDI module.
trogluddite ·
I see (I've not used FL since it had SM built in). So the notes could maybe come from a regular MIDI track in FL routed to LoopBe (instance 1), and then have a 'dummy' track to insert the dashboard into (talkng directly to LoopBe instance 2). ...or, if that was still problematic, as a last-ditch workaround for the workaround, export the dashboard schematic as an exe (some kind soul on the forum could do this if SM FL doens't allow it) - not ideal from a preset management point of view, but better than getting no music made while waiting for FL updates (at one time, I had to have 3 different synth patch editors open as seperate app's in the background like this - loved it coz I didn't have to scribble with a china graph pencil all over my shiny front panels!!).
AngularMomentum ·
Fl doesn't like the sharing of MIDI ports (just like most sequencers) with other programs. It is just too much work, which will destroy creativity and work flow in my opinion.
trogluddite ·
That's the whole point - it's not the applications that don't like sharing; it's the drivers.
With a multi-client driver, the limitation is overcome - it's just a case of the hardware dev's taking the time to write a more complex driver that will merge the incoming data from multiple sources (now that we're 'all' using VSTs, I suppose they believe it's not worth the effort). I've been working this way with Hubi's Loopback and MIDI Maple for years, and currently have a Novation controller that will hook up to multiple app's - it really does work!
As for it being too much work - personally I'm a bit sick of people whining about 'my plugin takes 10 sec to load', 'but I'll have to manage more file extensions' etc. - some of the most innovative music ever recorded was made in all analogue studios with no automation, no presets, synths that needed retuning every 5 mins, broken guitar strings to change etc. Whatever the technical pro's and con's of analogue v. digital - digital has certainly encouraged laziness. I call it 'Abbey-Road-in-a-box' syndrome - musicians who just don't get how lucky they are to have the tools that they do.
MichaelBenjamin ·
couldnt you aswell be lazy before and just crappily play the guitar? or take some chords from that pop song and write some drunk lyrics over it? the only difference with digital is that the lazyness is slightly better hidden behind loops and presets, but only for the first two sights, then the disguise quickly drops and its the same as every year - just a bit different.
trogluddite ·
MichaelBenjamin wrote: couldnt you aswell be lazy before and just crappily play the guitar? or take some chords from that pop song and write some drunk lyrics over it?
So you were that bloke all on his own stood at the back of all my gigs? 😉
Oh yes, I'm very fond of the lazy option myself (crawling out of bed very late being a favourite passtime of mine!) And of course pointing out what we see as omissions/faults in anything can lead to innovation - but anyone who loves music enough will just get on with making music and either surmount the obstacles, or even turn them into virtues. I suppose the real difference in the 'digital age' is that the laziest option of all is to just fire up our web browser and go have a moan (I'd like to point out before anyone else does that, yes, I do that often too!!) - I suppose that as I get older I have come to terms with being a crap musician and have stopped thinking that some new technology will come along and wave a magic wand giving me limitless talent.
BTW: Sorry if I came across a bit narky/cynical, but I wrote my post during lunch in the middle of a long day at work (walking 8 miles all week to get there in the absence of my usual transport), and was itching to try out a litle SM algo I dreamt up last night - now that really does dampen ones creative drive!!
AngularMomentum ·
trogluddite wrote: That's the whole point - it's not the applications that don't like sharing; it's the drivers.
As for it being too much work - personally I'm a bit sick of people whining about 'my plugin takes 10 sec to load'.
That is why I bought an MTR. 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker