Beiträge von HUBA

    Hi Huba,


    Have you got any luck with Modding your pedal with the 50k pot? Did it work?

    No, I never got to try it. Too many projects :) I will actually abandon the whole thing as I've decided to replace my pølar with the desktop version for ergonomic reasons, and the desktop unfortunately has no pedal input. The plan was to use the pedal input for external LFO. I guess MIDI is always an alternative, although I imagine it may clog and mess up the overall MIDI timing.

    I had a chance to test it myself but it didn't seem to work. I was able to make the MONO indicator blink in VC, but I couldn't make the LFO retrigger - not by sending the same value repeatedly neither alternating 0 and 1.


    Sure it's not changing anyway? The mono/poly mode I mean? (At least with the TI I'm pretty sure it's not possible to retrigger the LFO waveforms without pressing a key.) When I tried controling it with my remote, and viewing the corespnding parameter in the TI display, it wouldn't show the changes I sent even though I could hear them(volume, pan, release). Have you checked that you can hear a difference when switching LFO mode from the TI itself?


    I would really love to hear the official word from Access on this - was the above feature dropped, or was it simply overlooked?


    So is your impression, when reading that bit I quoted from the Virus B manual, that this function is meant to retrigger the LFO waveform when sending CC#70 to LFO 1? It's strange that the same midi CC message should switch between LFO modes, which, at least with the TI, means poly or mono mode. Maybe I misunderstand something. The way it's written it's certainly open for interpretation.

    Here's a diagram of the old Virus signal flow, available on the download section of this site. I hope it helps to clarify.


    Thanks!


    Are you referring to the retriggering of the LFO-s via CC#70 and CC#82 (LFO mode select)?


    Yes.


    You can try that yourself - just draw/copy/paste those CC messages (with value 0 for poly LFO and 1 for mono LFO) in your DAW and send them to a Virus part that is loaded with a patch that has some prominent LFO modulation, and see what happens.


    I'm having problems making my Polar respond to CC messages other than volume, pan and a few others, so can't try this before I find out what's wrong. (I've probably just overlooked something overly obvious as usual.) Anyway, if all this does with the TI is switching between poly and mono mode it's not too interesting, and if the same goes for the Virus B, then I'd say the Virus B manual is somewhat misleading:


    " External LFO Trigger
    You can also trigger an LFO at any time by means of a controller, in other words, restart its waveform cycle via remote control. LFO1 mode (Ctr #70), LFO2 mode (Ctr #82) and LFO3 mode provision controllers that you can use for this purpose (Parameter B 9, see the parameter documentation in the \"Appendix\" on page 251). \"

    Does anyone know what the specs are for the contol pedal input of the TI? Couldn't find anything in the manual. In case it differs, I have a Polar TI2.


    Basically, what I want to know is what voltage it operates with. I've seen the Yamaha FC7 pedal mentioned as a perfect fit, but I couldn't find any useful specs for the FC7. I could off course just get the FC7, but I want to try other kinds of control, and would need to know the voltage used to get a full control range without damaging anything.

    I've been reading and re-reading your post, and I find it hard to think of where to start, because your question is not phrased in "standard" Virus terms

    Hm.. Ok.

    (besides the fact that you posted it on the wrong forum section).

    I see now that I should have posted this in "Questions and answers about Virus synthesizers" in the public section. Sorry about that.

    The Virus line is backword compatible, and features are only added. Therefore, it is not possible that an older model had some routing scheme that is not supported by the newest TI.

    I think you're wrong here, as it certainly seems to be things you can do with the older viruses that the TI line doesn't support. Internal routing as mentioned, and external LFO triggering (Virus B manual page 241) are two examples.

    By AUX bus maybe you meant the effects bus? The A thru C models had a central effect unit for delay and reverb, and each patch could only choose how much to send to that unit. The TI models implement delay and reverb separately for each part, but due to the linear nature of those effects, if you set the same type for all of the parts, it will sound the same as a central unit [or mathematically: Fx(a(t))+Fx(b(t)) = Fx(a(t)+b(t)) where t is time and a and b are audio waveforms].

    I get that. I like the true multimbrality of the TI's effects section and I off course don't want that replaced with global effects.

    Regarding re-processing one part by another, that is possible to some extent in multi mode if you set some part a, e.g. to out3 L+R, then connect out3 L+R to the inputs using TRS leads, load/create an input based patch on part b and set it to out1 L+R (make it twin unison if you want stereo, and note the various input modes). Play part a, and part b will affect it, part b might behave differently depending on whether it gets keyboard input or not. This is limited to only one send between only two parts at any given time.

    Yeah. With the B I assumed it only was possible to add extra filtering and effects by routing one patch to another in multi mode, like with the TI, only without using physical cables, but as I mentioned before, I read something in some thread about it indeed being possible to affect the oscillator section of another patch as well, but it was an answer to someone having a problem with something, and there's always a chance that the one answering in that thread never actually tried this himself and just assumed this was possible.. This is what made me curious, as it would allow for a lot of complexity if possible.


    About the chaining of effects and filtering to the same patch, I'd expect this to be limited by the number of AUX buses, but I don't know. I don't have a Virus B here to test this.


    Here is an example of the result of such a setup, plus part b was also fed back to itself (custom cabling ;) ).
    [soundcloud]

    Externer Inhalt soundcloud.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.
    [/soundcloud]
    Hope I covered everything.


    Sounds cool. Anyway, thanks for trying to help.

    I've read the manuals but can't really get my head around how this actually works. I only have a TI so I can't try it out.


    Is it possible, with internal routing, for sound shapers to interact between patches, so that you could use an envelope or LFO from one patch to modulate pulse with or oscillator pitch of another patch? I read something somewhere that indicated that this was possible, but I assumed it would have to be a source doorway in the mod matrix for this to be possible(?) ?(


    Is it possible, in virus A, B and C multi mode, to chain several patches in series so that one could say place filters AFTER an effect, and then add another effect and then yet another filter after that and so on, everything affecting the same, one and only, single patch?

    HUBA, did you consider using 2 LFO's? You might be able to use a square waveform LFO to trigger your other LFO for the bar reset. I'll make some patches and experiment with this one.

    Yes that's what I did when I somehow got it to work. Recorded a key held down for one bar, got LFO 2 to modulate patch volume with a 1/1 clock square wave with envelope mode and LFO 1 set to whatever, and somehow got a "resetish" behaviour going. Not very powerful sounding, but somewhat usable.


    Thanks again for the interest!

    Thanks Ionis for trying to help. About live, I found that out too, and it works quite well. Problem is I don't want to use Live as sequencer for different reasons. Not just the latency (which is terrible). I want to be able to do as much as possible without the computer. Especially in the beginning of a project. It's something about having my eyes glued to a screen all the time that doesn't work very good for me.


    Anyway, it seems you know what I'm after with the LFO's. I'm trying to figure out if there's a way of getting the TI LFO's to behave that way when using a hardware sequencer.
    If it's technically impossible, it would be nice to know why. Maybe someone from Access could comment. Maybe I'm chasing a ghost by trying to solve this with hardware.


    About your first comment with the mono setting, I tried different things with that, and I somehow got it to work . Kinda. When only one note is held through one bar. It makes possible for some interesting results when combined with a lot of different other things, but it's not the same as the LFO behaviour with Live. I want to be able to do this whith riffs too and I want that snappy dynamic LFO reset you get with using Live. (The sequencer in Reason also makes LFO's behave like this when looped) Starting to think it's a thing with software sequencers that can't be done with hardware sequencers for some technical reason

    Are there hardware sequencers that will allow for a clocked LFO in my Virus TI to either:


    Follow the riff, so that for instance with a one bar riff, the LFO will repeat with the riff, sounding the same with each 1 bar repetition as in Live


    or: Resetting its cycle at the loop point,like with the sequencer in Reason?


    In Reason, the LFO will, with any clocked rate, sound exactly the same with each reset at loop point. However it wont hold its sync when say a 1 bar riff is copied into two identical bars in a 2 bar loop. The different copies of the bar will sound different, but each individual 1 bar copy will sound the same each time it's played through.


    In Live, running Virus Control, the LFO's sync quite well to say a 1 bar riff. Seems any LFO clock rate (at or below 1/1) resets its cycle at each 1 bar repetition regardless of how many bars the loop is. No Trigger Phase, Key Trigger or Envelope Mode used. Nice. Not as perfect as with the loop thing in Reason though.


    Haven't tried with Live running as a sequencer without Virus Control, as I don't have MIDI ports on my laptop.


    With the Command Station as sequencer, a clocked LFO on my Virus wont sound the same over time in any way it seems. Each repetition sounds very different. Not Nice. Envelope Mode and Trigger Phase makes the LFO's settle more, but it's not the same.


    Is this how all hardware sequencers will behave when running external equipment or are there sequencers that will allow for the LFOs to behave as in Reason or Live by sending loop point messages or something? Thinking maybe the sequencer would have to be in control both before and AFTER the synth to make this possible.. I'm Comfused