Hi all,
I was doing my research and in an earlier thread: viewtopic.php?p=239300#p239300 Our member @Funkybot mentioned that, MFT and SO don't seem to communicate well. Same thing's also stated in a vid's comment section: "Just bought it and I thought I was doing something wrong because the knob's position in the midi fighter did not change when I switched between channels. It is a realy big pain in the bleep, I might say. I did expect it to be bi-directional, other wise I don't seem to understand how it is useful in a mixing situation if anytime you open a channel, you need to re-mix it and start all over with the parameters. that's really strange and a big disappointment. because it is a very smart controller and the idea of the colors is very cool. " https://www.youtube.com/watch?v=QzqDm1WHp8w And I'm wondering if this problem is successfully sorted out, 'cause it's probably the main determining factor for buying MFT. Hope to know you guys' insight. regards, Seb |
Create a Studio One device for the Twister using this XML. Does that help? The trick another user turned me onto was that you had to separate the knobs and the feedback from what I recall, and that it had to be done in the XML.
On Windows, this is located under: users\AppData\Roaming\Presonus\Studio One 5\User Devices
AMD Ryzen 3950X, ASUS Creator x570 Mobo, 32GB HyperX Predator RAM (3600mhz), Radeon™ RX 5500 XT 4GB GDDR6 graphics card, RME Fireface 800, Windows 10 Pro, Studio One 5, Reaper 6, Cubase 10.5, Avid Artist Mix (EuCon please), Behringer X-Touch One, MIDI Fighter Twister, various other MIDI control surfaces and hardware instruments
|
Funkybot wroteCreate a Studio One device for the Twister using this XML. Does that help? The trick another user turned me onto was that you had to separate the knobs and the feedback from what I recall, and that it had to be done in the XML. Hey, I haven't got me an MTF and am just doing my research before buying. But after making sure that you had modified the script with success, I'll place the order and do the rest. |
sebastianchan wroteFunkybot wroteCreate a Studio One device for the Twister using this XML. Does that help? The trick another user turned me onto was that you had to separate the knobs and the feedback from what I recall, and that it had to be done in the XML. I'm pretty sure it works. I don't visit Studio One much these days at all as I've been working in Reaper-ville but from what I recall, making the changes to the XML above got things working. If you want to see crazy sh*t with the MFTwister, you should see what I'm doing with Reaper + the CSI extension. I have an iPad running TouchOSC that mirrors the Twister and adds multiple display labels. So I can control a bunch of Reaper actions from the Twister, map effects, use the hardware to twist the knobs but have display labels and feedback on the iPad via TouchOSC. I'm using that with a Eucon Artist Mix, and an X-Touch One, and they all act as an integrated setup. And everything stays in sync and happens instantaneously. It's sick. No DAW has the level of control surface integration as Reaper+CSI does. CSI is open source too BTW. I think of more DAW-makers knew about it, they'd seriously look into building it into their own DAWs. That's just a friendly hint in case any Presonus developer is curious.
AMD Ryzen 3950X, ASUS Creator x570 Mobo, 32GB HyperX Predator RAM (3600mhz), Radeon™ RX 5500 XT 4GB GDDR6 graphics card, RME Fireface 800, Windows 10 Pro, Studio One 5, Reaper 6, Cubase 10.5, Avid Artist Mix (EuCon please), Behringer X-Touch One, MIDI Fighter Twister, various other MIDI control surfaces and hardware instruments
|
Just heard of CSI now, after some googling it does look beautiful. Wish PreSonus would implement it soon. Incidentally I found that Hexler just released the brand new version of TouchOSC this month, in case you've missed out. The older ver. is now called mk1.
https://hexler.net/touchosc |
Users browsing this forum: dougasherman, Tacman7 and 12 guests