Recent Posts

Pages: 1 ... 8 9 [10]
91
Discussions / Re: Accessing the Cakewalk Track Output router
« Last post by norfolkmastering on March 10, 2022, 01:32:45 PM »
Hello Alexey

I did some tests as you requested.

For information my PC has a i7-8700K processor running at 3.7GHz and it has 32GB of RAM.

1.
Opened Cakewalk by Bandlab
Loaded the REPLAY_080322-4.spp preset
(all 24 x Track to Output Monitor set to Slow)
AZ Controller set to MIDI in and MIDI out "None"
Refresh Frequency set to 25ms
Loaded Test Project, 48kHz, 24 audio tracks and 9 buses, into Cakewalk by Bandlab.
CPU loading 12%
Fader response poor
Pressing play and moving a group of two faders makes little difference to CPU loading, saw a peak of 13.2%.

2.
Changed all Track to Output Monitors to Ultra
Project will not load.

3.
Delete all feedback events from the Track to Output Monitor controls (but did not delete the Track to Monitor controls, which are still set to Ultra)
CPU is under 1%
Fader response is very smooth
Playback is smooth

4.
My current 'live' system uses no Track to Output Monitor actions but instead uses 8 sends per track as the means to route tracks to buses.  The full system uses two AZ presets with a total of 466 controls (a much higher number of controls than the test preset I sent you).

I loaded both 'live' presets and connected to my usual MIDI ports, including MIDI routing via MIDI-OX.
Set Refresh time to 25ms (which I use in my current system)
Loaded test project to Cakewalk by Bandlab, running at 48kHz sample rate.
24Tracks, each track with 9 sends, 10 buses
All 24 tracks loaded with test audio.
Project loads okay
CPU loading is under 5%
Playback is very smooth
Fader response is very smooth

Reduce number of track sends from 9 to 1, CPU loading drops to under 2%

Add 6 Track to Output Monitors, set to ultra, add one MIDI feedback action to each monitor.
Project loads very slowly.
CPU loading rises from 2% to 13%
Fader response very intermittent
Playback is very jumpy

Remove MIDI feedback action for all 6 Track to Output Monitors (but leave the Output Monitors in preset)
CPU loading drops from 13% to 2%
Playback is very smooth
Fader response is very smooth

SUMMARY
Adding even a small number of Track to Output Monitors with feedback events has a dramatic impact on CPU loading and makes the system almost unusable.
The CPU load is only impacted when each Track to Output Monitor has a feedback event
My current 'live' system has a huge number of monitor actions all with MIDI feedback outputs BUT my current 'live' system has no Track to Output monitors.
My current 'live' system uses 24 Track Input Monitors with feedback actions.  These have no big impact on CPU loading
I am running Cakewalk by Bandlab.  I did one test with an old version of Sonar Platinum and the results were similar.
I did one test raising the refresh frequency from 25ms to 75ms.  It made no big difference to results.

So my tests suggest a problem with the Track to Output Monitor action, when it is linked to a MIDI feedback output.  It makes no big difference to CPU loading if I connect AZ to MIDI ports.

I hope this helpful to your analysis of the issue.

Regards
Robert
92
Discussions / Re: Accessing the Cakewalk Track Output router
« Last post by azslow3 on March 09, 2022, 09:03:32 PM »
Can you do simple test... Leave just one AZ Controller with this preset loaded, but set AZ Controller MIDI in and our to "None". So it works without your hardware.
Check the influence of such instance on performance (in terms of UI responsiveness and CPU use in the Task Manager).

In my test I loaded your preset and changed all 24 monitors to Ultra. The project just has "empty" tracks (32), and some buses (16). On some tracks I put one send, to check T1DAW like controls.
The result: my i9 has CPU load from Cakewalk under 3% (without GUI operations and the transport stopped under 2%). Cakewalk GUI has no perceived response change when your preset is loaded. Singe T1DAW definitively takes less then a second, but I can't test how long it will take to change all 24.

It can be my i9 is so powerful it is not possible to notice any performance penalties. AZ Controller was originally developed on Core2 Celeron, and Centrino based notebook. That time any performance problems was instantly reproducible. But I don't have such slow equipment at the moment (desktop is i9 and notebook is i7).

