Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by DCMG

  1. BTW, thanks for the prior thread links...very useful
  2. Curious if you've used the curved monitor for any length of time while using your DAW. I get the intended purpose for gaming but wondering what it adds in DAW experience. Thanks for all the input here. I've got a lot of options to look into.
  3. Read the post; specifically how CW readability/clarity rates across different monitor types ( I do this everyday for a living, so it absolutely feels pretty relevant). If you're using a setup that works great with CW, I'd love to hear about it. If not....feel free to sit this one out Thanks for the helpful replies already. Good to get some input on how the ultrawides are working for CW users, as well as the curved. I've also noticed a trend of people using smaller monitors very close and angled up, usually with larger ones placed elsewhere. So many options... Thanks again for the replies!!
  4. My 2012 LG 37" TV ( used as a computer monitor) is getting up in years. Tried a few various sized dedicated monitors/and or current TVs and have been surprised to find most of them look great on traditional sites, mail, apps, etc. Open CW and they look....fuzzy ( especially all the text). I sit approx 3 feet from the screen/sit/stand desk so it's bolted down and moves w/the desk at all heights. While I like having a large TV so clients have some visual, I'm wondering if "smaller but better quality" might be the road. But it's not like trying on socks. It's a major production to keep buying TVs or computer monitors to "test" until you find just the right one. So tell me what you use? Single BIG TV Multi Smaller Screens? Curved? LCD/LED/UHD/4K/Touch? ( it's entirely possible that my eyes are just bad, but that's a whole nuther thread " TIA
  5. Never had it happen on a VST, only audio tracks. I've had 10-12 tracks of backup vocals all through an aux that suddenly goes dead. Never mid project. Only after a re-open of the project at a later time.
  6. Yes, I've seen this before. Very rarely, random enough I don't bother and just create new aux, reassign, etc. Seem to recall it happening on some occasional track templates (multiple bax>aux track w/ misc processing). Aux track is dead for no reason. ( Yes I know about the echo being on for aux tracks to work)
  7. This is a really good point. I've been looking at some of those plugins to see if there's common culprits. Every project I have probably has Fabfilter EQ, Maag EQ, RenComp, Concrete Limiter ( this is often in place before real limiting on mixdown, and I try never to have this on during tracking but worth chasing down to be sure). There are others, but those are literally on every project in some measure. I've had it happen on a project where no software instruments are in place, so I think I can rule those out.
  8. OP here. I get what you are saying...but the setup I'm using is not unusual. Apollo USB is the only interface my system is seeing. The Presonus 192 is being used simply as a set of converters for 4 (nice) outboard mic pres. That way my Daw sees the analog ins of the Apollo along with the optical ins supplied by the 192. Not sure why externally clocking the Apollo would be the culprit, but I might try the test just to be sure.
  9. Yeah, I'm not seeing round trip latency issues offset by 128 samples or something. These are wholesale "off by 10 seconds" issues. Then the next immediate round of recording (literally seconds later) ...everything fine. Odd issue. Yesterday happened mid session, which I haven't encountered. It's a tough one to explain to clients ( when we already labor under the "why not ProTools?" dogma 😆
  10. Interesting note that the waveform preview is always in correct position, suggesting alignment is correct at moment of capture, then offset upon transport reset. Same always true here as well. I'm going to update all my system info along with typical plugins used so we can identify any commonalities. Regarding the suggestion about generic drivers, I only have the UA Apollo Twin USB drivers present and still have this issue. No conflicting ASIO drivers present.
  11. It happens so infrequently you might be waiting days or a week before the changed settings would show if they worked. I'll keep at it too. Strange elusive issue....
  12. Did some testing last night, couldn't get it to happen (or course) My only clue is I've never had it happen LATE in a session; always right off the bat, then subsequent takes are good once I observe the issue, stop transport and begin a new set of takes ( buffering, length of time program/OS/computer has been on? ) I've started doing a test run of 2-3 looped takes when I've got a client present. I don't tell them why I'm doing it, but I'm checking to make sure it's behaving. Shouldn't have to do that type of stuff to trust your system ( which BTW is a fast CPU, good RAM and all SSDs so no issue there) Will keep digging.
  13. Thanks for the input. Don't recall this issue in SONAR; seems like a recent ( last 2 updates?) Will do more testing this week, but it's pretty random so far....
  14. Random issue but happens enough, thought I would ask if this happens to anyone else. Typical circumstance: Loop Record Mode> run 4-5 passes> stop transport to find all passes are not in correct position (always early to where they should be). Luckily I usually am looping to a grid so it's easy to see the new misaligned passes are easily moved by 1/4, measure or whatever and all is well. Subsequent passes all land in correct position; not unusual for the problem to NOT present itself again for days or a week. Note: I did have this happen with a manual start (non looping mode) the other day, so it's not just a loop record issue. No pattern detected yet, and no other timing anomalies with my setup observed ( UA Apollo w/ Presonus 192 providing Optical ins and clock) TIA.
  15. thank you thank you!!!
  16. So glad to hear others questioning this. I usually use cntr+arrows for quick zooming and the (zoom+center) behavior I simply took for granted as normal. Now I have to zoom and hit G (center) to center where I was working *constantly*. It's a workflow mess and slows me down. Can we have this be a user option to have the old behavior ?
  17. I would like to know this as well. Is this new behavior discussed somewhere in another thread? Definitely prefer the previous <zoom+center> behavior .
  18. When it happens it's with every midi folder in the project ( ie if I have battery, Omni, AD, etc all will be closed w/tracks within folder hidden). It's also free of any pattern thus far, so I think it must be a keystroke ( perhaps custom one?) that is doing it when I'm not aware. Thanks for the input. I will continue to track it down. Creating a test file today with the usual midi tracks on board and run through some typical keystrokes to see if I can recreate with more regularity.
  19. I mentioned in my post that the pic I took was of a folder with nothing hidden yet. "Pic here is with tracks "not hidden". I posted this as there was some confusion in an earlier reply as to what "hidden" meant (?!) In this context...that is the hidden I am speaking of. So I just opened another project where I definitely did not intentionally go to this track and "hide" the midi tracks. Yet when I open it. If I'm not purposefully doing that upon close, I have to guess there's an errant keystroke or preference I've set ( or not?) that is doing this when I close a file. That is what I'm trying to investigate.
  20. pretty sure I don't but I will double check that. Thanks for suggestion.
  21. It does seem to be in midi folders. Hiding midi tracks within an instrument folder is (was?) a very specific process, but now something I'm doing is making that happen when I'm not aware. The term hidden applies to THIS scenario. ( Yes, I understand collapsing audio tracks in a folder...this is with midi tracks only upon further investigation). Pic here is with tracks "not hidden". When I re-open the file, the midi tracks will be "hidden" and I will specifically need to click the box to unhide. This seems to be happening without my input, but I know that's impossible. Wondering if a new shortcut or key binding that I use regularly is doing this. Will keep investigating, but any other observations of this would be appreciated.
  22. My apologies if this has been addressed, but some recent update appears ( at least on my install) to have enabled some sort of "auto hide" of tracks within a folder. It may have been discussed in a prior release note or something but I've been a bit too swamped in a few projects to continue searching for where or how this functionality is addressed ( be it a preference that needs to be checked or else?) Cursory search show nothing but it could be several updates ago. It seems I will often open a file to find that multiple folders ( maybe midi only folders?) that were expanded when i last worked, to now be closed and all tracks within hidden. Obviously I can just "unhide" within the box that shows how many tracks are hidden, but it slows you down when you're unhiding 10-15 folders. If this is a recent preference addition, can anyone direct me to the dialog box where I can have this disabled? Thanks!
  23. Got it. Guess I never ran across a situation when a clip was moved on the timeline prior to an unfreeze. I could make a case that the resulting frozen audio and the underlying data should both move when time was inserted...but the bakers disagree Thanks for the clarification.
  24. (2019 07 build 79) Liking the update!! Frozen track (numerous clips) > Time Inserted to project ( ex 1 measure) All this was done several weeks ago. Today: Unfreeze track> underlying data is now displaced; not reflecting the additional time that was inserted. 1. Was this always the behavior and I just never encountered it? or product of recent update? Thanks!
  25. Thanks Noel. Obviously I was doing a modified version of the Speed Comping process with some manual clip selection. That said, shift+click to do same is probably a fair compromise if it allows free time selection in the process ( like your examples above..I can see how that could be helpful). BTW..just reading the list of take lane/comping fixes/enhancements...you guys have been busy. I suspect I will find all sorts of cool improvements. Thanks!!
  • Create New...