![]() ![]() I think qmidiroute will do it, or amidimap if ubuntu has packages for it.Īnother way is to install the x42 plugins (they're great) and use the "MIDI CC Map" plugin - you set the input controller number to map, and set what it should output as. If you have one, you could remap it to cc#1 using your keyboard's config (if it supports it) or by using software on your PC. Since you're an organist, do you have an expression pedal? Expression will usually be cc#7 (main volume) or cc#11 (expression). This is especially audible for the brass presets, as you can play a note starting soft, then with the modwheel change it to forte, which blends in the loud samples so that you get a smooth transition. Yes, the PERF versions of the sfz instruments typically map their dynamics to the modulation wheel, which is midi controller cc#1. Right now what would be great is if someone can put an archive version of the template into the releases area in github so users can easily download it, and update the readme accordingly. This is one of the things that the script attached above is able to do. copy the template, replace all occurances of the local template path in the xml session file with $TEMPLATEDIR, and archive it as above.choose "Export All", unpack the resulting archive, remove the unwanted preset directories, and re-archive it (with tar -cvJf name.ardour-template-archive templates/template-name) OR.I've raised a feature request for ardour to include a button to export a single template (since currently only "Export All" is available), but until then one can either: This also means that we could package templates with a version number in them (so users can try out multiple versions) or users can freely rename templates themselves if they want to keep their known-good option before committing to a new version.įor the development side of things, it's only slightly more complicated. I've tested this and it works well, paths get fixed automatically and it doesn't clobber existing templates unless they have the same name. So for distributing templates to end-users, the "right"(?) way to do it is to package them as a template archive (this is simply an xz-compressed tar archive, named something.ardour-template-archive), and users should install them through "Window", "Templates", "Import". What doesn't work is just copying the templates manually from one place to another. This works really well, if you use that as a means for moving templates around. When Ardour imports templates, it does the reverse, replacing $TEMPLATEDIR with the local user's template directory. When you export templates from Ardour (Window, Templates), it replaces the paths in the presets with "$TEMPLATEDIR". ![]() While the issue is indeed caused by the way Ardour stores paths in its templates, it's not really a bug in Ardour, but rather a change required in how people share Ardour templates, and a lacking feature in how Ardour manages template archives. Which reminds me, I completely forgot to describe here what's actually going on! Just as a workaround until Ardour implements a fix. ![]() Since the template needs to have VPO installed in a specific path anyway (ie, there are "manual" installation steps required), would it be helpful to create a script that automagically munges the filepath? It could also do a quick file check to ensure that it finds VPO in /opt as well. home/agittins/.config/ardour6/templates/Virtual Playing Orchestra Users/michaelwillis/Library/Preferences/Ardour5/templates/Virtual Playing Orchestra So on my system, my templates are in /home/agittins/.config/ardour6/templates, so I open up /home/agittins/.config/ardour6/templates/Virtual Playing Orchestra/Virtual Playing Orchestra.template and change every occurrence of: If you've already used the template it will have borked up the state settings, so delete it and re-install the template, then edit the file. I've raised a bugreport for Ardour at for this, as I think it's a bug in how Ardour implements templates.Īs a workaround, I seem to be having success by editing the template (before first use!) and changing Michael's template directory to mine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |