Jump to content

azslow3

Members
  • Content Count

    344
  • Joined

  • Last visited

Community Reputation

177 Excellent

1 Follower

About azslow3

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. May be complete miss... but I remembered REAPER has RADAR projects import. May be worse a try.
  2. "The most popular" rumor about audio interfaces and latency: Latency importance is oversized (each 30cm from an audio source adds 1ms latency in any case). In general, latency limits are: vocal monitoring throw software - <3ms. Not used in practice, since partial direct monitoring (with zero latency) solve the problem. You normally want just reverb added, and it can have 50ms+ latency. e-guitar soft sim monitoring. Preferably <5ms. e-drums with soft synth monitoring. Preferably <7ms. MIDI keyboard with soft synth monitoring. 10-15ms is tolerable is most situations. Under 20-25ms is playable. for anything else latency is not important CPU power has little to do with lowest possible latency. The difference is like a truck vs sport-car, you can drive with 10t but that does not mean you can drive fast. Sure, in case you need that 10t (in audio case many heavy soft-synths and effects) you need a car which can do that. CPU characteristics are declared as "power", not as "speed", even so CPU frequency is naturally perceived like a speed. The fact is, any 10MHz DSP easily beats in latency (many times) most powerful 5HGz desktops. The key to success with latency is strict audio optimization in BIOS and OS. And there can be brick walls (in hardware and drivers). "The most popular audio interface" is Realtek. 2i2 is a good entry level music audio interface with pre-amps, it is not in top league in any category (latency, drivers, sound quality) but it is reasonable for many use cases. Stable usable latency is around 8ms, and so it can be inconvenient with e-guitar soft sims only. For comparison, under the same relaxed settings on the same system top (in latency) interfaces have under 5ms. The lowest allowed by driver latency is rarely usable in practice even on optimized top system. When looking into "latency charts", buffer sizes under 32 are not meaningful. Check what particular interface does with buffers 64/128 on 48kHz. "Accordingly" in the context means the highest setting of latency you are still convenient or the lowest your system and the project allows without pops and clicks, in case you get problems in your convenient range. That is human, project, system and tasks dependent.
  3. msmcleod probably will fix sends in HUI part. Theoretically, everyone is free to do this (the source code is on GitHub). HUI is even more archaic then Automap and Windows 7. And it was not invented to have cross-DAW compatibility nor to support different controllers. It just happened one particular DAW was (is) a "standard" in "professional studios". This DAW was almost refusing to use anything not "specific for me", hardware manufacturers was proud to claim "market leader compatibility" and other DAWs (with way more bright controllers support) could gain some users by "you can use pro hardware". BTW mentioned DAW has other owner and own controllers with new own protocol now (Cakewalk partially supports these controllers) Novation Impulse comes not even close to the capability of original "HUI device". It simply has way less physical controls (and those which are there are of lower quality...). So, it is "usable" with HUI software but functionality and usability is not at the level of specially build for such controller solutions. "InControl" on "Newer devices" is just... yet another MIDI button. The rest is up to particular DAW plug-in for particular device. I guess they was tired supporting Automap and decided to sell "MIDI controllers" instead (Automap devices was not standard MIDI class devices for OS). HUI protocol use 2 MIDI messages for most controls and is not symmetric (controls and feedback messages are slightly different). In contrast, Logic protocol use 1 MIDI message per control and is symmetric where possible (so except for encoder rings). There is a good reason to use 2-4 MIDI messages per control, when the number of such controls is huge (f.e. to map all parameters of digital mixers to the MIDI world). For dedicated DAW controllers it make no sense.
  4. Well, that confirms the device use Zone 0xb for Assigns 🙂
  5. You have realized that.. knobs are always sending the same messages. And since you can control Pan, they are working fine in Cakewalk. So record messages when you SWITCH to SendA...D, so messages from buttons.
  6. @chakko Well... if motivated... you can install AZ Controller (https://www.azslow.com/index.php/topic,6.0.html), load HUIv2 preset (https://www.azslow.com/index.php/topic,223.msg1386.html#msg1386) and with a bit of luck it will switch device into HUI mode. Then you can press keys Novation specify for switching into Sends mode and switching sends and write down what you see in the "Last MIDI event" doing so (in the Options tab check CC interpretation is in 14bit mode, HUI sends 2 CCs per button, but at the end any of them will give us some hint what should be defined).
  7. @msmcleod It is hard to find high resolution picture for original HUI, but knobs assignment section is in Zone 0xB ("Send a" ... "Send e") In your code I see you translate assignments from buttons in Zone 0x17 (Auto enable).
  8. I recommend find out and post which MIDI message the button responsible for switching into Sends mode send to the DAW (MIDIOx or simply recording it as MIDI event into track when Control Surface module is removed). Probably msmcleod will be able to help then. BTW I suggest to try MCU mapping on the device. MCU protocol (more precisely LC protocol) documentation is still freely available, HUI always was closed proprietary protocol. Mackie plug-in implements all features of MCU, while HUI as you can see is "Beta".
  9. Yes, I have started to write it when I was stuck in attempts to setup existing plug-ins the way I want 🙂 https://www.youtube.com/watch?v=Baoo0-CysSI&t=87s is a good starting point in your case. For switching between strip and sends control... that can be challenging for you at the beginning. In case you have future questions about AZ Controller, please use my forum or PM.
  10. With "Cakewalk ACT MIDI" you can't configure 8 buttons + extra 4 arrows (at most 1 of them as a "Shift" for 8 buttons). WAI based buttons (f.e. Mute) is also not an option, if I remember correctly. But with 2 Banks and corresponding switch buttons you can make vol/pan <-> sends working. With "Cakewalk Generic Controller" you can configure 2x8 + 8 + 4. But switching banks, like vol/pan to sends, is not possible. To avoid any limitations you can use AZ Controller (www.azslow.com). But it is harder to configure. The world is not perfect 😏
  11. Most discussions when it comes to 32 vs 64 bit (44.1 vs 96 kHz, etc.) ends discussing fidelity. While in practice the problem is in bugs/mistakes (sure they can influence fidelity up to destroying the sound or even crashing the DAW). 32bit floating point is sufficient to represent 24bit audio (fixed point) bit accurate. Really meaningful for the best audio interfaces are 20-21. Really meaningful for a human is even less (16-17 at most). But people which write music software are way less careful then people calculating atom reactors, also checking that cranking all possible parameters will not produce crazy math calculation is almost impossible. As the end effect final numbers calculated using 64bits and 32bit can differ in the first 16 most significant bits. F.e. if you export audio as 16bit after 32bit and 64bit processing the result can be (up to significantly) different. I repeat, that should not happened in case the author is careful in what he/she is doing, but all of us are not perfect. Also audio processors (f.e. VSTs) use different code to process in 32 and in 64 bits (VSTs process audio in these 2 formats only, f.e. they can't process 16/24bit fixed audio). Normally one code calls another or one source is used to produce both codes, but that is not guarantied. I mean it can happened one code has a bug while other doesn't. May be not really a bug, just different result. Based on written, I suggest to use the same engine all the time to avoid possible troubles. So after mixing in 64bit engine also export in 64bit engine (but not into 64bit file formats, that is not my suggestion). I guess when computers was old, there was people who prefered mix in 32bit and export as 64bit, a kind of "online"/"offline" quality. ----------------- Still OP question is valid and not yet answered: does the option in the Export dialog still switch the engine or just a historical artifact? F.e. in case 64bit is on in the preferences and that option is unchecked, does Cakewalk "downgrade" the engine to 32bit during export?
  12. Up to date there is no usable solution (since X1). But there was a thread where BandLab has mentioned a movement in that direction, so may be some lucky day Cakewalk is more accessible... Till than I can suggest another DAW with strong accessibility support and related active community: https://reaperaccessibility.com/index.php/Main_Page Original scripts for Sonar 8.5 are problematic since Windows 8 because of GUI change. There was rumor with some "classic" schema that was possible with Windows 8, but I doubt there is something stable for Windows 10. Better stay with Windows 7 in this case. On hardware side, NI keyboards are accessible. I mean Native Kontrol and so all wrapped synths are accessible using these keyboards (in any DAW, in REAPER a part of DAW controlling as well). With Behringer X-Touch Compact or USB Gamepad it is possible somehow control Cakewalk accessible way (last time tested long time ago with Platinum), but that will be disappointing experience.
  13. That was my impression. May be adding "preferred communication language is English" to the TOU as well as one single "International" board (for those who don't want or can't use English, threads like this one can be moved there instead of deleting or confusing some people) is a good idea. But that is up to BandLab. I am so used to be in multi-lingual environment (up to 5-6 different languages in parallel within one room) that I don't feel anything unusual once someone write/speak in any language (known or unknown for me). But I understand that can be confusing (as it was for me 25+ years ago). What I find really confusing is proposal "please write in English" (written in English) to someone who has used some other language... And even more confusing the same proposal to someone who has replied using the language of the question... That make no sense for me (unlike for example a suggestion to repeat the question in English, written in original language).
  14. If that is written to me, I think that violates the spirit (and may be community rules) of this forum. BTW my forum is in English, but I explicitly accept questions in languages I know. Everyone is free to define own rules on own resources. If you have a link which explicitly or implicitly FORBID other languages on this forum, please post it. I am not aware about such restriction and I am ready to apologize in case it exists. It is not so simple to find forum rules. I somehow remember on old forum there was some. https://blog.bandlab.com/community-guidelines/ does not mention any language (but has "Respect" section...).
×
×
  • Create New...