jksuperstar wrote:I was trying to see how Vectron could pull off bass. And it's the 128 samples length that is the gotcha...stretching that 128 samples over 3ms is a pretty big stretch, and I think it's too much for the interpolation algorithm. So that's when I mixed the vectron into a ModIV patch where I add the subosc.
Maybe I'd simply be better off with another synth (or just Modular), but I thought I'd work through the limitations and see if it could be done anyways.
It's not so bad when thrown into distortion, as there's a few extra harmonics to play with already there. But I haven't found a decent bottom end with Vectron yet. Lead sounds are lush & full with plenty of grit, a great compliment to the smoother Korg DSS-1 I have, I was just curious if the Vectron could get down deep and then I could take advantage of it's modulation possibilities. I had the same problem with my analog DSI Evolver, but I guess that's expected, they are both based on the same Prophet VS
that is a very good idea. when i was working on my hardware digital wavetable osc, i preferred 256 samples per cycle, I had to make "between" samples from the waldorf and other waves i found. even for 8 bits. 512 would be even better. no excuse not to have 1 or 2k these days.
thats why wavetables with 64 samples ought to be mixed with a similar "real" osc with a crossover. easy to do with the modulars and other great tools in scope!
your correct the problem people have using highe wave table sizes is that if you are taking samples fron synths are they have ant aliasing filters
so that they filter out the frequencies that cuase it
the problem with this is that the wavetable dont resemble or have the same spectra content as the 256 or 512 samples of the same waveform
128 samples is the smallest size to use this is what the blowfeld uses the uwave you need todo them in 8bits which are very steppy compared to the 16bit version
the vs uses 256 8bit waveforms
if i use mine in the blowfeld i just reduce the sample rate to 22.5k and they become 128 samples in size as the blowfeld is only interested in the size and not
the key or loop info as it takes the spectra of the waveform
for bass the wavetable size is good in 521 1024 and 2048
the only problem with these is that becuase they contain all frequency info when transposing them up more than 1 to 2 octaves you get very bad aliasing depending on what frequency your running the audio at
when i use my hardware modular i add a 30-60hz sin wave to the vca input along with the wavetable input from the filter so that when changing the filter frequency i still have bass content
ni razor for reaktor is a good example synth of this as its an additive synth when you modulate it and filter it you lose the bass frequencies they have a setting nob that puts back the fundimental suboctave partials back in the sound so that its always there
if you want i can add the funderment suboctave partial to the next set of wavetable sounds for the vectron as its easy in my resynthesis program
Thanks! I will play with these over the next few days and post some presets.
I was also thinking about the modular approach, and your comment of a filter (for smoothing?) per oscillator. I could add a resonant highpass in there, with cutoff tracking the fundamental note. This would boost/ generate the fundamental frequencies, and even have a slight lag just like a wooden bass body hitting resonance. Placed serially to the normal smoothing or aliasing filter, each osc could get tuned for how much sub freqs are added, so the deep bass stays clean and not muddy.
Experiment and you'll get some great results.
The SpaceF AUX Delay and Neutron Automatic Double Tracking plug can be swapped out, but those are my choices.
Give me a little time as the rig won't be back home until Sunday late...
They are unique, and I include Vectron with Solaris' joystick, so I can use the LFOs then over ride them manually with the Joystick.
The best sounding presets are layered with the EPianos of the FS1R and they are really Zawinul on Steriods....
XITE-1/4LIVE wrote:Give me a little time as the rig won't be back home until Sunday late...
Cool,- I can wait ...
XITE-1/4LIVE wrote:
They are unique, and I include Vectron with Solaris' joystick, so I can use the LFOs then over ride them manually with the Joystick.
The best sounding presets are layered with the EPianos of the FS1R and they are really Zawinul on Steriods....
I´m looking forward your examples now ...
Interesting you mention the FS1r,- that´s what I try to aquire actually because I want at last ONE 1HU hardware FM module in the rig, but selling DX7mkIIFD, TG77 and TX816 then.
Actually you´re using SCOPE/Vectron on Xite-1 and the FS1r together live ?
Sold the FS1R years ago and sampled the EPianos onto the E5000 Turbo, used them in Gigastudio, now in Kontakt.
They sound good, and use 8 different presets, each one is around 32MB's after compression using NCW.
Vectron sounds fine w/o the FS1R stuff, but the samples have lots of thickness so Vectron can get swirly w/o losing the meat of the sound..
next to nothing wrote:However most of the magic is done in the ProgOsc Section when it comes to sound design after the presets are loaded as you show here. You will need to select the wave from the dropdown menu within ProgOsc. When you select waves within wavecreate, you can morph between up to 4 waves (as you show) to create a new waveform that can be saved in a new user slot.
Ok heres lesson 2 then based on that :
vectron lesson 2 - making own waveform and mixing it with others
One last question : When you build synth presets, are they built in such a way as to include the wave presets ? Or does one have to load both wave presets as well as the synth presets that use them ?
once you have loaded the wave preset file then you can use them in the
program osc page one you have created presets using any of the wave data that is loaded in the wave create screen
you then save these to program .pre data which is seperate from the wave data .pre file
so wave data .pre are just the waves
preset data .pre is patches for the vectron that uses the internal waves and user waves
and contain all synth params that you have created from the synth its self
and this is where all the sound magic happens
the wavecreate .pre data file is your sound pallete where you get your paint from like colours each waveform is a different colour of sound
and the program page is your canvas where you mix and paint your scenary in sound sense you add your colours waves and mix and filter and modulate to create textures of coloured sound and these are your created patches works of art that stand for other to admire in the sound gallery
A beautiful old synth reborn thanks to few chaps who refuse to get new toys when we still haven't mastered the old ones...
I think a Modular version of this would be awesome, where each Waveforem could have it's own filter/FX/Loop EG/Pan /Grunge ( 12AX7 or Shroomz Tube Filter ).
Having a Joystick is really beneficial, and too bad I can;t figure out the C4Stick Modular Joystick thingy from Sharc.
It seems better suited than the stock ABCD x-y Axis Module...
i could do a patch with proper versions of the envelopes also with m4 mvc with unison
on the outs if i set the poly out if i have 8 poly outs that go to a panner then then to a stereo mixer for the effects so that
it performs the same as a prophetvs
and have it set to 8 note poly like the original
also the cem filters
i use win32 xp sp3
and i have heard people have problems with the wavwe osc in 64bit scope 5.1
i can also then add a folder with all samples in so that its included in the a folder with the .pre modular file so that any person who uses it its in the write location for presets
and then i can add transeint samples aswell as spectra and loop material and have the vector mixer on the final vca
