Vienna Symphonic Library Forum
Forum Statistics

196,754 users have contributed to 43,031 threads and 258,436 posts.

In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 91 new user(s).

  1. Home
  2. General & Hardware
  3. Halion and Opus1

  • Halion and Opus1

    C
    C
    I have so many weird things happening with my setup its not funny. I'm hoping someone out there uses Halion since none of the tech or programers are familiar with it.

    Ok, so everyone tells me "you have a routing problem". I am doing the following: Keyboard>Performace Tool>Sonar>Halion

    I have also tried Keyboard>Sonar>Performance Tool>sonar>Halion

    both somewhat work but here are the results...

    I can only use the first chanel of port 1 in the performance tool. If I add any other tracks to Sonar the 2nd chanel in the perftool doesnot work. (I can never play two instruments at the same time). If I change programs in Halion (switch the fist and second) then the instrument that didn't work now works. Some instruments don't play at all. Some do weird things like I will play a scale but I won't hear a scale (notes will be all over the place). I have checked the instrument range and that wasn't the problem. I am also getting lots of cracking and popping but it seems to be random so I don't think its a sound card problem but connected to the routing issue.

    I guess I could go on and on but lets just see if anyone out there has any helpful tips? (because I'm going mad!!!)

    Calaf5
  • P
    P
    Perhaps you saw this already, but there's a nice tutorial:

    http://www.timkiel.com/music/tutorials/tutorial.htm

    PolarBear
  • cmC
    VSL Team
    cmC
    welcome calaf5, i can assure you, it's a midi routing problem.
    your setup mentioned first cannot work - the second would be correct, given you have two virtual midiports, one between sonar and the perftool-in and one between perftool-out and the *ghost*-track in sonar, where your halion is hooked on. (you can use marble, local pipes from MoL or for the first even the new VSL MidiRouter)
    also please make sure _all_ your inputs to sonar only listen to the midi channel they are supposed to, otherwise unexpected behaviour like the ones you're describing ocurres
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.
  • C
    C
    I am using the method described in Tim Kiel's website. I have a ghost track set up. Certain samples work and others don't. For example I was using the piccolo the other day just fine (PFL_standard all) but when I tried the Cello_standard all with the exact same routing set up there is no sound - nothing! So what is going on?

    I did get one error message today when experimenting that said "MIDI Loop feedback. Disabling port 1" and then also when I looked up the properties of my hardware MIDI Yoke it said "No drivers are installe for this device". Do either of these things have anything to do with the problem.

    as you can see I'm a beginner at this stuff...
    calaf5
  • C
    C
    last edited
    last edited

    @cm said:

    welcome calaf5, i can assure you, it's a midi routing problem.
    your setup mentioned first cannot work - the second would be correct, given you have two virtual midiports, one between sonar and the perftool-in and one between perftool-out and the *ghost*-track in sonar, where your halion is hooked on. (you can use marble, local pipes from MoL or for the first even the new VSL MidiRouter)
    also please make sure _all_ your inputs to sonar only listen to the midi channel they are supposed to, otherwise unexpected behaviour like the ones you're describing ocurres
    christian


    Where can I find the local pipes from MoL? I did a search online and didn't find anything.

    Also, I downloaded the vslmidirouter but it doesn't show up in my selections in Sonar like all my other MIDI routers did when installed.
    calaf5
  • cmC
    VSL Team
    cmC
    calaf, MoL (aka Midi over Lan) is a product from www.musiclabs.com, it provides 8 local virtual midiports. the ports from the VSL MIdiRouter will only show up in the inports of the performance tool and as outport from your sequencer, that's why i said it could be used for your *first bridge*
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.
  • C
    C
    cm,
    Thanks - I will try local pipes out tonight.

    About the vslmidirouter...it shows up in both the in and out ports of my performance tool. (not just the in like you said) And nothing shows up in Sonar? Any idea why?

    calaf5
  • cmC
    VSL Team
    cmC
    thanks for pointing to that - the VSL midi route can be used to route midi _to_ the performance tool, however it should not be visible in the dropdown for midi-out of the perftool (has to bee corrected it seems)
    on the other hand the VSL MidiRouter will only appear in sonars OUT not in the IN selections, so you could use this device to route midi from sonar to the performance tool. to route midi from the perftool to somewhere else please use another type of virtual device
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.