FYI...DP 11.01 is out

[dewdman42]

Based on your assumption that Rewire support is built into CoreAudio, you are also assuming that CoreAudio does not provide a way to disable Rewire.

Ableton Live 11 did disable it, so there must be a way.

[dewdman42]

I think I am just now realizing for the first time that Michael Canavan and Mike halloran are two different people...my apologies if I have conflated posts from both of you, as coming from the same person.

[HCMarkus]

Mic Drop

[Tritonemusic]

EasyFind requires Indexing to be turned on and completed before it can locate anything.

Not according to them.

Here's the first paragraph of the "Read me" section from EasyFind:

Thank you for using EasyFind. EasyFind finds files, folders or contents in any file without the need for indexing. This is especially useful if you are tired of slow or impossible indexing, outdated or corrupted indexes, or if you are just looking for missing features like case sensitive or insensitive search, Boolean operators and wildcards or searching for phrases.

[Michael Canavan]

Mike you're wrong about this one

DP communicates with Rewire through CoreAudio. If it supported RW directly, it would work over Windows. It doesn't according to the DP manual.

How many ways must I rewrite that?

You can write it as many ways as you want to, it doesn't make it true.
DP is not magically protected from the Rewire code in your system by core audio.
DP has to be able to communicate with rewire to use it, i.e. DAW makers had to tweak their DAWs to use rewire in the first place. Rewire is not using drivers in Windows but none in Mac OS.

Rewire is not somehow incapable of messing up a DAW when it's deprecated and it starts acting up on various peoples set ups, and that's the part where you being wrong about it being sandboxed in some way by Core Audio and MIDI matters.

[Michael Canavan]

Based on your assumption that Rewire support is built into CoreAudio, you are also assuming that CoreAudio does not provide a way to disable Rewire.

Ableton Live 11 did disable it, so there must be a way.

Reason 11 disabled rewire support. The developers of Rewire took out support from their own DAW.

Out of curiosity rewire was introduced into DP with v2.7. they announced support for it.

[richhickey]

The term "malware" refers to software that is intended to harm or disable computers. It shouldn't be tossed around lightly by disgruntled users experiencing problems/bugs.

[dewdman42]

my malware detector marks all kinds of things as malware that simply follow certain patterns and there is no knowledge about the actual "intention" of whoever made it... Malware causes harm, regardless of the intent.

Rewire is currently causing harm to DP 11.01's stability. I'll call it malware all day long.,..that's what it is at this point. Rewire also has the attribute of showing back up automatically when you run certain programs like Live 10 (which we could I guess call a malware-generating virus. hehehehe

lighten up folks.

[richhickey]

Rewire is currently causing harm to DP 11.01's stability.

So, the only thing you change on a system is DP 11.0 -> 11.01 and it's Rewire that "caused" harm? Magically? Nope, DP introduced a bug (in whatever Rewire support they had). Had they not, you likely wouldn't have even noticed DP's Rewire support.

VST2 is similarly deprecated - did Steinberg magically go onto everyone's computer and remove/break things? No, they can't, nor can Reason. Similarly if DP introduces a bug that causes it to fail given a certain VST2 plugin, does that plugin become "malware"? Nope. If X changed and things broke it's X's fault. Here X is DP 11.01.

You can call bugs malware and tomatoes potatoes, doesn't make it correct.

[dewdman42]

bla bla bla, I'll call it what I want. the rewire malware causes DP 11.01 to crash on my system... Live 10 will automatically reinstall that malware after you have removed it.

So, the only thing you change on a system is DP 11.0 -> 11.01 and it's Rewire that "caused" harm? Magically? Nope, DP introduced a bug (in whatever Rewire support they had). Had they not, you likely wouldn't have even noticed DP's Rewire support.

Yes Rewire is the cause of the crash.... The mere presence of the rewire driver on the system causes DP 11.01 to crash.

