Jump to content

Eriksimon

Member
  • Posts

    7,323
  • Joined

  • Last visited

Recent Profile Visitors

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

Eriksimon's Achievements

  1. Hi there David, Alan; yes, I am still there, but I have a fulltime job now (well, since the summer of 2021 actually), and I appear to have switched passions, from music to photography. But I will no doubt someday return to music again. My daughter is in her final year at the conservatory in Utrecht, she's doing very well. I work for a small software company, (online) software for administrating CO2 emissions for around 3.000 companies, mainly in the Netherlands, some in the rest of Europe, and some elsewhere in the world. My by now gray-haired head is on the bottom of this page: https://www.smarttrackers.nl/en/team/ I do actually use the skills of supporting people using software that I (also) learned on this forum (and from you personally, David), even though it is quite a different kind of software. Nice to hear from you guys. The forum looks nice and crisp and up to date, there's been another overhaul I assume? Looks good! warm regards, Erik(simon).
  2. This is almost always a case of Pitch Bend messages being sent by a controller. If this happens during recording, it will keep happening on playback, as the pitch bend has now been recorded. So: first disconnect the controllers, then delete the Pitch Bend from the regions (using the List Editor), then play back and (probably) notice that the issue is gone. If not, let us know. There are more (albeit more complicated) ways you can make this happen (although it almost has to be on purpose then).
  3. Not quite what you meant, but sounds like a useful term for the "turd on the screen" phenomenon. This mix is somewhat overlouded:
  4. On the twelfth day of christmas my weird love gave to me: twelve Steinway Piano's....
  5. Could you upload the project (maybe with a "Save As" create a new project (as a package) and delete everything from that except the affected track - make sure to ZIP the package before uploading).
  6. Ah, missed your reply David. Again: several ways to skin this metaphorical cat apparently (never skin actual cats though).
  7. These are the options (also all available in "forward" version): So, with a x/8 or x/16 time signature, use "by 1/8" or "by 1/16", or use "by division value" and set the division value accordingly; only "by division value" for 4/4 with the division value set to (dûh!) 1/4:
  8. That looks like serious graphic card RAM corruption, with the folders weirdly folded (foldered?) over the Logic window skeleton. Don't restart. Shut down, wait a minute, and boot up again. And pray.
  9. Restart your Mac (if you haven't already), can be corruption of RAM content. If it happens again you don't have to quit Logic, you can simply restart coreaudio: Logic Pro>Preferences>Audio>Devices: untick and retick coreaudio, dismiss window. Coreaudio will reinitialize.
  10. If it is found in other DAWs also, then I'd say the problem may be in the hardware. Too bad we can't get a comprehensive list of IC's used in audio interfaces. I do remember over at Apple discussions there was an ENORMOUS thread about this, possible the longest ever on the Logic forum there. Some rigorous sleuthing was done by some top people, and they came up with that there was absolutely no common ground to be found between the reports: all different plugins, some projects with only Logicv plugins, some projects with just one track, some plugins loaded, all kinds of different Macs and even some Hackitoshes, all kinds of different versions of OS X and of Logic... all kinds of different interfaces, Firewire, USB, PCI-e, up to and including even the built in audio of Macs. My money for now is on something being fishy with one or more of the IC's in audio interfaces. Would be nice to find out if there are components that are common to all audio interfaces used in the reported incidents.
  11. ...also, that initialization can take some time if you have sampled instruments (especially Kontakt ones, especially especially if they are on an external spinning USB drive). For how long did you wait before force quitting?
  12. Yeah, ANC will also mess up your sound (muddy it, or introduce artefacts). Also, ANC headphones tend to be bass-heavy, or at least not as flat as you would want for critical listening. I also endorse the Beyerdynamics. Or a cheaper alternative: the Superlux HD-662F.
  13. Yep, what Triplets said. 190-210 ms - or more. Unworkable. even a pain when mixing, not to mention the encoding-decoding process which is not unlike mixing with 128 kbps MP3 "recordings". So: don't do it. Use headphones with... a cable. No latency, no fidelity loss.
  14. I would say it is the same as setting the input to 5 under unity gain. So, yeah, a pad of -5 dB. But, without knowing what interface it communicates with, I can't be sure. I'm also not sure if the numbers are equivalent to dB's or not.
×
×
  • Create New...