Couple of Rhapsody Questions

[iamlamprey]

• Does the Plugin Code need to be unique for each Instrument?
• Does the Bundle Identifier need to be unique for each Instrument?
• Can the Name parameter under Project Settings have a "-" in it without issues?
• Do I need to setup any of the User Settings like Company, Company Code etc?
• Are there any known issues with exporting the Instrument with Enable Loris checked?

I assume these properties are of no real significance since David skimmed over them in the video, but just want to double check

Thanks in advance!

[d.healey]

Does the Plugin Code need to be unique for each Instrument?

No it's not used, however if you ever want to compile your project to a plugin you'll need to set it to something unique.

Does the Bundle Identifier need to be unique for each Instrument?

Same as the plugin code

Can the Name parameter under Project Settings have a "-" in it without issues?

If HISE accepts it then it should be fine I think. Let me know if you notice an issue.

Do I need to setup any of the User Settings like Company, Company Code etc?

I think it's a good idea to set these. They aren't used currently but I think the next version of the Rhapsody boilerplate will include an about page that will pull some data from here.

Are there any known issues with exporting the Instrument with Enable Loris checked?

I don't think Rhapsody has been compiled with Loris so I expect the instrument wouldn't work properly. But let me know. For the next release of Rhapsody I can include Loris - however I'm also planning to add an AAX version of Rhapsody and this won't include Loris due to licensing (I might send the authors a message and see if I can get a proprietary license if they're willing and it's not too expensive).

[iamlamprey]

@d-healey said:

If HISE accepts it then it should be fine I think. Let me know if you notice an issue.

This seems to work just fine so far.

I think it's a good idea to set these. They aren't used currently but I think the next version of the Rhapsody boilerplate will include an about page that will pull some data from here.

Roger that! Will the new boilerplate break instruments made with the previous version?

I don't think Rhapsody has been compiled with Loris so I expect the instrument wouldn't work properly. But let me know.

So far in preliminary testing it's working just fine, the actual instrument isn't using any Loris methods, it's just enabled in HISE

I'm also planning to add an AAX version of Rhapsody

Very exciting, as much as I hate protools it's still quite a popular DAW

[d.healey]

@iamlamprey said in Couple of Rhapsody Questions:

Roger that! Will the new boilerplate break instruments made with the previous version?

Yes, I make no attempt for backwards compatibility (ok that's not quite true, but I don't worry about it if I break it). However it only affects a project if you choose to update the boilerplate, there is no reason you can't stay on the previous version for existing projects. Also if you're just using the Rhapsody template and not the full boilerplate with the additional includes and modules it probably won't cause any issues (or it will be minimal).

@iamlamprey said in Couple of Rhapsody Questions:

the actual instrument isn't using any Loris methods

Then there should be no issues.

@iamlamprey said in Couple of Rhapsody Questions:

Very exciting, as much as I hate protools it's still quite a popular DAW

Yup I have no love for it either, but it seems like there is enough demand.