Mixer volume not honored upon initial loading of project

Hello again,

I finally got around to taking a closer look on this. The screenshot shows the mixer strip in question which is set at 78.7% as well as the UI of the Sherlock MID Inspector which I've added between the appropriate MIDI Bus and Instrument hosted within Carla. As we can see, there are no controller events sent before the NoteOn event.

Of course, now I understand why my "nudge hack" works. When I do that, it sends those controllers and my mix starts sounding like it should (one track at a time).

I have verified there are no events on this track other than the notes themselves and I am running version 0.9.23

All the best

bump

The update I posted on Aug 11

I'm not sure how this would lend itself to the scenario where the session (instruments and routing) are handled by Carla rather than Qtractor. Traditionally, I've loaded my Qtractor project first in order to create the ports. Then I load the corresponding .carxp file in Carla in order to load the instruments and connect everything.Based on what we're saying here, I now understand why those controllers being sent by Qtractor had no effect.

If I swap the work flow and load Carla first, I have instruments loaded and ports established but they're not routed (which makes sense since Qtractor is not open). Loading the Qtractor project results in the audio routes being established but not the MIDI.

So basically, it would appear as if the method by which these controllers are sent is really centered around the assumption that Qtractor is being used in a stand-alone fashion?

This seems like an obvious race condition here since both Carla and Qtractor are persisting state.

Opening Qtractor first could never result in everything being routed since the instruments (along with their midi and audio ports) don't yet exist. They won't exist until the appropriate .carxp session file is loaded in Carla. As such, loading the project in Qtractor only results in the internal audio routing being established.

On the other side of the equation, loading the Carla session first wouldn't work either since all the ports maintained by Qtractor don't exist yet.

So basically, it's a chicken/egg scenario.

Can this "send initial controllers" thing be broken out in some way as to allow the end user to drive it as needed? Anything would suffice, a button, a pull down menu option, anything.

All the best

I have no problem with sarcasm but this is a seriously lame response on so many levels. Not sure what you're so angry about but there's no reason to take it out on me or the software. All I did was point out an extremely valid use case (one I know you are quite familiar with) and show where an oversight exists. It's this kind of "my way or the highway" attitude that's kept Qtractor where it's at in my opinion and this is why adaption isn't improving. Rather than telling people to go !@%! themselves, how about a little gratitude for those of us who use it and take the time to point out where obvious improvements can be made? Especially something like this where nobody is asking for anything new to be created. Obviously the code already exists to "initialize" a project... the ask was to simply make it accessible. This also has nothing to do with Carla so I'm not sure what's triggering you there.... not sure I want to know actually. Whatever, it's your choice. You like this thing the way it is, fine by me. I won't bother letting you know where it can be improved going forward.

I do appreciate this and would certainly be willing to try anything that would help overcome the issue. I'm obviously a fan of this software and have always posted to this forum with the intentions of seeing it become more and more useful. I do realize this software has been in development for awhile as work-flows have evolved and changed. Hell, 20 years ago, I started using a MIDI sequencer to control everything externally (insert SYSEX message flashbacks here). Now, everything (and I mean everything!) is software. Believe me, I totally get it. As I re-entered the world of DAW all these years later on GNU/Linux, I went through all the obvious candidates such as Ardour, MuSE, and a few others. I found Qtractor to be the most usable and most functional Free Software solution by far and never looked back. You may remember Carl, who showed us his awesome work flow where all the instruments were basically outsourced to Carla via MIDI busses and AUX returns... That was a huge milestone in terms of getting a solid work flow in place; one that was both very flexible and very stable. Sure, there are some downsides in terms of additional tedious steps one has to go through when it comes to the frequent need to create and route new endpoints) but it's well worth it. At the end of the day, it's about being able to sit down and be creative with a set of tools we don't have to fight with. Again, I appreciate your work and have been trying to help in my own way by simply sharing a particular end-user perspective. It's all good.

Boom! This is working as expected (verified via Sherlock MIDI Inspector). Thank you very much. This is a great addition as it lends itself to a repeatable environment that matches the expectation of the user. The fact I no longer have to "nudge" things before getting back to work on a loaded session is a huge time saver but more importantly, it removes a silly ritual from my work flow. Thank you for this!

Sweet. I'll git pull and spend some time with it later tonight. Thanks again.