Jump to content

fuzzfilth

Member
  • Posts

    6,495
  • Joined

  • Last visited

  • Days Won

    13

fuzzfilth last won the day on October 15 2023

fuzzfilth had the most liked content!

Recent Profile Visitors

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

fuzzfilth's Achievements

  1. Against the Play click, put a Noise Gate on the Stereo Out (don't forget to bypass this before the final bounce). The Stop click will be way more tricky.
  2. To me, space is so much about arrangement. If instruments are competing about space, the arrangement is wrong. Usually I'm not someone who recommends videos, but here is an excellent one, well worth the <2min of your lifetime:
  3. One thing to specifically look for is whether there are any tempo *curves*. The calculation of these may have changed between Logic versions. Also these have a tendency to cause drift in certain situations.
  4. Arrrgh. Just when my wounds had somewhat healed.
  5. Pretty much, yes. They took the deep dive and managed to plant their systems into professional studios during the third digital wave (the first being MIDI, the second being Fairlight and Synclavier) in the 90s to replace tape. There were a few competitors, but Digidesign managed to ride that wave by having a powerful yet simple GUI combined with reliable (if expensive) hardware. Having sunk tens of thousands of your currency into a working (and compatible) system, you're not going to throw that out just because Cubase got a pretty update.
  6. Here's what I'd do with a wild (i.e. not to a metronome) recording like this: - Beat Map roughly, like once every one or two bars, like I did with your file, so Logic knows how I meant what I played. This will create a Tempo Map which follows roughly what I played, leaving my little wanted or unwanted fluctuations between the mapped points. This leaves the human element in and avoids the mechanical rigidity that comes with hard quantisation. - after Beat Mapping, select the Region, ctrl-click it and select Tempo>Write Project Tempo To Audio File. - engage Flex in 1, 2 and 3 - now I can change the Tempo Map to lessen or remove unwanted fluctuations on a macro level or to change the tempo of the song entirely, and the Region will follow. However, my personal inaccuracies on single notes or phrases still remain intact. - Once I found a good tempo structure, I may (or not) try to refine my less-than-optimal playing skills either selectively with Flex Markers, or globally by using gradual quantisation, either on the entire Region or I may further divide the Region into sections which require more attention. I'd much prefer this approach to simply manually Flexing every note to a static tempo, because a) it's much quicker, b) it gives a much more natural feel and c) it is much easier to change later.
  7. I used Beat Mapping, which you can read up here: Since the guitar is syncopated, I used the loud transient on the 16th before each downbeat, which you can see if you zoom into the pic. You lost me a bit in the 4/4 part , so I'll leave that as an exercise for you to sort out 😁 Note that I matched Logic's Tempo to the recording, not the other way round. Write back to learn how to straighten out the fluctuations.
  8. So the first note in the file is one quarter upbeat ? i.e. on the 5 so the chord changes on the next 1?
  9. Your overthinking it. It's an exercise. Listen. Make the guitar as loud as the keyboard. Then try to separate them by EQ.
  10. First red flag is Dropbox. You *must* compress Projects into ZIP files before you move them to Dropbox, or any other cloud, to avoid data corruption. I haven't extensively tested this, but I can open a Project that is saved from LPX8.1 in LPX5.1. I get a warning "This Project was saved with a newer version, you may get errors, update your software", which I can dismiss. After saving the Project in LPX5.1, I don't get this message anymore. This will certainly be more problematic if features that are new in LPX8.1 are activey used in that Project. If you can list these and make sure all collaborators avoid them, you may get by without trouble. Another option would be to distribute the oldest Logic version to all collaborators and have them use that exclusively.
  11. As you've found out, Logic puts all MIDI data for one Track into one Region, whereas Cubase uses several Regions if it thinks its beneficial. This does not affect playback and does not matter, as there are no Regions in a MiDI file anyway. But this is not the cause of your problem. Arranger keyboards are notoriously finicky in combination with a DAW, they are specifcally designed to not require a computer, and this often goes against compatibility. It seems there is something in a Logic MIDI file which isn't in a Cubase MIDI file of the same music, which irritates your keyboard. Upload two versions and we may have a look. Narrow it down to the simplest file, maybe even without any notes, which still triggers the error. Also, it would help tremendously if you would tell the specific error message.
×
×
  • Create New...