SONAR 8.5.3 Producer and Arturia Oberheim SEM V - no patch change

Author
Post
Essentials Only Full Version
magek
Max Output Level: -90 dBFS
  • Total Posts : 34
  • Joined: 2008/09/02 14:53:15
  • Location: Lincoln, CA
  • Status: offline
2012/07/10 15:26:38 (permalink)

SONAR 8.5.3 Producer and Arturia Oberheim SEM V - no patch change

Using the Arturia Oberheim SEM V (1.1.2) standalone or in another host (Cantabile), I have no problem changing patches using the GUI.

However, with SONAR 8.5.3 Producer as the host, the patches won't change. The patch change is reflected on the GUI, but the actual patch (sound) does not change. The patch does sound, but it's always the same initially loaded patch.

All my other VSTs, including other Arturia products, work fine. Just this one new SEM V.

Anybody out there successfully using the SEM V in SONAR 8.5.3?

Any ideas would be much appreciated. So far, nothing helpful from Arturia support.

-Matty K

i7 2670QM 2.20GHz, Win7 Pro x64 8GB, M-Audio Fast Track Ultra 8R
Behringer X-Touch
SONAR Platinum, NI KOMPLETE10, Arturia V Collection 4 and 5 & other VIs
AKAI MPK88
M-Audio Axiom Pro 61 & Oxygen8 v2
Alesis Q49 (rigged for wireless)
Korg Triton Studio, O1/W & O5r/W
Hammond XK-1
(Fender USA Strat, PRS SE Custom 25th Anniversary, Ibanez EDB605 5-string)
#1

3 Replies Related Threads
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re:SONAR 8.5.3 Producer and Arturia Oberheim SEM V - no patch change 2012/07/10 18:38:56 (permalink)
    Make sure you use a MIDI channel that is free of other data. The patch will change back if your sharing a channel with another instrument or even an empty MIDI track. Patch changes don't always show in the event list.

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #2
    KevinK
    Max Output Level: -73 dBFS
    • Total Posts : 863
    • Joined: 2003/11/06 06:30:43
    • Location: Le Bar sur Loup, France
    • Status: offline
    Re:SONAR 8.5.3 Producer and Arturia Oberheim SEM V - no patch change 2013/02/05 00:48:10 (permalink)
      As per another thread that I started last night (I'd have resurrected this one if my search terms had found it), I ran into exactly the same problem when I migrated the SEM V plug from a 32-bit XP machine to a new 64-bit Win7 system. I did find a workaround - go back to Sonar 2 style and insert the SEM in the FX bin of an audio track, then assign a separate MIDI track to the SEM. In theory, I just did what Sonar does under the hood when you insert a soft synth, but in practice it makes a difference to the Arturia VSTi. Did you ever find a more satisfactory solution?
    #3
    KevinK
    Max Output Level: -73 dBFS
    • Total Posts : 863
    • Joined: 2003/11/06 06:30:43
    • Location: Le Bar sur Loup, France
    • Status: offline
    Re:SONAR 8.5.3 Producer and Arturia Oberheim SEM V - no patch change 2013/02/11 11:47:19 (permalink)
    Yet another observation on this bug: I create a new Sonar project. I insert SEM V as a Soft Synth with the canonical Sonar soft synth track folder. It plays, and the UI "analog controls" work, but presets do not load. I create an audio track and insert SEM V as a soft synth in the track FX box. I create a MIDI track and assign it to the synth instance. It plays, and presets DO load. I go back to the first instance - presets still don't load. This much I've recounted in previous posts. But wait, there's more... I create a THIRD instance by inserting a Soft Synth as a new track folder, just as I did for the first instance. THIS instance WORKS perfectly, including loading patches. I go back to the first instance - and the presets STILL don't load. It would appear that there's some global state in the VSTi that's copied into each instance at startup, but which is not initialized correctly by a Sonar Soft Synth track folder insert. That global state *is* initialized correctly by the Sonar VSTi "effect" insert, so that subsequent instances pick up the correct values. Any thoughts on how the Sonar 8.5.3 configuration might be tweaked to cause/avoid such a bug?
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1