|
From: Anthony K. <mai...@an...> - 2008-11-11 20:42:24
|
Rainer Schuetz wrote on 11/11/08 8:36 AM: > the new UB starts up well now and I can compile the project without > error (426 warnings, the resulting "release" file has exactly the same > size as the one you posted). Thanks for checking that it compiles for someone other than me! The warnings are expected. The debug target gives a couple thousand of them :) Someday, when I have nothing better to do, I will work on reducing the number of warnings ... > I can playback the -gr.Mozart with simple Synth. Fantastique! It seems the Intel half is working better than I expected. > I was not able to run the checkall script, but that may well be due to > my ignorance. I tried to "load" the script-file. *After* the script > was loaded (the text appeared in the windows) a second 'open-file'- > dialogue would pop up. Thanks for trying to run the script. The duplicate open file dialog is a bug that I also see. > If I cancel that and press 'check script' > another dialogue pops up asking for a file I am not able to identify. Right. The purpose of 'check script' is to verify the syntax of the script and to verify the locations of any files that the script will need to load. Whenever a BP2 script is moved to a new computer, the locations of the dependent files will be different. All of the files that this script asks for are somewhere in the "data" directory. I suggest that you don't worry about running the checkall script. It takes a _very_ long time (20-30 min) and makes a lot of strange noises ;-) I'm sure that Bernard will run it on an Intel machine when he has a chance. > One more thing: BP2 still eats a lot of recourses although doing > nothing at times. About 1 Min after starting the program BP2 eats > about 90% of processor time and the fans howl :) Ah yes, I still have not done anything about this. Since you are the second person to complain about BP2 causing excessive fan activity, I think that I should probably try to resolve the excessive CPU use problem. (My fans don't go crazy here even though I am using a PowerMac G4 "windtunnel" machine). I know what causes BP2 to use nearly all of the CPU time, and there are two possible remedies: a) a simple patch that still uses "ancient" Mac Toolbox calls to get user events but may reduce the CPU usage somewhat, or if that is not enough, b) a complete rewrite and modernization of BP2's event handling code. The latter would be a good idea anyways, but would be time consuming, so I will try the easy option first. Thanks again for your help!! Anthony |
