Heb Gnawd

Thanks for responding Yes , thank you that was it! Its one or the other not both. I guess Cakewalk assumes that if you've displayed the track its to operate manually. I was caught in a strange loop, the more trouble I had the more likely I was to open the automation track to see what was happening. The line is created simply by displaying the track. Its hard to believe that in over 20 years of Cakewalk I have never had the automation track open at the same time I was mixing... but there you go! I believe the "clear all " command removes the nodes and the "delete envelope" removes the line ( but notice it closes the display also becasue opening it creates the line!!!) thanks

Hello, I have no idea what triggered this. I was smooth sailing up until this morning automating levels yesterday. At first I thought I couldn't delete automation because deleting the envelope maintained an automated control which I couldn't override by re-writing. But the problem exists on all tracks in all projects. Its not the previous automation that’s controlling the level its more like a lock at the initial position. Whatever the track volume level is set at when I delete the envelope will create a new automation at that level that cant be removed, so as I write the track whatever changes I make immediately rebound back to the initial level. I ‘m hoping this is just a configuration error, some box unchecked or checked that shouldn't be, but this may be a symptom of a larger issue. I just as suddenly started experiencing insufficient memory for midi ports which standard remedies have not solved. To keep this simple I wont detail that problem here but it feels like cakewalk is having trouble with its memory. Here is a screen capture Any help would be greatly appreciated thank you.

Ok , so this isn't a problem just an inconvenient limitation, laptop is far too small to load the sound banks and with the number of takes I need to bring back its a bit tedious dragging them in individually. I'll have to do more field editing. thanks to all

Usually lack of response means its a local anomaly, probably something obvious I'm overlooking. I discovered the transferred project file is still functioning properly for any new tracks , but the VST and player interfaces of tracks that existed while open on the laptop remain inactive. I can restore the tracks by duplicating them once they are back on the original machine oddly enough, but rather than duplicate dozens of tracks its more simple to export the audio from the vocal session into the master project file. Thanks for your help at least this is a problem i can live with.

Thanks for responding, I don't think the problem is specific to Kontakt since it is also affecting the Play , Aria, and Ample players, and AVOX plugins, but what you are saying may be be true with all players. So, what you're suggesting is that having opened the project on a computer that is not licensed for the VST library or audio plugins the project file is somehow permanently tagged and plugins and VST banks will never function in the project again. That is hard to accept, especially since the Cakewalk missing plugin message indicates that the plugins will be restored "if you save the project and subsequently load it on a system where the plugins are properly installed" ( see attached)

Hello When I add vocal tracks I transfer the entire project to my laptop to take it to a small sound insulated room. The laptop does not have my VST banks loaded on it, so I bounce the project to a stereo audio track to hear while recording. The project switches with no difficulty between the 2 different sound cards but when I "save as" and transfer the project back to the original computer the the midi tracks have no audio. The plugins all load successfully while opening . The synth rack seems to indicate the banks are loaded but when I click on the player interface either I get a "this sample is not initiated" message ( Kontakt) or the interface is inactive ( Aria) . This problem is project specific, the original project still functions properly. So it is not about finding the libraries. Any help would be greatly appreciated thank you

I think I 've run through the whole list of algorithms with various polyphonic and monophonic audio tracks. I've also done what John Vere tried, making an audio clap track that follows the beat and dragging it up, and midi track ( I used the percussive tapping of the Ample upright) converted to audio and dragged up. Also as John Vere states, I abandoned any hope , both in Cakewalk and in Melodyn of AI understanding of 6 /8 ( unless you speed the tempo and lengthen the bars to include 4 triplets) I got it to play 6/8 @ 60bpm as 12/ 4 @ 120bpm , but the real beat is an off beat of the metronome. At any rate I cant get this to work in 4/4 either.

