EXT Problems

Nu Audio Science · 4 Jul 2005

OK more info and very strange it is too

Download the latest project file for SMC 303 and press the preset down button and it will trigger a note in the synth ?

If you continually press any buttons including the freq for the sequencer or wav shapes they trigger notes too ?

If you think this is an EXT problem i will speak to Jorgen and see what he says, If it is EXT he will fix it 🙂

malc · 4 Jul 2005

Thanks NAS, I'll have a look.

Nu Audio Science · 4 Jul 2005

I've posted the SMC Joono as a test plug at the EXT forum, I want to see how many people get the access violation.

malc · 4 Jul 2005

I get the same crash on exit that you've seen so there is definitely a problem there. At the moment I'd assume that it's SM that is the problem.

I will continue investigating.

Nu Audio Science · 5 Jul 2005

I dunno if this helps atall but there are a lot of crashs and bugs with selectors and drop downs and so on too in EXT.

rl · 5 Jul 2005

I did some tests with some VST hosts using FM3x since also Orion Platinum crashes on exit:

Orion Platinum: Crash on exit. Crash when deleting plugin.

Energy XT : Crash on Exit. Preset buttons in instrument do not sync with hosts preset selectors (no notification to hosts?)

FL Studio 5: no problems, but see below.

Muzys 3: no problems, but see below.

Traction 1 NFR: no problems, but see below.

In all hosts: Automation parameters show as blank strings in host. Test: automate cutoff (turn on record, move cutoff knob) This worked (audible response) but cutoff knob did not move at all (I think it should according to automation data)

Nu Audio Science · 5 Jul 2005

Yeah i had this with the knob not moving, Basically you have to add a redraw in a certain way but it make the CPU go through the roof (and my laptop nearly followed cause it also crashes a lot 🙂 )

Shifrin · 5 Jul 2005

I've got parameter automation working fine for my little test VA synth. If I load it into EnergyXT I can map a controller, like my modwheel, to one of the synths parameters using XT's 'CC Map'.

Then, moving the modwheel/controller updates the parameter it is mapped to in the synth. No problems, no CPU spikes or anything!!

I'm having a bunch of other problems though which seem hard to track down, but I'm getting some help from malc - once it's sorted there'll be a little 2 Osc VA for you to play with (custom osc's that work like Linplug's "Analogue" type oscillator) 😉

Shif.

Shifrin · 5 Jul 2005

Spoke a little too soon, there is a noticable (but not huge) jump in CPU when rapidly changing a mapped parameter with a controller. Perhaps this can be gotten around using a timer to update the knobs less frequently!?!

Shif.

NothanUmber · 5 Jul 2005

Nu Audio Science wrote: This happens with everything i compile, As soon as you close EXT that violation message appears. This is Jorges Classic synth example.

Just tested it with EXT 1.2.9 stable and the classic synth example that was exported some time ago with SM 0.9.3y and the problem doesn't occur there (but is reproducable with a SM 0.9.4 generated vsti) so it seems to have to do with things that were introduced or changed either on the SM core or the example.osm file between 0.9.3y and 0.9.4.

Edit: now the 0.9.3y version also crashed, I made the mistake of not opening the gui in that version, sorry... (If you don't do that neither the old nor the 0.9.4 version crash here)

Greetings, NothanUmber

malc · 5 Jul 2005

Thanks NothanUmber that's useful to know.

Malc.

Nu Audio Science · 6 Jul 2005

yeah sorry ishould have said i have been getting EXT users to open the GUI DOH

Tom7777 · 7 Jul 2005

Maybe there should be a sticky post where people test the example synth in all of the hosts every new release and this way any bugs can be fixed quicker.

malc · 7 Jul 2005

We do tend to do that Tom but only when we think that the VST export has been affected. Things can slip through the net though. It's a good idea though if someone is happy to do it.

The crash on exit is fixed now and will be in the next release.

malc · 8 Jul 2005

NAS,

When you get a chance to try it, do let me know if the problems in EXT are fully resolved.

Thanks.

Nu Audio Science · 8 Jul 2005

I'm gonna DL the latest version and repost my Access violation test at the EXT forum in a couple of minutes Malc, I'll keep you updated 😉

Shifrin · 8 Jul 2005

I'll just say that with 0.9.4b my exported VSTs don't crash EnergyXT on removal/exit any more 🙂

Shif.

Nu Audio Science · 8 Jul 2005

Yeah its been working here in two different versions of EXT on four different computers. Malc i'm not going to bother posting a test at the EXT forum it works 😉

Nu Audio Science · 8 Jul 2005

Wheres my manners DOH Cheers 😉

malc · 8 Jul 2005

Good to hear 🙂

Nu Audio Science · 8 Jul 2005

Spoke too soon 🙁 If you sit trying to use an SM plug for a little while it will do the same thing. I will try with other pluigs but this is the case so far with SM 303 and Joono. I will try with FM3x and Classic.

Nu Audio Science · 8 Jul 2005

Yep close EXT with FM3x running and boom Access violation Open the FM3x GUI first. Doesn't happen with Classic though (Also seems to be using less CPU ?)

malc · 8 Jul 2005

Ok NAS, this must be something else then. I'll look at FM3x.

jorge · 8 Jul 2005

Nu Audio Science wrote: Doesn't happen with Classic though (Also seems to be using less CPU ?)

There were some changes in the last releases that make the initialisation of voices a lot quicker. You'd only notice it at the times when a note starts and not when the note is already playing.

Nu Audio Science · 8 Jul 2005

CPU meter in EXT just seems a lot less spikey with Classic 🙂 (Still off the clock with Joono but that has got a lot going on to replicate the Juno osc)

malc · 8 Jul 2005

NAS, I just tried FM3x but couldn't crash it.

Anything I need to do. Does it happen if you just open the VST GUI then close? This is fine with me. It's fine playing as well. I'm using 0.9.4c to generate the VST.

Nu Audio Science · 8 Jul 2005

OK Malc my fault, Just brought up the about box to check and then soon realised that the SM install doesn't get rid of the old install DOH

The reasons the others where fixed and not FM3X

I double clicked the OSMs which loaded into the latest version of SM To test FM3X i clicked the link on my start bar which (Unkown to me) is still pointing to an older SM, It was quicker to do this than look for the default OSM DOH

My fault entirely but why has the install routine changed so that you have to uninstall before install now ?

malc · 8 Jul 2005

Hi NAS,

Cool, I thought there was something odd there.

Regarding the install issue - you shouldn't have to uninstall. When you say you ran from the Start menu, was that the shortcut under All programs\Outsim\Synthmaker_0_9_4?

The install hasn't changed. Is it possible that you chose the one under 0_9_3 instead?

Nu Audio Science · 8 Jul 2005

No i used to just install and it would copy itself over the prevous version.

The latest version didn't.

By start bar i meant my quick links that i set up my self on the bar at the bottom of the screen.

I never ever use Start/Outsim/Synthmaker i just use my quicklink which normally works fine after an update.

Another thing i noticed is that .94 and .93 both appear as .93 in the add remove dialogue in control panel ?

jorge · 8 Jul 2005

Nu Audio Science wrote: Another thing i noticed is that .94 and .93 both appear as .93 in the add remove dialogue in control panel ?

Thanks NAS, that's fixed now.

rl · 8 Jul 2005

just wanted to note, that FM3x created with 0.9.4c didn't crash Orion Platinum anymore