NVC - Series - General News

Officially Licensed 3rd Party Developer Libraries
Free 3rd Party Programs
User avatar
babiuk
Vip Member
Vip Member
Posts: 386
Joined: Tue Oct 19, 2010 11:16 am

Re: NVC - Series - General News

Post by babiuk » Tue Mar 25, 2014 3:40 am

I understand this is a so hard project and RJHollins did a very important work here, congratulations for it.

Anyway I don´t have so much time to try to understand the inner proccess who make it work. You are so kind for explaining it so well and teaching us about MIDI and nebula, but I think it would be clearer if we have a thread for "install the tool and use it" and another for "how it works really"(with all the info and knowledge about midi), so people could have the choice just to know how to use the tool and the choice to learn more about it.

I mean, I'm so happy with this wonderful tool and it change nebula workflow light years, but I think all the info mixed in the same place is a little confusing, or at least it takes a lot of time to follow

Well, just thoughts about it.
The real thing is you got a golden tool, RJHollins, thanks
Mac Pro 5,1 / 6-core Intel Xeon / 16 GB Ram / El Capitan / Reaper / H******* Mixbuss

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Tue Mar 25, 2014 3:46 am

RJHollins wrote:
So there is a MIDI learn feature in Reaper? Maybe that can help.
oh yes ... that is used to teach the BYPASS function as shown in the Reaper video.
Sorry, I misspelt that. I meant:

There is a MIDI learn function in Nebula! Manual page 22.

With that I am now able to have NVC to transfer information to Nebula.

However what is strange: The faders and values will only move when I double click the Nebula GUI. But the sound changes, and that is what counts.

@babjuk
The whole procedure in this thread here may then result into what you want, hopefully.

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 3:59 am

HI babiuk,

Still flying around :lol: But I do understand what you're saying. I think it's the problem of this writer stepping back to give a user perspective. It sounds easy, but the output wants to go off the deepend [without warning] :shock: :lol:

If you'd like ... tell me at what point you're getting stuck. At the very least, it may help direct me on how/what to put into a tutorial.

Certain things will be very basic stuff.

Editing the Nebula main XML file to define the [CC] numbers is a onetime operation.

