Jump to content

Helios.G

Members
  • Posts

    185
  • Joined

  • Last visited

Everything posted by Helios.G

  1. Hey 57Gregy, long time I haven't bothered you on this, so I hope you don't mind. I'm working on a project and was using my mx yesterday, when I noticed that the ins file doesn't have everything listed in correct order. I thought I'd take things into my own hands, and downloaded the john melas software, and ran that, but the same thing kept happening. My issue is, when you download the data list directly from yamaha, and compare it to the keyboards menu, they line up exactly, but when you compare it to the ins file, there are things that don't line up. Is there something I'm doing wrong? I just want the basic voicings in the order and categories they appear on the keyboard on the ins file. Am I missing something? Thanks man
  2. it's not free, but start here, and you'll learn everything you need to know, good luck... https://www.groove3.com/products/SONAR-Explained
  3. You've gotten a lot of great advice here already, but I'd like to add this one thing. Many novice producers/artists/musicians don't actually know what a good mix sounds like. Most people are accustomed to what the final product of a major label release sounds like, and they compare their mixes to that. Don't do that. Beyond the fact that you're comparing a finalized project to your still unfinished one, there are usually tons of people who work on these songs, with lots of knowledge on arranging, sound choice, recording in optimal conditions, probably with top notch gear and more importantly with years of know how in implementing all of these advantages. Your first/early projects will sound bad, that is part of this process. You're going to go through some growing pains, but if you do lots of songs, and stick to it, eventually, you'll start getting better, and hearing things you didn't before. Before you know it, you'll start to understand what people mean by the gear doesn't matter, only your ears do, cause fundamentally it's true. Once you get your ears to a level of proficiency where you can hear what a song needs and what may be extra fluff that it doesn't, you'll be golden. Then you'll start to make production, mixing, heck even gear acquisition decisions, based on what is actually important and not what you think makes you sound "professional". Good luck man.
  4. Or just have it's way of working built in, I'd love that. But I'm not complaining too much, at least it exists 😂
  5. I know this comment is old, but just wanted to thank you for sharing this plug here. One of my biggest bugaboos with cakewalk has always been getting a mix to have space and width and translating both in cans and on monitors/speakers. This plugin is amazing, I honestly can't go back to the way I used to mix. Thanks again!
  6. Why don't you just delete the offending sections and fill it in with copy paste from a section without the problem?
  7. How old is your ssd/hdd? Could be that, but would need more info.
  8. I thought you said in that other thread that you were going to let this go? ?
  9. Don't feel too bad, AI is coming for all of our ideas anyway.
  10. I can't help you with your specific project, but I'll give you this. Think about your most common workflows, whatever that may be, and set up a template with the tools and tracks you know you'll need. I personally have a few templates ready to go at all times for my projects. I have a folder, with several sub-folders split into 5. 1. pre-production 2. production 3. vox 4. mix 5. master Each one of those has the exact tools and layout for the specific task at hand. In pre-production I have basic keys, drums and chord instruments set up, and this is where I write song lyrics and figure out structure, before I commit to any specific sounds. In production, I go about choosing sounds and fleshing out the direction of the arrangement sonically. Vox I lay down tracks for vocals, etc you get the point. If you have projects that went well for you flow wise, I'd start there, and just delete all audio and leave behind the project setup and call it what you want.
  11. If you put your'e configuration setup in your signature, we can see what else you got and maybe help point you in the right direction.
  12. I'll tell you what I do. I make a folder for 3 songs that are in the vein of what my project is going to be. Look for similarities in tone and production. Then I find them on amazon and buy them from there for about a dollar and change. Once imported to cakewalk, I compare and contrast and pick the one that I think is the closest tonally to my song. After that I use a program I have called UVR 5 (ultimate vocal remover) that is free and open source. This program splits songs into different parts, bass, drums, music and vocals. Once I do that, I import the split stems, and the orginal into a folder in cakewalk which I call reference. Make sure to route the output of these 5 tracks to the main output of your interface and not your master bus. Lower the level of all the reference tracks so that they roughly match the song you're working on. Once I start my mix, I work the static mix first to sound roughly level with the individual stems of my reference. Once that's done, I do some light eq on the master to match the tone (brighten, darken, whatever) of my track to the reference, then add some bus compression to glue everything together lightly, one to two db of compression should do. Once that's done, I work down my busses and compare and contrast by section, using the split stems of the reference to measure how far off or not I am tonally. I work this way for about 75% of the way, then I mute the reference and finish the mix on my own. By this point you should have a reasonable enough facsimile of your reference tonaly, but still have enough wiggle room to give it your own flair. The idea is to get it in the ballpark, so that it sounds professional, not identical. Good luck!
  13. Good catch John, I delete all audio drivers that aren't going to be used for my work. That would definitely interfere, especially if you don't choose asio off the bat.
  14. I think it has more to do with cpu, motherboard, storage, ram combo than people realize. Everyone thinks that high ram and cores is always better, but you have to know if your components work together. I recently got rid of my previous rig, that had 64gb of ram. In theory, it should have handled whatever I threw at it, but it couldn't. Now my system, like yours, has 32gb of ram, and it breezes through everything, even though my core count is the same (4) and the ram is half as much. Most of it though has to do that I did my research on what I needed and tried to pair everything so it worked well together. I'm happy with my current setup.
  15. I'm still running a quad core over here, no latency clicks and pops, knock on wood.
  16. If your mouse has a scroll wheel, you can hit the control key and scroll left and right with the mouse scroll wheel pretty easily.
  17. Oh wow, He was always so helpful to me, and everyone else here too. Thanks for replying. I hope he's ok.
  18. Hey T, if you don't mind my asking... what happened to @Scook?
  19. I think you're seriously overthinking this. They're a corporation. A corporation wants to make money. They want to monetize all of their user base, not just the "kiddo's" or the "old timers", but everyone that uses their services. They made Next bandlab adjacent, but with some similar functionality to Sonar, so as to introduce young creators to more robust tools. That clearly is in the hope to have them "graduate" to Sonar eventually as their careers progress. All that said, I repeat, you're seriously overthinking this. I make "kiddo" music (pop). I'm not young, I'm not geriatric either. I'm not being catered to in either scenario. In the end it doesn't matter. Make music. That's what all of these tools are for. You don't want to pay? Don't, find another tool, and make music. You're ok with paying? Cool. Stick around, and make music. At the end of the day if you're on here daily fretting about what a company that doesn't know any of us personally is going to do next, you're not making music. I choose to make music, and I come on here once or twice a day to get out of a technical jam or to maybe help someone get out of theirs. Nothing more, nothing less. Make music. That's it.
  20. Hey Max, you're probably right, but since I had to keep working, I found another workaround and decided to move on. Thanks for trying to help though, I appreciate it.
  21. No effects were on the project at the time of the problem, and they were tracked clean, I tracked them myself. Thanks for trying to help.
  22. Whelp, that didn't work either, but it did give me an idea. I bounced down, and then ran izotope rx de-click on it. That worked great. So I'm considering my issue fixed, but in case anyone has better solutions than my workaround, I'm leaving the thread open for a bit. Thanks Jonesey and everyone else who chimed in to help. You guys are the best.
  23. I was under the impression that automation didn't bounce to clip like that, huh, I'm trying it now.
  24. project is set to 44.1khz and buffer is set to 2048. I set it to that for most of my mixing sessions. Apart from that, I have zero plugins instantiated right now, I was just gainstaging and setting up my static mix before I really dug in to processing.
×
×
  • Create New...