From the original SynthMaker forum (2004–2014), with its members’ names and dates.
phertel ·
Hi@all
Sometimes there are something mysterius when I work around.
Fore Example:
I have made 3 same Modules with Switches, Knobes and so on.
From one to the other Second one Switch or Knob in one Module dosent works again.
The mysterius is when I copy this modul in to the Toolbox and delete the
original and copy this modul back in to my schematic then it works correct aigain
and this without any modifications.
My id is the realtimecompiler from SM dosn't work correct.
When I coppy the modul back in my Schematic, the compiler compiles
this module correct and it's all OK.
I don't know if anybody understand what I mean but an manual compiling Knob
was really usefull in this Situation. So I think.
greatings
Peter
theun ·
Could also be a "state" - issue, where by copying the module one or more values are refreshed. E.g. in a sample and hold primitive (which is actually a sort of memory) a previous value might be kept, issues like that are not always directly obvious from a schematic.
Of course I am only guessing now....
Could you upload an osm that shows the behavior you described ?
Cheers, Theun
phertel ·
Hello @theun
The issue was at last with a standart static-switch-Module. Sometimes it's enought when I change this modul between visible and invisible and back. This aktivate the compiling procedure (but not ever I think) and remove this issue.
When I work along it can be this issue never come back.
So in my topical Projekt.
But your Id is good. I must keep an eye on it. Especial the Sample and Hold thing. THX
At this time I can't send the osm. Sorry! 😊
But I work on it!
greatings
Peter
phertel ·
... and the next Bug I 've detected.
I made my Synth as a VSTi and I use it in FruityLoops. FL is my Host.
Some times later they have a big Access violation and my Synth including FrutyLoops are gone in to the nirvana. 😠
Now I don't know is this a SM-Bug or a FruityLoop-Bug while I use the new FL8.5beta.
I start it again after an half hour but it don't crash again.
Hm???
What program to Hell is the crashmaker?
Or is it my Plugin made by SM?
I keep an eye on it!
My opinion ist there is any issue with the Memory Management in SM.
While some other Plugins, like NI-Koreplayer, ProteusX and some others dosen't crash FL.
The Kore-Player use many resources but it never crash FL. Also ProteusX. FL is also stable when I use this both in the same time. When I use this both more times again the FL-CPU using goes high but no crash.
greatings
peter
Nu Audio Science ·
I honestly wouldn't even think of blaming SM at this point
Isn't FLS 8.5 still private beta (Why they do that i have no idea)
If so then i would wait till it is released so others here can help with test to find the issue
NAS
phertel ·
OK,
I wait for the Final FL8.5 to!
I decide when I work with the final FL8.0 instead the beta FL8.5 then it's all right.
So, I think I must nag in the FL-Forum! 😉
thx for answers
Peter
phertel ·
Only one is wrong in the FL8.0 SynthMaker!
The Sampelrate bug. So long as u work with 44KHz there is all right but if u work with 48KHz then all Instruments are detuned!!! The work around is using the Standalone SM and make a VSTi.
This bug I had in earlyer Versions of SM-Standalone to but in newer Versions this bug is fixed.
But not in the SM for FL8.0.
This bug is fixed in the FL8.5beta but FL8.5 is crashing now.
OK, I've isolate the crashmaker!
FL is it! 😠
Now I go grumping in to the FL-Forum! 😈
greatings
Peter
oddson ·
Isn't it the same FLSM version in both FL 8.0.x and 8.5 so if it works in one and not the other then the likely source of the problem is from FL - even if it is specific to FLSM in FL 8.5.
phertel ·
@oddson
I have checked this. Yes, u are rigth, this bug isn't fixed. I have compare it directly now. The detunig bug is in FLSM.
Sorry for the hoax. 😊
But I must work so and so with FL8.0 and SM1.1.2-Standalone when I want to make music. While this Combination of this both are working the best and wihout crashes and detuning-bug at 48KHz-Samplingrate (my ASIO-driver works only with 48KHz).
The Intern SM works not correct with 48kHz. Only witrh 44KHz it works correct. I have post it some post before.
This is an old bug long before the current Version of the SM-Standalone was out (now1.1.3beta or the 1.1.2stable).
VSTi made with the current SM-Standalone(beta) are working correct.
It's hard to make the right statement when both are beta-programs! 😕
But the Access Violation at ... (I don't know?) was a real bug in on of this both betas!
The FLSM make the same crash. So I think that FL is the bad boy! 😉
Have any body others problems with this or is this only my bug? 😮
greatings
Peter
phertel ·
Next Mystery
The Modul in the attachment ought to work as an Demomaker. Will mean that thist Modul give every 5Sec an Noise to the Audiooutput.
It will start on a Keyboard Key is pressed and then this never ends to make this noises.
So far so good.
When I press the PC-Keyboard it works fine.
When I press a key on a Virtual Keybord as the Keyboard from oddson from this Forum it works fine to.
When I press a Key on my Extermal Masterkeyboard it dosn't work. In opposite this will stop the Noisemaker.
Otherwhise my Masterkeyboard works correct with MIDI and USB. I think it works fine.
I have attach the OSM.
Is this a bug in SM or is this a bug in my configurations?
Greatings
Peter
sunsynth ·
Hi Peter,
it's the old Midi Timer Combi Prob...
Look here:
Link
Walter
phertel ·
Ah OK
THX Walter! 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker