Yoshimi LV2 patches not restoring

Submitted by yuba on
Forums
qtractor

I've been using yoshimi as an LV2 plugin successfully for the last couple of years but have run into a problem this week - the patch settings are not restoring correctly when I use my standard template. The attached qtzs both have the first 3 tracks set to Bass/Bass 1, Bass/Bass 2 and Bass/Bass 3 (analog), as you can see in the qts's. However, they behave differently.

Test_YoshRestore.qtz
This was created from a bare file and restores correctly.

Test_YoshRestoreTemplate.qtz
This uses my standard template. On loading, only Track 1's patch restores; both Track 2 and Track 3 default to arpeggio1, the first patch in the list (your version of yoshimi may have different patches though).

Is something in my template causing a conflict? I've been trying to track down the cause of this (creating new yoshimi instances, as opposed to dragging/dropping between tracks; using different MIDI channels (have had problems with other LV2 plugins previously); resetting yoshimi's default patch directory etc.) but it seems to be something in the template. I've been using various versions of the template for a long time with no such problems.

I'm running Qtractor 0.8.0 (though the problem happened on versions from a couple of weeks ago) and Yoshimi 1.3.9M (which has been fine up until this week).

Thanks as ever.

Subscribe to this forum topic

Submitted by rncbc on Tue, 22 Nov 2016 - 16:25

Permalink

i see.

somehow your template sets PC#1 (MIDI channel program change #1) on almost every MIDI track in place.

now that's really interesting because yoshimi does support MIDI bank/program changes "by nature & standard" (my own wordings:)), as most full-fledged MIDI instruments in the world that stands for that name. too bad that the LV2 plug-in spec is still falling short on that front.

anyway, check that on your original template that every MIDI track is set for Instrument="(no instrument)", Bank="(none)" and most importantly, Program="(none)". note that you'll have to do it at the former or original template level.

thereafter, i guess and hope, things will work just as well :)

hth.
cheers

Add new comment

The content of this field is kept private and will not be shown publicly.
About text formats

Markdown

  • Parses markdown and converts it to HTML.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id> <img src alt height width> <strike> <pre> <p> <br>
  • Lines and paragraphs break automatically.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <b> <i> <pre> <img src alt height width> <strike>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
File attachments
Unlimited number of files can be uploaded to this field.
2 MB limit.
Allowed types: jpg jpeg gif png txt doc docx xls xlsx pdf ppt pps odt ods odp zip gz bz2 xz patch diff wav ogg flac ogv mp4 qtz.
CAPTCHA
Image CAPTCHA
Get new captcha!
Enter the characters shown in the image.