Jump to content

white flowers

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

7 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think it would be useful to have Melodyned tracks behave the way you suggest, but because Melodyne can be somewhat fiddly in various ways (although its implementation has improved since ARA2 arrived) I do think it's advisable to render in situations like yours. What I do, which Cakewalk makes easy, is copy the Melodyne clips to another track, archive that track, and send it to a folder (named "arc") where I send many, many archived tracks over the course of a project. Then, if I want to adjust the melodyne, it is usually fairly straightforward to retrieve that clip and work with it on the main track again. Melodyne (and other ARA effects) are generally just very complicated and best approached with a degree of caution. But yes, I hope that further work on ARA implementation is a priority for developers on all sides. It has come a long way, and I believe it will keep improving.
  2. Thanks John, actually ripple editing is still relatively new to Cakewalk, but Samplitude/Sequoia ripple-editing is one of the best and most mature implementations, is widely used for classical editing, and provides the automatic crossfade upon a ripple-delete, as I discuss in the linked post. Given that ripple editing can be a bit complicated, and that the auto-crossfade button is right next to the ripple edit button, it shouldn't be an unreasonable expectation that the editor will enable or disable automatic crossfades as necessary. So, implementing auto crossfades to ripple deletes does not remove any existing capability, while vastly improving the workflow for what is a common use scenario for ripple editing.
  3. I've more or less described the need here: Deleting a section of audio with ripple edit on should result in crossfades at the new junctions (when auto-crossfade is turned on). Thanks!
  4. Auto-crossfade can easily be turned off. Since ripple editing is already kind of a specialized use case requiring attention to the ripple-edit state, and since the auto-crossfade button is right next to the ripple-edit button, it's reasonable to expect to attend to the state of auto-crossfade. On the other hand, it's pretty much always going to be necessary to crossfade at the point where newly ripple-edited clips join - at least if you're editing a classical music performance, for example, which is a common use-case for ripple editing. I can see how with more midi-oriented music it could be complicated, but again, that's when you simply turn off the automatic crossfade. Those scenarios already exist, anyway, since if for example you quasi-ripple-edit manually by selecting everything after a section and moving it to the left, the automatic crossfade happens as expected. In the interesting case where there is no data at the beginning of a clip, Samplitude simply does not apply the auto-crossfade. Samplitude's ripple-editing is imported from Sequoia, widely recognized as an excellent implementation of ripple editing. Since in Cakewalk it's possible to drag a clip beyond the boundaries of its audio (not possible in Samplitude), an easily implemented solution would be to just crossfade away, exactly as happens if you do it manually. This would require attention from the editor, but again, ripple-editing already requires attention. So: it's easy to disable auto-crossfade whenever necessary, but currently impossible to have automatic crossfades after a ripple delete. Having those crossfades would improve the workflow.
  5. still puzzling about this - automatic crossfade should automatically crossfade after a ripple delete, right?
  6. In Samplitude, for example, deleting a section of audio with ripple editing with (auto crossfade turned on) results in a crossfade at the new join. I'm not seeing this behavior in Cakewalk. Is there a setting I can toggle? I can't think of a reason why, if I didn't want a crossfade after ripple editing, I couldn't just turn off automatic crossfades for a moment. Thanks!
  7. UA does seem to create these kinds of problems from time to time by renaming their plugins. Not sure what to do about it - presumably it will load presets saved by the old version if you need to rescue a project, but that's not a solution really. You could try looking for info at the UAD forum here: https://uadforum.com/general-discussion/
  8. This update seems to have fixed a problem I was having with 2021.04 as released, in which certain plugins (eg u-he Satin) caused a crash upon opening a project using them. I had to roll back to 2021.01 before I was able to figure out what was going on, but for what it's worth, this update appears to be stable again. Thanks!
  9. I'm not sure if this will help with what you want to do, but I have used Voxengo Recorder in a similar situation, streaming audio to OBS. It's a bit fiddly, but basically I place Voxengo Recorder on the Master bus and set it to output to "MME", and then in OBS I create a source called "Audio Output Capture". There's a bit of a delay in the audio that I compensate for by delaying the video using an OBS filter. Voxengo Recorder ends up acting as a kind of bridge out of ASIO-land into MME-land. Recorder is a decades-old 32-bit-only freeware plugin, but it gets the job done. It might be something to try playing around with.
  10. That could work in some ways - essentially I'd be using the UA interface as a voice/guitar effects processor. The Apollo Twin that I have doesn't have a digital output, and I don't think I can configure it with pre-fader sends, so the input to the RME would go through an extra conversion and the effects I'm monitoring with would print to the DAW... I do have the monitor out of the UA interface going to RME inputs, but this is mostly to avoid repatching the speaker cables. Actually what might work best along these lines would be to switch the roles: send to RME's digital outs to the Apollo, patch the speakers from the Apollo's outputs. Then I'd basically be using the Apollo with Cakewalk/other DAWS, and the RME with everything else - I use its "total mix" software a fair amount to digitally patch different inputs and outputs, for loopback recording, etc. The problem here is that I'd have to leave the Apollo on all the time (it gets hot and seems like the kind of thing that might eventually succumb to heat exhaustion), and I'd be generally relying on it more - the RME has been a rock-solid music tool for years, while the UA seems a bit more temperamental. Still, it might be better to settle on a constant situation instead of switching things around. Now where's that optical cable? It still seems like there should be some kind of method - or workaround - to switch interfaces on-the-fly... will update if I come across something down the road.
  11. Changing on-the-fly with "reload config settings" would be a good solution, but while exiting Cakewalk and reopening it after swapping aud.ini files does indeed cause the desired interface-swap, reloading settings doesn't seem to do it. I can see why there'd be an expectation that someone reloading their settings would generally want to keep whatever interface they have set up, though it makes me wonder why this is in the file at all if the file isn't wholly determinative of the results. Anyway, I can imagine that it would sometimes be useful to save, exit, swap aud.ini files, open Cakewalk, go get a glass of water while I wait for my plugins to load, then get back to work. Less fiddly than clicking on the little check-boxes. Auto hotkey a good idea as well - I've used it a bit but I'm not sure how I'd set it up to check/uncheck boxes in a window which may be moved/resized from time to time. I'll have to poke around sometime. Thanks
  12. Thanks for the quick replies! Since closing and reopening Cakewalk takes longer than what I'm currently doing (and the RME doesn't have an on/off switch), I think it's probably easier for me to keep going into preferences. Most of the time I only need a couple of ins/outs, so I can just leave the rest blank. Still it's good to think about these alternatives.
  13. I like the stability and features of my RME interface for most purposes, but when I'm overdubbing I like to use a UA Apollo for its no-latency effects and preamp options. At the moment, the way I do this is by going to Preferences, unchecking each RME input and output, and then checking the UA inputs/outputs, reversing the process to continue using the RME. It strikes me that there may be a simpler way to do this, perhaps some sort of workspace preset with an interface preselcted? Not sure, hoping someone else has an idea. Thanks.
  14. Yes, well, it would be best as an option. Even a moment of feedback can damage equipment or cause other problems. The difference between Input Echo and other track states, such as Record or Mute or whatever, is that none of those settings have the potential to create problems on startup if the audio system has been changed in the meantime. This is an issue with other DAWs as well, but I happen to use Cakewalk for most of my recording work, so it's where I encounter the problem, and I do appreciate that you listen and develop with the users in mind. The point about Aux Tracks is that when you change the input from the aux to an audio input, the input echo state is actually changed to off. Then when you change it back to aux, the input echo state is changed back to on. So this is a case where the input echo state of audio tracks is treated differently from aux tracks. In the same way that Cakewalk recognizes when the input of a track is switched to an Aux, it could recognize on startup when tracks are monitoring an Aux and leave their Input Echo state unchanged. Anyway, it would be helpful to me, and I can imagine that other people encounter huge amounts of feedback from time to time when they open a project with their monitors up and a live mic, so it might be helpful as an option. There's a difference when the mics are in the same room as the monitors, as is true for me, versus a conventional studio where there's a control room and a live room. I'd guess many of Cakewalk's users have everything in one room. Thanks for listening.
  15. I'm working with a lot of live recordings right now, where I monitor myself through headphones using various effects within Cakewalk - so I have to use input monitoring while I'm recording. I record for a while, then take a break, then record for a while. Sometimes while I'm doing other things, I use my monitors. Sometimes I forget to turn off input monitoring before I save the project, and then sometimes I forget to mute my monitors before I open the project. As a result, I'm getting massive feedback from my live mic, which upsets my dog. I'd like Cakewalk to check to see if any live inputs are being monitored, and disable them, when I open a project. It would be best if this was an option, just for the odd case where it's necessary to save the state with the project - perhaps someone has a large live-recording template that they need to load up quick to record rehearsals while monitoring the mics, for example. Personally, I would just make it always turn off input echo when opening projects, and if I had some special case where I wanted to easily have a bunch of tracks' input echo enabled when I start up, I could group the input echo buttons so that it would require only one click. But I generally think it's better to have more functionality than less, so the optional approach would be good. I've noticed that with Aux Tracks, when you change the input of an aux track from the "aux" to an audio input, Cakewalk turns off input echo. Then, when you switch the input back to an Aux, Cakewalk automatically turns on input echo. On the other hand, it's logical to turn off input monitoring when you switch to a live input, precisely because there could be a live mic on that channel. By the same reasoning, I think it would be smart to have Cakewalk disable live inputs when opening a project. Thanks
×
×
  • Create New...