Rhapsody 2.3.3 problem

[ospfeigrp]

When i load my .lwz file it takes about 15-20 seconds to actually launch and no feedback is given that it is loading. it does eventually load and all works but one could be mistaken and click something else as the spinner wont show and other instruments are clickable causing the player to crash

[d.healey]

@ospfeigrp If I remember correctly the spinner is triggered by the loading callback and I think this doesn't actually kick in until after the expansion has loaded. I should be able to get the spinner to run in Rhapsody as soon as the expansion is clicked, which will prevent others being clicked, but I'll need to test.

15-20 seconds is a long time. Does that happen also with Bell & Bone on your system or just your expansion?

[ospfeigrp]

@d-healey Hi David i just downloaded bell and bone and it loads no problem without delay my other instruments load fine just seems to be the one i am working on has about 600 mb compressed samples as well as multi samplers in the instrument. My broadband is very poor here unfortunately but i can tether my phone and upload you the files to test yourself.

[ospfeigrp]

@d-healey heres the onedrive download https://1drv.ms/u/s!ApAv4TfgiZ-Tnkt5Fj6b2r3Svjed?e=agImSs

Also when offloading kill all notes is needed to prevent crash

[d.healey]

@ospfeigrp said in Rhapsody 2.3.3 problem:

Also when offloading kill all notes

Ah interesting. I got a crash too when exiting. I'll add this in the next build.

Your expansion took about 2-5 seconds to open for me. The instrument sounds very nice. Since you haven't added any scripting the only thing I can think that is slowing the load for you is the background image which is about 3mb, I haven't used any images in Bell & Bone so perhaps that's why it loads a little faster. An easy test will be to remove the image and see how long it takes to load.

[ospfeigrp]

@d-healey Thanks David, the loading times are not a major problem just would be nice to show spinner so users can't click again. As far as the crash on offload adding this to expansion.js seems to solve the problem

thanks again.