After a long time, I started "Reason Rack Plugin" and played with it, and now I can do MIDI out from "Beat Map" etc.
(Previously, Player devices like BeatMap couldn't MIDI out)
Release NotesIf you look at it, it seems that you can do it in 11.2.
So, "Beat Map" by UJAMBeatmaker seriesIt is quite good to use it in, so it is an introduction.
ReasonStudio has other MIDI devices, and you can follow the same procedure for other devices.
It is like this.
Also, using "Dual Arpeggio", it looks like this.
First, play the MIDI data as it is, and then play it from "Dual Arpeggio" to change the preset.
Let's explain how to do it.
How to MIDI out from a Player device such as BeatMap of Reason Rack Plugin
It's very easy to do.
Since the Reason side has responded, it is the same as before.
First, start "Reason Rack Plugin".
Click the circle in the upper left to display the browser.
Double-click "Beat Map" from "Players" to load it.
MIDI Port settings
Set "Output port" of "MIDI" to "0" from the gear icon on the upper left.
Open the sound source to which you want to send MIDI information.
Here is Beatmaker's UJAMHUSTLE 2I used.
Set "Input port" of "MIDI" to "0" from the gear icon on the upper left.
Now you are ready to go.
Match the drum map
By default, the drum map is different, so adjust as needed.
(Even if it doesn't match, it may feel pretty good, so it's not necessary to match it.)
The setting can be changed by dragging the red frame part in the figure below.
HUSTLE 2In the case of, I think the following is fine.
Summary
The Reason Rack Plugin is pretty good to use as a sound source.
However, Reason 12 has been integrated into editions and the Suite has disappeared, leaving only Reason 12 ($ 549) or Reason + subscription + ($ 19.99 / month, $ 219 / year).
I wonder if there is only a choice of subscription or all.
As I have written many times, I think that the number of users will not increase unless the subscription is issued with a voucher like Rent To Own or according to the subscription period.
As a major premise, it is necessary to create attractive products, but if we continue to introduce new products while issuing vouchers, users will not leave.
(I'm happy with that and continue to use it)
Comment
It's a dry season, so please be careful about your physical condition.
Regarding information sharing, I mentioned earlier that Bitwig can recognize Serum presets, but I did not understand even if I looked it up, so when I contacted, "Bitwig recognizes VST presets in .fxp format, so it is a plug-in. The behavior depends on the extension of the preset. "
I didn't write this officially, but it was mentioned on GitHub. When I looked it up, fxp is the standard format for VST presets.
https://github.com/bitwig/dawproject
Sylenth 1 mentioned earlier is also in .fxp format, so I think it can be filtered and switched from the Bitwig browser.
However, I don't have it, so I can't verify it.I'm sorry w
Thank you for your concern.
Thank you for the information!
So that's it! Is it from fxp?
What about fxb?
(It seems that you have a table of which plug-in to associate with internally)
I'll give it a try with the demo version.
yosi
Hello.
It is NM of FL beginner.I'm playing while touching FL studio little by little.
It's not Reason this time, but I got stuck when using a plug-in that becomes a MIDI generator.In my environment (Mac), the plug-in was installed in AU (because I used LogicProX originally). I don't use VST, so put it all in the trash.I was struggling, but I learned last night that the AU plug-in doesn't support MIDI out.
If you look closely, plug-ins that you can't read if it's AU (Waves is annihilated) are also flickering.
I wonder if the seniors who are using FL on the Mac that can come here have VST installed. All you have to do is include both AUs, but I want to make the system as light as possible (I think it's more stable because of my age).
It may be rude to ask here because it is different from yosi's environment, but I would appreciate it if anyone could tell me.
NM
Hello.
I did some research, but it seems that there are quite a few DAWs that do not support MIDI with AU.
(AUv2 is not supported and Auv3 is supported in the first place)
Also, there were many opinions that VST is better except for Logic.
Also, since VST is cross-platform, you can open Song files created on Mac with Win if the same plug-in is included.
In my opinion, I think it would be good to include the VST version only for plug-ins that require MIDI out.
Other than that, if you use a plug-in like Blue Cat's PatchWork, you can do MIDI routing etc. in PatchWork.
(There is a demo version, so please give it a try)
You can answer in more detail by entering the specific plug-in name.
I've never used FL on a Mac, but I've also used Logic on a Mac, and I've used Ableton Live, which can use both AU and VST, so I'll answer.
In conclusion, be sure to install the VST version.
There are some DAWs for Mac that support reading of both AU and VST, but basically you should think that reading AU is a bonus.
Because, as you know, AU and VST have very different designs, especially around MIDI out, so if you don't design a DAW for AU, it won't work.
In the case of Logic, there is no problem because it is designed to be inserted as a MIDI FX plug-in, but FL, Live, Studio One, etc. are not designed to be able to insert AU as MIDI FX, so full functionality cannot be used. Hmm.
DAWs for Windows can only use basic VST and AAX, so they are not designed for AU.Basically, think that Logic is the only DAW that can use AU.
Native Instruments also says it's better not to use the AU version.
https://support.native-instruments.com/hc/ja/articles/360003070777-FL-STUDIO-20%E3%81%A7%E3%81%AE%E3%83%97%E3%83%A9%E3%82%B0%E3%82%A4%E3%83%B3%E7%AE%A1%E7%90%86-Mac-
However, as a concern, installing both AU and VST can cause your DAW to behave strangely.
This is caused by scanning plugins, so let's set AU plugins not to scan.
As long as you are using FL, you do not need AU, so you can install both and ignore AU in FL and use VST. (I checked it lightly, but I didn't know how to set it in FL, so I'll throw it to yosi-san.)
It takes up a little space, but the really heavy files are shared by VST and AU, so it's not as tight as you might think.
Using AU with FL is more likely to be unstable, so it's a hassle, but let's reinstall the VST version!
Thank you for always providing information.
I didn't know that AU was like that.
It feels like it's only for Logic.
(Mac users wondered if the AU version would be better)
yosi
good morning.How are you feeling?
Thank you for your reply.
It was reMIDI2 that got stuck in MIDIout, but of course the PhaseBox didn't work either.I did VST for these two first, but I couldn't receive MIDI with the AU sound source (Spire, Phaseplant), so I made VST and it worked fine.
For the sake of organizing, I re-inserted the things I often use, and settled down.
Since my current PC is old, I'm thinking about buying a new one, but moving the environment seems to be difficult, so I can't help myself.
NM
thank you for your reply.
Thank you for your concern.
I got a lot better when I got a sleep.
(Sleep is important, isn't it?)
It seems that it is useless if you take too much caffeine, so I will manage it steadily without overdoing it.
After all it seems better to think that the AU version is exclusively for Logic.
A fan of this site gave me information, but it was said that the VST version is essential when using a DAW other than Logic when using a Mac.
Also, as Mr. NM is concerned, it seems that the coexistence of the AU version and the VST version is not good, so it was the view that it would be better to use only the VST version in FL Studio.
To disable the AU version in FL Studio, you should have specified the folder where the AU plug-in is stored in "Plug-in Manager", so if you remove it, it will not be recognized.
This is really troublesome, isn't it?
You can organize plugins that you don't need when you move the environment, but it will take a considerable amount of time.
It would be nice if the plug-in could also be managed in the cloud, but it seems that such an era is still over.
yosi
Fans of this site
Hello.
thank you for your reply.
I'm still lacking in study.It was very helpful to teach me this time.
It seems that few people are still using FL studio on Mac, and the information is a little (I wonder if I'm weak ...).
It's embarrassing to be an amateur, but please tell me again in the future!
Thank you.
NM
thank you for your reply.
Don't worry about it before.
I don't know Mac at all, so I learned a lot this time!
(M1 seems to be doing well, so there is a good chance that it will change to a Mac in the future.)
Thank you for your cooperation.
That's not the case at all.Personally, I would like to evaluate just by choosing FL.
Japanese information cannot beat Cubase, Studio One, and Logic due to the number of users.
I think that I am motivated to learn when I decide to use FL without compromising.
By the way, the information about Audio Units and VST this time is not strange.
I'm a non-Mac user, but yosi misunderstood, and of course I used AU for somehow at first.
For example, even if you search for "audio units vst difference" in Japanese, you can't find an article that mentions MIDI routing.
I'm not sure about the CPU usage rate, but I'm verifying it.
By the way, it is better to avoid not only the coexistence of VST and AU, but also the coexistence of VST2 and VST3 plug-ins of the same manufacturer within the same project.
It can't be helped if only one is prepared, but Melda mentions in the manual that the VST3 version and the VST2 version should not be mixed.
Also, I think it's completely meaningless to determine which of VST2, VST3, and Audio Units, which I mentioned a little above, is superior.
First of all, as a major premise, plug-ins are compatible with DAWs.The last page of the various Melda manuals mentioned above also describes bugs for each DAW.
The Oeksound support page details the issues that occur in each DAW and the issues in each version of VST and AU.
https://oeksound.com/articles/known-issues/
In other words, different DAWs will cause different problems, so the correct answer is to verify if you think something is wrong.
NM's action this time is correct.Nothing is perfectly superior.Everything is compatible.
However, it takes a lot of effort to verify each one, so I think it's better to verify "if you think something is wrong".
For example, the sound is strange or the CPU usage is abnormally high.
NM has Logic, so I think it's better to compare the behavior between FL and Logic.
If you think something is wrong there, ask yosi-san and I think it will be solved.
I don't have FL so I'm sorry to throw it at the end w
Finally, I think that the difference in the specifications around MIDI between AU and VST should be known a little more.
It doesn't move, but it changes.
yosi
Fans of this site
Good evening.
Warm words will be absorbed in your body.
Even if you don't scan AU with the plugin manager, it will scan for some reason ...
I also saw the manual (it says that AU does not have MIDI out here ...), but there seems to be no way to ignore it after scanning.
So once I put out the component folder that contains AU, I can not read this as expected, but it seems that some of the plug-ins attached to Logic are in a different folder, so I went to read this for some reason It was.
I restored the component folder and started Logic, so I will try it for a while.
Thank you very much!
NM
Hello.
I wonder what it is.
It may be because some Paths cannot be disabled.
After that, even if I scan it, I think that there is no choice but to avoid using AU without registering it as a favorite.
Really.
It is also written that basic VST is better.
And since it seems to scan AU plugins by default, I think it is better to select the VST version when registering in the Plugin Database.
If you have to mess with the directory, you may not need to be that nervous.
At least the FL itself doesn't think it's going to cause any major problems with scanning, or it's designed to be free of problems.
In the case of Ableton Live, a simple scan is always included at startup, so there is an option to disable scanning, so I said that it is better to disable it.
If you can't disable it without overdoing it, it may not be stable.
As yosi says, if you can set the database to start the VST version instead of the AU version, that's okay.
By the way, this is not possible with Ableton Live, but w Bitwig is possible.
FL is the design concept of specifying in the database, and Live is the difference in the idea of disabling scanning.
Personally, VST3 and VST2 are mixed, so I think FL and Bitwig are smarter than Live's method.
I tried Bitwig for a moment, but it's amazing.
I'm not used to the operation, so I could see the Sylenth 1 presets normally.
Sylenth 1 is light and very good for using presets, but it's a legacy specification that doesn't have a preset browser for a few minutes.
It is a great advantage to say that it is easy to use.
Also, assigning LFOs is very easy.
I will consider the introduction.
(When is the next sale?)
Oh, did you load the Sylenth 1 presets as expected?
I heard that it's not very easy to use, so I didn't buy it, but when I bought the Serum presets, the Sylenth1 presets accumulated, so I was worried about it.
I can't expect an update and the sale doesn't seem to be enthusiastic, so I don't know if I'll buy it, but the sound looks good so I'll consider it at the next sale.
The LFO assignment is good, isn't it?Thanks to that, Melda's modulator is almost untouchable.
Melda is the top of the complex LFO, but Bitwig has a great design because you can easily add an LFO to the LFO and move the LFO parameters with the LFO.
You can assign parameters by clicking the icon above the modulator display icon, so if you set frequently used parameters, I like the fact that you can play with the parameters without touching the plug-in window at all.
Normally, only one parameter can be assigned to one knob, but since the modulator has a macro, you can assign multiple parameters that you want to set with the macro and assign the macro knob to have multiple parameters.
Also, it's designed to allow users to create their own Bitwig extensions, but thanks to this, it's really often possible to operate with a MIDI controller.
http://www.mossgrabers.de/Software/Bitwig/Bitwig.html
There are different things that can be done for each controller, but especially Push2 is custom-made, and even though it is a dedicated controller for Ableton Live, there are many things that Bitwig can do w
Push2 is soaring so I can't afford it, but I really wanted it.
I will put up with Launchpad mini for a while w
Sylenth 1 is for people who care about CPU load.
Although it is really light, it is a sound that appears on the entire surface, so it is easy to use.
It's just a preset browser.
If you don't care about CPU load so much, Hive is recommended over Sylenth 1.
Hive is quite light and easy to use among u-he.
And the preset browser is pretty easy to use.
You can use the demo version, so please give it a try.
The only downside is that there aren't many presets on the market.
The great thing about bitwig is that it's designed with modulation in mind from the beginning.
The other DAWs are obviously attached later, so I still feel the difference in the times.
Besides, management-related specifications are modern, aren't they?
It's great that Japanese is also compatible with defaults (I personally get used to English and English is more comfortable).
Japanese is easier for people who are starting from now on.
Bitwig is pretty much in the future.
I'm also worried about this.
It seems that FL Studio can be done quite well, but I'm leaving it alone, so I think I'll do it a little.
Is Push2 affected by the strong yen?
However, with Yahoo Shopping, there is a 86,680% reduction for 15 yen.
(On Sundays and days with 5s, it seems that you will get a 20% reduction)
Still, this price is high for the controller, but ...
yosi
Fans of this site
Good morning.
Thank you for everything this time.
I learned a lot from listening to the opinions of my seniors!
If you have any problems or problems, please feel free to contact us!
My lesson this time is, "If you have any problems, please go back to the manual."
Most things seem to be solved by reading the manual, but I have a habit of seeing it only when I'm really in trouble.