Jump to content

SergeMeister

Member
  • Posts

    153
  • Joined

  • Last visited

Recent Profile Visitors

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

SergeMeister's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Reacting Well Rare
  • Week One Done

Recent Badges

1

Reputation

  1. Very sorry to hear about your support issues, because I'm experiencing similar problems from almost all of the software publishers I use, including Apple. I was forced into an early (and very expensive) "upgrade" to a MacBook Pro M1 Max after my 2015 iMac died, and I have yet to attempt running it in Native mode. In addition to EW Hollywood I invested in Komplete Collector's Edition several years ago. I seriously doubt Reaktor will be compatible (and functional) this year. Fun fact: NI states (deep in the online user docs) that their software is NOT compatible with M1 MacBook Pro Max or Ultra models. Unexpectedly I've successfully run some of the orphaned NI instruments (Absynth 5, Reaktor) stand-alone in a Logic/Rosetta 2 session. I also do orchestral pieces, and was really looking forward to a track count that would support it. Haven't tried a large project yet but I expect to be bipping all over the studio even with my state-of-the-art (for a couple of months) MacBook Pro M1 running Monterey for the foreseeable future. Not even the Apple Store tech suggested upgrading to Ventura. I also heavily depend on UAD software and my Apollo 8p interface for that Ocean Way room I experienced in the 70's, as well as their actually excellent guitar amp plugins, but they also have support problems. Seems all support is handled by their forum, one of their original customer contact guys was still there until lately. I'll be morbidly curious about what their recent relationship with Apple produces. Starting to feel like my contractor days at MS Redmond in the 90's...
  2. Fascinating! I learned early on not to stand in front of my Marshall stack so I can actually hear this. Even more amazing at my age (middle 70's) it brings back memories (trustworthy or not) of a sonic artifact that I have heard in person without electronics. I studied classical bass for about 8 years logging many hours in orchestras, and I remember hearing sin vibrato quiet upper register string passages that sounded like the well-rosined bow moving across a string that was barely vibrating. I just ran a test myself in East West Opus of a sustained C6 solo violin without vibrato in Logic, velocity 89, heard it clear as a bell (or blow, it does sound a little like an AC vent running in the background). I checked lower octaves, no blow. Proximity of the bow to the bridge would change it slightly (more screech). My composition interest began while sitting in the bass section of orchestras counting many bars of rests (great vantage point for learning orchestration) which was probably when I first noticed this sound. FWIW, I agree with your choice of orchestra libraries, especially the EW ones. In the early 70's in L.A. I recorded my first two albums (second one actually included orchestra parts so I got paid for a double on guitar and string bass, VERY fun session) in the Ocean Way (United/Western back then) big studio. The sound had more impact than most concert venues I played in, the EW libraries capture it. And the Strad quartet library is the best solo string collection I've heard. Bass-ed (sorry) on my experience, this may be actually how violins playing long C6 notes without vibrato actually sound, especially in the C6 range where the bow can't actuate the high E string completed. Keep me posted on this, definitely an interesting trip down memory lane for me!.
  3. Somewhat comforting, my MPB M1 Max purchase was scary re. configuration choices. I opted for the 2 TB - 32GB version. Once I get everything else running (ongoing UAD and NI issues for 3 months resulting in a $4k paperweight) I'll report back on Opus.
  4. Understood, thanks for the kernel panic clarification. I haven't seen very many, but this move from iMac Catalina to M1 Monterey has been a month-long project, 30% complete, which sensitizes my kernel panic alarm.
  5. Thanks for your suggestion, Des99, trashing Prefs seems to have allowed the Color Palette to show up. I was able to change Track colors from the Track View and the Mixer View. I would consider this problem solved, although this morning I experienced a kernel panic after waking the MacBook M1 from Sleep mode. I don't know if these events are related (the kernel panic report was even more cryptic than I've experienced, no obvious app info to blame in the report) but I will be vigilant. Many more libraries and apps to reinstall...
  6. Further testing confirmed that the Color Palette window isn't "hiding" behind other screens or views. Both methods of opening the Color Palette window (Ctl - Click on the track's color bar, Track > Change track color drop-down)) fail to open the Color Palette. Next up: trash prefs. I'm assuming for Logic 10.7.4 Monterey 12.5 David's procedure from 10/2021 is still good?
  7. Thanks for the suggestion, des99 and fisherking, I'll look for the Color Palette window behind my Logic screen. Current activation (keystrokes, mouse pointer) behavior looks normal (Track Color drop-down menu appears as usual) but the Color Palette window never appears. I'll give trashing Prefs a try later today. Hadn't thought of trashing Prefs, does that still help on the latest (mine) Logic version? The Prefs settings would be fairly new, I updated Logic about two weeks ago after setting up the new MacBook Max. And yes, I have rebooted (all kinds) several times since updating Logic. This problem exists on new and existing projects from previous versions of Logic. I recall a forum post or YT video saying something about Monterey display settings (I changed the contrast setting) causing this, haven't found that reference yet, however.
  8. After recently updating to a new MacBook Pro M1 Max and updating all the Apple software (everything else is in reinstall-file-copy-limbo) and discovered I can no longer open the Color Palette to change a Track color. I have tried mouse clicks and key combinations, no luck. I have vague memories (common occurrence after 2 weeks of upgrade file copying...) of something like this being caused by macOS display preference settings but I have't been able to find any references in my own notes or the forum. I have come to rely on Track Colors for project organization, so any assistance will be appreciated.
  9. And I'll be proceeding SLOWLY, so far none of my 3rd party software (NI, UAD, Izotope) is M1 compatible.
  10. Thanks to all, proceeding cautiously into the last days of compatibility for my system, the only thing that's aging faster than I am.
  11. Indeed, I'm referring to Logic X 10.7. That's what I get for dropping digits. So if my hardware supports Big Sur it will run Logic 10.7(.0)? On the Big Sur compatibility page I've found that my part number (not an easy search) is on the compatible list: Part info: iMac (Retina 5K, 27-inch, Late 2014), 
