Hi,
I installed the new built over my last version of Cantabile Lite 64 on my Vista64 Notebook with 4 gig RAM. It seems, that things have changed a lot. I was used to play my Eastwest Ql Steinway (two perspectives) without any problems with the 64bit version of cantabile. Now trying to load, it takes hours and at the end it indicates over 2,7 gigs of ram used, in some cases (reloading) over 3 gig. That were formerly only a bit over 2 gigs. For playing it safe, I tried the same with the old 32bit version and here everything seems to be as it was: About 2,17 gigs of RAM use.
Has anyone an explication for this changed behavior?
Best,
Johannes
Bug with new built?
-
- KVRian
- 791 posts since 8 Mar, 2006 from Australia
Hi Johannes,
Sorry to hear your having these difficulties.
I can't think of any changes specific to x64 in the last build. Could you please let me know which build you were using previously so that I can perhaps narrow it down a little. If it helps, I can organize a copy of a previous build for you - just let me know which.
Also, could you confirm whether this occurs when loading a session, loading a fresh instance of the plugin or both.
Unfortunately I don't currently have this plugin so I'm unable to test it myself.
Brad
Sorry to hear your having these difficulties.
I can't think of any changes specific to x64 in the last build. Could you please let me know which build you were using previously so that I can perhaps narrow it down a little. If it helps, I can organize a copy of a previous build for you - just let me know which.
Also, could you confirm whether this occurs when loading a session, loading a fresh instance of the plugin or both.
Unfortunately I don't currently have this plugin so I'm unable to test it myself.
Brad
-
- KVRer
- Topic Starter
- 20 posts since 6 Oct, 2004
Hi Brad,
I always took the latest build, so it should have been 2010.
It occurs both loading a session and loading the plug in newly.
Btw: Play, the engine of QL Pianos, is known to be a little demanding for the hardware. But it was fine before. And I had no issues with dropouts and so on after playing for an hour or so like in the 32bit version (which also appears, using it in other hosts like Samplitude Pro). But loading forever and consuming nearly a gig more RAM is a real fun killer.
Apart from that, I'm looking forward to the final release of version 2. When will it be approximately? Will there be a vsti-version too, so you could load complete sessions in an DAW for instance? That would be great!
Best,
Johannes
I always took the latest build, so it should have been 2010.
It occurs both loading a session and loading the plug in newly.
Btw: Play, the engine of QL Pianos, is known to be a little demanding for the hardware. But it was fine before. And I had no issues with dropouts and so on after playing for an hour or so like in the 32bit version (which also appears, using it in other hosts like Samplitude Pro). But loading forever and consuming nearly a gig more RAM is a real fun killer.
Apart from that, I'm looking forward to the final release of version 2. When will it be approximately? Will there be a vsti-version too, so you could load complete sessions in an DAW for instance? That would be great!
Best,
Johannes
-
- KVRian
- 791 posts since 8 Mar, 2006 from Australia
I've made build 2010 available again here:
Cantabile Lite 32 bit
Cantabile Lite 64 bit
Would you mind reinstalling 2010 and confirming the problem goes away. I've double checked all changes between 2010 and 2011 and can't see anything that would explain what you've described.
Cantabile Lite 32 bit
Cantabile Lite 64 bit
Would you mind reinstalling 2010 and confirming the problem goes away. I've double checked all changes between 2010 and 2011 and can't see anything that would explain what you've described.
Last edited by bradr on Tue Feb 10, 2009 2:42 am, edited 1 time in total.
-
- KVRian
- 791 posts since 8 Mar, 2006 from Australia
Sorry about that, looks like it's the forum putting spaces in there. Try copying it to you web browser's address bar and removing the obviously wrong spaces.JoPiano wrote:I'm sorry, but the second link doesn't seem to work.
Btw: Thanks for your effort!
Johannes
EDIT: Actually, I think I figured out how to get around the forum corrupting it, try the above links now.
-
- KVRer
- Topic Starter
- 20 posts since 6 Oct, 2004
Thanks, Brad.
Now I have the next problem: I cannot install the older version. Even after uninstalling those I get the error message: "The development build of cantabile has expired. Please visit the homepage..."
Do you have some advice?
Best,
Johannes
Now I have the next problem: I cannot install the older version. Even after uninstalling those I get the error message: "The development build of cantabile has expired. Please visit the homepage..."
Do you have some advice?
Best,
Johannes
-
- KVRian
- 791 posts since 8 Mar, 2006 from Australia
Oh, sorry.
If you just want to test the previous build the easiest way will be to set the date on your machine back (say 1 month). (FYI: the reason for this expiration is to prevent possibly buggy betas from remaining "out in the wild". When officially released, the builds will _not_ expire like this).
I've been wondering whether this could just have been a problem with the last build. The next build should be available in a day or two.
Brad
If you just want to test the previous build the easiest way will be to set the date on your machine back (say 1 month). (FYI: the reason for this expiration is to prevent possibly buggy betas from remaining "out in the wild". When officially released, the builds will _not_ expire like this).
I've been wondering whether this could just have been a problem with the last build. The next build should be available in a day or two.
Brad
-
- KVRer
- Topic Starter
- 20 posts since 6 Oct, 2004
Thanks again.
Something different came to my mind: I think, I installed the latest version of asio4all (2.9) the other day. Do you think, this could have to do with my problem?
Looking forward to the next build.
Johannes
Something different came to my mind: I think, I installed the latest version of asio4all (2.9) the other day. Do you think, this could have to do with my problem?
Looking forward to the next build.
Johannes
-
- KVRer
- Topic Starter
- 20 posts since 6 Oct, 2004
Hello again,
I think, I found the solution: There was an update for the play-engine recently. This must have reset the buffer settings for the disk-streaming, but apparently only for the 64bit version. So this one loaded a much larger portion of each sample into ram, than the same vsti (only in 32bit) with the same session in cantabile 32. Strange, but now everything works as before.
Again thank you for your helpfulness!
Have a nice day,
Johannes
I think, I found the solution: There was an update for the play-engine recently. This must have reset the buffer settings for the disk-streaming, but apparently only for the 64bit version. So this one loaded a much larger portion of each sample into ram, than the same vsti (only in 32bit) with the same session in cantabile 32. Strange, but now everything works as before.
Again thank you for your helpfulness!
Have a nice day,
Johannes