Jump to content

reginaldStjohn

Members
  • Posts

    1,383
  • Joined

  • Last visited

Everything posted by reginaldStjohn

  1. So I tried to reproduce your issue and was unable to do it. Maybe yours is more complicated an so it is not as repeatable. Here is what I see. I made an envelope lane for volume in a track and made sure the value was 0.0dB Then I created 4 nodes and raised the inner nodes up to +3db. 1st number tells me what value I am on the the second the offset from the previous possition. I also closed the automation lane and just looked at the values in the track view. They seemed to be the same I moved one of the nodes to 6db. Then I moved bot the 3dB and 6dB nodes together so the 3dB one was back at 0dB. So, at least in this case everything seems to be working. If you are seeing something different maybe get a hold of cakewalk support and send them your project so they can look at it.
  2. One of the weakest parts of Cakewalk that I use.
  3. A corrupt project file is all I can think of. Try with a new project and importing all your audio/midi files. A pain but might solve your issue?
  4. I can't say as I know why that would be happening. Do you have any VST or VSTi's in the project? It might be helpful to narrow it down to if a VST is the thing looking for a file or Cakewalk. Save your project to a new location. Delete all VST and VSTi one at a time and see if one of them is causing it.
  5. Are any of the drivers you mentioned ones provided by Behringer? The best chance you have is to use the Asio driver provided by the manufacturer.
  6. My experience is that the two numbers shown are supposed to be represent the current value and the difference from the previous value. If you have multiple selected then I don't know what the current value would show but I would think the other number should be the changed amount. Maybe post a screen shot or two to show what you are seeing.
  7. Maybe someone with a Focusrite interface and chime in here since I don't have one. Somewhere, probably in the Focusrite control software, there must be a connection that is feeding the output that you have chosen back into the inputs.
  8. We need more information about your setup. Are you using the built in sound card? If you are they often have a setting "what you hear" recording option that will route the stereo output back to its input. Make sure that is not enabled. Try using a different input (left instead of right).
  9. I use Modo bass and have not had that problem. Could be a corrupt project. Try a new project and copy over the midi to the new project with Modo bass loaded and see if it happens in the new project.
  10. From my understanding that is expected behavior for take lanes. There are cross fades between take lanes because that is intent of the take lanes, to comp different takes of a performance together. If you move one take to another lane then you are saying that they are the same take and they shouldn't need a crossfade. I don't think the intent of the take lanes is to move other takes to the same lane and try to edit them together. That seems more of a job for a track.
  11. A quick look at the Reference manual gave me this information. Seems the multidock can only be at the bottom or floating.
  12. Check to make sure you don't have a punch in region defined.
  13. Midi doesn't contain any sound information only note information so that a synthesizer can produce sound. You need to insert an instrument, like Cakewalk's TTS or Studio Instruments (Bass, Drums or Strings). Then route the output to the inserted synth. You show the built in Microsoft synth but I don't know if that will really work inside of cakewalk. Look for a tutorial or better yet look into the Reference guide for how to use midi and instruments.
  14. I don't know what you mean by "Meter Peak". On a simple instrument track, one that combines a midi track with an audio track, there are two meters you can look at. If you open the inspector ('i') then there are two tabs at the bottom of that window. If you select the Audio one then the meter will show the output level of the audio. If you click on the midi tab then it will show the Velocity of the Midi note in the meter. There is a setting to "zero controllers" on stop. With some instruments this can turn the volume down. Try unchecking that option or add a volume node in an automation lane.
  15. Lo hace con otras programas or solomente con Cakewalk? si es solamente con Cakewalk busque en las preferencias y cambia el tipo de driver (WASAPI, ASIO etc.)
  16. It might be at the bottom of the screen and minimized. Try moving your mouse to the bottom and see if it turns in to a double arrow. If it does drag it up. Otherwise, try hitting 'd' key
  17. If doing something in Cakewalk, like opening a VST GUI, is causing the problem then you will need to run Cakewalk while running latencymon to see what pops up.
  18. Have you contacted support? Probably the best resource if no one here has the same issue or is going to respond. support@cakewalk.com
  19. It could be but you won't really know until you run LatencyMon on your machine to see what process or driver might be causing it.
  20. Sorry I can't be of more help. I don't use the Matrix View. Have you read through the Sections about Matrix view in the reference manual?
  21. Try some different driver modes. One that should work well for playback using the built in audio chipset is WASAPI exclusive or shared mode. Exclusive means that only one application can have the audio device open at a time, No YouTube while working with Cakewalk. Shared mode tries to share it between apps. Please see the user manual. https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf
  22. Try looking at pp 729 in the Reference manual on how to control the tracks you see in the PVR
  23. I would ask this in the Feedback Loop forum. https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/
  24. A glowing "red" would indicate clipping. I have had the prochannel clip and then just stay there and not produce any audio. The usual culprit was the console emulator but I also saw it with the BrickWall limiter. Try removing the prochannel modules and see if it works again.
  25. What video card do you have? I ask this because I had an NVidia card that would cause crackles and drop outs when I showed plugin, especially, VI, GUIs. I used latencyMon to track it down to the NVidia driver. I could never resolve it and switched video cards and the dropouts/crackles went away. Check with https://resplendence.com/latencymon to see what could be causing your issues.
×
×
  • Create New...