You are here

Some thoughts with regard to your Q*stuff workshop @ LAC2014

Hi Rui,

As discussed at your workshop:
* Possibility to enter automation values manually for example by right-clicking an an automation point/square.
* Possiblity to automate/MIDI control activating/deactivating plugins.

It would be helpful if the automation values are the same as the actual values, for example when automating Gain and then setting a value of 0.5 I fail do to the maths to calculate this value to the dB value. Really, I s**k at maths. But I reckon this could be quite some work to get right.

And I'll try to create a qtz that will allow you to reproduce Qtractor crashing when the number of channels of a bus changes or if you change to a bus within a track that has more than 2 channels or if you change back from a bus with more than two channels to a bus with 2 or less channels.

And I'm having issues with my BCF2000 recently and I don't recall having them before. When I have a project with both audio and MIDI tracks and I change the gain on say audiotrack 1 then also the MIDI volume of a MIDI track that has channel 1 changes. Same for the other way around, so if I change the volume on MIDI channel 1 the gain of audiotrack 1 changes too. Would it be possible to 'separate' MIDI tracks from the MIDI Control input/output?

Bye,

Jeremy

Forums: 
rncbc's picture

hi Jeremy,

thanks for recalling the requests about automation (entering direct values and plugin activation); both are now in the "soonish" queue ;)

about separating MIDI tracks from the MIDI control input/output, i fail to understand it in full. does it still happen when having dedicated MIDI control input/output ports and you connect the BCF2000 through it? otoh. which qtractor version? prior to v0.6.0 there was this bleending effect that was fixed on v0.6.1 and might just be the symptom your're telling, but it could be something else.

cheers

rncbc's picture

re.Possiblity to automate/MIDI control activating/deactivating plugins.

done. as of svn trunk rev.3831 aka. qtractor v0.6.1.3, commit log:

  • MIDI Controller assignment (aka MIDI learn) and/or automation of plugins (de)activation state has been added (as requested by AutoStatic aka. Jeremy Jongepier, thanks). (EXPERIMENTAL)

cheers

AutoStatic's picture

Awesome! Thanks. I'll look into the BCF2000 issue this weekend and report back.

rncbc's picture

re. Possibility to enter automation values manually for example by right-clicking an an automation point/square.

done, only that's double-clicking; as of svn trunk rev.3849 aka. qtractor v0.6.1.11, commit log:

  • Discrete automation curve node values may now be edited via a numerical entry floating spin-box on double-click (as yet another request by AutoStatic aka. Jeremy Jongepier, thanks). (EXPERIMENTAL)

cheers

ps. well, still have to do the maths though ;) but every1 knows that 0dB is 1.0, then -3dB is 0.5 and 0.25 is -6dB and so on... :P

AutoStatic's picture

Awesome, going to check it out! Thanks!

Add new comment