Toy

I use web translations, so this may not be what you are looking for.

Is the purpose simply to double the specified range?
If not from the menu process, but to be performed in CAL.

(do
    (EditLength From Thru 0 200 1 1)
)

This should double the selected target.

Note for CAL training only.
Although CAL processes the data within the specified range sequentially, there are many cases where the data is not processed in order of event time.
Therefore, CAL that simply uses the previously processed data may malfunction.
*Confirmed by experimentation with a self-made CAL.

CAL does not have an array, so there is no sort function. You must create your own arrays.

If the theme is to process continuous data in CAL, I think the difficulty level is quite high.

I too have the shortcut randomization happen often.
Sometimes a registered "CAL file" is executed, sometimes it is not found, sometimes a previously registered CAL is executed....
I don't understand why.
I have cleared all the shortcuts and imported them, but they are still randomized.

Is it a problem that only stereo connection is currently possible and it does not support surround multi-channel plug-ins?
I would like to use Dolby ATMOS etc ...
Or is it possible now?

https://www.organicdrumloops.com/ock-new/

How about this?

15 minutes ago, 4th Eden said:

i thought it was just a V13 plugin?

On my PC, there are no problems with CR8 other than the error during scanning.

However, "COSMOS" is not working ...

I used only up to V12 of Waves, but when I changed it to V13 with CR8 this time, I got an error when scanning.
I ignored the warning and chose to use it, but it worked without error ...
With other software, there is no error in V13.

The problem with this is that the events within the range are not acquired on time.
For example, even if "CDEFGAB" is selected, CAL may process in the order like "ECDBGFA".

Measures in my case.
There is no array in CAL. Therefore, create the necessary variables, get the information within the range, and create an array.
Variables can be easily understood by using "array.time00, array.time01, array.key00, array.key01, ..." and so on.
Arrays can be sorted by performing the necessary comparison processing using "while, switch", etc.
By executing (forEachEvent) again and comparing the event information with the array, legato processing etc. can be freely performed.

As a premise, knowledge of programming that can create arrays and sorts is required at a minimum.
It is quite difficult because it is necessary to customize the array processing, especially the comparison processing, for each Cal.
Of course, once you make it, the rest will be easier.

I haven't processed the chords correctly yet.
I would like to know if there is an easier way.

https://xtant-audio.com/product/dicky-deegans-uilleann-pipes/

I don't know what kind of thing you want, but what about this?

The "composite clip" of the folder cannot be labeled as'Articulation'.
* Check from the version at that time by rollback.

-Articulation is not correctly recognized as the start time in "Composite Clip".
-The end time is also not recognized correctly.

-"Composite clip" lost time when dragging Articulation by editing.
-"Composite clip" cannot do anything if Articulation is deleted in this state.


I thought it would be fixed soon, but I reported it because it hasn't been fixed yet.
I'm sorry if anyone has already reported.

It may not be the usual method at the moment, but you can do many things with CAL.
You have to make your own script to do complicated things, but ...

As an example of a simple CAL, a major 7th chord is created with the specified range as the root.
This is the one that was attached as a sample in the past CakeWalk. Is it still there?

2 hours ago, Noel Borthwick said:

>>Up to E.A.134, all "BOUNCE BUFFER SIZE" settings are invalid in ASIO. 

Yes this was a bug that was fixed

>>-As a result of the setting being enabled in E.A.137, there are no options other than "PlayBack Size" in my plug-in.
I'm not sure what you mean. In the latest release you can either use playback size or any other buffer size. If you leave it at playback size it uses the driver latency setting otherwise its whatever value you specify. As described in the release notes depending on plugins used, use conservative buffer sizes such as up to 50 msec. The only benefit to larger sizes is to speed up export time. 

Bounce Buffer Size 10 MS -50 MS export result.
It was clear that there was such a gap.
I haven't tried a single digit.

You can see that it is faster or slower when the settings are other than playback.
If the value is higher than this, the deviation width will increase.
* BUF.10 is not normal and some tracks are in fast timing.

Although it is a deviation when setting this buffer, it seems difficult to adjust because the result seems to change slightly each time.

1 hour ago, Noel Borthwick said:

I think you may be confusing it with an issue that was fixed in the EA. There was a bug where in ASIO mode it was not respecting the bounce buffer size and defaulting to the playback buffer size. In the final release it will use the bounce buffer size unless it is set to "follow playback buffer".

If you are using a high bounce buffer size some synths do not handle it properly so this could be what you are seeing. If so set bounce buffer to "follow playback buffer"

Well, I didn't read the forum in detail because there was no problem in operation until EA134.
I'm confused, so I'll check it.

-Up to E.A.134, all "BOUNCE BUFFER SIZE" settings are invalid in ASIO. Actually, "PlayBack Size" was set.

