v3 Beta Feedback And Discussion (Bugs, Features, Suggestions)

[sj1]

Improvements:

• Menu shortcuts displayed. Shortcuts in square brackets require the keyboard focus to be set before pressing the shortcut.

Excellent! That's a great addition.

I wonder if there is a useful way to do a visual showing operations that currently could be assigned keyboard shortcuts, but have not been. This as opposed to operations where no option for keyboard assignment exists.

[musicdevelopments]

Hi tanislas,

Nothing changed in the plug-ins. I was able to load all 3 plug-in formats in Reaper. Which macOS version do you use? Which was the last version that you used successfully?
Do others experience the same?

Thanks,
Attila

Hi Attila,
I m not able to load vst plugins in this one ( mac version) thanks

[tanislas]

I meant when using RC as a standalone, I m not able to load a third party plugin (virtual synth). I am using a macbook retina with High Sierra

Hi tanislas,

Nothing changed in the plug-ins. I was able to load all 3 plug-in formats in Reaper. Which macOS version do you use? Which was the last version that you used successfully?
Do others experience the same?

Thanks,
Attila

Hi Attila,
I m not able to load vst plugins in this one ( mac version) thanks

[musicdevelopments]

Standalone works too. I can load other VSTi plug-ins under High Sierra. Do you get an error message? Have you added the plug-ins lately (since the Settings / VST page was reworked)?
Thanks,
Attila

[tanislas]

Standalone works too. I can load other VSTi plug-ins under High Sierra. Do you get an error message? Have you added the plug-ins lately (since the Settings / VST page was reworked)?
Thanks,
Attila

thanks, no error message.
I just wanted to add sylenth wich I have on my computer for more than a year now and it won t add, same with kontakt and others.I attempted a clean reinstall of rc but no luck!

[tanislas]

Standalone works too. I can load other VSTi plug-ins under High Sierra. Do you get an error message? Have you added the plug-ins lately (since the Settings / VST page was reworked)?
Thanks,
Attila

I downgraded to the beta 37 version and I am now able to add the vsts as expected!!!I ll add the ones I use the most and I ll upgrade to b42 again but I think it s not a real solution!

[musicdevelopments]

You are right, I misunderstood something. The file selector stopped working and did nothing when you selected the plug-in. I have fixed this bug and will upload a new beta version in 10 minutes.
Thanks!
Attila

[musicdevelopments]

RapidComposer v3.9b43 is available!

Improvements:

• Fixed crashing bug during exit
• Stability fixes
• Fixed: some file selectors stopped working, selected file was not processed

[lulukom]

Hello Attila! Thanks for the new beta!
I want to ask you to make a couple of corrections in the built-in browser (if you find the time))
1. In the Browser options folder you cannot select the desired user folder, more precisely, you can select, but the selection is not saved.
2.It would be very convenient to make the same chain in the head of the Files tab as in the Phrases tab for instant auto-transfer of the selected midi file to the track. This would greatly speed up the work of choosing the right midi files. Thank .

[Dewdman42]

Now that you have AUmfx version of Melodya, any chance you will also build AUmfx version of RapidComposer pretty soon for easier use in LogicPro?

[musicdevelopments]

I haven't used Logic too much and I don't know it well. Why would having a AUmfx version be better than the current AU synth plug-in? How can you send the RC MIDI outputs to other tracks if it is an AUmfx? Is there anything you can't do now that you can do with an AUmfx plug-in? As far as I know AUmfx is for single-channel MIDI generation or processing.

BTW there is a crashing bug in the RC AU plug-in since the appearance of the audio level meters, which I am fixing right now.

Thanks,
Attila

[BluGenes]

Might want to reconsider what is what for the phrase inspector. With the newly added shortcut text, it's now obvious that some of the functions in the inspector don't really relate to "phrase" operations, but, rather on the "track" level.

The shortcut "D" in this case, no clue what is supposed to have focus...

[Dewdman42]

