User 905133

More info / details / etc. would help others to help you diagnose the two issues you mentioned: not receiving any midi signal no sound coming from instruments "loaded up" on track 1 Based on this: all anyone knows is that you have an audio track inserted into the project. There is no evidence that you have any instruments / soft synths inserted. There is no evidence that you have midi data routed / routed properly to an instrument in such a way as to produce sound. Etc. ** I am not very familiar with video tutorials, but there are a number of tutorial makers who have posted links to videos in the forum here. Not sure if those are some of the ones you looked at. Personally, I learn things from some of them, but others don't resonate with me (wrong learning style, too much stuff I know to wade through, etc.) However, there are plenty of comments in the forum that other users find the posted videos helpful. Perhaps you haven't found the right videos yet. If you haven't inserted / routed / setup VA-3 successfully, perhaps you need a tutorial on how to insert plug-ins / instruments / VSTs / soft synths, etc. Also there is a Cakewalk Reference Guide and also on-line documentation if you prefer text. **I typically use the Menu Bar > Insert > Soft Synth... method to insert an Instrument Track, but there are other methods that work (personal workflow preference).

That's a step in the right direction. In my experience, if data is going into the computer and midi-ox sees it, Cakewalk sees it as long as I have the device / port routed correctly. I am not sure what you mean by "Cakewalk won't detect the MIDI inputs." To me, if the E463 shows up in preferences, Cakewalk is seeing the device. Diagnostically, the next question I'd ask myself is "What then might cause the midi data to not be recorded onto a midi track?" and that would get me to look at other preferences (such as MIDI Driver Mode. I use MME for my older midi gear as opposed to UWP. Note: to change MIDI Driver Mode, access Preferences before a project is loaded. Probably more important, though is your track routing. "All" shows all of the track control widgets. [ I ] shows the selected device. [ C ] shows that I am routing my MK-449C to a soft synth called SI-Electric Piano. Note: the MIDI Echo / Input Echo button lets me hear what my MK-449 usb keyboard plays on my SI-Electric Piano Plug-in through the amp/mixer/speakers connected to my PC's Realtek Output. Top part of LED display shows I have audio.

Another option is to use Menu Bar > Insert > Soft Synth... but you don't get the wizard that way (if you like that method).

Did you save the edited sounds in a User Bank? and did you change the preset being loaded from the factory bank and preset number to the one you saved? Initial track preset: I just tested this and it worked for me when I stopped and restarted the project. However, when I saved the project and reloaded it, MyPiano 1 was no longer there. Not sure why (yet). Update: I had to save the bank and re-load it. Then, my tweaked preset was in the bank. But the preset widget still said Piano 1 (not the name I used).

Uh oh!!! 😨 Maybe I should have counted my blessings before signing up again. 🙈

2-3 weeks ago I spontaneously wondered if MSoundFactory's Meldaway Grand could be tweaked to do per-note, velocity-responsive pre-paired modifications. I need to teach myself more about how to do deep sound development with MSF. So far, I have just learned some basics. One idea is to simulate a ping-pong ball on two adjacent sets of string that bounce differently based on velocity, including bouncing inside the piano's structure. Other ideas include simulating a set of keys on a key ring. Maybe other prepared pianos like the ones mention already have macros that can do these kinds of things?

(1) Are these weekly giveaways new? (2) Does anyone here actually get the newsletter? (3) Has anyone signed up for the newsletter and not gotten them?

Correct me if I am wrong, there is also no evidence that midi data is coming from the E463. For something like that I use a tool called midi-ox. Do you have that? If so, the keyboard should show up as a midi device and the Input Window would show the midi data coming from it. I looked at the E463 manual yesterday. Let me look at that again. I seem to remember a statement that might be useful if the computer itself isn't seeing the data. Found it: MIDI-OX shows my connected devices: MIDI-OX shows keypresses from my MK-449C on MIDI channel 2: MIDI-OX shows data received: Notes (JMO): Don't let anyone tell you MIDI-OX is confusing. It can be overwhelming to grasp all at once. It can be very simple to use if you learn the basic tools first. For basic diagnosis, it is best to run MIDI-OX without other software that uses MIDI running (off; not booted).

Very nice--sounds happy and uplifting to my ears! Thanks for sharing. And congrats on completing # 12.

