Recent Posts

Pages: [1] 2 3 ... 10
1
Discussions / Re: Setting input and output ports to None in Sonar
« Last post by norfolkmastering on July 16, 2024, 07:56:12 PM »
Hi Alexey
Thanks for the new test version.
I’m now travelling for a couple of weeks so I will test it as soon as I get back home.
Regards
Robert
2
Discussions / Re: Setting input and output ports to None in Sonar
« Last post by azslow3 on July 16, 2024, 06:13:37 PM »
Hi Robert,

Please try Test version (b424). It should use the same names for getting and setting "Nones", in any Sonar/CbB/Sonar versions.
I could change it to "None" (removing dashes), but that will break existing presets which use the feature. So lets keep it "-None-" (input) and "--- None ---" (send and output).

Alexey.
3
Discussions / Re: Setting input and output ports to None in Sonar
« Last post by norfolkmastering on July 16, 2024, 04:27:20 PM »
Hi Alexey
Thanks for the information which is useful.

I will buy Sonar because they have implemented a major improvement to the external inserts code which has a huge benefit to my setup.  I will make sure to be able to revert to previous versions of Sonar if AZ Controller compatibility becomes an issue.

Windows 11 is also a potential issue I need to explore soon.

One more question please.
In AZ Control, when I have an entry named ‘None’ in a Software State, does the label have any meaning? Or is it just the position of ‘None’ within the Software State list which determines the Track Input which is selected?

I am trying to understand why I had to change the None label from ‘—- None —-‘ to ‘None’ when I changed from Cakewalk by Bandlab to the new Sonar.

Regards
Robert
4
Discussions / Re: Setting input and output ports to None in Sonar
« Last post by azslow3 on July 16, 2024, 02:33:49 PM »
Hi Robert,

AZ Controller "produce" the following "Nones" on its own:
  • None as Output "--- None ---"
  • None as Send output "--- None ---"
  • None as Input "-None-"

From what I remember, that was "mimicking" some version of Sonar.

Cheers,
Alexey.

PS. I don't have and I don't have plans to have "new" Sonar/Next. I guess my tools will slowly become incompatible with new versions of Bandlab software.
I was thinking about getting Sonar just to have it installed, but for me the price policy is ridiculous - one year of Sonar subscription cost like 10 years of
REAPER perpetual. Old Platinum at least had extra content and was perpetual for the money. The engine is the same, close to 30 years old, and there is no
indication that is going to be changed withing the next 30 years. Just yet another GUI change (previous was X1).

I see how REAPER is moving on. Bapu has convinced me to check Presonus S1, and even so I don't like it after REAPER, I see it is also moving. Cakewalk
is stuck in the past, but the owner want monetize it. Sorry, without me.
 
5
Discussions / Setting input and output ports to None in Sonar
« Last post by norfolkmastering on July 16, 2024, 01:00:55 PM »
Hi Alexey

I’ve been Beta testing the new Sonar release with a focus on the API and AZ Controller.  So far no problems but one small change which is not easy to explain, but I will try!

Setting a track source to the GUI displayed source of '-None-' using
Cakewalk would report via the API as the label '-None -' but if you
wanted to set the source to '-None-' remotely then you had to instruct
to set to '--- None ---' via the Software State entry.

In Cakewalk, the GUI displayed track output of  '--- None ---' was reported
via the API as '--- None ---' and could be remotely set using the label
'--- None ---'.

In Sonar the GUI displayed labels for track source and outputs have both
been changed to 'None'.

Setting a track source to 'None' via the Sonar GUI still reports via the
API as label '-None-' but to set the track source remotely to 'None' now
requires the label 'None' in the Software State entry.

Setting a track output to 'None' still reports via the API as label '---
None ---' but to set the track output remotely to 'None' now requires
the label 'None' in the Software State entry.

So, in summary, for track source or track outputs 'None':

- GUI names have been changed in Sonar

- How they are reported via the API is unchanged

- How they are controlled remotely has changed

I have reported the change to Mark McLeod who says there has been no intended changes to the API but the Sonar GUI labels have certainly changed.

So the change I had to make in AZ was to change the label in my Software State list from ‘—- None —-‘ to ‘None’. That change allowed both the track source and track destination to be controlled from my external controller.

Can I ask:

Which Cakewalk label does AZ read when it attempts to match to a Software State label?  Is it the displayed GUI label?

Regards
Robert

6
ReaCWP / Re: Possible ReaCWP bug (being passed to Project Converter by moss)
« Last post by azslow3 on June 17, 2024, 02:18:39 PM »
I pretty much (finally) got an MIDI only Orchestra Song from Cakewalk by Bandlab converted to Studio One (via ReaCWP and Project Converter).

It required some manipulation after these steps:

