Jump to content

Dragonwind

Member
  • Posts

    142
  • Joined

  • Last visited

About Dragonwind

  • Birthday February 12

Recent Profile Visitors

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

Dragonwind's Achievements

Rookie

Rookie (2/14)

  • Conversation Starter Rare
  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

2

Reputation

  1. Did the list vanish? I've been trying to find film composers that use LP. I know John Powell and Charlie Clouser do.
  2. This has really gone down the nostalgia road, hasn't it? I still use Cubase to this day (v12 now) and started with Cubase Score back in the day. I did have an Atari 520ST but I think I was on Cubase with a Mac Performa 200. The thing is, LP does some things great, and Cubase does some other things great, so knowing more that one is great but can also lead you down rabbit holes. Someone mentioned Macros for Cubase and those are great, as is simply being able to copy and paste CC data to a different kind quickly.
  3. I was starting to save several new strips from my template and in testing them on an empty project I see the associated articulation map is not recalled. Is this expected behavior? Thanks. Chris
  4. Are those sample library plugins or audio plugins? I use a lot of Spitfire ones and it does seem to be related to those even though they are native. 🤷‍♂️
  5. Sadly I've been running into a lot of problems and this error does come up a lot. It really does appear to be a problem plugin and I wish this error would tell you what plugin was causing the issue. From that point forward LP is garbled. From my experience, combining Native and Rosetta wrapped plugins, although convenient, is more trouble that it's worth. I did find running at a higher buffer (256) resolves some issues. In Cubase I can run 32 or 64 with no problems on this new machine in Native mode. I noticed LP is fine down there too as long as you keep Rosetta plugins off. That being said you might want to try just running in Rosetta mode till everything is updated.
  6. Gotcha. It was late and I was nearly asleep when I replied so didn't watch.
  7. Thanks for sharing. However I do rung Logic in native mode and still run spaces II
  8. I suspect the M2 would be in the Mac Pro since it hasn't been changed over yet. I just got the M1 Ultra Mac Studio and it's so powerful I don't ever see a need for a pro. The only thing I could think of is for the ultra heavy duty CGI and simulation people. Us music users will be fine with Mini's, Studios, and MBP's. Still, can't wait to see what comes next.
  9. Hi all. I finally received my M1 Ultra with 128gb Ram and 8TB drive and had a little time to start working on projects with it. I use both Cubase and Logic and see I'll be migrating back to LP full time. This replaces a Mac Pro 6,1 12 core with 64GB. The Mac Studio is excellent as far as speed goes and loading samples from the internal drive is much faster than off the external SSD's allowing projects to play in the fraction of the time it took to load it all from the SSDs. The transfer took some time and of course so many plugins needed to be re-authorized and remapped to the new location. I was writing a lot of music in Cubase over the last year with some occasional Logic use but now that I'm on Apple Silicon I'm dealing with the mess that is plugin compatibility and also driver compatibility (in Cubase). Some examples: Cubase in Rossata mode: You get most things back, but some of Spitfire's plugins don't work and need to be run in Native, but if you do run Native, then you lose tons of plugins because even though many have gone to M1, they still don't have a VST3 version. Plus, running Cubase in Rosetta makes my Avid S1 useless as it only communicates with Cubase in native mode. I'd have to run Avid in Rosseta first. It's a bit of a PITA. Logic, on the other hand, handles this a lot more elegantly as it apparently runs a hybrid mode where if a plugin needs Rosseta, it handles that in real-time and doesn't exclude it from being able to load it. Outside of that and just getting back in the groove of LP (and making sure all my plugins are updated) the machine is pretty amazing and should be part of the studio for years to come.
  10. I recently received my Mac Studio and have put all the samples on the internal 8TB drive while keeping projects on an external SSD so that the drive with all the writing can be easily replaced. One thing I will likely do though in the no so distant future is get a 2TB SSD and have an 'archived' sample external for libraries that I really never use but may still need to load an occasional old project.
  11. Yup. I’ve been using MS for 15-odd years and haven’t seen a release with more show-stopping bugs than this one. And you’d think that a fix would have been released by now for all those poor users who couldn’t downgrade but also can’t use 3.6 due to crashes. Crazy stuff. Indeed. And all that on top of the patch list is all white with white text so you can't see anything unless you highlight the patch is pretty useless. I heard the only way around it is dark mode (I never got that far as to try to figure that part out).
  12. 3.6 is a disaster. Don’t update till there is a fix.
  13. This was the one I've been waiting for and decided, after all these years, to put everything (sample libraries, etc) on the biggest drive they offer. So it won't be for 10-12 weeks till it ships, but did the Ultra with 48 core GPU and the 8tb drive, trading in the MacPro6,1.
  14. A couple of mine: 1) Hide Folders (track stacks) when all contained tracks in the stack are also hidden 2) First press of Stop returns to the last play position, 2nd press would go to the beginning (I thought it used to do this? My memory could be bad)
×
×
  • Create New...