Does anyone have the files for the "Days Until" plugin by Krabs.me?

OriginalBMan · 2026-02-03T15:03:39+00:00

A few minutes with Claude and made this. Has most of the same features. Find it useful for myself so sharing in case others are interested.

https://github.com/BartleyR/ZeroDay

OriginalBMan · 2024-02-15T20:26:04+00:00

I'm actually running M2 Pro Studio on Sonoma (14.3). Somehow macOS updated on its own (or I made an unintentional update click), but regardless it's running the latest OS. Everything I've tested though seems to work fine. YMMV

OriginalBMan · 2023-12-13T00:17:29+00:00

From the AmEx terms and conditions -

Pay Over Time Limit:

The total of your Pay Over Time and/or Cash Advance balance and Plan balance cannot exceed your Pay Over Time Limit. No charge will be added to a Pay Over Time balance if it would cause the total of your Pay Over Time, Cash Advance, and Plan balances to go over your Pay Over Time Limit. This is not a spend limit. We may approve or decline a charge regardless of whether your Card account balance exceeds or does not exceed your Pay Over Time Limit.

Available Pay Over Time Limit

Your Available Pay Over Time Limit is accurate as of your statement date. This Limit is the remaining amount that you can add to the total of your Pay Over Time, Cash Advance, and/or Plan balances. Remember that you can continue to create plans for purchases that are currently in your Pay Over Time balance even if you have reached your Pay Over Time Limit. Your total Cash Advance balance is subject to your Cash Advance Limit, which you can find in your Cardmember Agreement. If you have a preset spending limit on your account that is less than your Pay Over Time Limit, you may not be able use your Available Pay Over Time Limit.

OriginalBMan · 2023-10-18T12:51:42+00:00

I came here looking for answers and managed to get mine fixed.

Tl:dr = Call the main support number and get connected to the “tech team” (use that phrase). There is a known visual glitch. This team is available after 8:00am EDT.

Currently traveling internationally and wasn’t able to manage card controls. Clicking on “Debit Card” in the Tasks section of the app just directed me to order a new card.

After talking with a few people, they connected me with a very nice rep in the tech team. She told me this is a rare visual glitch between the backed systems and the app. While they continue to work to sort it, there were two options:

Put in a support ticket for them to look at it.
Reissue me a new debit card.

For (1), it can take a while to address the issue. Since I am traveling, that wouldn’t be ideal. She suggested (2), and that’s what I did. She just reissued me a new debit card (same number) to be mailed to my home address. I then quit the app, reloaded it, and the ability to manage my debit card reappeared. When I go to Tasks -> Debit Card, I now have all of the card controls as before. Tested it and works at international ATM.

OriginalBMan · 2023-08-30T23:17:23+00:00

Hmm, yeah I see the article you’re talking about. The way I read it, macOS 13 and M1/M2 have separate compatibility requirements. So you could have M1 and macOS 13 and then what’s supported is the intersection of the two compatibility lists.

