Jump to content

winkpain

Members
  • Content Count

    428
  • Joined

  • Last visited

Everything posted by winkpain

  1. Yes, it is in this way that I wished to use it (Input Gain control) with a Patch Point, as a summing gain for controlling recording level in certain instances. What is odd is that, in the Signal Flow diagram, it shows patch points and soft synths as flowing into the Input Gain as opposed to hardware inputs falling after it. But again, where does the tape/track lie in that chart when it's in record mode? My upper red arrow, right? (but with the hardware input flowing through it as well)
  2. Where exactly in the signal flow should we consider a live audio source (from hardware input, soft synth, or patch point in the image) to be "printed to tape", so to speak, onto it's track? Would it be at the point of the upper red arrow in the image below , or the lower one? It seems to be the upper one. This always causes a bit of confusion for me, as the "Input Gain" that falls between those two points doesn't effect what gets live recorded, either from a hardware input or soft synth (being recorded live) or patch point. Or should we rather think of live input during recording as falling outside of this flow, going directly from the audio card (in the case of hardware input) to the tape (or track in CbB) ? The confusion for me is "Input Gain" makes me think gain on an input (live input) like a pre-amp , but it's really gain on the "input" from tape (track) which, to me, is more of an "output". Clarifications?
  3. Thanks. Yes, that is the manual I have, and it really does not go into any detail about virtual ports and their specific purposes. I do not use Automap as it has been discontinued and never really worked anyway. The new firmware instigated the HUI protocol, and I believe it was after updating that that I first saw the "MIDIIN 3" added to the ports which started getting me curious. I just figured it would be nice to know exactly what these ports are for. They obviously are necessary, but I'm just flying with them blind.
  4. Right. I see that, but that's for setting up in Cubase of course. Cakewalk doesn't get a mention in the manual. And in Cakewalk they are simply listed as MIDIIN2, etc. and the manual doesn't go on to say what specifically they are for, why 3 and then 2, etc.. Perhaps it is obvious to many, but this is a realm where my knowledge is a bit more basic. I'll just leave everything as is.
  5. I'm definitely using it as a control surface in addition to the note input. And it's working that way now, so I'll just leave it be. Was just wanting to know more. Did you happen to notice what page/chapter those virtual ports are discussed? The HUI functioning is something that was just added in a firmware update that I just did the other day, so just got the updated manual were it discusses that a bit, but I don't see where it discusses the virtual ports or the difference between #2 and #3, for example.
  6. Unfortunately, I cannot find any information in the Impulse manual about how these virtual ports are purposed. Regarding MIDI ports, it only speaks of the physical USB or DIN MIDI ports. Virtual ports are not mentioned at all. In general 'tho, is there ever a reason to call on these ports (in a setting) by name other than having them checked "on" in Preferences/MIDI devices? This latter is all I do and if I do not, the controller functions do not work, but as I say, within the controller plugin's Preferences window (as well as anywhere else where I want to connect the keyboard/controller), I only ever have the first of the three ports chosen. Is this always the appropriate protocol?
  7. I realize that I have never understood exactly what the "MIDIIN 2" and "MIDIOUT 2" (with varying numbers and the name of my keyboard in parentheses after them). They are "virtual MIDI ports", I know, but exactly when and which ones do I use and for what, or do I? In my case at the moment and for example, for the available MIDI ports associated with my Novation Impulse keyboard I have (in Preferences/MIDI devices): In ports - Impulse, MIDIIN 2 (Impulse), MIDIIN 3 (Impulse) Out ports - Impulse, MIDIOUT 2 (Impulse) I have them checked "on" in Preferences/MIDI Devices, but nowhere else do I have them selected. Not in any tracks' MIDI ports settings, nor in the Preferences/Control surfaces ports settings (Here I have just "Impulse" for in and out ports in the AZController plugin that I use for this keyboard ). I know I have to have them checked "on" in Preferences/MIDI Devices for the faders, knobs, transport, etc. of my keyboard to work, but I've never really understood the which, when, and wherefore of it all. Why, for example are there 3 in ports but only two out ports? What exactly do the different numbered ones do? If there is more than one numbered virtual port (as is my case with the "Ins" ), which is which and how do I know? When, if ever, should I be choosing one of these numbered MIDI ports by name in a setting? Lot's of questions, but they are all kind of the same one. I am not suffering anything not working with any of it (at the moment!), but I would love to know more in order to understand more better 🙄
  8. For some reason, I would always have problems when going backwards to fill in a new beat before one already set. Now, when testing it doesn't seem that way. Good to know.
  9. Using SetMeasure/Beat at Now is the most straightforward way. Focus on the track with the obvious on-beat transients, go (with cursor and with Snap off) to first audio beat where you know what beat you want it to be (bar 2, beat 1 for example), choose SetMeasure/Beat at Now for that beat setting (bar 2, beat 1). Do that for the next bar, beat 1, and the next and next - if the tempo strays that much at every bar, or do it every 8 bars or whatever. (You must do it in an orderly and consecutive fashion, tho - you can't go backwards after setting a beat at Now and re-set a previous beat, in other words.) This is my "brute force" method. But from what I remember, the Mike's (CreativeSauce) tempo mapping video shows it pretty spot on without any stretching of audio. I actually had some posts on my working out of this issue which combines the CreativeSauce advice with the Melodyne drag-and-drop technique which you can read here - scroll down to near the bottom, a Jan 7 post by me that begins with "Ah hah!" for a description of what I do. In addition, I have great luck with Melodyne stand-alone which has the precise method you desire of dragging the measure/beat lines to match the actual played audio beats, if needed, but Melodyne does an excellent job of mapping tempo just by itself, I find. From there you can then export the tempo map and open in a blank CW project. But the above methods (brute force and combo) are the quickest in my experience within CW.
  10. .... I just sent in a Support request on this as well.
  11. And on that note, @David Baay, could you put up a link to your post on the old forum for curiosity and comparison? Is it still available?
  12. These are all excellent points. And I was coming just back on board to do something along the lines of "re-pinging" the issue, as it is, in fact, quite an annoying one. I have found that the odd behavior noted above leaves behind curious "remnants" that cause confusion. In my examples with grouping the Mute functions as seen in the second video, I have found that, going back into the project where I first noticed the problem, tracks that I had been working with in the manner shown have remained mysteriously muted without any indication on the track's Mute button. This is likely (I guess?) related to the Mute buttons not responding correctly as you see in the second video in that, maybe tracks are being muted without the indicator on the track showing it. I don't know. But I found that toggling the master Mute button on/off in the control bar would relieve it, although...not consistently. Suffice it to say, there is something very weird going on when grouping Instrument Tracks that warrants looking into.
  13. Wow! OK. Perhaps it was an issue when Instrument Tracks came in that never got ironed out? If it's been 5 years, I guess it's not on the table, then. Good to know about, at least.
  14. Further evidence: The Group function works as expected with Audio or MIDI only tracks. So, the issue is only with the special combo "Instrument" tracks, and no matter what virtual instrument they are connected to.
  15. Same thing. It perhaps showed as an "existing" group in video because I had sampled the scenario a few times. But Starting a new empty project, setting up as seen in video, choosing New Group, etc. all behaves in this same odd and incorrect way. I noticed it when working on a project and wanting to set up this grouped Mute toggle situation, but I have now tested it with, as I say, new projects, closed and re-opened, rolled-back to previous version, and re-installed current version. It is consistently f***ed up in all scenarios.
  16. There is something very obviously not right here! I am noticing some very odd behavior in grouping controls. I see it in the current release and tried rolling back to previous release and found it to be the case there as well. A quick description of examples and videos: I have several tracks that I want to toggle the alternating Mute states of in an "A-B" manner, so grouping the Mute buttons is in order. I mute every other track, then do a CTRL-A, select All, and CTRL-click any of the tracks' Mute buttons in the "Quick Group" manner and get the expected behavior, both in Track View and in Console View. This is shown in the "Working correctly" video. Next, I set the tracks up similarly with alternate tracks muted, do a CTRL-A select All, CTRL-right click and Group all the Mute buttons with a group letter and color (not Quick Group, in other words). After doing this, I expect that clicking any of the now grouped Mute buttons will have the effect of the toggling achieved in the previous arrangement. This is not what happens as you can see in the "NOT Working correctly" video. On the contrary, none of the Mute buttons work in the expected way except the last one (I have tried with different numbers of tracks, and it is always only the last track that works as the group toggle), and that is only the case in Track View. In Console View it's all very, very...odd. I show this in the video by clicking on each of the Mute buttons in both views, and well, you can see what happens. (In addition, at the end trying a CTRL-right click and "Remove from group" with all tracks selected does not function as expected here.) This is, for sure, not right. Quick Grouping works for my toggling purposes at the moment, but why this behavior with "permanent" grouping?? Surely there is something wrong...
  17. I am liking the Tempo Track addition! Couple questions, 'tho: Is there currently a toggle setting somewhere to select tempo changes with clip (for copies or moves) such as there are with envelopes and articulations? This can be done with a "Copy/Paste Special...", I know, but curious if there is a quick toggle option to lock/associate tempos to clips. and Is there a way to select multiple tempo changes and collectively alter their curve type to a preferred one? Or a way to set the default curve to something other than Jump?
  18. Interesting that you should have just asked that as well! I have never had the need until just now. Of course the multiple clips can be added to multiple lanes within one track, but they all start at the same time. So not the answer to our question/request. Nor is it a very likely oft-desired scenario: multiple clips all on top of one another on the same track. (?)
  19. Is there a way to drag many multiple selected clips from the Media Browser pane into a single track so that the clips insert themselves one after the other at their clip boundaries on that single track?
  20. I have found, over years of trying to decipher the Key Bindings settings, that it is best to: save/export your current settings so that they are easily retrievable (with an import) Choose "Zap all..." to return to only the default bindings which show as bold text in the key pane then attempt to troubleshoot creating just your one desired custom binding to see if that works in your desired instance Although it says in the manual that you can reassign defaults to your preferred binding, I have found this to not necessarily be the case, or not to work as expected. And I can't quite figure out why exactly it isn't the case when it isn't. But zapping all and starting fresh from the ground up is a way of figuring some things out that you can then hope to incorporate into your custom bindings file (that you exported/imported). The functioning of these bindings settings is somewhat opaque in my opinion. For example, the asterisks that appear next to custom bindings are sometimes black, sometimes red, apparently to indicate something. What that is, I dunno. It is not mentioned anywhere in the documentation (as far as I can tell). It is true that you can have the same keystrokes assigned to multiple functions in different "Areas", as well as in addition to their default assignments. So, it all can end up being a bit of a confusing mess if you are a customs bindings junky like myself. I spoke of it in another post from a while before - if you care to see more there, scroll the the Aug 30, 2019 entry and read a bit from there. If there is newer, more enlightening information, I would love to hear it as well! Anyway, this maybe doesn't help, just spreading the information.
  21. @Matt Dunn - just curious as I have been dealing with this too. Do you notice a difference if, leaving your Auto save time setting as it is, you set the changes setting to 0 as opposed to the maximum number of changes? (which is what exactly?)
  22. I too am seeing this. And the inconsistencies propagate with successive drag/move actions.
  23. My issue was insurmountable. Weeks of troubleshooting with two separate Tascam units and popping problems all over the place. I am convinced there is something wrong with the driver. I outlined it all here as well. The Tascams are returned and out of my life for good, I'm sorry to say (for Tascam), and now I'm the happy owner of a new Focusrite 8i6 which plugged in, loaded up, and worked like a charm within the first minutes and on! It is such a pleasure to just buy something and have it just work!
  24. @John Vere I hear ya. Don't think I'll go for the MOTU, then. I for sure want power supply option. Definitely looking at the 6i6 or just staying with Steinberg and upgrading to a larger one. I'm just tired of the back-and-forth shipments! "Good" thing life is still so shut down for me and there is still no work at the moment! That's why I decided now to have at all this now.
×
×
  • Create New...