-
Posts
3,958 -
Joined
-
Last visited
-
Days Won
9
Everything posted by Promidi
-
Option to turn off multidock capture hot spot area.
Promidi replied to bitman's topic in Feedback Loop
I believe If you hold down CTRL while dragging the window, the auto docking does not occur..... At least, on mine, it prevents the auto docking. It would be nice if the bakers could reversed this.... that is, unless CTRL is held down, auto docking does not occur. -
Confirmed! That worked here (using smart tool)
-
Yes
-
Please list machine specs.... CPU, ram , graphics, audio interface, OS, etc Have you tried the following? Updated all drivers (manufacturer's website, not via Windows update) Installed all Windows updates Disabled c-states and IEST Updated Vdist runtimes Disabled anything that mentions power saving. - Use Highest performance mode Disabled USB power saving CPU min and Max to 100% Disabled Core parking Makes sure all sound card and applications are set to the same sample rate Disabled wireless i/f while using CbB Start+run > systempropertiesperformance , select Adjust for best performance If you have an Nvidia card, Set power Management mode to Perfer Maximum performance. Nvidia Control Panel > 3D Settings > Manage 3D Settings These are some I can think of. Others may have more
-
I can assure you that it's MIDI..... Poly Aftertouch is part of the MIDI spec.
-
I already have - see my previous comment. I made sure it worked using X3ta 2 and assigned Oscillator level to Poly Aftertouch I created a three note chord on a single track, entered poly Aftertouch events to affect the middle note only (using my CAL script). The result is that the level of the MIDI node only was changed. So, depending on the synth, per note parameters on a single track can work already.
-
I just did.....
-
Currently, the only aftertouch events that are visible in the Piano Roll View is Channel aftertouch. While Cakewalk does support the entry of Key aftertouch events in Event List- editing them is tedious I have made a CAL script that when you have a note selected along with Channel aftertouch Events, the script will convert those Channel aftertouch Events to KEY aftertouch Events that affects the selected note. However, the only way to edit the resultant events is via the Event list - very tedious. Can we please have Key aftertouch events selectable as MIDI Event Types to edit in the controller lane in the PRV. In the MIDI Event Type dialog box, the value field could define the note of the KEY aftertouch Events
-
Some synths can already so this by assigning polyphonic aftertouch to level. Z3TA2 can already do this.
-
You might want to also rule out a hard drive issue causing this. It may not be a hard drive issue, but if it is, you don't want to have this keep happening and possibly getting worse over time. Check your Windows system Event viewer (Start + Run eventvwr ) for bad blocks on any hard drive. You could also check your drives with CrystalDiskInfo https://crystalmark.info/en/
-
[CLOSED] Cakewalk 2019.12 Early Access
Promidi replied to Morten Saether's topic in Early Access Program
Are you using the latest version of Melodyne? (Which is 4.2.4.001) If so, then you might want to get on to CbB support https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633 Or Celemony support: http://helpcenter.celemony.com/hc-2/support -
Those sample rates definitely sound non standard. I would have expected one of these: 44.1khz, 48khz or 96khz
-
What are you using as your MIDI controller? If it has USB ports (and you have the correct drivers installed), what happens if you plug the MIDI controller directly into a USB port?
-
The only reason you would need your old Cakewalk is if you need any plugins that came with it. That being said, if the required plugins that came with your old Cakewalk are only 32 bit, then you might want to give them a miss and find 64bit alternatives. Using 32bit VST plugins, while technically possible, can result in a less than stable installation. Cakewalk by Bandlab does not require your old Cakewalk to install. You can install Cakewalk by Bandlab on your new PC and have that as your only DAW. So, yes, Cakewalk by Bandlab does work with Windows 10. However, it has to be the 64bit version of Windows. 32bit operating systems are not supported. Cakewalk by Bandlab supports Windows 7 SP1 or above. Also, you might want to make sure your Windows 10 PC has all updates installed and that you have the latest drivers for all of your hardware. Confirm this with the manufacturer's websites rather than rely on Windows updates. Note: you did download the correct file.
- 1 reply
-
- 2
-
-
-
I am also inclined to suggest using the onboard sound enabled and have it set and set as the default audio device for Windows.
-
Someone claimed that the Facebook App is built in to recent Android devices. I responded about uninstalling the Facebook App for such Android device is possible by rooting their phone. With regards to disabling telemetry in Windows 10, I have disabled as much as I can and still, I have not experienced any loss of useful functionality. I still have the ability to install Windows updates come Patch Tuesday... and Windows 10 1909 still does I everything I need it to do.
-
Are you saying that the Facebook App is "part of Windows"?..... I have yet to see that....
-
It can if you know what your doing... and if you root your phone...
-
Why not just leave windows audio setting at 48 khz. ASIO bypasses Windows audio anyway.... so while you're in CbB, windows audio setting is being bypassed. (Though I can't explain why setting windows audio to 96k give pops and click in CbB) Maybe a CbB dev could chime in here.
-
You say you record at 96K. You also stated that changing windows audio setting to 48 khz and the pops go away. From that, I gather that changing windows audio setting to 48 khz and the pops return. Just confirming. As well as recording at 96K, Are your projects also set to 96K (under tempo) Preferences | Audio | Driver settings > Default settings for new project , set to 96K? (I am assuming so)
-
I was asking whether you disabled Intel Speedstep (and possibly C-States) via Windows or did you do it in the BIOS?
-
Did you disable Intel Speedstep (and possibly C-States) via Windows or BIOS?
-
Driver mode ASIO?