Jump to content

smashingly

Member
  • Posts

    27
  • Joined

  • Last visited

smashingly's Achievements

Rookie

Rookie (2/14)

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

Recent Badges

1

Reputation

  1. Results: Arturia MiniFuse 1 (USB-C -> Orico dock -> MacBook Pro TB4 port): correct pitch Mackie Onyx Artist 1-2 (USB-A -> Orico dock -> MacBook Pro TB4 port): incorrect pitch / slower playback MacBook Pro speakers (just as a reference): same pitch as Arturia All devices were set to 44.1k in Audio MIDI Setup. Attached is an audio file, I used music playback as that helps you hear the slowdown as well as lower pitch via the Mackie. Due to only having one set of monitors and no A/B switch, I've run my monitors through the Arturia and my headphones (turned up loud enough for the iPhone's mic to pick up). Interesting that the Arturia doesn't suffer from the same issue, it makes me wonder if this is actually a Mackie Onyx issue. Orico-audio-issue-demo.mp3
  2. Update: they've asked a few questions such as "did this happen straight after purchase, or did it suddenly start happening recently". They've then offered me a small partial refund of AUD$40 (purchase price was AUD$190) for the 'inconvenience' of this problem. This isn't workable for me though as it doesn't solve anything. Also, I've started to notice Logic's "incorrect sample rate detected" issue occurring even when the project sample rate is set to 48k - it just takes a little longer (a few minutes of playback) to occur. So for now I've ordered an Arturia USB-C audio interface on Amazon (with a change-of-mind returns window till Jan 30, 2024) and I'll try that with the Orico and see how it behaves. If it behaves just fine then I'll probably take their $40 offer to cover the losses I'll make eBaying the Mackie Onyx interface. If the sample rate persists with the Arturia too, then this means the dock is badly designed, so 'd return it for a full refund and would be forced to upgrade to a more well-known brand of dock.
  3. Update: short version - no resolution yet. Longer version: Initial comms with Orico have them asking me to send them a video, then logistical backflips trying to share a 350MB video with them in a way that they can view in China (it seems Youtube does not work). Their latest reply is below, but there's a bit of a language barrier, so I've asked them to re-explain and clarify which USB port they want me to try. Also, I think "installed audio modulation" may mean "you're using a third party audio interface". At least they're responsive and keen to help, though, so watch this space.
  4. Non-update update to avoid this topic being closed out: Mackie stonewalled me with "Our team only deals with North American purchased Mackie products", based on the serial number of my Onyx showing that it was purchased in New Zealand. I'll try contacting the distributor in New Zealand but that's going to take me further away from Mackie's engineering team, and towards a distributor that's essentially an importer and box-shifter. A bit disappointing from Mackie as I wasn't asking them to solve it, I just wanted some input and insight from their head office engineering team, who are the ones most likely to have encountered this behaviour. Orico's support have replied to my email asking for a video that helps them understand the problem better - I'm currently travelling between countries so won't be able to get onto that for a couple of days.
  5. Update: I've emailed Orico support in China about the issue, and submitted a support request to Mackie. Will update with any progress.
  6. Yeah - maybe that's what I'll do for now. In Audio MIDI Setup I've set the Mackie to 48 kHz so that other apps on the Mac won't try to play audio through it at 44.1 kHz. So that works around the issue for any Mac apps that follow whatever sample rate is configured in Audio MIDI Setup. I notice that as soon as I load a 44.1k Logic project, the Onyx switches back to 44.1k in Audio MIDI Setup, and this persists after I quit Logic. I may be able to convince Amazon that this constitutes a 'faulty' item, and get a refund. Thanks for your input @rAC.
  7. I was creating a new empty project. If I create a template with project settings -> audio -> 48 kHz, then create a new project from that template, the new project is in 48 kHz, as would be expected. Yep I can plug the Mackie into the Mac directly without the Orico dock - as I mentioned in the original problem description, the issue goes away when I do this. But this does defeat the purpose of having bought the dock.
  8. Hi, thanks for replying. When I create a new project in Logic, it defaults to 44.1 kHz. If I change it back from 48 -> 44.1, the pitch problem returns. Re: deleting the Orico in Audio MIDI Settings, unfortunately the "-" button is greyed out.
  9. *This isn't a Logic issue per se - it's an audio interface issue. Happy to delete post if mods deem that it doesn't belong on this board.* I've got a weird pitch issue with audio output on my Mac that I first noticed with Logic when it gave an error message about mismatched sample rates. But I've replicated it in Apple Music, so it's likely to be a hardware/OS issue. My hardware: 16" MacBook Pro M1 Max. MacOS is Sonoma 14.0. Interface is Mackie Onyx Artist 1-2 (USB 2.0, AFAIK) Symptom: audio plays back about a semi-tone lower than it should. How to reproduce it: Play an audio file on the desktop, go into Sound settings and change output between the Mackie Onyx and MacBook Pro Speakers. It only happens when the Mackie interface is plugged in via one of the USB ports on my Orico Thunderbolt 3 dock. For see if it was an issue with the Orico's TB->USB-C conversion, I tried plugging Mackie -> Apple USB-A to USB-C dongle -> Orico hub TB/USB-C port -> MacBook Pro and the issue still occurs. Workaround 1: Plug Mackie -> Apple USB-A to USB-C dongle -> Mac, or play audio through MacBook Pro Speakers. I initially thought this couldn't be relevant, but the Orico dock has an onboard audio interface (1ch in, 2ch out) that I never use. I wondered if that is somehow interfering with any other audio interface plugged into the dock. So I checked Audio MIDI Setup, and I see that the Orico onboard interface is hard coded to 48kHz with no ability to change this (which is kinda weird). So I tried changing the Onyx to 48kHz but when I play Apple Music back, it reverts to 44.1kHz. So I went into Logic, spun up a new project with some simple C major chords, reproduced the pitch issue, then changed the project sample rate to 48 kHz. Boom - problem gone. I'm not an expert in Audio MIDI Settings on the Mac, does anyone have any clues as to how I might solve this, or troubleshoot further?
  10. Just adding to this in case anyone else lands on this page - I had a very similar issue, and it was solved by deleting the plist file (com.apple.logic.pro.cs.plist) as suggested by @xgman. My symptoms were that Logic was responding to MIDI keypresses on the S61 Mk2 keyboard, but none of the S61 transport controls were working (play, record, up/down a track, rotary encoder moving the playhead, etc). I deleted the keyboard from Control Surfaces > Setup, quit Logic, deleted the plist file, and loaded Logic again.
  11. Yeah but I don't see BIP'ing the offending track as a solution to this issue, it's a workaround (which I'm grateful for you suggesting btw, don't get me wrong). I don't want to have Logic doing this randomly, and to have to BIP all tracks preventatively, or just the problematic ones. Logic shouldn't do this in the first place, surely? I guess I should clarify something - this doesn't happen every time I bounce the track. It's seemingly random - about 50/50 if I had to guess. Further testing: Bounced out only the first 1m15s (55 bars or so) and the issue did not occur. Repeated this partial bounce again, and it was again fine. Then I bounced out the full song and the issue did occur. Bounced out the full song a second time and it did not occur.
  12. Hi @triplets, thanks for the idea - I presume you meant to BIP the bass track to see if the issue occurs on the bounced version. I just tried BIP'ing the track with 'mute original track' and played it back, and it's playing as it should, i.e. no unwanted pitch-bend going on.
  13. Hi all, I've got a Logic Project that has some synth notes that are pitch-bent midway through the song in a kind of -12 steps bass-dive - I've done this by drawing automation in the MIDI region. Immediately after that bass dive the pitch bend is reset back to 0 so the bass is back to its original pitch. When I play it back within Logic it sounds fine. But when I bounce it out to AAC and play it back, the first bass notes that appear in the song are bent down -12 steps. These first regions that are pitched down incorrectly have no pitch bend automation in them. I could just insert a PB automation node with a value of zero at the very start of the first MIDI region for this instrument, but I'd rather figure out why this unwanted behaviour is happening so that I can learn from it and avoid repeating whatever mistake I may be making! The setup: Logic version: 10.7.5 running in Rosetta mode OS: Ventura 13.0 Hardware: MacBook Pro 2021, M1 Max 32 GB mem. SW instr plugin: Reaktor 6.4.3. Reaktor ensemble = FM4 (one of the Reaktor Factory Library synths) Other info: I'm using offline bounce Let me know if I can provide any further info.
  14. @David Nahmani All I did was record some notes using the keyboard keys, I didn't touch any of the other controls. But yes the M32 is probably configured as a control surface - I didn't configure anything explicitly though, all I did was install all the NI software, plug in the keyboard then fire up Logic, and Logic popped up a dialog box, I think it was a control surface configuration dialog. I just noticed after changing my Control Bar display to include MIDI In/Out data, that this SysEx is appearing every 1.5-2.0 seconds, even when nothing is playing - playhead stopped, no keys being pressed, nothing happening. See attached screen recording. @briansin I will open a case with NI and see what they say, but I'm not gonna get my hopes up - they must have a constraint on tech staff, judging by how long it's been since the M1 was released, yet all of their products bar one are still Rosetta-only. Screen Recording 2022-07-10 at 10.43.19 PM.mov
  15. I bought an M32 recently and have also just upgraded to a new M1 MacBook Pro, and just recorded some MIDI and noticed these "X" marks in my regions, and "Mackie Designs" SysEx messages (I'll attach a screenshot of one bar of 4 notes recorded on the beat). There's not many Google search results for this issue - if I do a search for 'M32 Logic Pro SysEx "Mackie Designs"' then I only get three relevant and one irrelevant result - which says to me this is a rare issue. I've been using a Komplete Kontrol S61 for a few years now on my two previous Macs and never saw this issue. @briansin did you ever find a resolution to this issue? I doubt it's a bug, since two years have passed since your post, if it was a bug I'd have expected NI to resolve it by now, and I'd expect to see way more hits on a Google search. And it's interesting that I'm seeing this issue on a fresh MacOS/Logic/Komplete/NI install - everything was downloaded & set up from scratch, no use of Migration Assistant from the old Mac, the only data copied across was my Logic projects. I guess it's not causing an actual issue? @David Nahmani is it safe to filter out these events via Project Settings > MIDI > Input Filter > SysEx? Or will that actually prevent the SysEx messages communicating with the Komplete Kontrol plugin? I guess what I'm after is a way to allow them to be received by Logic but not recorded into the region. But if this is a harmless thing that just looks weird ("X" marks in the region) and clutters up the event list, then I guess it's not functionally (or musically) detrimental?
×
×
  • Create New...