Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Can't load patch
Last post Tue, Jul 22 2008 by Conquer, 12 replies.
Options
Go to last post
Posted on Fri, Jul 18 2008 19:03
by elsner
Joined on Tue, Jan 01 2008, Posts 8

Hello, I'm using Appassionata Strings (extended) with Cubase4 and WinXP.  Sometimes it happens in the middle of a project that I can't load patches anymore: during "drag and drop" comes the "not-allowed-sign" (a barred O). Double-clicking instead of dragging doesn't work either.  This happens with all patches, even the empty patch is not allowed to load.

It can't be the RAM since it's a single patch (1x1 matrix) in the whole instrument, and when I remove the instrument and open it again, then it works, but it's a waste of time and I loose many presets. 

Of course I tried to expand the 1x1 matrix in order to get a 2x1or 1x2 matrix and then put my patch into the matrix position  --  but the matrix seems to be "locked" the dimension 1x1, it can't be extended.  When I overwrite my "locked matrix" with the empty matrix, still no other patch can be loaded.

Who knows help?

Posted on Sat, Jul 19 2008 09:20
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

Hi elsner. I run Appassionata Strings extended on a standalone VI with WinXP and have not encountered this problem. I don't use Cubase so may not be able to help, but next time you encounter the problem please tell me the name of the matrix in question and I'll look at it on my system.

elsner wrote:
Of course I tried to expand the 1x1 matrix in order to get a 2x1or 1x2 matrix and then put my patch into the matrix position  --  but the matrix seems to be "locked" the dimension 1x1, it can't be extended.
That sounds like a bug. You're doing this on the 'Patch Assign' page, right?

Posted on Sat, Jul 19 2008 09:28
by elsner
Joined on Tue, Jan 01 2008, Posts 8
Conquer wrote:

You're doing this on the 'Patch Assign' page, right?

Yes. The 1x1 matrix is A1. It seems like a bug to me too, because when I delete the instrument and then create it again, all works fine, until the bug occurs another time.

Posted on Sat, Jul 19 2008 09:43
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

I see - is the 1-cell matrix something you created from scratch, or did you edit a VSL matrix?

Posted on Sat, Jul 19 2008 09:50
by elsner
Joined on Tue, Jan 01 2008, Posts 8

The 1x1 matrix into which I load is the default empty matrix whenI open the instrument first.

It happens like that : while composing I load a patch to try it out, then I replace it by another patch, and again another, and so forth, and suddenly it gets locked.

Posted on Sat, Jul 19 2008 09:57
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

OK - as you say, you're only using one patch at a time so you shouldn't be running out of RAM. Have you tried opening the VI standalone outside Cubase to see whether the same problem occurs?

Posted on Sat, Jul 19 2008 10:14
by elsner
Joined on Tue, Jan 01 2008, Posts 8

No, I have never opened a standalone of an VST-Instrument (I even don't know how I should manage the connection with my sound card).

Of course my RAM is also used by other instances, so theoretically it could be the RAM.  But I don't belive it since the empty patch can't be loaded too and since the matrix is locked to its size.  These things don't have anything to do with the RAM.

Posted on Sat, Jul 19 2008 10:34
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

If you look inside the Vienna Instruments folder on your PC hard drive you'll see a program called ViennaInstruments.exe. Clicking on that opens the standalone player. Hooking it up to your sound card is easy - once you've launched the standalone VI, select Options -> Configure (top left on the UI) and select your sound card and MIDI interface from the menu that appears. This selection won't affect the running of the VI in Cubase.

It's best to open the standalone with no other programs running. It takes time to load (maybe 2-3 minutes), after which you'll see the same interface on screen that you're used to working with in Cubase. The advantage of doing this is that you'll be able to establish whether the bug has anything to do with Cubase!

elsner wrote:
Of course my RAM is also used by other instances, so theoretically it could be the RAM.  But I don't belive it since the empty patch can't be loaded too and since the matrix is locked to its size. 

I agree, but to be absolutely sure it's not a RAM issue you should test it using a single instance.

Posted on Tue, Jul 22 2008 08:09
by elsner
Joined on Tue, Jan 01 2008, Posts 8

 I opened the standalone.  It seems to work fine, at least during the minutes I tried...

Posted on Tue, Jul 22 2008 08:19
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

Great - if the problem never occurs with the standalone VI, you'll then know it's likely to be a Cubase issue.

Posted on Tue, Jul 22 2008 08:40
by elsner
Joined on Tue, Jan 01 2008, Posts 8

 

Conquer wrote:

Great - if the problem never, you'll then know it's likely to be a Cubase issue.

I don't know that it NEVER occurs with the standalone VI since I didn't spend much time on the standalone.  And it doesn't happen all the time within Cubase.

Posted on Tue, Jul 22 2008 10:19
by Conquer
Joined on Thu, Sep 28 2006, Posts 812

Those intermittent faults are the worst. Good luck with discovering the cause!Geeked

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.