Great thanks! NB Measures and beats don't line up without a click track. I am afraid I was never able to get the Melodyne Studio "drag to click-track" function to work with any of the offered algorithms ( default, automatic, universal, percussive, polyphonic etc.) not only does it not interpret the meter and tempo correctly but it also modifies the audio ??? which is perplexing since that is exactly the opposite of how I would expect it to work. and I'm too lazy to manually adjust all the transients.

Thanks for the precision, when you say "extend the audio clip" do you mean select using a "snap to event " like a marker, midi note or audio transient?

thanks!

Hi This is a simple rudimentary question, I'm surprised I couldn't find the answer in the manual. I thought there was a keystroke to drag a selection from one track to another without any movement on the timeline but I cant find it. Am I confusing this with another program? , if so any suggestions? I am trying to splice together pieces from different takes all synced to human tempo. Appreciate any help or suggestions Thanks

I'm not an expert but I dont think SSHD is tech terminology. I think its a marketing term ( scam) which appears to be exclusive to Seagate. In my view its tarnishing Seagates reputation more than any money it might be making them. Truth is if I had never upgraded to these "Solid State "drives and kept my original HD drives I would never have had this problem. My HD drives in the SATA III ports of the z390A are reading at 170mbs. SO, yes the Z390A remains "rock solid" if you avoid weak link components. ( My wife always tells me " respect yourself and your tools, don't buy the cheapest!) Best Regards and thanks for your help

SOLVED! Ok I'm back after more than a month of trial and error. I wanted to update this post in case anyone in the future finds themselves where I was. Imagine my surprise when the dropout problem survived , stripping the system of video cards and all non relevant drives , then a clean re-install of Windows followed by days of re-installation of ILOK, and other security software as well as 650 GB of virtual instruments. The culprit was, what I thought were SSD drives ( Seagate Firecuda 2TB SSHD). I have since learned the difference between SSHD and SSD, even though both are billed as "Solid state" drives and ( in the case of the Firecuda) pretend speeds of 5 times that of traditional drives. These drives may start out at 125 mbs ( which is actually lower than my traditional HDD ) but they degenerate over time, such that 6 months after formatting they were read / writing at 70 mbs, ( which despite Seagate's claim is actually less than half the speed of traditional drives). As soon as I replaced these "hybrid" drives with real SSD drives the problem disappeared. This was probably a mistake not many of you would have made which is why it wasn't considered. Thanks for all your help , very happy to get out of computer tech and back to music after many months.

OK , Thanks for the suggestion, I,ll pull out the video cards and test, I'd have to pull the cards to activate the on-board video, I haven't done that yet. I have disabled all nonessential devices to no avail. So am I understanding that as far as you know this has to be a device /software problem? Sparks in my headphones is a red herring?

Hi Tecknot, thanks for your response. Sound card sample rate is set to 4800 Mhz, buffer size is 256, Cakewalk is set the to the same sample rate, using ASIO Mode my understanding is that the bit rate is fixed at 24. Usually when there is a conflict I hear a tick as the project opens and realize that Cakewalk has reset my sound card to match the project configuration. I'm not sure how to set sample rate in Windows, my Windows sound settings defer to the device selected. Drop out and static occurs also with brand new project files with nothing more than a single audio track, but the more severe blue screen drop outs are from heavily packed projects with many virtual instruments. In such cases I have gone through the project deleting track by track to observe changes, for a while I was thinking there was a problem with one of the libraries. There could very well be more than one thing going on here. But I've never found a clear identifiable culprit. Regards Heb

