Jump to content

winkpain

Members
  • Content Count

    467
  • Joined

  • Last visited

Everything posted by winkpain

  1. You guys seem to be having your own discussion not necessarily related to the OP's issue. That being me, I will re-iterate that the issue as shown in the original video only occurred once in a single session and has not reoccurred so perhaps is not entirely relevant, for what that's worth. This remaining issue that this post is about is better shown in this, however crappy, video taken with phone. (When trying to capture with ScreenToGIF the resulting video does not show the extraneous lines for some reason. seen here - https://imgur.com/kgFcWFF This discussion as it has developed, while perhaps providing fodder for some of your own personal issues and opinions, does not however provide me with any convincing proof that what you discuss necessarily has anything to do with my problem as presented here. It's nice to know that folks are out there, tho! 😁
  2. I started having the issue, then updated my NVIDIA card but continue to have the issue. I believe the NVIDIA card is my onboard graphics card... It is a laptop, built by PCAudioLabs, and the NVIDIA card is the only adapter mentioned in the system. I am aware of no other, unless it is perhaps made available thru the BIOS...
  3. I do, as always, appreciate the feedback here. Thank you. But I feel like all this focusing on space, 'tho a worthy issue of discussion, is perhaps off-topic, as I see no evidence or definitive suggestions that this must be the situation I am suffering. I have followed advice to maintain at least %15 free on my main drive for years now with no adverse effects. Indeed, the drive has been at that capacity for a couple years now and this minor issue (I say minor unless someone can logically show it to be otherwise) began only last week. Only Windows and programs reside on the drive (SSD) in question. All data, projects, TEMP folders, scratch disk locations, and many plugins are on greater capacity auxiliary drives. Besides CW, I use Ableton, SpectraLayers, Sibelius, SoundForge, Premiere, all with running/following playback cursor lines as well as many other more intensive visual real-time display feedback. There are no issues anywhere with these applications, nor in Windows itself. Indeed, in Cakewalk it is only within the full PRV that this issue appears. The in line PRV, for example, does not exhibit this behavior with the Now Time line, nor is there evidence anywhere else within the CW environment of display or performance issues. I also run Latency Monitor regularly (and have recently) and it continues to show nothing but LOW green meter response. I do not believe there is cause to think that I am at hardware/system/capacity end of life scenario. I would certainly want more evidence or explanation to determine that hardware or drive capacity issues are likely to blame.
  4. I guess I'd want a second opinion, or some other indicator on the machine, in its performance, or anywhere else. Before a tear-down, hardware reconfigure,total upgrade, that is. But I do appreciate the first guess. Machine was actually serviced by PCAudio Labs one year ago.
  5. Not to belabor the point, Will, but none of the foundational specs have changed on a professional system that has not been suffering performance issues for the years of use in it's current state. This issue started a week ago. However, it doesn't effect my audio workflow except for a little minor awkward confusion while it is displaying, so I will assume no biggie here unless hearing or experiencing otherwise.
  6. ....For what it's worth, the issue exemplified in the video only happened once and has not reappeared. The trailing playback, but randomly spaced, Now Time Cursor lines continue and only happen in the full PRV, whatever the grid resolution - not in the inline PRV for example.
  7. My problem is having over %15 free? What do you mean? Certainly not that I should have UNDER %15 free for better performance. I am well aware of this. It is not my proverbial first rodeo. The project is MIDI only on a single piano plugin with no effects. I am on a machine custom built and set up by PCAudio Labs that I have been working on professionally and successfully for 4 years - Windows 10 64bit, latest updates, 3.5GHz i5 CPU, 16 gb RAM, NVIDIA GTX 970M video card with latest drivers (2/2022) Perhaps not the absolute cutting edge latest/greatest hardware specs, but... nothing has been recently changed in that regard. And I have added nothing in terms of programs or plugins in the last 6 months or so. The free space on the HD has not changed. In fact, I have cleared out stuff and made more room most recently. This weird cursor trails display thing has only just started in the last week.
  8. Hmmm. Hard drive has got over %15 free. It's a laptop, so I wouldn't be comfortable opening it up and removing CPU for fresh paste. Best I can do is vacuum it from the vents, but.... really? You think this is definitely what is causing it? Does it mean something bad is likely about to happen? It just started.
  9. Yup. It's already set that way. Thanks, tho.
  10. I've been having occasional weird display issues lately. I am on the latest update, but not sure if it's from the update. First this: [Edit: The issue shown in this video only occurred during one session and has not reoccurred since] Also, whenever in the main PRV the moving playback cursor leaves trails of randomly placed vertical lines behind it as it goes. These lines disappear if I simply move my mouse or change the screen view briefly, but they continue to generate again if playback is still going. This one I have tried to do a screen capture while it's happening, but when I view the captured GIF, the superfluous lines do not appear despite having been generated while recording. Any ideas about this very odd behavior?
  11. Yes, I tried creating a MiniDump from Task Manager (as Cakewalk has not created any dump files for these hangs) and I get the "Access is denied" message when trying to do that.
  12. I am getting consistent application hangs with no error report message showing up. The only way out is to "close" CW but it remains in memory and even trying to kill the Cakewalk.exe process returns an "Access is denied" message. In order to restart CW, I must either reboot the computer or at least log off of Windows and then log back in again. This has happened on multiple projects opened over the last couple days since installing the update with no reproducible common cause between the occurrences being noticed. Sorry, I know this is almost nothing to go on.
  13. Maybe we should all start a therapy group to work out all our issues on this - actually get together to bitch and moan about how the other people just don't understand us. Say, once a year? In Tahiti or somewhere?.....
  14. I can't believe I'm looking at this again, but I couldn't resist; it's so WEIRD! I cannot get this method of saving a PNG file with the <template name>.cwt.png fomat in the templates folder to work at all, saving, re-saving, whatever. None of that works for me it does not connect my image file with the .cwt file. It actually makes no image at all show up for the named template in question. In fact, re-saving a template with the same name does not work at all, even if I've added a new image in the Notes browser. When I do a "Save as" with the same name, nothing happens. I can verify this in Win Explorer where the Modified time/date stamp does not update for the template file. I must either Save as with a new name, or delete the original file in order to re-use the same name and have the file update. The .cwt.png file, however, still doesn't get attached even doing this. What continues to work for me is what I have outlined before and above in the thread, so no matter. But whatever is going on behind the scenes with these template images is beyond comprehension on this front end of it! How we can all have different methods that work individually and yet not share in the experience of those methods truly defies computer logic. There is still something we just aren't quite getting! It must have been coded by the original CW bakers long, long ago and is now buried in the mists of confusion and time, or someone who actually knows and is reading this thread is just rubbing their hands together with a devilish laugh at our woes 😞
  15. I am getting no response on this issue from the Help Desk. It's been 10 days so far. Has anyone else had this issue with their Support activities being cleared over there??
  16. Yes, thank you. I sent in a request there as well. I just wondered if anyone else had this issue here. I (we?) used to log in through Zendesk and now I'm automatically logged in through Bandlab, so perhaps that change has something to do with it. Waiting on response from Support....
  17. That's it! It's been a while and the Event Inspector had faded from my use and muscle memory. Thanks! In my opinion, this way is more direct than Find/Change.
  18. ...I do realize that a Find/Change request is a way to do the above. But is there a more direct way?
  19. Over at help.cakewalk.com and I log in as always, and all my previous, some unresolved, requests are gone. In fact, under My Activities, everything is gone. Has there, perhaps, been an update to Support that wiped account histories clean??
  20. I can't recall... How is this done? Say I want to force associate channel 10 to a selection of multiple notes in a clip (or the entire clip itself) that have been recorded or written on channel 1 (or any other channel) in order to then save that clip as a groove clip that will default to playing thru that channel (ch. 10) whenever I bring it in to a track with no MIDI channel chosen ("none") or be previewed from the browser on the preferred channel ? Or, to put it more simplier, how do I batch edit multiple MIDI notes' channel?? I thought that I could do a multiple note selection and then right-click that selection for note properties, then change the channel and have that apply to all selected notes. This is not what happens, tho. Only the note under the cursor is affected with this right-click. Again, this is for "burning in" the MIDI channel to the notes themselves to be saved with the clip.
  21. Ah! So it's not intended. That's good to know. Also, while CTRL+SHIFT dragging the clips directly to a track lane does not technically overlap the previous clip, it does overwrite the last note of the previous clip, placing the first note of the following clip at the very point in time that this overwritten note once was. (I mentioned this with a later edit in my original reply.)
  22. For the new function, Perhaps this is explained somewhere else here? I could not find it: I find that the "back-to-back" import with CTRL+SHIFT actually places the consecutive MIDI clips with their first note, whatever beat it may fall on in the original clip, to be placed not after the last note/beat of the previous clip in what I would call a back-to-back fashion, but instead it overlaps this clip's first note with the last note of the previous clip whatever beat that happens to fall on. This is unexpected behavior to me, but perhaps it is the intended one? And if I force the clips to be imported to only one open track lane, the last note of the previous clip is simply overwritten by the first note of the next clip at the precise beat where that former last note would have fallen. Can someone explain the logic behind this overlapping for consecutive clips? I had expected the following clip to be, at least, placed at the end boundary of the previous clip.
  23. SO... I am still scratching my head on how to really understand the signal flow indicated in the above chart, specifically where it seems to indicate that the Soft Synth and Patch Point signals indeed come before the Input Gain control as marked with my upper red arrow. In my (perhaps just wishful thinking) desire for what is shown in this chart to be true and that using a Patch Point would allow actual input gain control over a live signal (that is otherwise at a fixed level) before being recorded, I have been trying things and have noticed very odd (to my understanding) behavior... As a test, I first tried playing a soft synth live while record enabling its associated audio track only and varying the Input Gain from -18 to +18db throughout the recording process. The audio I heard while recording changed with these gain variations, and the waveform that displayed while recording clearly showed the gain variations as well. Immediately upon stopping recording, however, the waveform reverted to a consistent unity gain display and the playback did likewise. I then tried patching this same Soft Synth's audio track to a Patch Point, record enabling this track only and repeated the procedure varying the Input Gain on the original audio track (of the synth), and this resulted in a gain varied clip being recorded on the Patch Point track. (This, of course, can be achieved with varying the track fader of the original synth audio track as well or a combo of Input Gain and track fader. - Varying the Patch Point's Input Gain during recording made no difference, as in #1) Then, changing nothing but the input source of the original audio track to a hardware input and leaving that track patched to the Patch Point set to record, I recorded audio while varying the Input Gain control of the original audio track exactly as in test #2. Unlike in test #2 however, this had no effect on the recorded clip. (Varying the track fader did vary the recorded level as desired.) What, then is the difference between # 2 and # 3? In my mind they should have had the same result. There is obviously something nuanced in the signal flow going on in the variations between these examples that is not being explained, certainly not in the signal flow chart above. I understand and see that a hardware input is indeed bypassing the Input Gain and this is indicated in the chart where I have the lower red arrow. But the Soft Synth/Patch Point signal line shows then arriving above/before the Input Gain. And why does a Patch Point behave differently to the Input Gain of its source track if it's receiving audio from a synth as opposed to audio from hardware ? In both cases, the Patch Point is just receiving audio from an audio track. How does the Patch Point track "know" that there is a difference between the original sources of the audio??
×
×
  • Create New...