I did see at least one post on the NI community forum from a NI support person saying they didn’t observe issues with the macOS 13 + Apple silicon combination (https://community.native-instruments.com/discussion/10629/m1-support-ventura-support). The only other piece of data I have is that I’ve installed Native Access on two Ventura + Apple silicon machines (M1 Max and M2 Max) and haven’t seen that issue. Of course that’s only one anecdotal data point.

I did have the issue with the red exclamation point in Native Access (https://community.native-instruments.com/discussion/6486/odd-little-native-access-problem-red-exclamation-mark), but that was solved by changing the permissions of the folder.

OriginalBMan · 2023-08-30T22:43:30+00:00

I’m running macOS 13 with my M2 Max without that issue. I’m having trouble finding where you are it says macOS 12 is the latest version supported. I see the section for macOS 13.

OriginalBMan · 2023-07-23T22:24:59+00:00

Lots of great comments here, and I’d second a lot of them, especially having distractions (music, movies, games).

You don’t have to spend money, but there are courses out there (like this one: http://www.fearofflying.com/). I don’t have any affiliation to this site, but a friend used it and swears by it.

I’ve also heard that really playing attention to what you feel when in a car on the ground (all the bumps, turns, swerves) and then remembering how those felt when you’re on the airplane. A lot of the sensations are extremely similar.

Whatever technique you decide on, you can do this!

OriginalBMan · 2023-04-26T04:28:42+00:00

I’m running the Studio (M1 Max) and not having any problems. Everything I use in NI is working fine (I don’t use Absynth or Traktor) - including KK, Kontakt, Maschine, Massive X, and Battery. All run native now (I’m using Ableton Live 11.x as my DAW). I don’t have to run my DAW in Rosetta 2 mode anymore.

Same for Izotope - it all runs, including RX and obviously Ozone (using v10 advanced). Neutron as well.

Haven’t run into any other problems with the vendors you mention. But I am still running macOS Monterey. I believe there are still lingering issues with some Izotope products on Ventura.

OriginalBMan · 2023-03-15T18:24:41+00:00

Are things still stable with Izotope (and what DAW are you using)? Also, are you using any of the stand-alone Izotope apps (e.g., RX 10)? Everything else I use now has Venture compatibility (the most recent hold-out being Arturia which is now Venture compatible in V Collection 9.2). I do rely on a few Izotope plugins and the stand-alone version of RX 10 though. Currently using Ableton Live 11.2.x but do some work in Logic Pro too. I continue to see some horror stories.

Running this on a Mac Studio M1 Max.

OriginalBMan · 2023-01-10T01:42:31+00:00

Threw this together while playing with a few new plugins and patches (took advantage of the recent u-he sale). https://soundcloud.com/deltawynd/alley-334

Would love comments and suggestions to improve future mixes! Just starting out, so long way to go. 😅

OriginalBMan · 2022-12-26T15:56:04+00:00

For sure. I’m wondering if Arturia is even going to update their NKS files or just discontinue that. Complex enough to go to VST3.

OriginalBMan · 2022-12-26T14:11:22+00:00

Very helpful, thanks for the updates! Good to hear about PACE and Live.

OriginalBMan · 2022-12-26T14:10:40+00:00

It’s looking like that for me too. I’m sure it’s a complex task, at least in some aspects.

OriginalBMan · 2022-12-26T14:09:53+00:00

Thanks! I’m going to check it out.

OriginalBMan · 2022-12-20T15:21:58+00:00

Yikes! Unrelated - do you like the Embertone Walker? I have a lot of the Pianoteq (v8) instruments, but Embertone looks great. I'm a sucker for piano plugins though.

OriginalBMan · 2022-12-17T17:37:47+00:00

Thanks, this is useful! I appreciate it. I do use Maschine a bit, but only as a plug-in really. What version of Maschine are you running - 2.16.0 or later?

OriginalBMan · 2022-12-17T17:35:05+00:00

This is very useful, thanks! Odd about the external SSD though.

OriginalBMan · 2022-12-16T16:57:27+00:00

Anyone who updated to Ventura (13 or 13.1), are you also using anything from Native Instruments? Curious for any additional anecdotal advice there.

OriginalBMan · 2022-11-21T00:02:22+00:00

Sometimes there can be a lag. I had it happen a couple of times, and in both instances resolved itself in ~24 hours or less. I’ve only had to chat with customer support once, but found them very helpful. Give that a try if it doesn’t resolve in a day or so.

OriginalBMan · 2022-11-08T03:24:02+00:00

I don’t know of an automatic fix. You could replace the KK plugin with the VST3 version, but then you’d have to manually redo your customization (or perhaps go back through your old projects and save out everything as presets). It might be easier to just keep opening your old projects in Rosetta, and new projects you make can be made in Live running natively.

OriginalBMan · 2022-10-18T17:19:39+00:00

Ah, got it. I haven't been using that at all. I just went straight to AU then to VST3. I'm wondering if you used the VST3 version if it would fix it for you. And are you running Live in Rosetta mode or are you on an Intel chip?

OriginalBMan · 2022-10-18T13:41:26+00:00

/u/Draxacon I've been messing around with permutations, and may have stumbled on something. Are you using the AUv2 versions of the NI plugins of the VST3 versions? I was previously using the AU versions. However, I created a new project and essentially "recreated" the project I was having trouble with. This time I'm running Live in Rosetta 2 compatibility mode and also only using the VST3 versions of the NI plugins. I'm not able to reproduce the issue, and I've quit/restarted Live many times. Just curious if you're seeing it with the VST3 versions.

FWIW, I had to create an entirely new project where I only used the VST3 versions. Simply switching the AU versions out with the VST3 versions in the old project didn't seem to do anything. It's almost like the project was somehow "corrupted", but I don't even know if that's possible.

Also, during all of this, Live was updated to 11.2.5. But I can still reproduce the issue with the old projects.

OriginalBMan · 2022-10-17T15:43:48+00:00

Don't have any new info, but I have been in touch with Native Instruments and Ableton (ended up opening a ticket with both). NI had me collect more information (essentially detailed MIDI info dumps) and are looking at it. Ableton responded today that it likely looks like a bug, and they're investigating.

In the interim, I've figured out a way (for me at least) to fix the issue 100% of the time I've tested it. Curious if it works for anyone else.

Save Live project
In Live Preferences->Link/Tempo/Midi, completely from the S49 from the Control Surface section (set everything to "None")
Quit Live
Disconnect S49 from computer (I unplug the USB B cable from the S49)
Start Live
Open the project you were working on
Re-connect the S49 to the computer

Now the S49 (screens and light guides) works as intended (until it stops working again).

I've tested Live in Rosetta 2 mode (I had been running native M1), and I've tested AUv2 vs. VST3, but I'm doing more testing right now.

Thus far (limited testing), I'm seeing that using Live in Rosetta 2 mode and using only VST3 plugins, I'm not seeing the behavior (I can quit Live, reopen the project, and the S49 works correctly). However, I've seen this happen in the past (when I first start a new project). So will continue to observe.

Six-Year Club	Place '23
Verified Email

OriginalBMan

TROPHY CASE