Model Identifier: iMac15,1, Part Number: MF886xx/A Corrections welcome.
  12. Read this thread and linked Apple Logic 7 info, haven't found the hardware (Mac) requirements for Logic 7. Will this system work? Model Identifier: iMac15,1 Processor Name: Quad-Core Intel Core i7 Processor Speed: 4 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 8 MB Hyper-Threading Technology: Enabled Memory: 32 GB Thanks in advance.
  13. Having owned Logic since the Emagic years and logging many more usage hours with it the last three years, Retep62's experience has "resonated" (phaser plugins on stun) with me somewhat. After finally becoming somewhat proficient with Logic I find myself in the unhappy position of considering other platforms also for the same reason Retep62 mentioned. I worked for that Seattle company in the 90's during their worst years (while I was on the main campus Office 2000 shipped with 2000 DOCUMENTED bugs) and knew that 55,000 employees can't be all wrong. A high level developer friend there explained it (while he was checking his email on his Titanium Powerbook, also my first Mac) as a management problem. Comparing the history of Apple and MS during 25 years of management changes tends to support that conclusion. I have a few years of experience on Retep26 having started working with PC's in the early 80's at the end of a 20 year music "career". Back then I read the article in the Seattle papers about some youngster from Seattle buying an operating system and starting a company called "Microsoft" while I was already employed as a personal computer "expert". Anyone remember CP/M? If you could spell "PC" you were an expert. Back then backwards compatibility was required, much of MS development went to insuring it, so by the early 2000's the vast majority of business PC's were running Windows 95 and probably still are. Those of us using computers in the arts usually do not have the luxury or the time to "upgrade" (buy more hardware) every two years, which seems to be Apple's business model now. I'm writing this on an iMac i7 now officially classified as "vintage", which means it will no longer be supported by Apple even though I MAY have it running with some stability after months of downtime. All of the major 3rd party products I rely on (UAD Apollo 8p, Native Instruments/Izotope, EastWest) are NOT completely compatible with the current macOS version and M1 processor, let alone the threat, sorry, "impending release" of the next macOS. This is the situation that reminds me of MS in the 90's. Steve may have been many unsavory things but I fondly remember those years, now an Apple employee, of everything just working. His motto I heard around the release of OX 10.2 of "It's the SOFTWARE, stupid" has become "it's the STOCK PRICE, never mind compatiblity". Ironically, it was that latter attitude from MS that opened the door for Apple.
  14. Very helpful, des99, thanks for your explanation, your closing paragraph should be in the Logic manual. And I just confirmed that the Izotope Product Portal Uninstall procedure seems to have worked (after running it twice), Plug-in Manager no longer shows the product I just uninstalled. The Izotope Product Portal Uninstall option produced some "folder not empty" error messages but clicking through the messages had the desired result. As long as it works I don't care if it had to be executed twice.
  15. By "manual's procedures" I was referring to the "Do one of the following" actions.
×
×
  • Create New...