I was curious about Sekaiju when I saw it and tried a few things yesterday to get Cakewalk to insert random patch changes that showed up in Sekaiju like you had. I couldn't. I did notice the bank switching in the event listings you posted. Today I also see there are "Normal" patch changes as well as "Patch 100.." patch changes. Given the different ranges of the bank values for the two (Normal v. Patch 100..), I am wondering if different bank switching methods were used.** I only used bank switching for my specific gear and I haven't looked into bank switching on soft synths. With my limited understanding, it sounds like you have done an excellent job trying to pin down what's going on that results in the random program changes. Maybe someone who knows what is going on under the hood of Cakewalk has some insights into why its happening. BTW: Sounds like video game music!!! **https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Instrument_Defs.07.html

Does Neo Piano respond to your E463 in standalone mode? If so, (and assuming the plug-in has been installed correctly and Cakewalk's vstscan picked it up correctly), perhaps you haven't set up the routing properly. When you say "Perhaps CbB isn't sending the inputs to Neo Piano," what steps have you taken to diagnose that? When you play notes and record them onto a midi track, do they show up in the track (even if you can't hear them from Neo Piano)? If so, try inserting the Neo Piano and then point the midi track to the Neo Piano. Does the recorded midi track play? If not, does Neo Piano have any indication it is receiving midi data (e.g., keypresses seen in the UI, a flashing led, response to a patch change command)?

https://archive.org/details/virtual-sound-canvas-vsti-vsc-mp-1-1.6 https://www.cakewalk.com/Support/Knowledge-Base/2007013096/Using-Virtual-Sound-Canvas-DXi

website seems to be working now.

[withdrawn for now, pending some more exploration]

Thanks for confirming that some PC modules do accept remote control.

It shouldn't do. ACT controls the parameters directly via the VST API, not via MIDI. Suppose someone uses MIDI [aka Remote Control / Learn] within ProChannels, not ACT, to control parameters?

For fans of Echo/Delay that have Voltage Modular, R_Ware has has a basic, but useful Tape Delay in the R_Ware X Airwindows free collection of tools.

Thanks for the clarification. I read this too quickly 😞 : Actually, now that I think about it, I read it before my morning coffee. NOTE TO SELF: Drink coffee early--even on the weekends! 😜

Thanks for mentioning this. I wonder if Melda's MTuner would be a good tool to use with Hexcel to generate MIDI (real time audio to MIDI) perhaps using a very stable (pitch-wise) waveform.

I took advantage of the discount previously and like the sound and mechanics of Softube's Echoes. I wish there were a way to turn off the tape-through-the-record/play-heads animated graphic. The plug-in uses more CPU that other tape/echo/echo plug-ins I have** and I have wondered if that's due to the animation or the DSP. I suspect it might be due to the animation because minimizing the UI or switching to another window drops my CPU usage by 8-10% [Task Manager: Cakewalk Application]. **Disclosure: The quickie test included plug-ins from Cherry Audio, IK Multimedia (TR5 instance and inside MixBox), MeldaProduction (including MB versions), and PSP Audio. A single live layer was performed on top of a MIDI performance using a Sample Tank instrument/Preset (one track). ST4 in CbB routed to Voltage Modular (as FX Rack). As a fan of echoes and delays, I really like having Softube's Echoes among my tools in part because the aesthetics of the UI impart a nice feeling. And it sounds quite nice!! But if the animation is using that much extra CPU in a single instance, I'd really like to be able to click on an additional display button at the top to turn the animation off, to not see it, and ideally to save some CPU power. Here --> A setting would be OK as an alternative, but the display button would be quicker. Note: This might not affect people with more powerful CPUs. Just thought I'd mention it as long as I checked it out for myself.

Thanks for the explanation. I used to use index cards as a reminder of which knobs and sliders were set up for different CCs/parameters. Now I have tiny stickers with the CCs numbers below the knobs and above the sliders and I tend to use CCs numbers consistently for parameters. So, I am a fan of reminders. Out of curiosity, did you try adding the text comments to an instrument definition?

Are you talking about having text reminders in dedicated midi track so you know why you are using certain CC parameters and CC values?

It should come through the other device--the one that hasn't been disabled. The original problem related to an audio device that was not being used for Cakewalk's audio. The solution suggested was to turn off the device in Device Manager that wasn't being used. If you only have one audio device and you turn it off using device manager, you have a different problem than the one stated. Are you saying you only have one audio device?

From what I have seen, telling loved ones they should quit, getting on their case, etc. can be counter productive.

Feature Request: Add right-click MIDI Learn / Remote Control to Tap Tempo Reason for request: pressing a mouse button to set the tempo is not intuitive, not natural, and inaccurate. Pressing a key on a keyboard (or any other preferred MIDI controller, e.g., pads on a drum machine, breath on a wind controller, etc.) are more intuitive, more natural, and more accurate.