AZSlow

So, something set "Device->Offline" before Context Monitor is called...

You have not mentioned where you set "Device->Online". Also you have "Device:Offline", but not "Context:" when sending hello from the monitor. Context can be triggered during project working (as I have explained before, you can avoid that by using new "Project" Set), may be that unexpectedly triggers something.

Hi Alexey

I am returned from my travels, so I spend time today to implement the final handshaking elements based on your advice.

It is mostly working well except for one issue which I will try to describe carefully.

Default states are as follows:
Device, Offline
Hello, active

I use a Logical 'Context' Control to sense when the project is closed.
Monitor, Monitor State, Context
with the action condition, Device: Online

This triggers the following Feedback actions:
'Context:NoProject' - Device -> Offine, set engine state
'Context:NoProject' - Hello -> active, set engine state
'Device:Offline' - Ch:15 CC:14 Value (14bit)@ 3f80

The problem is that the 'context' control is only triggering every second time the project is closed.

Here is the simplified sequence:
- Load Sonar
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control triggers correctly.
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control does not trigger
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control triggers correctly
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - control does not trigger

This sequence continues over and over.

If I remove the action condition 'Device Online' then the 'Context control works every time.
I am using 'Set engine state' for all Set state actions.

Do you have an idea why this is happening?

Regards
Robert

I have only started to dig into that, but it seems like the bug is triggered by REAPER 7.

So, please try to convert using REAPER 6 (you can download any previous version, install as portable and use the same license file).

I can only check "FOCUSRITE SC Plugin" later (the only I have in your list), for the moment I have just checked different plug-in with recent REAPER version.

Note 1: that take lanes will not be converted correctly (since ReaCWP use REAPER 7 style for them). But at least you can check presets are fine. If yes, I can upload a version with "old style" REAPER 6 compatible lanes conversion.

Note 2: once saved in REAPER 6, REAPER 7 opens the project with correct preset (at least for one plug-in I have tested).

So I see the "roadmap" I can follow to understand and hopefully fix the issue. But I unlikely have time for that next days.

EDIT: may be early versions of REAPER 7 also work, I have not checked that yet. That will be preferable workaround, especially if new take lanes was already working in "compatible" version.
 

Thanks for the response. I couldn't hear any difference, so it sounds like the utility guessed correctly!

is there a known working older version?
Also I have Windows 10 if it makes a difference in your research.

It seems like something in fact broken in current version, I will investigate.

The utility has very simple wav parser, so it doesn't support all "normal" files. Also if you have Cakewalk running, try closing it (especially if the project you convert is open).

That is not a problem as long as the result is fine. When guessed parameters are "wrong", the result will is bad...

Hi AZSlow,

Hope you're well!

I have done some conversions to .song format using your utility, and I have a question about warnings after conversion about some audio files. The message is below, and I checked some of the files, they seem to be normal stereo files at 32 bits and 44.1 khz. The converted file sounds fine to me, so my question is what is this warning and what may be lost or changed in the converted file?

The messages look like this example:
>>
W: Parameters for file 'C:/Users/My PC/Documents/Studio One/Songs/Can You Not Tell/Audio/Fragment Guitar Dark Atmos 01_CMajor_125.0 (9).wav' will be guessed : format not supported
<<

Thank you for making these utilities available!

The Plugins are from Universal Audio like the 1176 compressor and others, Plugin Alliance FOCUSRITE SC Plugin, I have some Waves Plugins, KIVE AUDIO Plugins, ALL analog Obsessions plugins.
No plugin carries over correctly on any project for me some do not work at all till I delete the plugin and add it back. on some the graphic for the plugin is a black background and the plugin is shrunk to about half or one third size.
Thank you for helping.
 

AOSC is just accessible OSC app. At some point, RME has considered OSC protocol as a way to control TotalMix remotely and I could use that. Please note that RME since then has switch to proprietary protocol and app for the job, that new app is not accessible since it is just TotalMix running on different computer. Also the last is mandatory, I mean the protocol technically doesn't allow running client on the same computer as TotalMix itself and so I couldn't construct a new app which use it.
RME still supports OSC in the form it was back in time, but I don't know there plans for the future. Also bug fixing in that part is definitively not in there priority list, that has prevented me adopting AZ AOSC v2 for RME some years ago, I hit a bug and they have not fixed it in time. I have not checked recently.

How good RME 12 mic can be controlled is a question I can't answer. From the documentation, it is controlled by web app, so theoretically can be accessible. But as you know, in practice web apps are rarely accessible when not checked for that by developers.

I recommend to ask on RWP and other resources if someone has or at least has tried 12mic. Especially if it is difficult return the gear in case you are unhappy.

Another potential problem can be AOSC itself. It was designed and tested with small amount of channels. Also OSC implementation of RME is paged by 8 channels by design. Controlling 64 channels is going to be relatively slow process. I mean the tool is not for live adjusting in RME case.

That is why we have targeted Behringer X32. Its console version is live capable, AOSC is used for audition physical operations and for initial configuration in this case. But the sound is not even close to RME, even in MIDAS version, so that solution is not good for recording.

I guess all that is not the answer you have expected, sorry.