F.J. Lamela

Aqui te muestro el problema que he explicado.He creado un multi con 3 sonidos cada uno ruteado a la salida A,B,C,D... Como veras una pista en sonar donde esta encaminada la salida A de Omnisphere, todo bien.Pero cuando encamino la Salida B, tambien sigue sonando en la B lo que solo tendria que sonar en la Salida A.Cuando ruteo la primera pista hacia la salida B, deja de sonar en la B incuso estando routeada en sonar.Fijate en el video y te agradeceria si puedes chequeases lo que aparece en el video. Here's the problem I explained.I created a multi-track with three sounds, each routed to outputs A, B, C, and D.As you can see, a track in Sonar is routed to output A of Omnisphere, and everything is fine.But when I route output B, it also continues to play in output B, even though it should only play in output A.When I route the first track to output B, it stops playing in output B, even though it's routed in Sonar. Please watch the video, and I would appreciate it if you could check what's shown.

Mi configuración es igual a la tuya, luego postearé un video donde se puede comprobar el problema. Gracias de nuevo.

Hola Andrés, si hablo Español. He reconfigurado O3 varias veces, he hecho diferentes pruebas pero por el momento no consigo que se activen todas las salidas. Imagino que es algun tipo de bug que tiene el plugin, ya que la version anterior no daba ningun problema y logicamente ,el funcionamiento de la ultima version,no difiere absolutamente nada en ese respecto. Te agradezco tu ayuda igualmente, me pondré en contacto con el soporte de Spectrasonics para ver si hay alguna actualizacion en camino. Gracias

opsss, sorry for my english. Is not a hardware amplifier....sorry (LOL) i wanna mean , i have a Omnishpere multi (with independent audio outputs a,b,c,d,e,...) that works ok in omnisphere 2 and sonarworks but, when i swith with omnisphere 3, the same multi dont send audio to bus D,E,F... only A &B, i've checked all and omnisphere 3 dont send audio to these outputs, i dont know if a problem with omnisphere or Sonar.

Thanks Andres. I've checked everything and it's correctly connected. It's a multi-channel amplifier that works fine in version 2, but when I switched to version 3, it doesn't send a signal to outputs D, E, F... Thanks anyway.

Thanks for your recommendation, they've been thoroughly checked. Also, since it's "backward compatible" with projects that previously used version 2, the projects don't work correctly when loaded; as I mentioned, the multiple outputs don't work.

Hello, I've been using Omnisphere 2 for years and never had a problem. After updating to version 3, I'm encountering an issue with Omnisphere's multi-outputs. To explain, the synth has 8 independent outputs (A, B, C, D, E, F, G, H), but unfortunately, only output A is working. The rest show a signal in the plugin, but the sound doesn't reach Sonar. I've tested it in another DAW, and it works perfectly. Can anyone confirm this or has anyone experienced a similar problem? Thanks.

Greetings. I've had several different monitor sets. NS-10, Alesis Monitor One MK2, Auratones, Yamaha MSP7, and finally, Neumann KH150. The truth is that they're very flat, very neutral nearfield monitors, with very powerful bass for their size and good transients. Are they better than the ones you currently have? Technically, YES. Are they better for you than the ones you currently have? I don't know. I can tell you that, as a user of the Neumann range, the entire line is very, very neutral, a far cry from the ADAMs. Perhaps at first, they may seem a bit dull, but they don't boost or emphasize anything that isn't in the mix. (Isn't that what we want from a studio monitor?) For the size of your room, I would even recommend the KH120II, because, as I said, they might fit better. Likewise, buying these monitors indirectly involves purchasing the MA1 monitor alignment kit. They "manage" to mask some serious room problems, mainly peaks, which are recorded within each monitor, without the need for programs like SoundID or ARC within the DAW. I don't know if my explanation will help you. P.S.: Speaking of ADAM, the new line has improved a lot compared to the previous one. But having a ribbon tweeter, it has that characteristic sound that you either love or hate. It also doesn't have Neumann's level of precision. If you have the chance, listen to them in person with some tracks you know very well.

I have downloaded your project and tested it. I cannot reproduce the bug. Automation works correctly in the VST3 version of serum. Regards.

Thanks. I've looked at all the local help and the pdf document. Either I'm really dumb or I can't see anything related to creating new patterns.

Greetings. While I have no complaints about the operation of the arpeggiator (midi), there is something I don't quite understand. How is it possible that I can't find a way to create new patterns and add them to the existing ones? It would be logical that from the step sequencer it could be exported as a pattern for the arpeggiator, or failing that add some option to be able to add new content. If you are forced to use only the default patterns of the internal arpeggiator and to create new ones you are forced to use an external arpeggiator (blue arp for example) then the included arpeggiator would not make much sense. Is my deduction correct or am I wrong and is there a way without the need for third party software to add new patterns to the existing ones? Thanks and sorry for my english.

It's a shame can't change it, thank you!

I mean slope of spectrum view, no for band. Sorry for my english.

Greetings. Is there any way to change the spectrum view slope in the equalizer? Currently it is 0 but most of us work in 3db/oct and more commonly in 4.5 db/oct. Commercial equalizers have the ability to modify this slope and I would like to know if there is any way to modify it in sonar via aud.ini or similar. Thanks.

Thanks for the tip, but in my opinion its interface and workflow are a bit outdated. I think that by bringing ideas that are already implemented in other DAWs, CakewalkSonar can be competitive among other DAWs. Staying stuck in 10-year-old technology and plug-ins without improving the workflow is nonsense in these competitive times. I believe that a picture is worth a thousand words.