MuTools

pljones · Post by **pljones** » Wed Sep 20, 2006 9:19 pm

muzycian wrote:Can you check forcing RAM samples, i.e. disable Kontakt's DFD.

At the weekend I'll try some more stuff using Kontakt generally. (ns_kit7 full is very demanding - I'm not sure it'll all load into RAM...)

jpumphandle · Post by **jpumphandle** » Wed Sep 20, 2006 10:38 pm

Here's a link to a crash description (CMUSIC).
http://tech.groups.yahoo.com/group/Musi ... ssage/2940

Easily duplicated crash. Two instances of a large plugin caused a crash. This could be memory related. Maybe it is related to some of the above?

guitarfrodo · Post by **guitarfrodo** » Wed Sep 20, 2006 10:39 pm

Jo and or Supersonic, Hope this explains things: try to import a 5 minute audio at 80 BPM in 4:4 time = 100 measures. First pass gets 32 bars. The audio is truncated at 32 bars when you expand the session to 48 bars by zooming out.

Import again gets another truncated audio at 48 bars. Zoom out expands to 72 bars, import, expand, etc til the whole 100 bars is allowed.

This of course could be saved as a template eg. 'long audio import' session but...

Sequencing is not so much a problem as Supersonic and Drenholm mention as the sequence can be expanded within the editor as much as is needed.

I hope this explains it, I may be missing something.

Drenholm · Post by **Drenholm** » Thu Sep 21, 2006 10:13 am

Well, here, Supersonic's solution works: draw the longest part you can, import the audio, zoom out as far as possible, use the pencil tool to expand the part's length, zoom out and repeat as necessary.

For me, increasing the track's length works and the audio from the file is present and correct. I hope this helps.

Supersonic1 · Post by **Supersonic1** » Thu Sep 21, 2006 11:11 am

Just a thought Guitarfrodo.

You need to drag the audio part from just before the end of the last visible bar. If you try and drag from the first half of the last visible bar, it will move the whole part. If you try and drag from after the last visible bar, it thinks you want to create a new audio part.

You probably realise this already, but it works for me. I just tried with an 8 minute audio file - all was fine.

muzycian · Post by **muzycian** » Fri Sep 22, 2006 3:27 pm

jpumphandle wrote:Here's a link to a crash description (CMUSIC).
http://tech.groups.yahoo.com/group/Musi ... ssage/2940

Easily duplicated crash. Two instances of a large plugin caused a crash. This could be memory related. Maybe it is related to some of the above?

I've tried Abakos, and here it crashes even when scanning.

I'll email hercsmusicsystems about this.

Thanks for reporting!

muzycian · Post by **muzycian** » Fri Sep 22, 2006 3:35 pm

Drenholm wrote:Well, here, Supersonic's solution works: draw the longest part you can, import the audio, zoom out as far as possible, use the pencil tool to expand the part's length, zoom out and repeat as necessary.

For me, increasing the track's length works and the audio from the file is present and correct. I hope this helps.

Yes, this is the way it currently works.

pljones · Post by **pljones** » Sun Sep 24, 2006 7:58 am

Jo, have you got VST3 on the radar?

muzycian · Post by **muzycian** » Sun Sep 24, 2006 10:03 am

Yes, i read the news.

Why do you ask?

pljones · Post by **pljones** » Sun Sep 24, 2006 1:16 pm

The changes sound good to have, particularly stuff like resizable windows and reconfigurable numbers of outputs - both of which would benefit Kontakt2... and hence I'd be after support in LUNA

.

pljones · Post by **pljones** » Sun Sep 24, 2006 1:53 pm

pljones wrote:
muzycian wrote:Can you check forcing RAM samples, i.e. disable Kontakt's DFD.
At the weekend I'll try some more stuff using Kontakt generally. (ns_kit7 full is very demanding - I'm not sure it'll all load into RAM...)

It appears to be one hihat (nki) that's causing the problem. Even on its own in a new session. Mmm, so I guess it's K2!

muzycian · Post by **muzycian** » Sun Sep 24, 2006 7:37 pm

pljones wrote:The changes sound good to have, particularly stuff like resizable windows and reconfigurable numbers of outputs - both of which would benefit Kontakt2... and hence I'd be after support in LUNA .

Yes it sounds like an important update.

muzycian · Post by **muzycian** » Sun Sep 24, 2006 7:39 pm

pljones wrote:
pljones wrote:
muzycian wrote:Can you check forcing RAM samples, i.e. disable Kontakt's DFD.
At the weekend I'll try some more stuff using Kontakt generally. (ns_kit7 full is very demanding - I'm not sure it'll all load into RAM...)
It appears to be one hihat (nki) that's causing the problem. Even on its own in a new session. Mmm, so I guess it's K2!

How does that go in other hots?

What does NI say about this?

pljones · Post by **pljones** » Sun Sep 24, 2006 10:02 pm

muzycian wrote:How does that go in other hots?
What does NI say about this?

There are other hosts..?

Like I said, same problem in Muzys. I've not got any other hosts installed currently. I could dig out some demos.

NI... well... I've not been on to their forums yet... I always get a bad feeling about going there...

Either during the week or next weekend I'll dig more. If I can pin anything more down to the instrument in question, I'll post over on natural-studio, too, to see if anyone there has any similar experiences. (I know both K2 and Hal3 have their problems...)

muzycian · Post by **muzycian** » Sat Sep 30, 2006 8:31 pm

muzycian wrote:
jpumphandle wrote:Here's a link to a crash description (CMUSIC).
http://tech.groups.yahoo.com/group/Musi ... ssage/2940

Easily duplicated crash. Two instances of a large plugin caused a crash. This could be memory related. Maybe it is related to some of the above?
I've tried Abakos, and here it crashes even when scanning.

I'll email hercsmusicsystems about this.

Thanks for reporting!

I've been communicating with Steve and Robert of HERCs Music Systems, and the issue has been resolved.

One of the days, they will publish a new version of Abakos

MuTools

KVR Audio

LUNA PreRelease 3