Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
Posted: Thu May 21, 2009 10:00 am Post subject:
Thanks guys.
I actually did it wearing headphones early this morning, doesn't sound as good through the speakers thats for sure. When I first heard it through my speakers I thought something was wrong with them, very weird!
Its a factory patch with me running stuff from Live into it, I didn't touch the patch. I will have a look in a minute to see if I can work out what it does.
Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
Posted: Thu May 21, 2009 10:16 pm Post subject:
Muied Lumens wrote:
That sounds pretty radical in headphones!
So what's going on in there? Can you give a rough outline?
Ok I have had a look at the patch.
The left channel of the input audio is split into two paths.
Each path goes through a LowShelf and HighShelf filter and then a compressor.
Each then goes to a REResonator which is a time varying filter whose coefficients have been derived by analysing a audio file with the RE Analysis tool in Kyma.
RE stands for resonator/exciter so basically the analysed audio is the resonator and the input audio is the exciter. The resonator audio is the words you can hear.
These signals then go into a DynamicRangeController which is a compressor/expander and then are mixed into stereo.
Hope this makes sense!
I have included a simple audio example, first is the unprocessed drum track and then the processed audio.
I talked to Carla yesterday. She said that a Paca was 75% of a loaded Capy. She also mentioned it could be a little more then that as there were not as many processors involved as with a Capy.
I will upgrade within the year, my budget right now does not allow it!
Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
Posted: Fri May 22, 2009 10:20 am Post subject:
The CPU.
It doesn't handle it well either, first you get an overload message, then a firewire error and you have to reset the DSP from within Kyma to get it back!
So maybe a bug? I'm not sure as I have only just started playing with the Spectral stuff.
Joined: Jun 04, 2009 Posts: 5 Location: Minneapolis, MN
Posted: Thu Jul 02, 2009 5:45 pm Post subject:
BobTheDog wrote:
The CPU.
It doesn't handle it well either, first you get an overload message, then a firewire error and you have to reset the DSP from within Kyma to get it back!
So maybe a bug? I'm not sure as I have only just started playing with the Spectral stuff.
I have encountered the same thing, but I am a rookie at the Kyma. I know you can set DSP allocation in these situations using a prototype that achieves this goal.
There are a couple particular things that trigger DSP allocation issues. One is feedback loops where you read and write things in a loop. This has to be on 1 processor if using the memory writer, so watch out for that. There are a few tricks around it though if you come across that. If you are running into this issue often, feel free to ask the SSC forum. If you post an example, I am sure people will be more than happy to propose solutions.
It seems that the Pacarana also has an issue with a few modules during the port over to the new hardware. In particular, the CrossFilter_long with the setting to maximum causes problems. Just defining the impulse length fixes that issue.
Re: the overload. The Pacarana is much, much less graceful than the Capybara was. SSC indicates that is being worked on so I suspect it should sort out in due time.
there was a new update today that may help with 'firewire robustness'. this may help with some of the resetting issues. i've also wondered if the amount of IO I have hanging off the macpro is also causing some level of trouble. Apple is known to have some problems with the built in fw bus. i just order a new Sonnet FW800 card as I could use the ports anyway. i'll post if that seems to help at all.
also, a mere 6 days after request there is a new feature to support shutdown hardware upon exit. i love how faster SSC turns around little request like those.
These guys do a lot of performance testing and the interesting part is here.
"Apple continues to produce Macs with FireWire 800 ports, but they always share the same single data channel/controller with the FireWire 400 and USB 2.0 ports. Why is that an issue? For one thing, we've experienced some strange slowdowns in FireWire 800 devices when FireWire 400 devices are added to the mix. And they continue to run slowly until you disconnect the FireWire 400 device and Restart the Mac Pro. "
So I used Sonnet cards in the past with great success, so ordering a Tango Express 800 to get some more reliable and fast ports.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum