From the original SynthMaker forum (2004–2014), with its members’ names and dates.
A to the Lex ·
Hi,
I've experienced crashes while working with Synthmaker in FLStudio.
I've noticed when the synthmaker window is open in FL the page fault count increases at a rate of about 1000 per second. Is this normal / bad? I haven't noticed it with other FL plugins.
That is not my main concern. It crashes all the time. I could just be connecting a matrix to a target or source and I get an access violation, which freezes FL, until I open the task manager and manually kill the FL process. I find myself having to save after every single change, whether I am connecting the left output of a module to the left input of another (hit save) or even in the front panel (with the editor closed) if I am selecting a target or source in a matrix the same thing happens, an access violation which prevents me from saving or using FL in any useful way, requiring the process to be manually killed again.
I'm using the latest official FL release which is bundled with Synthmaker 1.1.1a. I can also replicate this just with the basic example that loads by default if I add a matrix or two and some targets/sources.
I have a hunch it's something to do with the redraw rather than anything in the audio processing side of things. I don't really know what to base this on though, other than occasionally the synthmaker window seems to freeze and doesn't redraw, followed by external exceptions and the like.
I've just reinstalled everything to make sure it wasn't my system, which is a Q6600 using asio4all drivers and 3gb ram, graphics card is an ATI 4850, running 32 bit Windows XP SP3.
I'm not sure what kind of supporting material you guys need, being new here and all. Let me know what you need from me to get to the bottom of this. Cheers 🙂
A to the Lex ·
It might be related to this thread as I also had the same issue:
Mono Readout crash
If that is the case, I need to read up on the difference between poly and mono sections, because instances like the echo delay module having a single poly in and dual poly outs made me think that poly streams are not stereo.
I have much to learn.
A to the Lex ·
Heres a screenshot of me adding a module from the toolbox just like any other time, only this time it decides to crash.
A to the Lex ·
Ok, this can be moved. I don't think it's a bug anymore...
Check out this screenshot to confirm. Where I have put floats into a mono input, is that asking for trouble? I'm not quite sure though, so I need some confirmation on this.
Anyway I am putting an dezipper in there and that should fix it right? Or what should I do to convert a float value to a signal of some kind?
Cheers.
TomC ·
A to the Lex wrote: Check out this screenshot to confirm. Where I have put floats into a mono input, is that asking for trouble? I'm not quite sure though, so I need some confirmation on this.
No, pluging Float into mono/stream isn't a problem.
Tom
exonerate ·
How do you have the Lfo control module set up? I'm assuming your using the mono to float?
I looks to me like you shouldn't be converting to float at all. Your output should be mono.
I would read up on the differences between data types, it's very important.
There's a quick introduction on the WIKI, but check the User Guidefor a more indepth overview.
Cheers 😉
Exo
A to the Lex ·
Hi, thanks for the reply, those links were a good start thanks.
The issue with the LFO is it has no "base level" wheel... So I use one of the bitmap wheels to provide a control for the user to set a base level (so instead of oscillating around 0 you can set it to oscillate around say, 0.5).
The problem I had was that the bitmap wheels only output in float... So I had to convert the LFO output to float (triggeting 100x a second), then do the math to add the base level to the LFO level, then convert it back into a mono stream.
It would be nice if there were also a clamp option so that I could prevent the stream from exceeding a maximum and minimum value, like 1 and 0.
Is there a different way to add a base level control that does not rely on floats?
The other thing I noticed was the state variable filter accepts values between 0 and 2 for the cutoff value. I am doing some math to combine the LFO signal with the control knob. Basically adding the two together and dividing by two. It sounds OK but again with the conversions to and from float to do the maths.
Is that what is causing the crashes? Or is SM generally OK with float to mono and vice versa? Is the main problem when you are working with poly streams and convert to mono or vice versa? Cheers
nix ·
"It would be nice if there were also a clamp option so that I could prevent the stream from exceeding a maximum and minimum value, like 1 and 0."
I think there is stream max and stream min?
"Is the main problem when you are working with poly streams and convert to mono or vice versa?"
poly-mono conversions are fine I've found.
Please post your FLSM preset, if you like.
Hoping solutions
A to the Lex ·
I think I worked it out. I was being an idiot!
I can just use the LFO directly on the cutoff input to the filter to do exactly what I wanted to do.
Duh. 🙂
I'll go through and change everything because I used a lot of complicated workarounds which may be causing the crash. If I still get crashes I'll post the preset.
Cheers 🙂
egoadsr ·
Have tested Fl synthmaker 1.1.3.3 beta.
Crashes with some downloadable modules, seem to crash in trial version of synthmaker too here the list :
Modules ok : Karbass
SMG 30X
SMG Kickdrum Player
SMG Kicklab ( Access violation at address00070000.Read of adresss00070000) but work without crashing Flstudio
SMG Snarelab
SMG Supersaw
SMG Unitable
Problem too with my soundcard, i have a vaio vgn-nr21z ( vista 32bits ) with realtek onboard soundcard. Synthmaker say that directsound is used by one application even with no asio4all drivers installed, same with asio4all installed.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker