Testers Needed for Rhapsody v3
-
@Bart I don't usually add effects to my plugins unless for very specific use cases. Your DAW probably has a filter already.
I'll check out the keyswitch issue now.
-
Was assuming the other controls aren't meant to be working yet.. but then your first message here is stating the plugin is 'ready'.
Regarding the Dynamics knob, the Vibrato and Effects knobs - they're not working while in Performance state.
-
@Bart said in Testers Needed for Rhapsody v3:
Regarding the Dynamics knob, the Vibrato and Effects knobs - they're not working while in Performance state.
By not working do you mean the controls are disabled or that they are not having an effect on the sound?
Is this in the plugin/standalone or both?
-
@David-Healey said in Testers Needed for Rhapsody v3:
@Bart said in Testers Needed for Rhapsody v3:
Regarding the Dynamics knob, the Vibrato and Effects knobs - they're not working while in Performance state.
By not working do you mean the controls are disabled or that they are not having an effect on the sound?
Is this in the plugin/standalone or both?
Oh no wait, they are working.. they didn't seem to be sounding before, maybe it was related to the keyswitch issue somehow, or I just wasn't hearing them clearly.
Only testing with VST.
-
@Bart Actually I can confirm the dynamics knob isn't working. I've fixed that now though. Looking into the keyswitch issue, I can recreate it in Reaper, but it works in Ardour and within HISE, so I'm going to try and track down what's causing it.
-
The key switches are neither working when exporting to audio file, even if the plugin is open and in focus at time of export.. but this will likely fix itself when you patch it up.
Sounds nice, but stuck on Staccatissimo here

-
@Bart I've been down a little rabbit hole today with global cables, the articulation switching should work now
https://e.pcloud.link/publink/show?code=XZm4ycZWRIqN1pUCPmGxb4Vxktn7LJfhul7
-
Someone mentioned that the unload button (the little grid icon) wasn't very intuitive and something like a back arrow might work better.
Any thoughts on this?


Or this?

-
@David-Healey I like the first option icon. What if you put that icon where you're placing the arrows so that it implies "going back to library"?
-
I feel that is less intuitive, it starts to look like a logo. But you like the original with it next to the settings icon?

-
@David-Healey It does confuse with the logo looking at it now. I guess where you had it was good. For sure I like this icon better than the arrows because for me it says "library".
-
@David-Healey said in Testers Needed for Rhapsody v3:
@Bart I've been down a little rabbit hole today with global cables, the articulation switching should work now
https://e.pcloud.link/publink/show?code=XZm4ycZWRIqN1pUCPmGxb4Vxktn7LJfhul7
Did you intend to link the sample pack again, or meant to be a patched app update?
Within 10 seconds of unloading the sample pack Rhapsody crashes FL Studio consistently.
Maybe place the library icon on the left side of the preset header, possibly with a gap.
That's where I'd expect to access it, yet I'm not familiar with sample based plugins. -
@David-Healey Of the left-edge arrows, I prefer the one with the tail. Seems fairly obvious what it does when you see it. But it's also easy to miss in the UI because it's separated from the preset browser.
Maybe a different icon in place of the grid, next to the preset browser?
I know this is usually 'upload' but if you have an 'Unload' tooltip on hover it might be clear enough.

Also, if the Unload button is near the preset browser, I think it should be right next to it instead of the settings icon.
As a user, I might also expect to be able to click on the expansion name to load a different one, or get back to the library.
But on the whole, if the action of the button is to take you back to the library so you load another expansion, then the left-edge arrow button is probably best.
-
@Bart said in Testers Needed for Rhapsody v3:
Within 10 seconds of unloading the sample pack Rhapsody crashes FL Studio consistently.
What are the steps to recreate the crash?
@Bart said in Testers Needed for Rhapsody v3:
Did you intend to link the sample pack again, or meant to be a patched app update?
Yes, a limitation of the hr format is you can't really do partial patches.
-
@David-Healey said in Testers Needed for Rhapsody v3:
What are the steps to recreate the crash?
It was happening by simply unloading the pack / click unload button and accept.
Trying it now has inconsistent results..
Sometimes can't get the sample pack to reload at all after unload.Try unload | reload.
Move some controls.
Toggle play stop.
Crashing randomly doing these now.Unload seems like the culprit.
Haven't noticed crash without unloading first.
Doesn't necessarily have to be reloaded to get crashes. -
H HISEnberg referenced this topic
-
-
@Bart I only have the free trial of FL Studio and can't figure out the UI. But when I drag Rhapsody into the place it seems to want to go I get this.

-
@Bart Aha I figured it out (watched a YouTube tutorial).
I'm able to load/unload the instrument multiple times without any issue.
Which OS are you using?
Which version of FL Studio?
Which CPU?
Are you testing in a new empty project?I've updated the Rhapsody build with a couple of tweaks, let me know if that improves the crashing issue.
https://e.pcloud.link/publink/show?code=XZt75cZ38LCNl1BtXVrWXQ3s1xTDH4vfpLV
-
Windows 11 25H2
Build 26200.8457
Intel i7-11800H 2.30GHzFL beta from 2 months ago
I'll get the new beta and test it later todayIt doesn't matter if new project or not, was consistently crashing with method stated.
-
I've completely uninstalled Rhapsody and the sample pack, then reinstalled new versions, also installed latest FL Studio beta.. unfortunately seeing the same crashes 10 seconds after unload.
The 10 second delay between unload and crash might be a clue, but sometimes it takes changing something in the plugin or DAW after unload to see the crash.
Key switches are working

They also working now when triggering sequenced key switch notes and melody notes @ same time.. before your fix the key switch notes had to be placed before the melody notes.
