|
|
|
04-10-2015, 01:53 AM
|
#1
|
Human being with feelings
Join Date: Jan 2011
Location: Zürich
Posts: 1,008
|
Enable midi monitoring without rec button
As it says. If a midi input is chosen, and input monitoring is enabled, it should do just that, enable midi input to that track.
Recording enable should also do just that : enable recording
|
|
|
04-10-2015, 04:05 AM
|
#2
|
Human being with feelings
Join Date: Jul 2009
Location: Ljubljana, Slovenia
Posts: 3,801
|
|
|
|
04-10-2015, 05:44 AM
|
#3
|
Human being with feelings
Join Date: Jan 2011
Location: Zürich
Posts: 1,008
|
Take it as a bump, I do not want to wait another 5 years ....
|
|
|
04-10-2015, 06:00 AM
|
#4
|
Human being with feelings
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
|
I couldn't agree more - and have already voted in 2009.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
|
|
|
04-14-2015, 03:35 PM
|
#5
|
Human being with feelings
Join Date: Dec 2012
Location: Germany
Posts: 3,015
|
The same applies to audio tracks. "Record: disable (input monitoring only)" is a usable workaround, though. I think that's why the devs are not looking into this issue at the moment.
|
|
|
04-14-2015, 05:06 PM
|
#6
|
Human being with feelings
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
|
We currently have everything in place for track arming to work correctly, logically and as one might expect, but still it doesn't. Here's how it could:
1. The current Arm button is now REDUNDANT. Whatever it's doing on a code level, Cockos should simply turn it on permanently. It's required for monitoring and recording, and we have extra options for both of those! There is no advantage I am aware of with being able to turn that on and off. It's just a needless extra step.
2. Create a new version of the new workaround action "set track record mode to none" that toggles between 'record: none' and 'record: input or output' (whichever the user had chosen).
3. Assign this action to the arm button and now track arming will work like it does in any other DAW, without extra steps or confusion. This way, arming a track would simply enable recording, turning on monitoring would work independently and things are suddenly simple, easy and conform to universal standards.
4. In a nutshell: recording and monitoring are dependent on track arming. Track arming does nothing but enable those functions to work. Therefore track arming never needs to be off, doesn't need to be an option and the function corresponding button should be replaced by the appropriate action (toggle record enable).
I hope I'm not wasting my time trying to make this clear. All the elements are there, it just needs a bit of reconfiguring.
|
|
|
04-14-2015, 05:56 PM
|
#7
|
Human being with feelings
Join Date: Dec 2012
Location: Germany
Posts: 3,015
|
Quote:
Originally Posted by foxAsteria
All the elements are there, it just needs a bit of reconfiguring.
|
Best words to describe this DAW!
|
|
|
04-14-2015, 06:03 PM
|
#8
|
Human being with feelings
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
|
Quote:
Originally Posted by SonicAxiom
Best words to describe this DAW!
|
haha, right? i've been "reconfiguring" steadily for 5 years+. now i'm learning ReaScript and WALTER...it never ends!
|
|
|
04-14-2015, 06:17 PM
|
#9
|
Human being with feelings
Join Date: Dec 2012
Location: Germany
Posts: 3,015
|
Tweaking this DAW easily fritters away more of my time than producing. But it's fun
|
|
|
04-14-2015, 06:27 PM
|
#10
|
Human being with feelings
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
|
it's pretty worthwhile, if you already know how you want to work. my workflow is as smooth and fast as any i've seen. and yea i love tweaking shit as well...
and the faster you are, the more you can get out of inspiration. in all other daws i would constantly hit inspiration-destroying roadblocks. obstacles are pretty rare now.
|
|
|
04-14-2015, 06:47 PM
|
#11
|
Human being with feelings
Join Date: Dec 2012
Location: Germany
Posts: 3,015
|
have been working with Qbase for 15 years: no tweaking, no options, no workflow, no fun, no nuthin'. Came to Reaper in 2011: rocket-speed-workflow, flexibility (notion never associated with Qbace), forgot how to even spell this Qbass thing; and after a while I got into tweaking Reaper ... and never stopped since. Paradoxically, Reaper triggers a constant urge to speed up a lightspeed app. Who knows why?
|
|
|
04-14-2015, 06:58 PM
|
#12
|
Human being with feelings
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
|
haha! i only spent 3 years with cubase. don't miss a single thing. least of all spending an hour+ to install the bloated beast. get what you pay for? not even close. unless you like to pay for headaches.
|
|
|
04-14-2015, 07:02 PM
|
#13
|
Human being with feelings
Join Date: Dec 2012
Location: Germany
Posts: 3,015
|
you're so right
|
|
|
04-14-2015, 09:12 PM
|
#14
|
Human being with feelings
Join Date: Jan 2011
Location: Zürich
Posts: 1,008
|
Before we end up in praising reaper and its reconfigurability....
... And forget about solving the problem.
... because we already know how to to, we do not have to start doing it....
@Foxasteria: very clever approach. Although I would prefer to have it solved in the code, not in an external script.
How do we make sure that this script is not only part of the install/download, but also that it is automatically installed / bound to the actions ?
And how do we provide visual feedback, because the red light should stay off if the track is monitoring only.?
And ... Who should write that script ?
Last edited by Mink99; 04-14-2015 at 09:19 PM.
|
|
|
04-14-2015, 10:12 PM
|
#15
|
Human being with feelings
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
|
@mink99
Unfortunately, I don't think it can be solved via script. I didn't mean to imply that that and sorry for the tangent.
All I meant was that everything is already there to have this work, if only Cockos would reathink the approach. I thought it could be done through WALTER, but we cannot change what the buttons do. That has to be on a code level.
Since the devs gave us that workaround (disable record), it shows that it's fundamentally possible and that the old arm button is something of a relic. They simply didn't take it that next step. Not sure why, because clearly it's just a matter of changing what the Arm button does and removing the option for what it currently does.
I guess the option doesn't need to be removed, but certain removed from the track panel; I can't think of any situation it would be useful.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 10:12 PM.
|