Apologies for the length of this post, Its a complex knot and I've been at it a long time. The problem is sporadic and doesn't seem to follow any consistent logic. I'm writing here after several weeks of running the well-beaten trail of this problem with the usual suspects, (sound card and Microsoft support). I have not changed anything significant in the last year but suddenly encountered severe dropout and static about 3 months ago. The static is sometimes only heard and not recorded, the dropout sometimes so severe I get the blue screen ( blue screen report only says Windows stopped unexpectedly). The dropout records as an electric buzz. Here is a short synopsis of questions, a longer description follows: -Could 2 video cards ( both NVIDEA) using the same driver cause this -Could 4 monitors cause this, ( sometimes disconnecting a monitor or disabling one of the cards ( 2 monitors) seems to reduce the chance of dropout ( or red ink in latency monitor) -Could there be a physical electrical problem , (short circuits, overloaded power demands) -Is there an inherent Windows 10 problem with sound recording revolving around the ACPI Driver for NT routine? I am running windows 10 Pro up to date ( latest build) on a SSD drive, projects and VST banks on a separate SSD drive. Board is MSI Z390-A Pro with i7 3.6Ghz and 64 G of RAM. I have a Native instrument controller (USB powered) and a digital piano connected via separate midi cables to a Powered USB bar that is plugged to a USB 3.1 Gen 2 port. I have 2 sound cards ( not using simultaneous, just to say I've swapped them out and the problem persists) Focusrite scarlet 2i2 and EVO 8. I believe I have swapped out every component listed above including the computer. I do not experience this problem with the same sound card connected to my laptop running Windows 10 Home. Windows, sound card drivers, video card drivers and chipset drivers are up to date, ( and throttling is disabled). Power settings are specifically set for sound recording (including disabling USB suspected suspend). This problem persists after deactivating all other unrelated devices, (network card, Realtek onboard sound, wacom tablet, NVIDIA high definition audio) I am turning in circles because behavior is not repeatable. Running a test several times produces a consistent result one day and not another. At times I thought the problem could be electrical, because I often get shocks ( little sparks) in my headphones that cause the mic light to flash which means they are being recorded. But they don't correspond to moments of static while recording and the shocks aren't new. For a short period it seemed as I was getting a correlation between dropout and touching the keyboard or pedal of the piano, but that too was not consistent. Computer and 3 monitors are connected to one bar, midi controller, USB bar, piano and a fourth monitor are connected to a second bar, each bar to separate 3 prong outlets. USB bar has both MIDI USB cables and the NI controller power. Steps taken Starting with the sound card I explored the full range of buffer settings, and then ( with tech support) installed and ran latency monitor several times while recording. I ran the utility many times while experiencing dropout and static, Latency Monitor blames a large spectrum of services and devices on my computer rarely the same. ( dxgkrnl.sys direct X, nvlddmkm.sys - NVIDIA Window, ACPI.sys - ACPI Driver for NT. The ACPI driver is the current darling culprit for this problem on the Microsoft forum, because latency monitor frequently records that it is the highest DPC routine execution time. I am starting to ask the question what is causing the ACPI Driver for NT routine to overrun? On one occasion I tried swapping out Cakewalk ( I have the latest update but the problem has survived at least 2 updates) I ran latency monitor while recording a single audio track in Cakewalk and then in Audacity. Latency Monitor turned red within seconds during the Cakewalk recording which produced static all the way along and dropout that recorded as an electric buzz yet it remained green during the Audacity recording which produced no static or dropout. The latency monitor reports are very similar (expect one is red and one is green) both showing Direct X as the highest ISR Routine execution time and NVIDEA as the most DCP routine execution time with roughly the same numbers. However, these results, just like every other test I run are not consistent, immediately afterwards the cakewalk recording produced a green “suitable for audio” conclusion??? On another occasion it seemed to be the weight of playing back multiple VST banks. I open a new project file and record midi with no problem then add an audio track that produces static while recording but which is not recorded, then I open a full project with multiple tracks and I experience dropout and latency monitor flashes red. Any help with this problem would be greatly appreciated. Thanks

That would explain why the session drummer is version 2. SO I guess Drop Zone and RXP are also residual phantoms from Sonar 8.

Ok thanks for confirming this can work . It motivated me to dig deeper. I uninstalled cakewalk for band lab ( again) and reinstalled Sonar 8 just to confirm that there were no Windows problems and session drummer 2 worked. Somehow the installation of Sonar 8 woke up or corrected what ever was wrong and now Session Drummer 2 functions in Cakewalk by Bandlab Thank you for your help PS Yes I believe that session drummer 2 is one of 3 32 bit VSTs in the CbB package.

Hi Can anyone verify that session drummer 2 ( 32 bit) VST functions in the Bandlab version of Cakewalk. Its the only VST in my entire collection that wont load. I wanted to make sure the problem wasn't local before reinstalling an earlier version of Cakewalk that housed Session Drummer 3. thanks

Just to close this post, I don't know what this was, but when I realized it was only affecting midi tracks I uninstalled and reinstalled both midi interfaces and their drivers and that fixed it.

Thanks for responding, I thought of the same thing , but all projects, even new projects are affected. I have since reinstalled cakewalk and the sound card driver and the problem still persists. The problem is sporadic for a while it seemed to be working properly with "On stop rewind to now marker " unchecked, but that is no longer the case. It feels like a Windows or Hardware problem except that everything functions, its just not responding to Cakewalk record settings correctly. Obviously I can continue to work by selecting the track and deleting between takes, but the way I'm set up, this means I have to leave the keyboard and return to the main computer each time. Its also an indication that something is awry ,

Hi I am experiencing a strange dysfunction during recording that isn't restricted to, but primarily concerns the inability to overwrite. I just thought I would check if this is familiar to anyone before replacing hardware that otherwise appears to be working properly, or reinstalling Cakewalk. I have been working on the same project for over a month, Record is set to overwrite and this has worked for me fine up until now. I am running Windows 10 pro with i7 9700k 3.6GHz 64G ram, I have 2 midi controllers connected through separate interfaces. sound card is focusite scarlet 2i2, I can describe my setup in more detail , but this might not be necessary if someone recognizes this problem. 2 days ago I had a fallout ( something i haven't experienced since the late 90's). and then Cakewalk froze and had to be force quit. After reboot I had to redo all cakewalk settings ( midi inputs audio etc) so its possible I just misconfigured the setup after reboot. Periodically I cannot record at all, ( no white region following the curser and no data afterwards) other times I can lay down a first recording but nothing afterwards. For a while I was able to double the track and record them both simultaneously and this "woke up" the dormant track for a take or two. Now i simply cant overwrite. I've tried all reconfiguration of the record settings including "create new land" Any help would be greatly appreciated! thanks

SO the problem was Komplete Kontrol. True to its name , its power to usurp and lock MIDI ports is complete. Simply having once used a midi interface in conjunction with this keyboard seems to have reserved it exclusively. When I got a second interface for the NI controller and tried to use the first one for my piano, it was no longer available. I couldn't even reinstall the drivers for this MIDI interface because of a devise descendant allocation. I had to uninstall Komplete Kontrol in order to reinstall the MIDI driver , and now the two MIDI inputs are working side by side in Cakewalk Thanks for your help!

I'm adding this post script for others who encounter this problem . This is a Windows problem. I assumed the keyboard was not outputing MIDI because MIDI-OX was not registering a signal . The fact that the same keyboard shows up red in Ableton Live eliminated Cakewalk from the equation. I just thought to connect the same keyboard to my MACBook and saw the signal was being sent and recorded correctly into Garage band. Something in WIndows MIDI port configuration is blocking the device. The Cakewalk memory message is the same as the Ableton red highlight , I think it just means there is a driver or port problem with the device. If I ever figure out how to fix this I'll add another post script, but for now anyway , I wont be replacing the piano.

Thanks for the link. Rebooting didn’t help there are no cakewalk ghost processes running and the MIDI ports seem to be clear. However, today I am not getting a signal from the digital piano (Kurtzweil RG100) its an old work horse, faithful as they come, but its 30 years old. Though I was getting a signal before today, its hard to see this as a coincidence. My suspicion now is the problem was always the keyboard. I will know when I replace it. Until then thanks for your help