Jump to content

jonathan boose

  • Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

Recent Profile Visitors

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

  1. And the stock 6x9s in your '69 Impala weren't the aftermarket coaxial ones with tweeters, either. That probably wasn't the only thing he checked on. Berry Gordy, who worked on an assembly line before he formed Motown, had engineers build a mock-up of a car system to check the mixes on. And the portable Phonographs of the day? A 6x9, if you were lucky! It's the reason people used the original Auratones, the "horror tones". You'd want it to sound good on the kitchen radio, translate to a clock radio. But trying to make it sound good on cheap earbuds is probably a fool's errand. At this point, I just try to make it sound good on my monitors and headphones, and if it's critical, send it to a mastering engineer.
  2. Windows actualizaciones ocurren con frecuencia. Y actualizaciones automáticos no son suficientes.
  3. No entiendo la pregunta. ¿por qué no usas esto?
  4. I mix mostly on monitors (I don't have a neighbor problem) but I find cans helpful for checking things my monitors don't reveal as easily. I used to use Sony MDR7506. You don't have to worry about the pleather flaking off because the plastic swivels will break, the super glue you use to fix it and the duct tape tape you use after that will all fail first. Aside from being delicate, they are a good bang for the buck. The AKG ones are more durable. I have an old pair in a box somewhere -- remember the 600 ohm ones? You need a fairly powerful headphone amp to overcome the resistance. I've been using the newer, lower ohmage version, the K240 Studio for a few years now. I think they're probably hard to beat in that price range.
  5. I seem to recall having a problem with it at some point. I haven't, lately. In general, freeze tracks with automation and/or fx that use a lot of cpu, check that your mixing latency buffer setting is sufficient and make sure that you have the latest updates from MS -- the automatic ones aren't enough, you have to manually check. It isn't just the SOC, there was Auto Align and something else that gave me trouble. If those things don't help, the guys at Waves are very helpful. I LOVE SOC and use it on many things. I just used the DS2 to get rid of plosives on a vocal track in about 5 minutes 😁 Win 10 Pro Intel Core i7-3770 @ 3.40 GHz, 3.40 GHz 16 GB RAM 64 bit op sys Lynx Aurora 16 ADC w/ AES16e card
  6. Once again, there is no audio clip in the project. CbB changed the sample rate to 96 AUTOMATICALLY when I changed the bit depth to 24. It wasn't me, it wasn't a poltergeist. I never ran a project at 96 so it didn't get it from anything I ever did. "If a new project does not use the new project sample rate from preferences, the template used to create the project contains one or more references to 96k audio clips." Apparently not.
  7. That isn't something I did. I didn't set it on 96. Can you see how this is confusing? "Go to the ASIO panel and change it as desired." ASIO panel? There isn't any. It's controlled by CbB preferences. If I put a CD in my computer to play through my monitors the Lynx automatically switches from 48 to 44.1 I'll just delete this project and start another with the same title and it will default to 48 24. The point is, I can't do this on the fly. According to Sonar X2 documentation, since there isn't any CbB documentation to be found in a search, you can change the settings if nothing is recorded. That doesn't appear to be the case now so that is misleading. And a waste of time.
  8. This is a new project with no audio clips, as mentioned in the OP. So basically, since this is a new project with nothing recorded, I can just delete it and start it again and it will be 48 24 since I can't get this one to behave. I already opened another project that was a new project with no audio clips and the track module on that reads 48 24.
  9. I guess it must've defaulted to a CD I "mastered" for my brother because that's the only time I record at 16 bits. So when I change the record bit depth to 24, how come the transport display suddenly says 96 instead of 48? I made sure it was set to 48, saved the project and it still says 96.
  10. "It is the record bit depth set here" What does that mean? If we record and mix at 24 bits we expect that to be what is indicated.
  11. Thanks, Scook. What is not solved is why the transport module says 16 instead of 24. But I guess as long as it's a DAW and not a plane or a submarine, NBD 🙃
  12. I haven't added audio or MIDI at all. I can choose a sampling rate but not a bit depth. Moreover, the drop down menu for the bit depth which is greyed out and inoperable says 24 while the display on the transport module says 16. Win 10 Pro Intel Core i7-3770 @ 3.40 GHz, 3.40 GHz 16 GB RAM 64 bit op sys Lynx Aurora 16 ADC w/ AES16e card
  13. Enhancements Automatic Picture Cache management. On startup, Cakewalk now auto detects when the wave picture cache is full and will self delete the oldest files to make room for new files. The Max size of picture cache has been raised to 10000 MB.
  14. D'OH! I never use it and forgot about it. Pretty sure early versions of Sonar didn't have it. I'll have to start using it. I usually bypass fx the old fashioned way, but this is a good way to gauge their cumulative effect. I suppose you could also clone the track, turn one fx bin off and do a parallel fx thing.
  15. The only track I need to unfreeze won't unfreeze. When I 'unfreeze' it, the ice crystal isn't orange but the fx are still browned out (see attachment) and I can't access the fx. I checked to make sure CbB was up to date and I had all the latest optional updates for Win 10. Win 10 Pro Intel Core i7-3770 @ 3.40 GHz, 3.40 GHz 16 GB RAM 64 bit op sys Lynx Aurora 16 ADC w/ AES16e card
  • Create New...