combined with MOTU not officially supporting it any longer despite the fact that it in the user manual. Could MOTU fix it to support it still in legacy mode? Yes I believe they probably could, but they seem unwilling to do that at this time and very much agree with them too, I wouldn't waste one minute trying to support Rewire in 2021 and beyond if I were them. Since this malware now causes DP to crash, even for people that have no intention of ever using it...they should update DP to ignore it entirely. Or else support it by fixing it.

Too bad for you, if you want to continue using this malware you might try a different host that is supporting it better.


By the way, VST2 is not deprecated for those people that have licenses, including DAW's that continue to support it. What is the case with VST2 is that new developers can no longer obtain licenses to ship VST2 plugins.

Also, Steinberg does not ship any no-longer-supported binaries related to VST2...it is a source level SDK. Steinberg themselves continue to ship hosts that officially support VST2. There is no dependence on any no-longer-upated-binaries, as is the case with Rewire.

that is poor analogy and I don't really understand this needless argumentation.

[cuttime]

Has anyone used the new Nanosampler yet? They seemed to put a lot of effort into it. I keep meaning to check it out, but keep forgetting it's there.

[Michael Canavan]

So, the only thing you change on a system is DP 11.0 -> 11.01 and it's Rewire that "caused" harm? Magically? Nope, DP introduced a bug (in whatever Rewire support they had). Had they not, you likely wouldn't have even noticed DP's Rewire support.

This is just wrong. The entire industry is going away from rewire, Reason 11 itself released two years ago does not support Rewire, the company that made rewire doesn't want to burden itself with rewire support. In contrast Steinberg still supports VST2 in Cubase.

Rewire itself hasn't seen an update in years, you cannot download it from reasonstudios.com, and there are almost zero references to rewire on their site. Rewire will not be supported or get any help for any new OS, and I doubt Big Sur or even Catalina is supported. In no way is any of this on DP. DP did not introduce a bug in 11, it exposed bugs due to lack of updates for years on end now that rewire has accumulated.

I was an early adopter of rewire, Reason 1.0 into DP 2.7. It worked great, but it's effectively dead, and it will continue to cause problems on your system.

I'm actually curious now? I have the notorious crash on quit bug where DP thinks you quitting the program means it's crashed, started in version 10. This could be due to rewire, going to removed it from my system and see what happens.

[Michael Canavan]

Has anyone used the new Nanosampler yet? They seemed to put a lot of effort into it. I keep meaning to check it out, but keep forgetting it's there.

It's cool, the fact it can use the ZRX pro engine can be dangerous!

My only complaint is the same with all native MOTU plug ins, they're tiny, and not resizable. Can't believe they didn't use remaking it as an opportunity to have it scale.

[seamonster]

Automation control point bug fixed yet? I’ve poked around in Motunation for 45 minutes, without joy (not least because “bug“ is too short to be used as a search term). I don’t see it mentioned on the list of new fixes in DP 11.

Since DP 3, when you add a new automation control point at the same value as an adjacent point, it’s often not precisely the same value. For example, if the proceeding point is value -6, the new point might be value -6.05. This produces inadvertent, unwanted "micro ramps" in automation. If you put many automation points in a track, discrepancies can accumulate.

The degree of inaccuracy is affected by the vertical zoom of the track — the taller the track on screen, the more likely the point inserted will be accurate. So either you have to be constantly resizing track heights, or manually typing in individual control point values.

Over several decades, this one bug has wasted probably several months of my life, total. Many others have discussed it in the past; Scott Fraser has been one, as I recall. It kept me from upgrading from DP 4 for a long time, till I finally jumped to version 9 when it came out (as there were new features that made the upgrade worthwhile, despite). I’m now still on DP 9.52, and pretty certain that I will never upgrade until the automation control point bug is finally fixed.

Someone please tell me that it has been fixed — in v.10, for example — so that’s why no one seems to be still talking about it. (There should be a “fingers crossed“ emoji.)

Best,
Hoagie K Hill

[bayswater]

when you add a new automation control point at the same value as an adjacent point, it’s often not precisely the same value. For example, if the proceeding point is value -6, the new point might be value -6.05.

What exactly are you doing to add the second automation point?