1. Consolidate all MIDI tracks (not 100% sure this is necessary but a 'safety' step' Save song as well as Fabfilter C 2 VST3 settings as a preset (more on this later).
I also think that is 'safe' option. I try to fix issues with incorrect conversions once spotted, but since they are still spotted after years, there are probably more.

Quote
2. Open Reaper (with ReaCWP plugin installed) and open the Cakewlak project(.cwp), Save as a Reaper .rpp file. The piece plays just about how I expected it to.
At this stage it is better check that all synths and FXes are loaded, show correct presets and sound correct. Note there can be differences (loaded but with incorrect preset,
looks like have correct preset but not applying it, etc.). FX/Synth preset extraction and saving is partially "guess work" (even so from what I remember I have fixed some issues
toward documented structure... at least in other related project... I hope I have ported that part into ReaCWP).

If there are any problems on that state, they are definitively ReaCWP problem (DAWProject should not be blamed).

Quote
3. Open Project Converter (v1.2.2) and convert the saved .rpp in step 2 to a DAWProject file.

4. Open Studio One and open the DAWProject file.

Now here is where the fun started.

1. Project tempo was off (120, not 90) and the MIDI performed as such (too fast). This is probably moss's issue, but maybe not? So, I went back to Cakewalk and saved the project in MIDI 1 format.
Your test project has constant 90pbm. Converter put that as "project tempo" and as "tempo envelope" with just one point. The second one is not essential (new REAPER project with 90bpm has no tempo envelope points). So there can be differences after DAWProject conversion. Try delete the point in REAPER (and not "View/Tempo envelope" again before saving RPP, that re-creates the point...). 

Quote
2. Removed all MIDI in Studio one and replaced it with the output of the MIDI 1 saved file. Just FYI.

3. Now the DAWProject file seemed to think that Kontakt and Opus were audio FXs not instruments (unzipped DAWProject file and confirmed). So, it created audio tracks with Kontakt and Opus as 'inserts'. Studio One has an Instrument Rack and then uses instrument tracks feed their MIDI data to the respective instrument in the rack.

The conversion did create instruments tracks with the MIDI correctly. But they had no "instrument" to point to. Is this due to how you stored the VSTi's in the .rpp file?

Nothing played.

This mishap is on Instruments that either you or moss need to solved. Please verify that.

Small issue is that although FabFilter C-2 (VST3) was in the Reaper project on one instance of Kontakt (since it was in the Cakewalk project). The guts of the DAWProject file created by Project Converter knew about it. Studio one did not have Fabfiler C-2 VST3 in it (nor the VST version either).

But here's the weird part. All instances of Kontakt and Opus do a send to EW Spaces II. Spaces II is in the .rpp and DAWproject files. And it's in Studio One after opening the DAWProject file with the correct settings (on an audio track).

That too needs to be solved probably by moss unless there is something different on how you store FabFilter C-2 vs EW Spaces II in the .rpp file.
From what I see in REAPER, there is no difference. Both are on original buses ("Reverb bus" , "Kontakt 7 Action strike drums") and have receives from synths. I mean there should be no difference, apart from the number of receives (the bus with C-2 has just one).

== The structure of REAPER project created from CWP (short version) ==
1. Buses and Audio (!) tracks are in a tree, based on "Output" settings of original Tracks and Buses.
1.a Those with Output to Hardware are on top level, with "Master send channel" ticked (so auto-routed to parent folder, if moved into folder)
1.b Those with other Output (to some Bus) are put into corresponding Bus folder. But they have "Master send channel" unticked and instead have explicit send to the "parent".
1.c original Sends are converted as such (explicit Sends to corresponding bus)
2. Synth Rack is a top level folder, just for organization (it receives no audio nor MIDI)
2.a Synth is an FX on track in the Synth Rack folder (REAPER has no separate "synth" definition), the track is also a folder for
2.b MIDI tracks for the synth, with explicit send to synth track
==

I don't think Jürgen is ready to use ReaCWP specific RPP structure to convert better.

Direct conversion to DAWproject is more logical then throw REAPER, but I am not ready to dive in. Sorry.
If there are any bugs in ReaCWP, I will try to fix them.

7
ReaCWP / Possible ReaCWP bug (being passed to Project Converter by moss)
« Last post by bapu on June 16, 2024, 05:20:59 PM »
I pretty much (finally) got an MIDI only Orchestra Song from Cakewalk by Bandlab converted to Studio One (via ReaCWP and Project Converter).

It required some manipulation after these steps:

1. Consolidate all MIDI tracks (not 100% sure this is necessary but a 'safety' step' Save song as well as Fabfilter C 2 VST3 settings as a preset (more on this later).

2. Open Reaper (with ReaCWP plugin installed) and open the Cakewlak project(.cwp), Save as a Reaper .rpp file. The piece plays just about how I expected it to.

3. Open Project Converter (v1.2.2) and convert the saved .rpp in step 2 to a DAWProject file.

4. Open Studio One and open the DAWProject file.

Now here is where the fun started.

1. Project tempo was off (120, not 90) and the MIDI performed as such (too fast). This is probably moss's issue, but maybe not? So, I went back to Cakewalk and saved the project in MIDI 1 format.

2. Removed all MIDI in Studio one and replaced it with the output of the MIDI 1 saved file. Just FYI.

3. Now the DAWProject file seemed to think that Kontakt and Opus were audio FXs not instruments (unzipped DAWProject file and confirmed). So, it created audio tracks with Kontakt and Opus as 'inserts'. Studio One has an Instrument Rack and then uses instrument tracks feed their MIDI data to the respective instrument in the rack.

The conversion did create instruments tracks with the MIDI correctly. But they had no "instrument" to point to. Is this due to how you stored the VSTi's in the .rpp file?

Nothing played.

This mishap is on Instruments that either you or moss need to solved. Please verify that.

Small issue is that although FabFilter C-2 (VST3) was in the Reaper project on one instance of Kontakt (since it was in the Cakewalk project). The guts of the DAWProject file created by Project Converter knew about it. Studio one did not have Fabfiler C-2 VST3 in it (nor the VST version either).

But here's the weird part. All instances of Kontakt and Opus do a send to EW Spaces II. Spaces II is in the .rpp and DAWproject files. And it's in Studio One after opening the DAWProject file with the correct settings (on an audio track).

That too needs to be solved probably by moss unless there is something different on how you store FabFilter C-2 vs EW Spaces II in the .rpp file.


=== FYI about Studio One ===

Fortunately, the inserts of Kontakt and Opus (11 in all) were configured correctly. So, I simply dragged them to the instrument Rack and then pointed the instruments tracks to their correct instance of Kontakt and/or Opus.

Then I added Fabfilter C-2 VST3 and loaded the saved preset made back in Cakewalk.

The project plays "pretty much like the original Cakewalk. I did not do a null test. I'd expect them to probably not null but I'd rather just trust my ears that it's good enough to start with if I were inclined to either edit/add to/remix the orchestra piece.

Knowing what I know now, it would take about an hour or so to do similar sized projects. But if the VST3 (Fabfilter C-2) and the Instrument Rack (Kontakt 7 and Opus) were solved it should take considerably less time and be less prone to human error I took in the steps above.

=== end of Studio One info ===

If you need to see the guts of the DAWProject file, you can rename it to add .zip and open it to see/read the xml file that describes all the contents that Studio One/Bitwig uses.

Lastly, I've included a DAWProject file created from the "fixed up" version of the Studio One project for reference. I appreciate that Project Converter is not your responsibility, but I wanted to provide you with all the information about Studio One I could.

FYI Bitwig suffers the same issues that Studio One does except it does set the bpm to 90 and the MIDI looks to be correct, but I did not go through all the steps to get it work there as I only use Bitwig for educational purposes at this point, but if the Instruments get sorted out, I could confirm that the MIDI is correct.

Once again, as I've said in the past, I would be happy to donate a copy of Studio One Pro license or a year of the new subscription to you to help sort out where the disconnect lies in the FabFilter C-2 and Instruments Rack issues I've outlined.

Here are the relevant files: https://www.dropbox.com/scl/fi/eiu9lvxv2qlfa9ertg6xh/ReaCWP_ProjectConverter_Examples.zip?rlkey=f31toyyguxndcgbaus63uwyk5&dl=0
8
Discussions / Re: Controlling VST Synth in focus?
« Last post by azslow3 on June 11, 2024, 12:11:46 PM »
I think I forgot to mention https://www.azslow.com/index.php/topic,13.0.html
Please read it (and try to understand).

You don't need Function->Context->Focus. (As written in the "User manual"...) it is for changing which plug-in you want control. You have mentioned you want use mouse for that.

So:
ACT->R1 (or other "type")
Value->Endelss->MIDI (or other granularity)

does the trick (plus Monitor with sending value back, for led ring feedback)

There are several way to modify XML files, including manually, but "ACT Learn" and "AZ ACT Fix" are simpler to use methods (see the documentation for "AZ ACT Fix"). I have not checked if they have fixed some old bugs recently. But I strongly recommend to start with "empty" XMLs and use "AZ ACT Fix" for backups.

Cakewalk's mapping is over-complicated with "generic" and "surface specific" mappings, but once you understand it and use "AZ ACT Fix", it is usable. NI NKS, Automap, Akai VIP, etc. are based on the same ideas and technical solution.  So, in two sentences, "Automation parameter" -> "Virtual control" -> "Real control". The first mapping is "ACT learn" and saved into XMLs. The second is surface plug-in specific (mentioned Actions in AZ Controller).
9
Discussions / Re: Controlling VST Synth in focus?
« Last post by cupax on June 10, 2024, 11:02:21 PM »
Hi,

I managed to make a rotor work, by Logic:
Function->Context->Focus
ACT->R1
Value->Endless->MIDI

This now works well for same kind of synths. What about when I switch to another synth? Do I have to manually edit the xml file? Can AZSlow somehow read the synth name and acordingly set a custom state based on it's name?

Thanks!
10
Discussions / Re: Controlling VST Synth in focus?
« Last post by cupax on June 10, 2024, 10:34:40 PM »
Hello.

Thank you for your reply, but this thing is really confusing and your attached preset, while it works well, is just too complicated to understand or decypher :)

I am able to program synth controls, but they work just on the synth on the 1st track, not the one that is in focus.

Could you please just describe the steps, for example, how to map a single rotaty knob to control a master volume of a synth, that is currently in focus?

Thank you!
Pages: [1] 2 3 ... 10