Jump to content

Gswitz

Members
  • Posts

    1,451
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Gswitz

  1. Does it sound overloaded on playback and just look that way? If it sounds fine, it might be the graphic waveform scaling hosed up. If in track view you click and drag on the scale of the track divide with clip selected, you can expand and contract the wave form. You are recording a single input to a mono track?
  2. My water bottle checking out the place... It stayed after i left. ? So i went back later...
  3. Wasn't him. It was me that pushed that. Still, your post was funny.
  4. Lose the money you might have paid! Ha ha
  5. https://www.orbitalmusicpark.com/ I haven't been by yet, but I sure am curious. Do you have a place like this in your home town?
  6. I turn a bunch of books backwards. Pages out. Deters snoopy guests and invites judgement that makes me smile.
  7. Spending time to make things smooth when I go out is worth it. @msmcleod I love rack lights. They look so cool. @craigbI love the ads for more gear. haha. That's great! @bitflipper Since I don't take my home with me when I go out, it doesn't have to be organized as well. ?
  8. Chuck Surack has sometimes chimed in on threads in the old Cakewalk forum. https://en.wikipedia.org/wiki/Chuck_Surack I buy things there when it's financially defensible. I've always had good experiences.
  9. How many drummers to screw in a light bulb? None. We have machines for that now.
  10. 24 is bit depth not sample rate. Sample rate examples are 44.1, 48, 88.2, 96... I agree with others that your conflicts are coming from another device sharing your driver. For me, if I'm watching Netflix while doing exports or setting up for the night etc and changing projects that have different sample rates, i might have to hit f5 on my movie to get it to reload using the current device sample rate. I use asio. My solution to your problem would be to discover the device using my interface at a different sample rate and take action to make them match. The project you have that has recurring issues is not matching the other app. Try a new project at a different rate. Like if you've been using 44.1, try 48 or vice versa. Switch back to asio and see if you get the alerts. I find double and half rates work fine together, like 88.2 works with 44.1 in anther app, but 48 will collide causing the message you see when Netflix is using 44.1. Again, i usually just refresh my browser window.
  11. It would help to hear the recording.
  12. Make sure they aren't just failing to play by checking the event list. Failing too play a midi note has a separate cause. For that problem you raise a buffer in preferences. Can't remember it, but someone will chime in with it.
  13. @Esteban Villanova Fx chains work in the pro channel and also in the old fx bins.
  14. I made this video to demonstrate what I was talking about above. When I first learned of this, the first thing I thought was... the expensive VSTs won't have this problem, but I've learned they do. As a matter of fact, I haven't found a VST delay that doesn't have the problem. I suppose to avoid the problem the delay would have to span new threads for new tempo changes and persist them until the last sounds at that tempo complete and return to zero. The problem would be the number of threads that might be required. I suppose for continuous tempo changes the delay could resist new threads for windows of time reducing over-all processing. I'm probably way off-base. I don't really know how to write VSTs. I'm just appreciating the problem. All of my VSTs I've tested have the same problem. When they are tempo-sync'd and the tempo changes, the can clip audibly.
  15. Does Latency monitor say you're good for real-time audio when you leave it running for 4 hours?
  16. Good start with latency monitor. So, it always shows green now? Or sometimes is red. If sometimes red, look at the dll tab for why. Sort descending. If yes, always green now, then make sure your virus scanner isn't scanning wav files. If not an ssd drive you could be pushing io constraints, especially if files just saved on stop start being scanned. If first shot always works and second is iffy, doubt your virus scanner that might be scanning your new waves while you also record.
  17. Caution: lots of time based fx like delays locked to varying project tempo will click through tempo changes. Try it and see. When i want to put tempo based fx on a live performance, i approximate the tempo for the song to a single tempo.
  18. You can use some contact cleaner too. Deoxit for example.
  19. It would be cool to spread voices over threads so that a single processor doesn't get over worked too. I like to use a lot of voices.
  20. Noel makes tons of money selling software to us. Oh wait. Well Gibson! They sell awesome guitars... Right? right? No? I think it is possible that music has gone with the soul of the world to find help. So, help is on the way?
×
×
  • Create New...