2. Making a custom Nebula [using Zab's SetUPs] is standard. Nothing specific needed for the NVC.

3. The NVC needs to be pointed [the first time] to the XML file made by Zab's program. This is usually in x:/nebulatemprepository/SETUPs folder. The NVC needs to load that specific file the first time only. Afterwards, the NVC takes care of itself.

Basically ... that's it.

The way things get routed in the various DAWs is where each is different. [That is why an 'chainer' like BIDULE or METAPlugin are so useful].

I'll be happy to try to help ... but I need to know where you've stopped at.

Hey ... this can help many users.
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 4:02 am

Hannes_F wrote:
RJHollins wrote:
So there is a MIDI learn feature in Reaper? Maybe that can help.
oh yes ... that is used to teach the BYPASS function as shown in the Reaper video.
Sorry, I misspelt that. I meant:

There is a MIDI learn function in Nebula! Manual page 22.

With that I am now able to have NVC to transfer information to Nebula.

However what is strange: The faders and values will only move when I double click the Nebula GUI. But the sound changes, and that is what counts.

@babjuk
The whole procedure in this thread here may then result into what you want, hopefully.
Hi Hannes_F ...

Hey ... I'm going to follow along with your findings. Without doubt, there is more than one way to do all this. I cannot say that my way is the best or only.

If a simpler, better way is exposed ... or if I need to change the way the NVC operates ... that's fine.

I'm learning too 8-)
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Tue Mar 25, 2014 4:03 am

RJHollins wrote:.Be sure you have downloaded the latest Reaper support files that I posted on my site. Inside there you should see 'MIDItoReaControlPath_v1.0_x64.zip'. that is the 64-bit reported working.
Nope . . . I still see the old version on your site. However I was able to download it here
http://reaper.mj-s.com/MIDItoReaControl ... .0_x64.zip

I have Bidule too, would you share an example project?

Thanks, Hannes

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 4:06 am

Hannes_F wrote:
RJHollins wrote:.Be sure you have downloaded the latest Reaper support files that I posted on my site. Inside there you should see 'MIDItoReaControlPath_v1.0_x64.zip'. that is the 64-bit reported working.
Nope . . . I still see the old version on your site. However I was able to download it here
http://reaper.mj-s.com/MIDItoReaControl ... .0_x64.zip

I have Bidule too, would you share an example project?

Thanks, Hannes
OK ... I'll recheck my site ... I thought I updated that ... i'll check.

Ah ... you have BIDULE ... I'll be glad to share the preset chain. Which NVC controller would you prefer to see it with?
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 4:25 am

RJHollins wrote:
Hannes_F wrote:
RJHollins wrote:.Be sure you have downloaded the latest Reaper support files that I posted on my site. Inside there you should see 'MIDItoReaControlPath_v1.0_x64.zip'. that is the 64-bit reported working.
Nope . . . I still see the old version on your site. However I was able to download it here
http://reaper.mj-s.com/MIDItoReaControl ... .0_x64.zip

I have Bidule too, would you share an example project?

Thanks, Hannes
OK ... I'll recheck my site ... I thought I updated that ... i'll check.

Ah ... you have BIDULE ... I'll be glad to share the preset chain. Which NVC controller would you prefer to see it with?
---- EDIT ---

I've update the 'Reaper Stash' link. It indeed was missing the 64-bit version. My fault :oops: It is now included.

Also ... why the host cannot fix the filenames to be correct as I have them is beyond me :roll: I need to call tech support again about this. :evil:
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Tue Mar 25, 2014 4:56 am

RJHollins wrote:Ah ... you have BIDULE ... I'll be glad to share the preset chain. Which NVC controller would you prefer to see it with?
The Mammoth if you don't mind.

I have it now running halfway conventionally. These are the remaining problems:

- It seems not possible to assign fixed midi channels to a Nebula instance. Nebula wants to return to channel 16 all the time here. Therefore I tend to set the output channel of the Bus_Router instances to 16 too.

- The Nebula GUI does not refresh automatically (minor problem).

- So far the BW and Boost values work fine while the frequency hiccups.

I close my shop for today, talk later.

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 6:47 am

Hannes_F wrote:The Mammoth if you don't mind.

I have it now running halfway conventionally. These are the remaining problems:

- It seems not possible to assign fixed midi channels to a Nebula instance. Nebula wants to return to channel 16 all the time here. Therefore I tend to set the output channel of the Bus_Router instances to 16 too.

- The Nebula GUI does not refresh automatically (minor problem).

- So far the BW and Boost values work fine while the frequency hiccups.

I close my shop for today, talk later.
The crux of the Nebula MIDI issue ! :twisted:

This is a highly requested change to be asked for with Nebula. The current mode is OMNI, which means, Nebula responds to every MIDI channel, at all times. This affects not only the NVC ... but any attempt via DAW, MIDI stream, what have you ... we do not have a way to 'speak' to a single Nebula directly ... we have to isolate each Nebula with a filter.

Taking the podium once again ... NEBULA COMMUNITY ... as nicely as you can ... please continue to request improved MIDI support with Nebula. :!: :mrgreen:

This can be done all within the Reaper chain as shown in the video on this. It is not really complicated as it seems at first glance. There is a definite, repeatable pattern used to address each Nebula. Once this is seen completely, its like ... yeah ... ok, that makes sense.

As for the BIDULE chain. I'll look to post here or at my site.

For BIDULE, I have a special chain and wiring that is working great. But this is my configuration, and I'm using tools that I prefer. There is no reason for anyone to be locked into what I'm using.

The big question is ... what happens in BIDULE if you don't have the plugs I use ... or what if the names of the plugs are different. What happens :?: This I do not know ... not the end of the world, but we may have to 'hand adjust' the plugins and their connections. Hey ... let's try it and see what we need to do.

Just a heads up ... this is what I have in my BIDULE chain. It is made from components included with BIDULE, along with 'my stuff' :lol:

1. Two main BIDULE modules. One is Audio, the other is MIDI.

2. I use the 'DUMMY' plugins to help keep the wiring organized.

3. my custom NEBULA built from Zab's SetUPs app. I've named the DLL something I can remember.

VERY IMPORTANT !

BIDULE needs to scan for new VST's. Strange as it might be, BIDULE actually uses the special VST plugin identifier number [magic number] to identify and acknowledge the plugins. I think some DAWs also do this [Cubase?]. This is an easy fix ...

The main NEBULA XML file has an entry:

Code: Select all

<MAGIC> o010 </MAGIC>

each of the custom Nebula's share this same number.
We need to change this number to be unique for each custom NEBULA Library.

Leave the original Nebula XML as is ... but go to where you have your custom Neb's. Each one of those has an XML file. Open that XML file, and near the top is this <MAJIC> number.

So for <MAGIC> o010 </MAGIC>, I change the o010 to o011 , and the next is o012 , then o013 , o014, etc.

**** I'm showing this list of numbers ... but, to be clear, each custom Nebula needs its own special number ... you might be using 5 or 6 or 13 Nebulas of a particular library for your chain ... that is fine ... you only need the one custom NEBULA that you would use as normal ... just have it a unique 'majic' number. [just didn't want confusion here]. The NVC design does not need anything different than what you would normally do [well, except to be sure it has the correct MIDI numbers edited in] :roll:

This is the way to do this according to Neb Tech.

BTW ... if you had already edited the original XML with the [CC] data [20 - 27], then Zab's app will have included that in each of your custom XML files.
If you didn't ... then you need this data in there.

Now when you tell BIDULE to scan for plugins, it will find all your custom ones too. :D

4. my MIDI CHANNEL FILTER/AudioRouter VST plugin. [FREE from my website]. This is an extremely simple looking plugin. There is 1 setting on it. :shock: Select the MIDI Channel you want. That MIDI output is then wired to the NEBULA MIDI Input.

Now ... That single Nebula can only respond to MIDI data on the channel selected. This must be set to the same channel on the NVC controller. Each sub-module of the NVC directs it's data down the MIDI channel selected. Just match them one for one.

Now ... the 'Audio Router' section.

The plugin has 4 outputs. [basically 2 stereo pairs].
One pair are for audio to go INTO Nebula. The other pair is to skip over Nebula [BYPASS], and gets wired to the next segment.

Remember ... each sub-module has a BYPASS button that allows taking a selected Nebula OUT of the audio chain. The AudioRouter is MIDI aware of the NVC's command and will switch the internal routing. [it also has some special 'ramping' feature that gently transition the bypass. NO MORE snap in the audio, nor overload LEDs on your DAW meters :D

Lastly ... I use the Klanghelm VU meters attached to each NEBULA in this chain. With its gain control, I use these to adjust each section back to 'unity'. The NVC has a 'CAL' module built in that makes this adjustment a breeze. The chain ends into BIDULE's 'mixer' module. That's it. ;)

I should probably repost a picture of this Bidule chain to show the wiring, AND the order of the plugins I've chosen.

I've gone through a couple variations, but this is where I'm at with the order. It looks very logical as to signal flow.

Again ... this is just the way I'm doing things. There is more than one way to 'patch a bay' :lol:
Then we look at serial or parallel processing, sideband control ... lots of options and routing power.

This said ... I should probably do a video tut of this, but I hope this helps guide everyone. The added bonus is this all gets saved as a preset !

Another benefit of BIDULE ... the 'SWAP' plugin function. Once a nice chain is built, it is simple to swap out a different Nebula library and keep all the wiring in place. Very efficient.

So now, my Reaper chain consist of a

1. FreeG at the very top [perfect 1st plug to set level from the start].

2. the NVC of choice

3. BIDULE with matching library

4. an extra FreeG to check RMS/Peak

5 ... whatever else I need. There may be Consoles at the top and bottom for example ... it all depends on whats being done.

OK ... I'll pull some stuff together.

I really hope everyone gets to try this out for real.
It is really worth the initial effort.
8-)
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 8:56 am

Already then ...

We have a little BIDULE action for ya !

Just to give a sense of my wiring layout, I have a partial screenshot of my NVC-BXQ-BIDULE.
Bidule screenshot-2.jpg
NVC-BXQ-BIDULE
and then, here is a Bidule PRESET of my NVC-MAMMOTH [mini].
Bidule for NVC-Mammoth[mini]-1.rar
(31.88 KiB) Downloaded 176 times
Had to RAR it to post here.

Inside is the preset to load into BIDULE.
I'd be curious to hear how this preset behaves on a completely different system.

Be mindfull of my plugins included in this preset.

1. my custom Nebula with Mammoth library, with a unique 'majic' vst number.
2. Klanghelm's VU meter
3. MIDIChannelFilter/AudioRouter. This is available on my site [free utility VST].

If doing this in REAPER ... then you do NOT need any of the 'support' files [ReaControl, ReaRoute].

Let the testing begin ;)
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Tue Mar 25, 2014 12:29 pm

RJHollins wrote:
Hannes_F wrote: - It seems not possible to assign fixed midi channels to a Nebula instance. Nebula wants to return to channel 16 all the time here. Therefore I tend to set the output channel of the Bus_Router instances to 16 too.
The crux of the Nebula MIDI issue ! :twisted:

This is a highly requested change to be asked for with Nebula. The current mode is OMNI, which means, Nebula responds to every MIDI channel, at all times. This affects not only the NVC ... but any attempt via DAW, MIDI stream, what have you ... we do not have a way to 'speak' to a single Nebula directly ... we have to isolate each Nebula with a filter.
OK, by now two initial questions of mine have been answered:

1. Why is it necessary to use all those MIDItoRea and MIDI_Bus_Router inserts?
- Because it currently is not possible to assign a specific MIDI channel to a singular NEBULA instance . . . except Giancarlo has a magic xml edit in the sleeve . . . Giancarlo?

2. Why is it helpful to use Nebula Setups?
- Because this helps to only use 4 or 5 Nebula instances which will then automagically reload different programs for cut/boost, bell/shelf, colored/clean.

Here is one more question for the 'standard setup':
Could you please post the list of programs that you included in your 'Nebula Setups' setup for the Mammoth? The reason why I am asking is that the reloading of programs worked as long as I had only few of them but when I try to include them all including the filters it Nebula will only do the Init thing.

BTW I have added the Reaper midi parameter automation to the sliders and now it works - except the reload / switch function.

What I want to have is a setup that runs 100% reliable and stable in REAPER 64 and I will then upload that as FX chain here for sharing and testing.

I looked into the bidule setup but I would need to replace every device there because I am on 64 bit. I'll spare that for a next step after the 'standard' Reaper version works stable.

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Tue Mar 25, 2014 8:06 pm

Good morning ... still on the first few sips of coffee ... lets take a look.
1. Why is it necessary to use all those MIDItoRea and MIDI_Bus_Router inserts?
- Because it currently is not possible to assign a specific MIDI channel to a singular NEBULA instance . . . except Giancarlo has a magic xml edit in the sleeve . . . Giancarlo?
Basically true. I would add that Reaper's current design contributes to this need. A track in Reaper is 'universal' [?] - can be stereo,mono, audio, MIDI.
The one instants of MidiREAControl seems to add the MIDI intelligents. NOTE: it seems Reaper is getting a lot of MIDI attention ... maybe this will all get integrated in future versions [?!?].
As for the MIDI_Bus_Router ... we need 1 per Nebula. It grabs data off the main MIDI line, filters to a specific MidiChannel, and routes it to the BUS that NEBULA is assigned too.
2. Why is it helpful to use Nebula Setups?
I'm not quite following the reason you posted. I would say that NebulaSetUPs basically allows us to draw from a massive library and create specific Nebulas that have a user defined prest bank to select from. It is common to house a specific library [such as the Mammoth] in is own Nebula. Since the NVC is designed to work a specific library, it made sense to make it a package of one library. It also greatly improved the loading time of the chain.

If this helps understand ... the NVC uses a 'parsing' routine to read the custom XML file and 'pick off' key preset names and their PROGRAM#. From there, these preset names get grouped and sorted, then sent to specific sub-module destinations.

The specifics of the how the parsing works I determine at the time I design. This is based on the naming procedure/style that the library creator used.
Sometimes this requires several strategies to organize the presets into proper categories.

