This 'unofficial' Forum is dedicated to the Clavia Nord Keyboards, including the Nord Stage, Nord Electro and Nord Piano. Discuss any issues around Nord's keyboards, share your favorite patches, samples, and music. We are not affiliated with Clavia!
Hello, i have problem:
I want to make a bundle with the soundmanager. The program has the synth activated and one sample (3mb) in use.
But when i start making the bundle, the statusbar tells me that it takes 12 minutes and its starting to upload the silver grand piano.
In the soundmanager i right clciked on the programm where i can see, that there are linked 2 pianos to that programm (the silver and even the italian grand).
How can i delete these pianos from this program that should only play a sample?
Thx!
These users thanked the author Schulti for the post:
The Piano Section(s) may be disabled in your synth program, but it still contains piano assignments. Perhaps someone might create a program which is synth only for the early part of the song, but then the performer wishes to engage the piano mid-song to add it to the mix. "Waiting in the wings" so to speak. ALL programs will necessarily contain two piano assignments, regardless of whether or not those piano sections are actually turned on.
What I do to optimize bundle size on these kinds of programs is to:
1) turn on Piano Section for Slot A
2) change Piano Type to CLAV
3) turn off Piano Section
4) repeat above for Slot B
5) STORE program
The Clav is the smallest available file in the entire Nord Piano Library if I'm not mistaken, or close to it. This will speed up your bundle operations.
Note that if the bundle you are creating also contains programs on which you ARE using a piano, you can use THAT piano model for your selection in the disabled piano sections of other programs -- it's going to be loaded to the bundle anyway.
Note also that the same rules apply to the Synth Sections. You will want to momentarily turn ON Synth Sections which are OFF to see what OSC TYPE is selected. If set to SAMPLE, the bundle will include a copy of that sample. If you don't need that sample, switch OSC TYPE to anything other than sample, turn OFF the section and STORE the program.
These things will make your bundle files smaller and more efficient.
Bless,
Pablo
These users thanked the author pablomastodon for the post (total 2):
Its me again. Anyway I think it would be a simple firmware change providing the possibility to deselect a piano within a program. This would also lead to a more precise piano usage info in the sound editor.
Please Nord go for it, I think lots of us would appreciate that.
No, it sould not be a simple firmware change -- it would require an altered program structure. Additional data space needed to accommodate additional information. This would create HUGE headaches for tens of thousands of people worldwide. This is simply not going to happen.
Bless,
Pablo
These users thanked the author pablomastodon for the post:
Hmm, I don't get it. Of course I don't know the NS2's program structure. But as I am a software engineer myself I cannot understand why pointing to an (defined) empty piano would lead to a rearranged program structure. But well, ok, I just was thinking loud...
I have a simple solution that requires no firmware change : Clavia could provide a nearly-zero size dummy piano npno sample, that could selected in patches that require no pianos.
These users thanked the author Mr_-G- for the post:
: Clavia could provide a nearly-zero size dummy piano npno sample, that could selected in patches that require no pianos.