I haven't used Logic too much and I don't know it well. Why would having a AUmfx version be better than the current AU synth plug-in? How can you send the RC MIDI outputs to other tracks if it is an AUmfx? Is there anything you can't do now that you can do with an AUmfx plug-in? As far as I know AUmfx is for single-channel MIDI generation or processing.

Yes it’s true that aumfx would only go to the current channel but could also go to IAC like you are doing with au now, theoretically. Main advantage of aumfx is that the midi rendering would be sample accurate Including all considerations about plugin delay compensation, when it goes over IAC it’s pretty good timing but not sample accurate. Also people need to realize that it’s easy to get a midi feedback loop happening when you use IAC to loop around the midi. It depends on RC, but if the RC track is selected then the looped around midi will be fed back into the input of RC, even if the user is not aware of it. Depending on what RC does with the incoming midi this can cause a midi feedback loop that will freeze logicpro and probably they will have to force quit the application, losing their work. The IAC loop around method has to be used with care because of that.

For logicpro a better approach would be to have multiple instances of AUmfx that are all linked to one master RC interface. So that each AUMFX does the midi rendering for one channel but they all share a master project with shared chord progression.

But there could be cases where RC is useful for just one channel, and even someone if they wanted could use multiple seperate instances of aumfx, each one with its own chord progression thst we’d have to manually keep in sync between the instances but it would avoid IAC complexities and provide sample accurate midi.

BTW there is a crashing bug in the RC AU plug-in since the appearance of the audio level meters, which I am fixing right now.

Probably the same bug I found but just in case; when I open the plugin and click on the pink chord bar that says I IV I I, It crashes straight away.

[Dewdman42]

I'm at my computer now I can say about more about LogicPro. When you use IAC loop around, the midi output from RC will be fed back into the input of LogicPro and will be directed to whatever track is currently selected on the arrange page, including RC itself (which might cause midi feedback loop). Typically the way to avoid getting accidental midi feedback loops is to go into the environment and intercept that IAC line. So for example if I were going to use RC in LogicPro and only use the sound fonts or plugin hosting inside of RC itself...then I would want to make sure to block that IAC port to avoid feedback loops, like this:

nofeedback.jpg

If I need to also have that IAC midi be directed to other channels in LogicPro...then the best way is to route it here in the environment, though most people are not comfortable with doing things in the environment, but that's what you have to do...that way the IAC will not be routed back through the sequencer, it will be directed exactly to the instrument channels you want, like this:

toinst.jpg

That is all kind of complicated, definitely doable, but complicated. not sample accurate.

I think most people will either just use RC with sound fonts or by hosting plugins inside of RC itself.

Now there is one use case where AUmfx would be really helpful and that is when combined with something like Vienna Ensemble Pro. Then you could put RC in the AUmfx slot and VePro in the instrument slot and VePro will channelize all the midi channels. In fact its even possible to have more than 16 midi channels, the AU3 version of VePro supports 768 midi channels on 48 ports. So if an AUmfx version of RC could also assign events to those ports, you'd have the ability to control 768 separate tracks from one RC. Just one example.

You could also use Plogue Bidule, Patchworks, KushView Element (free) in the instrument slot instead of VePro, etc. All sample accurate.

I think you should also consider having a setting to turn off the IAC thing, it should only be on when specifically asked for, otherwise people may accidentally get midi feedback loop happening.

Also, if there is more than one IAC port, then that is another way to have more than 16 midi channels from one RC.

[Dewdman42]

It should also be noted, that the only way to actually RECORD the results from RC into LogicPro tracks is by using some kind of IAC loop around method. Well sorta. There are other complicated work arounds.

So another feature that would be really useful for LogicPro for that reason, is the ability to drag and drop a track from RC onto LogicPro Track area in order to get the data recorded as LogicPro regions to work with from there. Rather then trying to capture it over IAC and record it, which is not even sample accurate and has the other concerns about midi feedback loop.