Last nite I made a squelchy 303 kinda bass in old Klangformer beta (2002)… So this morning was mucking about using SVArTracker’s multi-temporal patterns feature plus a few quick & dirty use of the Effect Processor… Nothing serious as this ain’t no ‘tune’…
Pretty advanced feature for 2008, man in 2 years SVArTracker 1.22 will be 20 years old!…
OK… after more testing finally gonna make a ‘serious’ tune in this as feature set kinda fascinating… But if anybody else wishes to try the most problem you will encounter is weird reactions to plugins, really different from other trackers & sequencers in that respect as it may be 4-5 song saves till evil shows up… So I find best that if I am thinking about adding a plug, then I will add it without doing anything serious with it but will hook MIDI keyboard to it then loop pattern that’s playing other stuff & jam out really giving the plugin a ‘good rogering’ whilst playing… Any inkling of evil shows up even a ‘hiccup’ do not use the plug…
On the good side 16 instances with tracklinkers heading to each one for a single SF2 that’s been made into a bank from 16 separate SF2 then going into DX DMO Chorus & a few going into DX DMO Echo no problem at all jamming & switching for an hour… Just using alot of RAM (about 1 GB) But that’s loading about 1,200 samples, very little CPU…
So the big worry is third-party plugs, mostly VSTi, VST not so much…
One thing to keep in mind when you have many instances you must also choose the correct one to automate in the param header-
An anticipation of work in the Effect Processor made me think that VSTnotes would be a benefit because once you have packed many curves into a ‘cell’ thus it’s own command code you would then hafta keep reopening the Effect Processor to refresh the memory in one’s brain, easier-better to write down defining characteristics of the command…
So far 17 iterated saves on song Wusik EVE has been quite stellar, not a hitch… Might upload this as well it was facebook freeware back in 2012-
Continuing on… When using Effect Processor it’s difficult to get exact point to where to start first & last curve vertex… The middle does not matter much… At first I thought of using a screen pen or annotator but the param knob is small so I downloaded a 12-point star then made a trans GIF out of it then turned it into a screenmate drag-drop type… Since I cannot rotate it any of the star points will do as a ‘pointer’ thus I can see if curve is starting smooth & ending in correct spot… I’m sure there’s probably other means one could use-
Also forgot to add that the plugin adapter has settings that should be de-ticked otherwise track bouncing & WAV export will probably end up as gibberish… If opening the Anti-Wave sampler they are de-ticked by default but on other plugs they are not-
Continuing with ‘SVArTracker Studies’ Looks like one can go up to 9 notes per track restructure which will leave one with a program change lane & volume lane then up to 6 FX command lanes… Which may seem excessive but say You are only doing a curve or two in the effects processor you can then trigger numerous curves (up to 6 cells) at the same time rather than packing 6-8-10 into a SINGLE cell…
Forgot to add here’s my current WIP in SVArTracker maybe 1/3 done I dunno… Could change alot before finished… Just trying to endure & last out the ice/snow baloney haven’t been able to leave the homestead for 2 weeks…
Moving on I have discovered the source of an ‘everytime crash’ which results from SVAr not seeing a MIDI-In device hooked up that it’s trying to connect to-
