Reaktor plug in3/1/2024 ![]() dll where it actually was, it just installed a whole new instance of Reaktor where it felt like doing. This meant that when Access wanted to update Reaktor, instead of actually updating the. The thing is, when I was installing NI VSTs myself, I was directing them to install into specific directories so I could actually find them later, and to make them easier for apps to find in the Windows labyrinth Native Access installs things wherever it decides is best and you just have to shut up and take it. Everyone and their pet moose these days is trying to get you to use their plug-in managing app, and NI is no exception. Well, one thing that's happened between me getting Reaktor and me getting TRK-01, aside from Reason becoming able to use VSTs, was Native Instruments pushing its Native Access app onto me. That could account for why it wasn't loading the TRK-01 ensemble, which might need the latest Reaktor updates to work. For some reason, Reason was loading an older version of Reaktor. Then I opened Reason up, put Reaktor in the rack, and checked its version again - 6.0.1. So I opened Reaktor and in standalone mode, checked its version - 6.2.2. What NI had wanted the guy to do was check which version of Reaktor was running in Maschine. The NI staff had answered, with a preliminary inquiry, and although the person never replied, it was at least a clue. Google and a search of this forum didn't show anybody else having a problem with TRK-01 or Reaktor in Reason, at least not like mine, so I was feeling stumped - until I stumbled across half an entry on the NI forums where someone else was complaining about not being able to load TRK-01 inside Maschine. I was beginning to think there was something about TRK-01 that was completely incompatible with Reason somehow, but that didn't quite make sense - as long as Reaktor itself worked in Reason, it shouldn't matter what the ensembles do. I quit Reason and then ran Reaktor by itself. I loaded a different ensemble - Skanner XT - and that worked just fine. Manually, I located the place where the demo copy had been installed and tried to load that - also no go. I had run the demo in standalone mode just fine months ago, couldn't figure out why it wasn't working here and now. So I started Reason, put an instance of Reaktor in the rack - no problem so far - and then tried to load the TRK-01 ensemble.Īn error message appeared - "problem reading trk-01.ens". Well, TRK-01 is one of NI's "needs to run in Reaktor" synths, just as a number of their other devices need Kontakt. But for Black Friday, I bought TRK-01 for half price, which I'd demoed before, and thought I'd see how it worked out in the rack. So I've had Reaktor for a while, and a clutch of other Native Instruments things, though since Reason started I hadn't really used it directly in Reason for much of anything. Since part of it had to do with how Reason handles things, I figure there's a chance it might come in handy to one of you someday. I came across an interesting problem, and managed to fix it, but for a while it was confusing and frustrating.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |