|
 Kyma Forum
 Kyma Support
 AU Plug-Ins to access kyma?
|
| next newest topic | next oldest topic |
| Author | Topic: AU Plug-Ins to access kyma? |
|
Denis Goekdag Member |
posted 30 November 2012 07:23
 
Hi, just wondering whether there is any news on the AU plug-ins that are supposed to tunnel audio to and from Kyma? Best, IP: Logged |
|
Denis Goekdag Member |
posted 26 March 2013 21:49
*bump* :-) IP: Logged |
|
SSC Administrator |
posted 26 March 2013 22:35
We've decided to take a different approach. More soon... IP: Logged |
|
oivindi Member |
posted 19 April 2013 15:49
This certainly made me curious! IP: Logged |
|
Kyle Hughes Member |
posted 26 April 2013 11:37
I think we're all tingling with excitement to find out! Ah... I know it was bad.  IP: Logged |
|
Denis Goekdag Member |
posted 30 April 2013 04:42
Bring on Kyma XI! ;-) IP: Logged |
|
SeanFlannery Member |
posted 03 May 2013 23:43
Rewire? That would be pretty damn awesome  IP: Logged |
|
Douglas Kraul Member |
posted 04 May 2013 06:53
quote: ReWire would be a nice way to integrate MIDI to Kyma and audio from Kyma. Unfortunately ReWire hosts cannot send audio to a ReWire "slave" so Kyma could not be used as an effects processor. IP: Logged |
|
SeanFlannery Member |
posted 05 May 2013 06:27
I wasn't aware of that aspect Douglas, kinda shoots that approach down in flames eh?  Oh well. IP: Logged |
|
Douglas Kraul Member |
posted 05 May 2013 10:29
quote: Oh I still think the idea has a lot of merit, even with that restriction. It could certainly be put to good use when using Kyma as a sound source (like a synth) instead of a processor. ReWire is usually very well integrated in a DAW, to the point that it makes the ReWire instrument behave almost like a plugin. Kyma is currently not too bad to integrate if you follow a hardware approach, and that is not too far fetched for most set ups because there are always two soundcards involved, one dedicated to the Pacarana, and one to the host computer/DAW. Like I am sure many other users, in our studio the Pacarana has a multichannel soundcard whose ADAT I/O is connected to ADAT I/O on the computer's soundcard. So we have the equivalent of multiple sends and receives from whatever DAW we use. Some DAWs, like Ableton and Logic, go one step further to help hide the complexity with "device" plugins. But even without that you can usually "tease" the DAW into an expectable level of integration. Its just tends to be a bit fiddly. IP: Logged |
|
armand Member |
posted 05 May 2013 14:28
The hardware approach works perfect for me: Apple Logic Pro DAW It's almost latency free! The only limitation is 44.1 kHz! The Capybara 320 runs immediately out of realtime at 96 kHz, even on my fully loaded system... IP: Logged |
|
oivindi Member |
posted 07 May 2013 11:25
I'm thinking it's probably the stand-alone version of Kyma, that can run on any PC or Mac. It's called Kyma XXX. Ok, probably not. IP: Logged |
|
ChristianSchloesser Member |
posted 08 May 2013 15:42
i would like a simple virtual audio driver via firewire for os x with 8 Kyma ins/outs... IP: Logged |
|
Douglas Kraul Member |
posted 09 May 2013 06:32
quote: Agreed! Its one of the Capybara/Flame features I miss the most. Extra credit if the virtual audio drive lets you use the Paca(rana) without a dedicated soundcard. That would simplify set up in the studio IP: Logged |
|
ChristianSchloesser Member |
posted 09 May 2013 10:27
quote: Yes. For me...a "must have feature" Maybe the only thing why i get frustrated about Kyma. I don t mind having my TC Konnekt 48 in the studio... but if i travel i really would like to programm Kyma and monitor/mix the 8 Channels through my DAW without connecting the extra stuff. I have often ideas on the road "Outside" my studio ...then i have to "fall back" to more conventional solutions via reaktor or maxMsp... which i recognize is not good for my work-flow. IP: Logged |
|
Denis Goekdag Member |
posted 18 May 2013 16:34
While I wouldn't exactly *mind* that functionality, it's not something I would use. I have a regular DAW I/O setup that hooks up all sorts of speakers and outboard, based on two ULN-8. The Pacarana is hooked up using a TC interface...now why would I want to use the TC and lose all the I/O I otherwise use? I do see the rationale for small setups or when travelling though. ReWire I haven't really had good experiences with in terms of performance, but that may be down to the implementation of some of the apps that use it. The route of having a *plug-in* inside the host that tunnels audio/MIDI/OSC to and from the Pacarana opens up another plus: saving the Pacarana sound with the host session, so you wouldn't need to load the Sound into the Pacarana separately when recalling a session. Loading stuff into various pieces of hardware is one thing I really do NOT miss from ye olden days ("Now WHERE was that MOD for the AKAI S3000 again, and what was that preset in the Lexicon called again...")....;-) IP: Logged |
|
wallerian Member |
posted 19 May 2013 00:30
I know the vst wrappers for rtas and au don't currently work with vst3 plugins, but I personally would be very happy with the flexibility that something like the vst 3.5 specification would give. (Besides it's also supported on Mac AND Windows, unlike AU plugins) From Steinberg: "Among the novelties of VST 3.5 Note Expression will most likely be of highest interest for virtual instrument enthusiasts. With Note Expression, each individual note (event) in a polyphonic arrangement can contain extensive articulation information, which creates unparalleled flexibility and a much more natural feel of playing." "VST 3.5 also provides a new, XML-based controller interface, allowing plug-in parameters to be exported, structured and grouped, which is beneficial in case of remote control. A more precise description of parameters is also possible." Cheers IP: Logged |
|
Douglas Kraul Member |
posted 19 May 2013 06:20
quote: If the plugin route is to be taken then you realistically have to support at least VST, AudioUnits, and AAX (RTAS replacement). Otherwise you end up excluding some very large segments of the user base, and the whole "wrapper" work around can be its own support nightmare. Also while something like VST 3.5 has desirable new facilities it could be some time before it is supported by every VST-capable host. We are still waiting on universal 64-bit DAW support after a number of years. Industry-wide DAW improvements tend to move glacially. By the way the XML description of plugin parameters while a nice new addition really does not bring much new to the party. Each plugin standard has provided a means for a host to interrogate the plugin for its parameters, value ranges, and value units for a good while now. In fact Audio Units have had a very complete facility since version 1. The problem is that a facility such as XML parameter description is only useful to a plugin host. So in the end the DAW itself has to do something with it to make something like an OSC control surface possible. At this stage of the game every DAW is already deeply invested in the way of doing control surface support. Its unlikely an improvement in the plugin spec is going to impact that in the near term. I am personally a big fan of the notion of a "Kyma Plugin" with all the benefits others have mentioned. But its is a substantial undertaking to develop such a plugin that requires a deep understanding of not only all plugin architectures, but also all the subtle differences between host implementations. To me this implies trading off Symbolic Sound's focus on this verses focus on other Kyma enhancements. IP: Logged |
|
wallerian Member |
posted 19 May 2013 14:59
Totally agree, Douglas. The plugin route is a very busy one. Besides, SSC have already stated that they have "decided to take a different approach". I guess the most realistic way for doing this without getting sucked into the world of eternally adjusting to other companies multiple specs would be the firewire driver route (ins/outs for MIDI, OSC, audio and what not). Add me to the list of those who can't wait for this to finally happen (on OSX of course AND Windows). IP: Logged |
|
Kyle Hughes Member |
posted 19 May 2013 20:43
Yes... It may not be the most practical route, but a "Kyma Runtime" plugin might be interesting, where one can compile and play sounds already created in Kyma- something that speaks directly to the hardware, but does not modify the sound loaded. This way, the capybara/pacarana still does the processing; the plugin gives instruction and then receives the resulting audio stream to the track its on in a DAW. IP: Logged |
|
tompty Member |
posted 21 May 2013 08:02
I would be interested in helping out create a VST/AU etc for this purpose if a few of us got together on it. IP: Logged |
|
ChristianSchloesser Member |
posted 21 May 2013 17:57
If the firewire connection of the pacarana would be used like an additional audiointerface then every software which is able to use multiple audio interfaces would be able to send audio to and receive audio from the pacarana. (on Mac OS X using multiple Interfaces is possible via the OS aggregated devices even if the application is not able to do that like Ableton for example) Additionally i would to like have the ability to host the Kyma Application inside an AU and a VST ... to save a Kyma session or timeline within my DAW Project ;-) my 5 cent have a nice day p.s.: I used "Plugin based" solutions like Audioport Universal and Audio over Lan to network multiple Macs/PCs and i was never really happy with that... [This message has been edited by ChristianSchloesser (edited 22 May 2013).] IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
  |
|
Contact Us | Symbolic Sound Home
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.
Ultimate Bulletin Board 5.45c