Thanks. I did have the localhost issue before but I'd already done that step as I had it in my set-up notes. In /etc/hosts, I have- 127.0.0.1 localhost 127.0.0.1 linux-wo40 ...which is what worked before. "linux-wo40" is the name given by "hostname" and is the default that was set on install. Does that look right? From looking back at that old thread I checked- jack-dssi-host /usr/lib64/dssi/fluidsynth-dssi.so and it was OK, so fluidsynth does appear to be working - it's just restoring Qtractor sessions...
Hang on loading projects (possible fluidsynth-dssi issue)
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
Manual - 5 Qtractor Menus
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Just tested in the latest build and all looks good. Thanks very much for the swift response :-)
scala kbm file import: Yoshimi ignores "A" Freq, "A" Note and Middle note values
Manual - 5 Qtractor Menus
How To - Sample MIDI Composition Workflow
Manual - 2 Installing and Configuring Qtractor
Manual - Table of Contents
Manual - Table of Contents
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
How To - Sample MIDI Composition Workflow
Manual - 4 Qtractor--An Overview
How To - Sample MIDI Composition Workflow
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Thanks very much for this. Have tested the new build and it looks good. In terms of the functionality this is very usable for me now, as I know how things work and what the limitations are, so even if Scales end up dropping down the to-do list (I imagine they're not important for the majority of people) it's no problem for me personally.
Thanks for the quick response. ISSUE 1 Thanks for the information. I'm not a developer so am not that familiar with the mechanisms involved. I've been regularly saving states after making changes to avoid losing work due to patches "randomly" (or so I thought) not restoring, but it seems this practice has actually been making things worse :-( Until this can be addressed (if it turns out to be possible), I'll have to avoid saving states in Yoshimi and just save them at the end of a project for archive...
Update to Bug 30 [LV2 plugin in Qtractor - state not saved correctly]
Manual - 4 Qtractor--An Overview
Thanks very much for the tips. That looks a much cleaner way of arranging things. I've also now removed all Program/Bank settings info from my standard Qtractor template (I had default info in there, which I think is what was throwing things off in the first place) so this issue hopefully shouldn't happen again. I imagine you can close this now, as it seems it might be covered by Bug 22? In any case, I'll leave that to you. Thanks again.
Thanks very much for the swift reply and also for your dedicated work on Yoshimi. It's much appreciated. The workaround would be fine for me as I don't use program changes. It seems generally to work, but when adding new instances in other tracks I encountered patches reverting. One thing I noticed is that, rather than selecting the patch straight after disabling program changes, it seems better to: 1) Add new Yoshimi instance; open Yoshimi [patch will default to Arpeggio1]; disable program changes...
LV2 plugin in Qtractor - state not saved correctly
How To - Set the number of channels an audio track records
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
How To - Sample MIDI Composition Workflow
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
Manual - 5 Qtractor Menus
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - Table of Contents
Manual - 3 Learning Qtractor--An Example Session
Manual - 3 Learning Qtractor--An Example Session
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Have tried various exports and haven't seen the message once, so it looks fixed/mitigated....
Great - glad you've been able to reproduce. I'm on Qt 5.5.0 here.
QObject message on session export: Cannot queue arguments of type 'QVector<int>'
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 1 Introduction
Manual - 2 Installing and Configuring Qtractor
Manual - 2 Installing and Configuring Qtractor
Manual - 2 Installing and Configuring Qtractor
Manual - 2 Installing and Configuring Qtractor
Manual - 2 Installing and Configuring Qtractor
Manual - 1 Introduction
Manual - 1 Introduction
Manual - 1 Introduction
Manual - 4 Qtractor--An Overview
Home
How To - Sample MIDI Composition Workflow
How To - Sample MIDI Composition Workflow
How To - Sample MIDI Composition Workflow
Manual - 4 Qtractor--An Overview
How To - Sample MIDI Composition Workflow
Manual - 4 Qtractor--An Overview
Manual - 5 Qtractor Menus
Manual - 4 Qtractor--An Overview
Oh, well. I suppose it can be closed then, unless you particularly want to keep it...
Yes, that's the menu. It happens 100% for me: start new session, no template create...
Sorry I didn't get time to check this before it was closed, but yes, it's still occurring...
Haven't seen it for a while, so it's probably OK to close. Thanks.
Manual - 4 Qtractor--An Overview
Manual - Table of Contents
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview
Manual - 4 Qtractor--An Overview