PlanetZ forums - scopeusers.com

I have this wonderful Bug, when I wnat to start Modular (Empty Modular), it's very strange...
When I want to save it (as a *.dev) it doesn't save the presets I have created...
And always when I want to use a module this wonderful dialogbox is going to attack me... But then everything works.

I have used a trick. I took a patch which was already saved (as a *.mdl) and deleted all the modules. This Modulardevice I saved as "New.mdl" and it is my sartdevice - without the bug.

But:

1.I can't use the 8-8 Modular
2.Such a bug shouldn't exist!!!
and
3.I have another bug when I want to use two or more of John Bowen's new devices:



My Scopeversion is 4.0

Is it known, that Bug? What can I do?


<font size=-1>[ This Message was edited by: Koloh on 2006-01-24 02:19 ]</font>

on which modular shell are you encountering the problem?

<font size=-1>[ This Message was edited by: djmicron on 2006-01-24 07:10 ]</font>

It is the modular 2, sorry I've fogotten to say this...

You can just safely click away 'nil reference left side of', it's an annoyance without, IMHO, any consequences.

The other one is a bug you filed already, and John Bowen said he'd have a look at it.

re: .mdl/.dev:
.dev patches are post SFP 2.04, since then only modules (and older, backwards compatible patches) use the .mdl extension. You should not try to change the extension which Scope OS proposes when you save the patch. There's no reason to change current EmptyModular.dev to a .mld. Even the 8x8 patch has a .dev extension.

A big difference between both extensions, is that the old version, .mdl, stores it's presets inside the device. For the more recent .dev patches, you should save all presets in a separate file, just like you would do with other devices.

So, in practice, keep the extension and save the presets as a new file, preferably with the same name as the patch, so you'll end up having newpatch.dev and newpatch.pre.

Hopes this helps.

Perhaps it's in the way you are connecting things? As I said, I didn't find any problems, and this with connecting all inputs and outputs to valid places, and then switching them back and forth.
Maybe you can show or tell me exactly the connections you are trying to make...and at what point the message shows up, etc. As much exact detail as possible will be helpful!

how many cards u have installed koloh? i suspect this is either a fault regarding IRQ assignment or other driver related issues.

Take an empty project (no mixers, audio in/outs whatever). How many masterverbs can you load without getting issues? u dont need to have a sound input.

I use the *.mdl instead of the *.dev because this way I don't have to click away 'nil reference left side of' on EVERY ACTION (when I want to to start the modular, always when I want load a module,...). That's the reason I use a mdl as my empty modular, so I can't use th 8-8 modular without clicking the away the dialogbox.

everythings work, but *.dev extensions don't work without clicking away this annoying dialogbox...

Since I use the mdl, me and other users don't have any problems using my modularpatches, but when I used the dev (with a *.pre file) the presets didn't work (The presets could be loeded in a list, but clicking on them did'nt cause any changes).


I have a Pulsar Project Classic with 6 DSPs using just one card. I can load 8 Masterverbs without having any DSPtrouble.

@piddi Why do you ask?

I have a tuning programm for Win XP in which I have set the IRQ priority of my Pulsarcard to "high" - could this setting be the cause of my problems???

So while I was writng this replay I have testet something:

I have no trouble with John Bowens Modules, when I use the *.dev extension, everything works...

But then I still have the annoying problem that I always have to click away 'nil reference left side of' when I want to load a module...

So how I suspected, my first problem is related to the problem with John Bowens modules (which don't seem to work in Modular devices with *. mdl extension).

Can I perhaps change/refresh any file? I have theese problems since I bought my Pulsar...

dunno about those problems, but i do know that there's no reason to have scope at "above normal". that setting could drastically reduce resources for other programs....

I have disabled the IRQ settings of my "tuning"programm, but nothing has changed, I have the same problems...

Is there another possiblity?

<font size=-1>[ This Message was edited by: Koloh on 2006-01-25 21:47 ]</font>

Maybe a reinstallation of scope will solve your problem.

Koloh,

OK, I tried changing my Empty Modular to .mdl type, and I made versions of my bypass switches as .devs as well...and loading any combination of switch (either .mdl or .dev as well), into either a .mdl or a .dev Modular Window still gives me no problems! So, I really am not sure where to look to help.

Maybe you can send me a saved Patch where it creates this error message?

regards,
john b.