Andres Medina

Hi, I'm having trouble with glitches using the new Omnisphere 3 (3.0.1c VST3). The Performance Module in Sonar indicates a very high Engine Load (57% - Max. 110% !!) at 1024 samples buffer size (which is too high - very high latency). This happens only with Omnisphere. I ran the LatencyMon tools and it says everything is Ok. I have plenty of RAM (64 Gb). As I play the audio, the core monitors in the Performance Module doesn't go very high. Still, I get lots of glitches. Any suggestions? Thanks!

He hecho la prueba en el orden que sugieres y si ocurre lo que mencionas: el audio de Omnisphere Out B se salta a la salida C. Sin embargo, esto ocurre solo si inhabilitas en Sonar el track de audio que toma la señal de la salida B de Omnisphere. No sé con qué propósito realizas esta operación? estás deshabilitando en Sonar una señal de audio que viene de O3. ... Al parecer O3 no silencia esa señal sino la asigna a otra salida de audio existente y habilitada, lo cual tiene lógica, ya que al menos el audio de esa parte que está sin señal asignada no se pierde...

Si, veo el problema. No sé si estás insertando Omnisphere en Sonar como Simple Instrument Track o el midi y el audio separados? Yo siempre lo inserto como midi+audio separados. Chequea la imagen: Adjunto un Project Template con Omnisphere como lo tengo configurado para que pruebes en tu equipo. En mi sistema responde de manera normal al cambiar los In y OUT en cualquiera de los dos extremos. Tengo la sensación que hay un problema en la configuración entre O3 y Sonar, pero no en Omnisphere como tal. Omnisphere 3 Routing.cwt

Con gusto! Te muestro mi configuración de audio de O3 dentro de Sonar, para que compares y veas si hay discrepancias. No creo que haya un Bug en Omnisphere, ya que mi sistema debería ser igual al tuyo. Sonar (última versión)+O3 v3.0. Recuerda que cada out del audio del multi de O3 debe estar enrutado a 1 track específico de audio en Sonar. Va resaltado un ejemplo con el Out 2 (B) de O3, enrutado a Audio 2 en Sonar.

Si es así, te recomiendo reinsertar O3 en Sonar y reconfigurar los In y OUT cuidadosamente. de nuevo. Tienen que corresponder de manera exacta los out's de O3 con sus tracks de audio en Sonar. Supongo que esta es la razón por la que no obtienes audio de las salidas B-H

Hablas español?

So, is it a hardware amplifier, right? If it's not a Sonar issue, Spectrasonics support are very helpful.

Hi, I do have Omnisphere 3. At the moment I have no issues with the Omnisphere multi outputs feeding the corresponding audio tracks in Sonar (latest version 2025.09 Build 038). You said you already double checked the I/O configurations in Omnisphere and Sonar right? I did have a problem accessing the Envelopes sections in the patches view. O3 crashed. I contacted Spectrasonics customer support and they found a bug, that was fully corrected in a newer version (still not available for the general public).

I got it. It's the screensets. Each screenset stores this information separately.

... I wonder which part of the software stores this information: the Console Strips selections?

Thanks, I tried the following: saving a new Workspace; Saving a new Screenset; creating a new template. However, everytime I open the template the hardware outs are checked...

Hi, Is there a way to open projects or templates with the Console Strip configuration set to hide hardware outs? I have to hide it everytime I open a project. Thanks!

[SOLVED] I had to select <default> in the Instrument tree And to add new names to the Standard Controller name list you have to select the last item on the list. ---

I also tried assigning my midi outputs to the "General Midi" instrument definition, to no avail.

Thanks, Maybe I messed something in the process… I didn’t find the "Standard" controller list tree, so I created a new instrument and a new controllers name list and then dragged the "Standard" controller list to the instrument tree. Then I assigned my output channels to this new instrument. … but still don't get my custom controller list. See pics -

Hi, Is there a way to change the controllers names of a VST midi track? I can do it in a blank midi track assigned to a particular instrument definition but didn't find a way to do the same to a VST track. Thanks!

Hello, Unable to use Sonar when disconnected from internet (due to a temporary cut in the provider service). Sonar hangs and start loading very slowly, like 10 minutes to load the main window...! I guess this is not expected behavior?

Thanks! I see. In fact, I'm trying to make my articulation map work, but the cc101 mapping does not trigger the intended articulation. Maybe I'm doing something wrong here? See pictures and video: Video_1.mp4

Hello, I'm having trouble making cc101 trigger a switch in VSL Duality Strings (Flow View) - see pic. VSL customer support checked in Cubase, and it works as expected. I found out that cc101 is a different type of controller (RPN) which I'm not familiar with. Am I missing something when I write a cc 101 lane in PRV to make it work? It should work as any other controller, but it doesn´t in Sonar. I tried selecting RPN Type from the controller list in prv, but I don't find a way to select cc101. Any help much appreciated. Thanks!

Also, creating a new preset from the track view menu does not update the presets listed in track manager when the track manager window is open. It needs to be closed and then reopened to refresh.

Track Manager: Rewriting a track manager preset does not work. When retrieving the newly saved preset, it does not update - keep showing the original layout.

...and, interestingly, this does not happen in Cakewalk. I tried the same procedure, and the output file is correct when using CW, no matter the number of hardware outs or the send between buses. It seems to be an issue of Sonar. I will report it.

After more tests, I found out that this happens only when more than 1 hardware outputs are present in the project AND one of them (typically Main out) is feeding a secondary Output (typically my Speakers Out) via Sends. If both hardware outs are present but there is no Send from one to the other, the export file is named as expected. Is it a bug or is this expected behavior?

Hi, Still having issues when exporting audio using "Tracks Through Entire Mix" source + labels. Steps: Select tracks Select "Tracks Through Entire Mix" Source Select {notesname]-[trackname] labels It should export the notes name + the track name, right? (the preview dialog seems to confirm this) However, the exported wav files show an extra(-1) at the end of the file name. In large export tasks this makes the label system unusable, as you have to rename manually each exported track. Any suggestions? See pics. Thanks!

... but still I have issues with the pointers in the Tempo View: Freehand Tool displays an arrow pointer (and Sonar creates an empty rectangle on the right) Line Tool creates an empty rectangle on the right Is this happening on your system as well? Thanks!