-As a result of the setting being enabled in E.A.137, there are no options other than "PlayBack Size" in my plug-in.

Is this the right situation?

After posting on E.A.137, I verified it again.
Everything from 2021.06 to E.A.134 was working fine.
However, from E.A.137, it was not possible to export normally except for "buffer size: playback" and "real time bounce".

Ver 2021.09 cannot output normally, I would like to use E.A.134, which was the most stable, for the time being.

When exporting, there was a gap in the playback timing of the track.
So I tried the freeze track.
As a result, it was found that the playback timing was shifted back and forth. The difference in this timing was different every time.

It can be played normally without exporting or freezing.

Playback status
Cakewalk　2021.09 Early Access [Updated to build 137]  ＋ ViennaEnsemblePro7
ASIO: OCTA-CAPTURE Driver 1.5.2

A sample that shifts.

"Cakewalk_by_BandLab_Rollback_Setup_27.06.0.053 (Rebuild_3) .exe" requested "ver.2021.07" and could not be rolled back.

As far as I can see in the screenshot, I think the difference in dB is because it is boosted by Maximizer.

For more information on RMS and Peak, see "Ozone9 Online Manual".

About fonts in the new plugin menu.
I noticed that some symbol characters are not displayed.
Is this the correct specification?
The symbol character currently confirmed is "&".

If Kontakt is fine, I like Fujiya Instruments.
The base is Organic Bass Suite . (Amp simulator is not included.)

There is no trial version, so please refer to the demo play and manual.

1 hour ago, gmp said:

Hey Toy, I'm unsure from your post if this Tempo crash bug and quirky behavior you outlined was fixed in build 175 or is it still being worked on.

This has been confirmed multiple times in build 175 that it definitely occurs on two Japanese PCs. The video is the reproduction procedure.
 After confirming that "Change the Most Recent Tempo." Was not initially selected, it was very inconvenient, and then an operation test was performed. As a result, it was found that the operation was very strange.

There was a bug in the tempo track that included a crash.
*Cakewalk 2021.04 Update 1 (build 27.04.0.175)

It was deleted when "Change the Most Recent Tempo." was set to the same value as the tempo immediately after.

If there is an envelope setting, "Insert a New Tempo" will be executed instead of "Change the Most Recent Tempo.".
* In this case, it is linear.

If the two situations overlap, double registration will result and the tempo will be out of order.


If the same tempo continues, the "Change the Most Recent Tempo." is not selected and the "farthest tempo" is changed.


First, move the "default tempo (1:01: 000)" and it will be duplicated.
I was able to change it by continuously editing the "default tempo".
Erases tempos other than "default tempo".
It crashed when I edited the tempo before the "default tempo".

 

8 hours ago, Ben Staton said:

Thanks for the report. I'll investigate.

After checking, it seems that the screen is distorted by the plug-in with "GPU acceleration" setting.

When "Windows 10 high DPI rendering option" is enabled, the display of plugins of some manufacturers is distorted.
I tried "EnablePluginMenuFix = 0", but it didn't work.
※Ver. 2021.04 build 144&155(JP) | DisplaySize 3840x2160 125%

Checked owned plugins.
- Melda Production: All owned plugins.
- United Plugins: "Royal Compressor"
There may be others, but not all have been checked.

When "Windows 10 high DPI rendering option" is disabled, there is no problem.

Display example.

12 hours ago, msmcleod said:

It isn't clear from your gif / conditions what exactly you were doing to get this behaviour. I've tried to replicate what you're doing, but can't.

Can you detail the steps one by one from a new project?

The explanation was insufficient.
I reproduced it again, but the order of registration in the MAP has been reversed from the previous time.
The conditions have become uncertain.

conditions


The display setting "Only Show Articulations for Active Track" is enabled.


Multiple Articulations Library is used.
It seems that 3 or more are required.
This [TEST] is only registered and unused.



In this movie, Tracks 1 and 2 include Articulations and 3 does not.

First, [Limit100] has been successfully deleted.
Change the track.
 when I delete [C], everything disappears and the data of another track is displayed.

The reproduction procedure is like this.

I wonder if Google Translate was wrong ...

Doesn't it mean that the function defined in the shortcut [T] is not working in the Piano Roll view?
I currently have [F] and [L] not working properly.
I don't know from which version, but some keys are not working in the bind settings.

I found a bug. (I posted it in a different place earlier, so I moved it here.)

conditions
-Multiple Articulations Library is used.
-"MIDI tracks with unused Articulations" are mixed.
-The display setting is "Only Show Articulations for ActiveTrack".

Under this condition, delete "Second registered Articulations" in Articulations Maps in Projet.

All Articulations will be hidden.
Then, the "Articulations registered first in the map" in the non-Active Track is displayed.
It can be redisplayed by reselecting the track.

There may be other conditions, but it was possible to reproduce it in a new project. (gif movie)