Jump to content

giovannibuchelli

Members
  • Content Count

    19
  • Joined

  • Last visited

Everything posted by giovannibuchelli

  1. If someone has a spare RBass license please DM, maybe we can trade.
  2. My PC has a 2012 AMD FX 6100 six-core processor. What value of Thread Scheduling model would be more recommended? 2 or 1? Right now is at the default 1.
  3. Solved! https://discuss.cakewalk.com/index.php?/topic/28871-solved-timing-issue/page/2/&tab=comments#comment-236488
  4. Hi, thanks for the update. I tested normal record, loop record, punch record, and some variations of punch+loop, and I got perfectly aligned clips every time.
  5. Yep, same here. I tested normal recording and it's ok, but I've just tested punch recording and it's still off. In my test, the recorded signal is placed ahead of the original, by the same amount of samples of the reported latency.
  6. @Noel Borthwick ASIO latency working fine here. Thank you sir.
  7. I did the rollback to 2021.01 and manual offset works as expected (98 samples for my interface, same number I got in Reaper, Cubase, and other DAW).
  8. I'm having a problem with ASIO reported latency and with manual offset (not working at all).
  9. Same or similar here. There seems to be a problem with reported ASIO latency and with manual offset. I didn't use the feedback threat because I don't know it this is some new problem of the latest version. I've done loopback tests in the past, but not very recently. https://discuss.cakewalk.com/index.php?/topic/28875-asio-reported-latency-and-manual-offset-not-working-properly/
  10. Hi, I did a loopback test and I'm getting a consistent latency of aprox. 413 samples between the original signal and the recorded one, and after entering that value in 'Manual offset', I repeated the test and still get the same delay. In fact, the latency is exactly the same with 'Use ASIO reported latency' checked or unchecked. I've done the same test in other DAW (Reaper, Cubase Elements 11, Samplitude Music Studio 2020, Studio One Prime 5) and both reported latency and manual offset work as expected. CbB 2021.04, UMC204HD audio interface, ASIO buffer 128 samples.
  11. Thank you, that's a nice white theme. Also I already downloaded your guide to create themes.
  12. I was about to ask about this same topic. Cakewalk is the only DAW I know that applies color only to the waveform or the midi data, and not to the background of the clips. Changing manually the color of the clips can be a bit cumbersome if there are too many tracks in the project. Would be great if there's an option to change this behaviour by default.
  13. Solved! I had to manually delete these couple of lines from Windows registry: HKLM>Software>Cakewalk Music Software> HKCU>Software>Cakewalk Music Software> Then I reinstalled CbB, and everything is back to normal.
  14. Hello, I'm having this error message every time I try to activate the Quadcurve EQ in ProChannel: This is a fresh install of the latest version. I also downloaded the 2021.4 early access version and the problem is still there. I'd appreciate some help. Thank you.
  15. The second example is very simple and effective, that's all I needed. Thanks again.
  16. Oh yeah, those are some really great alternatives. Thanks a lot.
  17. Hello there, Cakewalk documentation says: "Mute always takes precedence over Solo", that means if you have both Mute/Solo buttons activated in one track, that track will stay muted. https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=Playback.17.html Is it possible to change that behaviour in Cakewalk? In Cubase, Reaper and others, I can have muted tracks, and if I press Solo in one of them, that track will change to Solo. That's a very quick way to do A/B with reference tracks loaded into the project. In Cakewalk that's not possible because first the track needs to be unmuted, so there's an additional step. That's probably the only thing that keeps me from using Cakewalk for mixing. Unless of course there's a way but I'm not yet aware of it. Thank you.
×
×
  • Create New...