As a side though: If we mixed in other libraries ... could the NVC parsing routine get fooled ?? it's possible given the thousands of presets in the main pool.
- Because this helps to only use 4 or 5 Nebula instances which will then automagically reload different programs for cut/boost, bell/shelf, colored/clean.
This is confusing me ... maybe 2nd coffee cup will kick in ... but this leads to the next question...
Could you please post the list of programs that you included in your 'Nebula Setups'
I probably can ... but something confusing here :?
Take the MAMMOTH as example. Using NebulaSetUPs, I filter it down to show ALL the Mammoth presets available. With that, I select ALL the Mammoth presets and create a new custom Nebula. Given a identifiable name, this custom Nebula is all we need to have the Mammoth EQ. The NVC uses the custom XML file made with SetUPs, and now it knows what presets are in this Mammoth Nebula. [the NVC goes on to then write its own personal 'Configuration' file that contains all this info [and more]. From then on, the NVC AUTOLoads this file to bring in the configuration. It does NOT need to parse the setup XML file ... UNLESS the user changes the custom Nebula. If that happens, we need to teach the NVC the available Presets. So we load that SetUP XML, and the NVC will update its' Config file.

The CONFIG tab on the NVC might be a bit confusing too.

When the LOAD XML button is clicked, navigate to where the custom SetUP XML file is and load that in.
On this page is a display of 'Bank Names' and Preset numbers. These are ONLY FOR DISPLAY ... they don't control anything :o
... in fact, it is still there as my quick de-bug and verify display.

The important part is that LED next to 'Config File Loaded'. When it is lite GREEN, the NVC is working from it's special config file.

The XML data shown above could all be blank [0] or show INIT ...[remember, this is only display from the parsing routine]. The GREEN LED tells the whole story here.
The reason why I am asking is that the reloading of programs worked as long as I had only few of them but when I try to include them all including the filters it Nebula will only do the Init thing.
I'm really not following this part. sorry :oops:

If you go to the 'custom Mammoth' Nebula GUI, are you able to see and load all the presets you assigned ??
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Wed Mar 26, 2014 1:31 am

RJHollins wrote:
2. Why is it helpful to use Nebula Setups?
I'm not quite following the reason you posted.
I was initially thinking: Why don't we just use one Nebula instance for each band and steer them with Midi? Then I noticed that there is the need for reloading because different programs boost and cut, and also there are variations for shelf/peak and clean/colored. So one would need like 11 instances of Nebula all loaded at a time, and even 22 if one wants them clean + colored - or one decides for reloading programs. And then this makes much sense:
As a side though: If we mixed in other libraries ... could the NVC parsing routine get fooled ?? it's possible given the thousands of presets in the main pool.
... but something confusing here :?
... Using NebulaSetUPs, I filter it down to show ALL the Mammoth presets available. With that, I select ALL the Mammoth presets and create a new custom Nebula
OK, I see I did bring this question forth in totally the wrong order. I start again:

1. I create a NebulaSetUps program called 'Mammoth_all`with all Mammoth programs as seen in screenshot. Please note that I defined one program as default (Low shell boost).

Please right-click on links, I did not want to mess up the forum format by embedding these big screenshots.

http://www.strings-on-demand.com/data/Mammoth_all.jpg

2. I load an instance of 'Mammoth_all' into Reaper and also load the `Mammoth_all.xml' into NVC.

3. I see the command 'Configuration has Changed! ReLoad XML'. Hmm ... I loaded it just seconds ago. But probably it has been re-written, so I reload it. Again the same message. I re-load and re-load. The message does not go away. The Nebula instance shows a smile filter now.

http://www.strings-on-demand.com/data/M ... loaded.jpg

4. I switch from Boost to Cut. The Nebula Instance performs a reload, however to a different Smile filter.

http://strings-on-demand.com/data/SwitchToCut.jpg

Problem description better now? Thanks.

RJHollins
Expert
Expert
Posts: 4047
Joined: Sun Mar 28, 2010 5:53 pm

Re: NVC - Series - General News

Post by RJHollins » Wed Mar 26, 2014 3:47 am

Hi Hannes_F,

Thanks for the details provided.

To start, we should clarify the design of this NVC controller. It may or may not be obvious ... but let me explain.

The NVC-Mammoth can function is several different modes. Each mode will relate to the number of NEBULA instances needed.

In what is called the MINI mode ... we have 4 sub-modules plus the filters always displayed.

The 'toggle switches' at the top of each sub-module allow switching to the various functions the Mammoth can do.

Looking closer ... lets take a simple one. The LO-MID module. It has 2 functions, CUT or BOOST. When we toggle the switch we can view the specific controls and settings available. Notice that the MIDI CHANNEL on these switching modules is set to the same CHannel. [probably MidiCH #2]. This CH2 talks with the NEBULA that is also assigned to listen on CH #2.

So what we have are 2 modules [Cut & Boost] that talk to the same NEBULA.

This one example mirrors how the 'Mammoth' hardware works ... we can Boost OR Cut.

The same concept is used in each of these sub-modules.
The HI-MID [on CH3 works the same ... Boost OR cut].

When we look at the Low and High Peak/Shelf modules, we see that we have 4 choices per module.

By keeping EACH sub-module assigned to the same MIDI CH in the 'group', each of the PRESETS that we load into that section will each talk to the same Nebula instance.

In this 'base' mode we have mirror the choices the hardware provides. In doing this we have 4 Nebulas to handle each section of eq'ing ... and then a 5th Nebula to handle the FILTERS.

Always from the main GUI, I have tried to provide visual indicators of the status of each sub that is hidden in view. Fundamental access such as bypassing the EQ gains, or switching a Nebula IN/OUT of the audio chain are available from the main GUI.

... and yes... this did put a hurting on that last brain cell to try to figure out :roll: :lol:

If we're good to this point ... we can expand beyond the normal function of the hardware via Nebula :o

The KEY ... are the MIDI Channel assignments.

Each Channel needs a Nebula to link to, but the strategy used to assign these channels offer additional flexibility, and more simultaneous 'band' control if desired. This is accomplished by how the Channels are assigned [within the sub-module].

example: say you want both Cut AND Boost of the 'LO-MIDS'. Without messing up the aleady assigned midi channels. you can leave one of the modules on CH #2, and assign the alternate module to, say, CH #6 or maybe 'reserve' the channels for the LO and using CH# 9.

On the LO band ... maybe you'd like to have them in PAIRS [which would need 2 Nebulas]. Maybe have the Shelf and Bell on separate channels.

I've tried to make this a condensed and flexibile at the same time. Of course, the ultimate Mammoth is each sub-module assigned to unique channels and linked to 13 Nebulas. Just remember ... you don't need to use every modules ... but you can 8-)

OK ... sorry ... I felt I needed to get that info out there for everyone.

Now to the issue at hand.

Hannes_F ... There seems to be additional Presets showing up in the HMF PK Boost and Cut banks. Also in the HI PEAK boost and cut.
The HI Shelf boost looks correct, but not the Cut.
Also, the Filters don't seem right :?

What I mean by that ... are the total number of PRESETs that should be there in each bank.

The library I use is the original Expanded release. I'd not heard that any of the presets were changed ... nor any modifications to the names used.

Just to be sure ... confirm for me that these are indeed the 'original names' of the presets :P I have to ask, because that would be first concern.

I'm still looking over the pix you posted to gleen a clue.

I see the 'User Config File Loaded' with GREEN Led ... a good sign. But I also see the 'Configuration has changed' alert.

Now that alert can come up if you clicked in the [CC] control edit boxes. This will throw an alert that something might have changed.

It may seem confusing, but it asks to RE-LOAD the Setup XML file. The reason for this is the preset data and the [CC] data are stored together in NVC's autoload file. If you changed or clicked on the [CC] edit ... go and then Re-Load the setup XML file to update the NVC file. That should clear that alert.

See what that does ... but I'm still puzzeled with the quantity of presets in certain banks. :?

I may need you to send [email] a copy of your setup XML file to examine if something is wacked.

ok ... lots of stuff here ... let me post, and then see where we are.

Thank-you for the details you've provided, and apologies for the delay in getting running. We'll workto get this solved!

Thank-you
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

User avatar
Hannes_F
User Level X
User Level X
Posts: 129
Joined: Sun Apr 18, 2010 12:08 pm
Location: Hannover, Germany
Contact:

Re: NVC - Series - General News

Post by Hannes_F » Wed Mar 26, 2014 6:38 am

@RJHollins
Thank you for the explanations. Until the two smilies in your last post all was understood here, then came a part that was new but pleasant :) . I will often have to use more mid bands than one while the bass range is already set, for example.

To the problem at hand:
Now that alert can come up if you clicked in the [CC] control edit boxes. This will throw an alert that something might have changed.
Nope, definetively no click on the CC edit boxes. This alert comes always. I think for finding the reason for it some sort of log or debug version would be handy.
It may seem confusing, but it asks to RE-LOAD the Setup XML file.
That is what I did then.
go and then Re-Load the setup XML file to update the NVC file. That should clear that alert.
Nope, it doesn't.
Also, what puzzles me is that if I save and reload the project I will again see the default xml file in that line.
but I'm still puzzeled with the quantity of presets in certain banks. :?
Understand now why I asked for the 'official' list of presets that you use? :mrgreen:
I may need you to send [email] a copy of your setup XML file to examine if something is wacked.
I attach it to this post. Thank you.
Attachments
XML_Files_Hannes.rar
(1.43 KiB) Downloaded 165 times

Post Reply