I have custom juggled my devices and modules directories structure a bit, to get things organised the way I like it. However, I can't get the right headings to appear on the toolbar menus in the Mod2 empty module. What I want here is, of course, all the Mod2 components, grouped under menus headed "Filters", "Oscillators", "Envelopes", etc, etc, the way it was in my off-the-shelf setup.
Which things appear in these Mod2 menus appears to depend on where vaious bits lie in my folder hierachy, but I can't get it to come out right.
Does anybody know the logic to how these menu headings and contents are determined? When Mod2 is opened, are the menus set according forlders relative to which folder the Modular Empty Module sits or relative to the overall app?
Similar question for the overall environment. I am now using LunaII 2.5 environment with PulsarII and Powersampler cards S/TDM'ed together, with LunaII drivers. I have copied all my Pulsar Modules and devices into various directories around the LunaII app, so all these show up in menus on the Luna project window bar. Usually works, but some funny behavior.
Anyone know the key to this logic? The best way to set up the directory structure for devs and mdls?
menus on Mod2 command bar
I just opened Windows Explorer and dragged and dropped the various devices and modules into the folders I wanted. That's how I drop in new devices from zipped files, delete files and move devices from the general list into my "preferred devices" folder.
I don't quite know what your problem is, so this probably irrelevant....
I don't quite know what your problem is, so this probably irrelevant....
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
Having the same problem, i don't know where to put de Modular2 folder so that modules appears in the menu bar.
In Luna, it would be directly in devices directory, but seem that Pulsar isn't working the same, didn't find solution yet for Pulsar.
If in Luna I know that it supposed to be in \Luna\Devices\Modular2
Marcus
In Luna, it would be directly in devices directory, but seem that Pulsar isn't working the same, didn't find solution yet for Pulsar.
If in Luna I know that it supposed to be in \Luna\Devices\Modular2
Marcus
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
Hey Subhuman ! Your setup is Pulsar1 + Luna2?
Mine too, and i would be interrested in knowing what your system setup is (mobo, cpu, mem, AGP, ata/66 or ata/100) and also in what slot your pulsar is, and Luna ?
Did you ever have an error that say 'Communication error with luna board(0), try reloading the DSP...etc...' ?
Cuz, i have this message very often, and this force me to close Logic and Pulsar to restart again. Hoping this time's the good one.
Don't seem to nail the problem here.
Well, thank in advance...
(Hey hey, now I'm a 'Budding Pulsarian' !!)
Marcus
Mine too, and i would be interrested in knowing what your system setup is (mobo, cpu, mem, AGP, ata/66 or ata/100) and also in what slot your pulsar is, and Luna ?
Did you ever have an error that say 'Communication error with luna board(0), try reloading the DSP...etc...' ?
Cuz, i have this message very often, and this force me to close Logic and Pulsar to restart again. Hoping this time's the good one.
Don't seem to nail the problem here.
Well, thank in advance...
(Hey hey, now I'm a 'Budding Pulsarian' !!)
Marcus
My system is identical to the "P3 1Ghz" machine listed over at <a href=http://www.infinitevortex.com>Infinite Vortex</a> only I have just a 27gig Maxtor HD (I've had this setup since August 2000). Pulsar1 (slot 5) + Luna2 (slot 1) both on IRQ 5.
I haven't run into the Communication error in awhile, but I remember seeing it when I first installed the Luna2, try reinstalling 2.04a over top of what you have and see if that fixes it-- it seems to have here, it has something to do with mismatched drivers, or HEAT related (you have a fan blowing across your DSP cards?)
My next machine will be a 2.0Ghz (dual?) SCOPE system.
I haven't run into the Communication error in awhile, but I remember seeing it when I first installed the Luna2, try reinstalling 2.04a over top of what you have and see if that fixes it-- it seems to have here, it has something to do with mismatched drivers, or HEAT related (you have a fan blowing across your DSP cards?)
My next machine will be a 2.0Ghz (dual?) SCOPE system.
