Jump to content

Light Grenade

Members
  • Posts

    141
  • Joined

  • Last visited

Everything posted by Light Grenade

  1. Agree with this 100%. As it stands, 4 free i/o on my interface is only allowing me to run 2 mono compressors, when ideally it should allow 4. Also fix the bus solo error when using external inserts. When mixing with external inserts, solo'ing any bus doesn't work and it's impractical. Sadly, I think anything to do with the external insert plugin will be a low priority for the team.
  2. I use buses for submixing, but I tried using AUX tracks to do exactly what you're trying to do. I got the same error. I can't remember exactly, but I'm sure I got it to work by internally recording audio into the AUX track and then freezing. I assumed the freeze aux error was happening as I was trying to freeze a track that had no audio inside of it. If you don't know already, you can arm the aux track for recording and hit record to capture the audio inside the aux track. I'm too used to bussing, so quickly forgot about it, but let me know if this helps.
  3. Go with an interface better A/D + D/A a headphone amp inputs for recording outputs for monitors you primarily play guitar You have a lot more options with an interface, and you can use the piano roll/step sequencer with your mouse in the meantime.
  4. Agree with this, AudioSnap needs an overhaul. It's really clunky drum for drum editing and quite behind other DAWs.
  5. Same here, I only have the C1 version. Its more than enough like you say. Great sounding strip, especially for shaping busses.
  6. The main thing I enjoy about the console one channel strips is that it makes so many of my other plugins obselete. I think it's ended up saving me money!
  7. This is great. I'm definitely gonna cash in on this now. All I need is a good distressor emulator and I'm free of all subscriptions.
  8. I totally forgot to say, but this solved my issue and made my life way easier. I disabled 64 bit exporting and it exported as normal. The error seems to only occur on heavy sessions. Before this I was re-routing my entire project so I could record into an aux track. Thanks!
  9. Hi all, I'm encountering a really bizzare bouncing issue. Upon export (fast bounce, or slow bounce) my waveform peaks at the very beginning and the rest of the file looks like white noise. After I have exported, the session goes a bit haywire, and pressing any button results in clicking, crackling, and general horribleness. I had a listen to the file outside of the daw, and this happens. I can only get the session back to normal upon re-starting. It's a heavy session, but everything plays fine. I have frozen every track to lighten the CPU load, and haven't installed any new plugins recently. As you can see from the video, I am experiencing what seems like some sort of interference noise when moving any control on my interface when the file is opened. This only happens when I open the dodgy file, all other bounces are totally fine. This also happens with bounce to track inside the session. Any help would be appreciated.
  10. This happened to me as well, a year or so ago. Navigate to your audio folder, and drag the recording in from there. You will probably find the full file intact - I did. This problem, thankfully just dissapeared for me. I'd bet on an update somewhere sorting it.
  11. I feel the best thing to do with kick and bass is to identify what instrument you're going to use as the overall low-end. I usually opt for the kick, as I feel the subs are easier to tighten than a bass guitar. For example, if the kick is driving the track, I'll cut everything under 100Hz on the bass track. The kick will be the only source within the 20Hz - 100Hz range, so it's much easier to shape and level resulting in a much cleaner low end. This gets rid of issues a lot of the time. Additionally, there's plugins such as Oeksound Soothe 2 which help suppress resonant frequencies across the frequency spectrum. Another technique is to use something like Wavesfactory Trackspacer to duck the bass slightly upon kick drum impact.
  12. Because not every engineer I'm working with uses Cakewalk. The majority of them ask for tracks to be named this way, it's pretty standard. If more control over file naming existed, everyone would save time.
  13. No, because I'd still need to go in and edit the ''-'' out of every file, and the numbers would still occur at the end. The idea is that a mixing engineer could import every single file, to any daw, in order without renaming anything at all. I bounce tracks weekly, so it's time consuming renaming 50+ tracks all the time.
  14. Yeah, that's what I do, but the tracks export with a much longer name than needed, and then I have to rename in the file explorer. I'd just like exported tracks to use the track name only. With the Cakewalk naming convention, DAW's, or the file explorer don't know how to automatically order the tracks, Examples attached.
  15. Boz plugins are a hidden gem. The +10dB channel strip, The Hoser and Imperial Delay are my personal favourites. His stuff isn't on sale half as much companies like Waves for example. Well worth the money at full price.
  16. I'm regularly boucing stems and tracks, either for archiving or for sending to another engineer to mix. I'd really benefit from the track export function to keep the same names as the cakewalk track names. I know Reaper lets you do this. If this existed, I could name tracks like: 01_Kick In 02_Kick Out 03_Snare Top and they would appear in the window file explorer, in order, and in a naming convetion most engineers are happy with. It would also mean tracks could be imported into any DAW in order. As it currently stands, the export with a convention like: Songname-TrackName-Number They're then all out of order in the file explorer, and I have to go in a rename every single track, which can be time consuming.
  17. Yep, I've been working from a Samsung T5 connected via USB-C for the last year. No issues to report, great drive.
  18. What is it you don't like about the AT? Are you finding it too bright, too muddy, or something else? Once you identify that, it will be easier to pick the right microphone. I currently use a Blue Baby Bottle for 75% of my vocal recording. It's considerably darker than other condenser microphones. It's response seems closer to a ribbon microphone but I really like that. If that's not working, I'll shift to a Sontronics Orpheus which is brighter. I'm in Scotland so I'm not sure how much these mics are in USD.
  19. Have you installed any new plugins? This happened with one of my sessions and Voxengo SPAN was the culprit. It worked fine for ages, then I started getting this exact error. Everything loads fine, then the window just closes - no error box or error code. I found the error via disabling it in safe mode. It's a bit of nightmare, but it definitely sounds like one plugin is messing with your session. I uninstalled SPAN VST3 and reinstalled the VST2 version and it fixed the issue. Hold shift when opening a session and disable plugins one by one until you find the malfunctioning plugin.
  20. I have no experience of doing this, but the last studio I worked at, one of the engineers had a macbook that was 'bootcamped' and it seemed to work ok. That enabled him to use Logic on the apple side, and windows utilities on the other. https://support.apple.com/en-gb/boot-camp
  21. Yeah, same here. I got rid of plenty and now only have have one high end piece for the mix bus. I was looking at getting a higher end compressor for the drum bus but I think I'll give it a miss now.
  22. Sorry if I'm mistaken, but do you just mean a shortcut for bounce to clip? ie. right clicking the melodyne region clip and rendering? If so, you can create a custom key binding, I have one exactly for this.
  23. Ah, okay. That's not great, but I will be able to find a workaround by solo'ing track folders. Cheers for saving me lots of time fault finding. I was sure it was something to do with my routing.
×
×
  • Create New...