Modular bugs

Faybs · Post by **Faybs** » Thu Feb 05, 2004 5:38 am

Everybody is talking about bugs and unstability that occur in Modular.
I am a everyday user of this system, and seems that it is stable.

I would like that topic to be a synthesis list of all the known bugs of every users.
I think it can be very useful for curative purposes.

valis · Post by **valis** » Thu Feb 05, 2004 8:30 am

http://www.planetz.com/forums/viewtopic ... forum=9&65

roy thinnes · Post by **roy thinnes** » Sun Feb 08, 2004 10:36 am

ok, but this link (sick&tired of messed up presets) is just one point in the modular bug history.Some other bugs coming to my mind which are more or less annoying:
1)SampleOsc, version 01/23/08 - system crashes or "cannot load...[wave]" (sometimes);version 02/08/07 - wave(s) not loading on preset change
2)same thing with sampleDrumOsc
3)all seq modules - not starting tight at bar 1 (that's why some people like me love Flexor)
4)gateSwitcher - gate2 is not corresponding to the desired key note
5)multiSegEnvelopes - display does not update if you change preset
Don't know if these are common issues or it happens just on my system.This preset bug thing, on the other hand, did not show up again after reinstalling my system one year ago.
Anyway, everyone is invited to add other modular weirdos or to correct me if the listed bugs are not happening to him.

[ This Message was edited by: roy thinnes on 2004-02-08 10:37 ]

shabdavan · Post by **shabdavan** » Sun Feb 08, 2004 12:39 pm

Oh yeah, I've noticed (3) the seqs don't start exactly on bar 1 and the value by which they are innaccurate seems to be arbitrary each time you press go. It's quite annoying. A lot of time is wasted restarting over and over to get it spot on. Logic takes 5-10 seconds to 'start' recording once the record button is pressed. It's painful to have to stop and start and stop and start just to wait for the seq to sync out of its own free will. Flexor is indeed looking better every day.

shab

[ This Message was edited by: shabdavan on 2004-02-08 12:40 ]

shabdavan · Post by **shabdavan** » Mon Feb 09, 2004 10:50 am

This (3) is actually really starting to get on my nerves. Creamware should fix this bug asap and provide the updated modules for us all. I doubt whether they will because they know it's just another reason for mod users to buy flexor (sales from which I'm sure they take a handsome dividend).

Perhaps that's a little below the belt? I don't know.

Casper · Post by **Casper** » Fri Sep 24, 2004 5:31 am

Link to the 1) subject.

http://www.planetz.com/forums/viewtopic ... forum=9&16

Sampleosc won't load
anything (never)in SFP4.0 .
fileversion 7-8-2002
fileversion 9-20-2004
fileversion 2-7-2002
These three won't work. Does anybody have a diffrent version of the SampleOscillator.mdl ?

greetings,
Casper
casper0@student-kmt.hku.nl

Counterparts · Post by **Counterparts** » Fri Sep 24, 2004 8:44 am

There are two problems which I've encountered, one not very serious, one terminal.

Whenever I create modular synths/effects/whatever devices in a project, and then open the project up again, for every modular device in the project, I get the following message box:

"Warning: The presets in modular.pre are 0.00% compatible with this project! Proceed anyway?"

Well, yes, proceed, especially since there aren't any presets for that device!

Most annoying. Why does it presume that "modular.pre" is the preset file for every single modular device that I've created (without presets)? This is a stupid, trivial bug which should be fixed, IMO.

The second is that sometimes when loading/unloading lots of modular devices e.g. to try them out, this can destabalise SFP and it crashes. No real pattern to this behaviour that I've noticed.

Royston

JLS · Post by **JLS** » Mon Sep 27, 2004 3:12 am

New bug Mod III - not stored diode parameter in preset list

fra77x · Post by **fra77x** » Mon Sep 27, 2004 4:06 am

Hello, i 'm using modular everyday in sfp 3.1c, i don't experience most of the bugs you are saying. There is a specific behaviour with the new preset lists and you should follow the correct procedure by creating a new preset list every time a new module is added. If u have created preset and after that you import a new module you should try the following. Load one by one the stored presets and overwrite the preset name (so to have the new module appear in the preset data). There is some modules that (like the matrix) create problems in the preset list and if that happen then some of the modules don't react to any changes) but everyday i use modulars with the matrix and other modules in XtC mode and it doesn't happens in there!!. I 've never experienced the problem with the seq modules and i used them all the time. Maybe these are problems in SFp 4.0, i don't know, but i once installed it and experienced problems in xtc and i get back to 3.1c imediatelly.(i don't like the new logo also!!

.

alfonso · Post by **alfonso** » Mon Sep 27, 2004 5:05 am

On 2004-02-08 12:39, shabdavan wrote:
Oh yeah, I've noticed (3) the seqs don't start exactly on bar 1 and the value by which they are innaccurate seems to be arbitrary each time you press go. It's quite annoying. A lot of time is wasted restarting over and over to get it spot on. Logic takes 5-10 seconds to 'start' recording once the record button is pressed. It's painful to have to stop and start and stop and start just to wait for the seq to sync out of its own free will. Flexor is indeed looking better every day.

shab

[ This Message was edited by: shabdavan on 2004-02-08 12:40 ]

In order to have seq.modules restarted you have to connect both they restart input and the start-stop input of the clock divider with a "gate or" module output receiving gate from MVC. at that point every incoming note will restart correctly the seq. This way you can just set a matching bpm value and have the modular internally clocked, without having to depend on flacky daw clock signals.

darkrezin · Post by **darkrezin** » Mon Sep 27, 2004 8:08 am

On 2004-02-08 12:39, shabdavan wrote:
.. Logic takes 5-10 seconds to 'start' recording once the record button is pressed. .

This is only a problem if you use a FAT32 drive for recording audio with Logic on Win2000/XP.. if you use an NTFS drive you won't get this delay.

roy thinnes · Post by **roy thinnes** » Fri Oct 01, 2004 6:53 am

@Alfonso:
your tip opens a new way for me thinking about the creamware sequencer stuff.I mean, now I can use all these modules that I haven't used bevore because I couldn't integrate them into my host sequencer software (because of the wabbly timing).This is absolutely fantastic!

[ This Message was edited by: roy thinnes on 2004-10-01 07:54 ]

valis · Post by **valis** » Fri Oct 01, 2004 4:33 pm

Is there an example patch for this? Might help others who are dealing with figuring that out understand the proper cabling and use of modules to achieve internal timing & external retriggering...I'd do it but I'm short on time atm.

alfonso · Post by **alfonso** » Fri Oct 01, 2004 5:28 pm

http://www.planetz.com/forums/viewtopic ... forum=15&6

This is a very old one, but M2, so good for everyone. I checked it first and made another connection in it so it will react better. it has the old preset scheme so will not show any preset incompatibility.

It uses a Multi lfo as oscillator, for it's modulation and gate inputs, and I think it sounds cool, despite being a very basic and stockish patch.

valis · Post by **valis** » Sat Oct 02, 2004 6:46 am

Thanks alfonso