RapidComposer v5 beta feedback and discussion

[sj1]

When we bring in song-length .mid or MusicXML files we are currently getting a single song-length Part (assuming a successful import).

It would be helpful in general if we could have resulting Parts and Lines on the 8m and 4m boundaries.

Of course it would be possible to get creative with a GUI, or with config settings, to allow flexibility as to how Parts and Lines would be assigned. Certainly it would be nice-to-have.

But I know I would get alot of mileage out of even one simple choice to either import to a single Part (as now), or split by 8's and 4's.

Another complementary possibility would be to offer an operation on any given Part in the Composition to divide it into multiple Parts and Lines based on the user's specification.

Dealing with this at import time would help us with the bulk case, and being able to do it as an operation on a single existing part would just be a speeder-upper for individual cases.

This is also relevant when dragging song-length progressions from the Progression tab in the Browser into a composition.

[sj1]

Q. How can we create our own sub-sections in the Progression Browser?

Snag_184a1de.png

I've experimented for awhile now and consulted the manual also, but I haven't figured out how to do it!

[BluGenes]

from the master track browser, just add a slash in the title..

[sj1]

Thanks, but here is the result I get:

Snag_456d6c1.png

This is not the goal, which in this example would be for MyDir to be an expandable/collapsible item ala >Converted, >Absolute Chords etc.

Instead, I merely get slashes in the progression name.

Am I not doing this correctly?

[musicdevelopments]

Ok, that midi was actually from Ample Sounds VST, they do that on purpose sometimes because of how it's played in their VST. I think it's mentioned in the docs about this, too. I just changed the instrument when I posted that so that you could use it without the VST. Still sounds ok with out the VST, I think..

I think in their VST, an overlap like that triggers a pull off or hammer on..

OK, no problem with the overlap, which will be handled by RapidComposer. Also, I fixed a small issue with musicXML export. Now I believe the exported file is correct, still Guitar Pro 8 is hanging during importing it. I am stuck, so I contacted Arobas for some hints.

Thanks,
Attila

[musicdevelopments]

This is not the goal, which in this example would be for MyDir to be an expandable/collapsible item ala >Converted, >Absolute Chords etc.

Instead, I merely get slashes in the progression name.

Am I not doing this correctly?

Use backslashes ('\') for groups.
Forward slashes are often used for signatures in the names, e.g. 3/4.
Forward slashes work on macOS too.

Thanks,
Attila

[BluGenes]

Awesome, and on another note, pun intended, at some point you should look to add the ability to handle offsets in VST play back. For example, those Ample Sound VST's have the ability to change the offset of the sample, but, would need compensation for that in the DAW. It allows more or less attack, I suppose, of the sample sound. (by adjusting the beginning of the sample, you can remove pick noise by lengthening when it is played)

In Reaper, for example, it can be adjusted from the track's routing like so..



The way it works, is, you change the offset in the VST, but, you have to also adjust by the same amount in the host. (as I understand it anyways)

[sj1]

Use backslashes ('\') for groups.

Something is still not right.

Snag_3f246d.png

[lulukom]

CRASH. Opened various plugins inside DAW, including RC was opened. Perhaps RC is to blame for this .

[musicdevelopments]

Dealing with this at import time would help us with the bulk case, and being able to do it as an operation on a single existing part would just be a speeder-upper for individual cases.

This is also relevant when dragging song-length progressions from the Progression tab in the Browser into a composition.

There is a MIDI import option for that:



Though this is not offered when dropping a MIDI file directly on a track but that assumes you have already set up a structure.

Thanks,
Attila

[musicdevelopments]

Awesome, and on another note, pun intended, at some point you should look to add the ability to handle offsets in VST play back.

Good idea , I plan to add more DAW-like functionality in the near future, like flexible routing and VST3 parameter automation. A simple routing of one track to the other is a pain in many DAWs.

[musicdevelopments]

CRASH. Opened various plugins inside DAW, including RC was opened. Perhaps RC is to blame for this .

Thank you, lulukom. This crash was not caused by RC, I am 100% sure. No RC threads are running at the time of the crash except for one, but that just waits. The main thread crashes during handling a dispatch_async or dispatch_sync call, which was made by a thread that was started before the RC plug-in was loaded. So I don't think RC is to blame this time.

Thanks!
Attila

[lulukom]

Ok, thanks. Try to figure out how to drag midi to the master track. For me, either the length freezes everything or the new master track simply doesn't hold and remains the old one.

[sj1]

There is a MIDI import option for that:

Yes, true, thanks, and I have used that. So in the MIDI case only specification of a leading offset is really needed.

MusicXML though is also an excellent chord progression source.

In the MusicXML case we have two paths:

1. Direct drop on the Master Track
Issues: a) Composition is not resized (extended) to match the span of the incoming, b) no Parts or Lines are created for a full length drop.

2. Drop into Prg Browser tab, then generate composition.
Issue: No Parts or Lines are created for a full-length drop (followed by a conversion)

So hopefully the direct drop of MusicXML on the MT can be a bit more fully supported, and the conversion from Progression to Composition also.

Thanks.

[sj1]

Ok, thanks. Try to figure out how to drag midi to the master track. For me, either the length freezes everything or the new master track simply doesn't hold and remains the old one.

If you haven't tried it yet, the path MIDI FIle -> Progression, Progression -> Composition might work for you. (and I have commented on how that could be even better than it already is)