But it can be something else is degrading the performance on your particular system and/or project and AZ Controller is just "the last drop" which render the degradation visible (once Cakewalk GUI can't do what it wants within fixed time slots, the whole interface becomes almost unusable, but till that happens, independent how far it is from the limit, everything is smooth).

We have to understand which case you observe. What is "idle CPU use" of the project? I mean without AZ Controller(s) and transport stopped? Do GUI operations (f.e. moving sliders) significantly increase CPU load?
93
Discussions / Re: Accessing the Cakewalk Track Output router
« Last post by norfolkmastering on March 08, 2022, 06:21:18 PM »
Hello Alexey

I started to implement the revised method of controlling my analogue audio mixer, track to bus routing, using the Cakewalk track output parameter as feedback MIDI values to my PIC.
My development preset is attached. It runs in the 8th instance of AZ controller.

There are 24 AZ controls used to derived the 24 tracks to output status.
T1MONOUT is for track 1 etc.

I have found that these Monitor actions are slowing down the response time and smoothness of the Cakewalk user interface, especially for faders which is an issue.
I have tried setting all the Track Output 'Monitor parameter value' actions to 'Slow' but I'm not sure if that is helping improve the general response of the user interface.
The user interface gets worse as you add more tracks into the project.  With 24 tracks it is not very usable.
Could you have a look at the attached preset please and let me know if there are any ways to adjust the Track Output monitoring to improve the Cakewalk user interface response please.
Or any other ideas to improve the responsiveness of the system due to this issue?

I have a similar but less critical issue.  24 AZ controls are used to set the output of one send in each track to a specified output.  This is driven from my PIC.
The controls are 'T1DAW' to 'T24DAW' in the preset.
When I send the 24 MIDI messages from my PIC, it is taking round 20 seconds for the 24 track sends to set their outputs.  This is a very long time!  It has never failed to work but I am concerned.

Your help would be very much appreciated on these two track to output selection issues.

Regards
Robert
94
Discussions / Re: Accessing the Cakewalk Track Output router
« Last post by norfolkmastering on March 05, 2022, 11:03:58 AM »
Hi Alexey

Yes I meant the "Output" parameter.
I previously thought that the "Output" parameter was only a way to access sends.
I did not realise you could access the track output directly using this parameter.  My mistake!

So I made a quick test preset, creating a Software State including the buses which I named 'Group 1' through to 'Group 8'.
I was able to derive feedback MIDI values which tell me which bus each track is routed to.
Fantastic!

So now I will be able to greatly simplify my track to bus routing control.

Many thanks
Best regards
Robert
95
Discussions / Re: Accessing the Cakewalk Track Output router
« Last post by azslow3 on March 04, 2022, 09:36:25 PM »
Do you mean "Output" parameter? It is directly in Strip Action.
96
Discussions / Accessing the Cakewalk Track Output router
« Last post by norfolkmastering on March 04, 2022, 05:20:13 PM »
Hello Alexey

This question relates to my use of AZ Controller to allow remote control of my external analogue mixer (which is complete and fully working - so a big 'thank you' for all your help to date)

At the moment I have to use a total of 9 sends per track to allow:
Track routing to Groups 1 -8 (8 Cakewalk buses)
Track routing to a hardware output

I'm finding on large projects that Cakewalk Screen update response time is very slow and this method also fills the mixer control screen with large number of send level and pan controls which I never use.  This means I'm constantly having to scroll up and down the screen to get to controls I do want to use.

I don't ever need to route a track to more than one bus at the same time, so rather than use sends for this track to bus routing, does the Cakewalk API allow access to the track to output routing function?

If this is possible, I would programme a software state group which could provide MIDI feedback values to tell me which group each track is routed to.

This would be a more elegant way control the track to bus routing in the hardware mixer, rather than the current  method of having to read the send enable states for a very large number of sends.  It would hugely reduce the number of elements in the AZ preset which in turn would speed up the response time of Cakewalk.

Best regards
Robert
97
AOSC / Air Access 12
« Last post by gadeuvall2000 on March 01, 2022, 03:57:01 PM »
Welcome to the Air Access 12 forums.  You you will find information as well as the official download for the Air Access 12 project.

The concept of this project is to make the functionality of the X-Air XR12 accessible through the means of a more screen reader friendly user interface.  For more information on how AOSC  works, please see  AOSC post.

This project works under Windows with NVDA and Narrator, under Linux Wine, and may work under Apple Wine, but has not been tested.  There are no current plans for apple support.

The zip package contains a group of files that were designed to work with AOSC.

Please read the EULA.txt and ReadMe.txt files contained within the zip package before using.

Here's a playlist of videos to help you get acquainted with Air Access 12:
https://www.youtube.com/playlist?list=PL_KlosoJFir0p17B3kMRiTGJctP4PBIia
The videos were made using the Air Access 18 template, but it's very similar.

You can find and download the zip package here:
https://www.azslow.com/index.php?action=downloads;sa=downfile&id=87

If you have any questions, feel free to post on the forums.

Updated 2022.03.21
Current version is Version 1.7.

Change Log:
2022.03.21
- Tap Tempo has been added to any "Delay" based effects.  pressing "space" on "time" fader activates this function.
- Alt+T is now a global shortcut for tap temop, and will only apply if a Delay based effect is loaded.  IF more than one is loaded, the shortcut will apply to the highest numbered slot.
- Added an input meter in Gate page next to threshold.
- Moved FX Processing meters to Parameters page
- Added a dedicated Main section for extra controls such as mute groups, Automix controls, and solo claring

2022.03.07:
- Added shortcuts to "Configure" pages
- Fixed Reduction meters on Gate and Compression pages.
- Aux Input has it's own section

2022.02.28
- Added keyboard shortcuts
- Some names have been changed for clearer understanding.


2022.02.22
- Added the ability to name Main LR strip.
- Added Clearsolo button on Main LR Strip
- All Input pages have been renamed to "Configure".
- Configure" page has been renamed to "System"
- Channel strip Color, Name, Mute Group, DCA Group, LInking, and any preamp and headamp configurations  are under respected strip's "Configure" page.
- General organization of "Routing" section.

2022.02.17
- Removed unused parameters in Master Compressor
- Added a Master Bus fader to bus mix sections.
- Added Aux Send output Meter to Bus mix section

2022.02.15
Updated EULA and Readme files
Fixed small bugs in XML
Organized templates in XML

2022.2.11:
- Fixed Typos
- Changed FX Routing from Return/Insert to Return/SideChain to better fit the original terms.

98
AOSC / MXAccess32
« Last post by gadeuvall2000 on March 01, 2022, 02:28:52 AM »
Welcome to the MXAccess32 forums.  You you will find information as well as the official download for the MXAccess32 project.

The concept of this project is to make the functionality of the Behringer X32 and Midas M32 accessible through the means of a more screen reader friendly user interface.  For more information on how AOSC  works, please see  AOSC post.
You must have latest version of AOSC in order for this project to work properly.

Currently, this project runs under Windows with Non-Visual Desktop Access, and Narrator screen readers.  IT also works under WIne for Linux, but has not been tested in Apple Mac and Apple support is not currently planned.

The zip package contains a group of files that were designed to work with AOSC.

Please read the EULA.txt and ReadMe.txt files contained within the zip package before using.

You can find and download the zip package here:
https://www.azslow.com/index.php?action=downloads;sa=downfile&id=86

If you have any questions, feel free to post on the forums.

Updated 2022.06.22
Current Version: 1.8

Change Log:
2022.06.22:
- Typos in coding corrected for some channels
- Linking identified for auxiliary and fx return strips


2022.04.14
- Fixed Global Master Volume shortcut.
- Added full names for EQ band types.
- Clearified some labels within the X-Live section

2022.04.11
- Userbank Selection is now possible.  You can determine if the UserBank screen is selected, as well as choose what userbank you want to choose.
- Global shortcuts for Mute Groups 1 through 6


2022.04.05
- Added X-Live card page with controls and configuration sub page.
(Available number of sessions/markers per session, Currently selected session/Marker, Jump to and delete session/marker edit boxes, play, stop, pause, record, card info, error message, card format, and many other options)
- Added additional keyboard shortcuts for X-Live controls.
- Added Alt+Shift+L global shortcut to view and change system lock status.


2022.03.25
- MixBus Mute and Send To options under Mixbus Section of Main LR and M/C mixes.
- Minor fixes

2022.03.24
- User Assigned Input Routing is now possible.
- User Assigned Output Routing is now possible.
- Assigned XLR input is now visible on Channel and Auxiliary Configure page if available.
- Channel assigned Gain and Phantom controls are now visible on Channel and Aux Configure pages
- Input meters are available on Bus and Matrix Configure pages
- Removed Headamp section from navigation Tree since it's available on Strip configure pages.
- Removed Pan section from Mixbus Mix pages (was causing conflicts).
- Updated Keyboard shortcuts.

2022.03.21
- Included a Input meter on channel gate pages
- Added Keysolo function on gate and compression pages
- Implemented channel ID selection on strips
-- Added Sconsole screen selections on gate, compression and eq pages.
- Updated and changed some shortcutsw
- All Ctrl+ Function keys have been moved up by one to make room for Ctrl+F2 for Channel ID Selection.
- Added shortcuts to gate and compression filtere and filter types
- Re-arranged some controls in the compression pages
- Added tap tempo to all delays that ere initially missing function.

2022.3.17
- Added Meters
- Added "Channel ID" and "Fader Bank" options
- USB Recorder is working
- Added Tap Tempo to "Delay" effects, global shortcut available.
- Added and updated shortcuts
- Added Talkback Routing sections
- Updated Icons list
- Mix pages are pages rather than a dropdown
- Output Polarity available in routing
- Console Initialization is now in Preferences




2022.02.28
Initial Release

99
Presets / Re: [azslow3, almeister_65] Behringer X-Touch Mini
« Last post by azslow3 on February 26, 2022, 11:31:11 PM »
It can be AZ Controller related or Cakewalk related, AZ Controller has several workarounds for old ProChannel control bugs, may be yet another is required.
But without project in question, or some test project with the same issue, there is nothing I or Cakewalk can do... CWP file alone, I mean without audio files, normally can reproduce bugs.
100
Presets / Re: [azslow3, almeister_65] Behringer X-Touch Mini
« Last post by jpfliegner on February 26, 2022, 09:45:38 PM »
Hello everybody!
First of all thanks to everybody for their great efforts and sharing it with us, particular to Alexei and his marvelous work.
I also took part on it and installed the AZ Controller an the preset for the x-touch mini. Everything works fine, but  at least in one of my projects I have a ctd issue. Engaging prochannel (layer B, long push on transport-backward-button) crashes sonar (bandlab). I recognized, that this only happens in this particular song. It seemed to be damaged, for all my other songs everything seemed to be OK and working.
Btw I also got back to cakewalk after some time with presonus, a realy good product anyway. But Sonar it feels like home :-)

jp
Pages: 1 ... 8 9 [10]