New script to build releases

[agittins]

setup.sh will build new template-archive files for direct importing into Ardour (fixing issue #5) and can be used for "localizing" the raw template to other machines or user accounts.

[johnjacobkenny]

Thank you so much for sharing the effort you have put in :smile:

I would like to try this out in practice, could you please guide me on how I can try this on my existing installation? Or maybe I should start from scratch, if so could you tell me what directories or files I should remove?

I'm fine with going either ways, just want it to work efficiently :smile: Also, are you able to get this to work with the performance scripts of VPO?

[agittins]

Also, are you able to get this to work with the performance scripts of VPO?

There shouldn't be any changes required in that regard, the PERF scripts seem to work fine.

could you please guide me on how I can try this on my existing installation?

The only thing to bear in mind is that if Ardour opens a template that has someone else's directories in it, the template will then be broken. In that case, delete the template and start over from Michael's version.

Put the setup.sh script in the same folder as your "Virtual Playing Orchestra" template folder. That is if you did an "ls -l" it would look like:

total 52
-rw-r--r--  1 agittins agittins 15997 Apr 26 05:51  license.txt
-rw-r--r--  1 agittins agittins  5136 Apr 26 08:12  readme.md
-rw-r--r--  1 agittins agittins  2411 Apr 26 05:51  seating.dia
-rw-r--r--  1 agittins agittins 12522 Apr 26 05:51  seating.png
-rwxr-xr-x  1 agittins agittins  2578 Apr 26 08:23  setup.sh
drwxr-xr-x 68 agittins agittins  4096 Apr 26 08:34 'Virtual Playing Orchestra'

The script will need to be executable, run chmod +x setup.sh if it isn't already (if you apply it from my pull request I think it will already be OK).

If you just run ./setup.sh it will give you the usage instructions:

Usage: ./setup.sh       [local|generic|build]

  build:
    This creates a new template archive that you can import directly
    into Ardour. (Look in the 'build' directory). This is very likely
    exactly what you want.
  local:
    update the template file with the full path on your local system.
    this may or may not be what you want.
  generic:
    updates the template with '' ready to be archived. This
    is even less likely to be what you want.

So to build a template archive directly from there, run ./setup.sh build. When it finishes you should find it inside the new "build" directory. The other options (local, generic) let you do the steps along the way, which may or may not be useful.

Does that cover it? Let me know if I've missed anything or if it's a bit unclear - or if it just works! Are you using linux? It will probably work on MacOS, but it won't work on Windows unless you have bash and sed available.

[johnjacobkenny]

I'm on linux.

I tried these steps

• downloaded your branch as a folder from github
• ran the script ./setup.sh build

Is this likely to work for Ardour 5 or should I use Ardour 6? For me on Ardour 5, that file isn't showing up

[johnjacobkenny]

After that I took this

and copied over to

This template works in that I can create a project, but the soundfonts are not auto linked, see below

Then I manually browsed to the file

[agittins]

Ahh... yes two things here, sorry.

For the template archive, it seems that ardour5 used to name them whatever.tar.xz, not whatever.ardour-template-archive.

If you copy or rename build/Virtual Playing Orchestra.ardour-template-archive to Virtual Playing Orchestra.tar.xz then ardour5 should be happy to import it.

The other thing is that if you want to just copy the template directory over, you can copy the setup.sh also into your templates directory, then (Before trying to load the template) run ./setup.sh localize from that directory. It will then fix the paths in the template, and when you load it it should load the sfz files. I think if you've already tried loading that template then ardour will have messed up the paths so you might need to copy a fresh version back over first.

I'll change the script so that it creates both filenames.

[johnjacobkenny]

I took the tar.xz version from https://github.com/agittins/virtual-playing-orchestra-ardour-template/releases/tag/2.0.0-RC3-ajg

It works correctly in that the font files are loaded from the correct path, and I am able to play the different instruments without fiddling with anything really. Thanks! :smile:

This might sound funny, but Ardour is crashing when I play the Tubular Bells, specifically the note A - below middle C (A3) :sweat_smile: I'm using my Yamaha Keyboard as the input, using a2jmidid to get it to be recognized in Jack. This has been my setup since the beginning, and this is the first time that Ardour has crashed.

Any idea what's going on? WIth the track midi editor and sfizz midi keyboard, there are no crashes, and all the other instruments seem to be working as expected (and not crashing) with that A note.

[agittins]

Ha! I found the exact same thing a week or so ago. I just haven't got around to analysing the issue and filing a bug report yet. Pretty sure it's an issue with sfizz itself, crashing when it sees something odd in the vpo sfz file.

Thanks to your inspiration, I've raised a bug for it against sfizz :-) https://github.com/sfztools/sfizz/issues/215

Very glad that the template worked for you!