User 905133

oops; sorry.

I have almost no experience with PRV, but I looked in Sonar 3 Producer and am wondering if this is what's being discussed? First png: I had no data, but had a line drawing tool. It had a big + [plus] on the right side of the line that didn't get captured. ADDENDUM: Second png: hand drawn and line tool with data. Third png: tool bar with "Draw Line [L]" Tool

I copied both "OK" and "Key/Mouse Killer" into the User Workspace folder. I opened Cakewalk, then a project, and first switched to "OK." No problems. I then switched to "Key/Mouse Killer." Both my typing keyboard and mouse worked. I will try a few more times. (2019.11 build 54) UPDATE: I tried playing projects, loading up to 3 more projects while one was playing, stopping and starting the transport, switching to and from the K/M Killer. At no point did I lose the ability to use my mouse and/or keyboard. I hope support/staff and help track down this elusive problem.

Not sure if its just me, but are the preference boxes in English on both the German and French pages? If so, it makes sense--the help pages tell users in German and French how to change Cakewalk from English.

@David Baay OK. Got it working. Thanks!!!!

I appreciate the opportunity to test the consistency of my Workspaces-in-Progress. I now have more confidence in their design. Good to know the cause in your case.

Try [P] > Customization > Display > Languages (Just a guess. I tried switching to German and got a Windows Pop-Up (UAC) asking if I wanted to allow Registry Console Tool to make a change.)

I suspect this might be related to discussions in recent threads addressing screen sets, locked screen sets, and Workspaces. Are you using any of those to save/restore your project? This is one recent thread. I recall others. Also, in a thread related to a recent hotfix, there's this: See also Noel Borthwick's comments in the thread linked above. I recall other related references, too; I hope these (above) help get you to a customized solution that works for you.

I like this as an alternative to going into Event List mode (multiple methods to do a task). Thanks!!

I know I did this; I'd have to find the project (or the thread where it was discussed). I seem to recall a specific thread** where someone wanted to be able to stretch/shrink an audio file to make it fit a certain length. There might also be a method where audio is turned into a clip that has tempo. If I tried that, I don't remember. Maybe someone else can explain that process. UPDATE: See David Baay's setup steps for using Audiosnap. Footnote: From what I have seen plain old inserted/imported audio plays at its own rate while midi (and groove clips, I believe) track with the transport tempo. **Addendum: This is the thread I was remembering. PS: I seem to remember reading or seeing a video tutorial about other possible techniques (possibly mapping the tempo of audio). If so, those might be better options. I will defer to other who have more experience with / knowledge of those techniques. Addendum 2: Just found my "Fit-to-time" test to visually show at a glance the effect of the stretch. Mine was a textural piece, but it might work for your needs.

Not 100% sure if this is what you want, but it seems to me the Custom Module on the Control Bar might be what you are looking for (based on your reference to the save and cut buttons. I will work from that assumption for the time being. If the Custom Module is not on your Control Bar, enable it by (1) right clicking on the Control Bar, (2) selecting Modules, and (3) enabling the Custom Module. From there you can right click on any button and choose what functionality you want the button to have. Footnotes: (1) Below is one of "Mine" just as an example. (2) If you get into creating different Workspaces for different tasks/workflows, you can have different sets of customized buttons. For example, I have been working on a Staff Entry Workspace to help me focus on (1) entering notes either by a usb keyboard or by the Tools Module and (2) editing them either in the Staff View or another view (including the Event List).

Hi. I am just a user of SONAR/Cakewalk; I am not staff and have no official connections. I would not even call myself a "power user," though I have been exploring it since this past summer. When I first saw your post, I explored the fret board because I had never seen it even though I have used the software for decades. I like learning new things others mention about my DAW of choice in case I can use new-to-me features. I set up a simple loop and I did see some problems with notes. Unfortunately, since I have no need to use the fret board display, I did not explore it as much as I have done with other features. It seemed to me (just a guess) that there is some sort of intelligence with the fret board display. For example, an isolated note will show up in one position, but based on later notes, the position will change. Maybe there is some sort of look-ahead process in the note placement algorithm (again, just a guess). I seem to remember that depending on the size of my multidock window, sometimes when the loop restarted, the first note was there and sometimes it wasn't. Again, I am not 100% certain of this as I didn't explore it extensively. I am just guessing here, but maybe the re-draw fret board itself interferes with the drawing of the first note. From what I have seen based on a very obscure bug I found and reported (which was subsequently fixed), I believe the team definitely wants to fix bugs. From what I have seen in this forum, it helps if they can reproduce the bugs. Maybe there is a configuration setting (just a guess) that can be changed that would help. @mgustavo Glad to see someone else looked into this. The things I saw were in the fret board display (as opposed to the Tab display). Let me see if I save the project I used to test. If so, I can post a screen shot. UPDATE: It does not look like I saved my fret board test.

OK, you convinced me. I looked at Cantable again. It looks like they have a fair number of issues, complaints, feature requests, etc. That being said, I didn't see any verbal abuse of staff or users who like Cantable. For the time being, I will stick with a known quantity, even if it seems to be optimized for non-live uses.

Will Workspace users still be able to design some with icons hidden and some with them showing?

Is the multidock floating? If so, dock it. Or are you trying to have something like a full track view on Monitor 1 and a floating console on Monitor 2? Also, thanks for clarifying which specific visual elements are problematic. PS: I just tested one of my Workspaces [developed when they were Lenses]--"Undock-Float-001d." The console and Inspector open up on Monitor 2; other panes open up on Monitor 1. Not sure I can post a screen shot--will try. You don't have my custom Theme, but if you want to test drive the Workspace, let me know. On three tries right now opening three different projects, the console and Inspector opened up on my 2nd monitor and the first monitor has the expanded track view, floating Control Bar, and Floating Browser. Here's a different project with the same Workspace plus the same project when I switched to the Advanced Workspace [all on one monitor]. When I switched back to Float-Undock-001d, the visual arrangement returned. The second monitor had no Cakewalk panes/windows because I used the Advanced Workspace which only uses one monitor. Did I mention I think Workspaces are great (definitely improved from the former version of Lenses) and am looking forward to further refinements as forecast in another thread? In any case, I posted these in case you can use them to help with your Dual-Monitor setup. ADDENDUM: See warning about undocked / floating windows when having multiple projects loaded. Based on my experiences, not recommended!!

I used to take the "Widget Filter"** for granted. It's usefulness solidified for me when I used the Track Control Manager. I think taking 3 -5 minutes on two different days creating my own Track Control presets [or "Widget Filters"] when I got back into Cakewalk in the summer really helped me. For each type of strip we can decide what "widgets" are useful to us personally. It helps me to focus by reducing visual distractions. For example my "==> MIDI" filter helps me focus when all I want to do is assign midi I/Os, banks, and/or presets. OK, now I can take the rest of the day off! ? ------------------------ ** Officially, I think its called "Track Control" in the Reference Guide. "Widget" is defined as being related to StudioWare panels, though "Widget Section" is the first column in the Manager, the Reference Guide refers to "Track view controls (widgets)," "Cakewalk knob or widget," etc. The term "widget" seems to have many uses (function overloading?). Anyhow, I think "Track Widget Filter" fits.

Thanks for confirming this. I have one range (C2 to C4) going to an instance of TTS-1 on a single midi channel. I will try another range to create a second zone. (I am more used to setting up zones on usb keyboards!) OK. Got two different ranges going to two different channels on TTS-1. Addendum: with overlapping ranges you can get layering. Thanks for asking about this @bertus weyers and thanks for the suggestions @scook This technique fits in with a couple of personal project templates I have been working on.

I have never used it, but maybe the MFX [Midi FX] Event Filter might help to route different note ranges to different soft synths. Edit: Before today I never used it, but the MFX [Midi FX] Event Filter can be used to route note ranges to the same or different soft synths. Sorry. If it can be done using the Midi Even Filter to route incoming midi data to VSTis, I haven't been able to figure out how. See below for other options per scook and for the "Proof of Concept" marked up screen shot.

There should be several options. Here's one: Insert a midi track, point the midi out of that track to Cakewalk Sound Center.

What ROMs for you have installed? Based on the screen shots, it looks like you have the Holy Grail ROM. If so, it looks to me like the Instrument Definition is set up correctly to have Cakewalk switch to the ROM's presets. [E-MU P2k: Holy Grail (8192)] . Do you also have ORCH1 and ORCH2 installed in the Virtuoso 2000 ROMpler? Are there any others installed? It looks like you have Cakewalk set up to use the User Banks 0, 1, 2, and 3. If those are filled with Virtuoso presets and you don't have ORCH1 and ORCH2 installed, they will produce no sound at all. Also, what MIDI MODE are you using (in the Virtuoso) omni, poly, multi? Out of curiosity, what OS does the virtuoso have install? As David points out, "Insert Instrument" is not for external gear. Addendum: Also, in one of the screen shots your track "widget" filter is set to "All" and in another "Custom." If you are missing some "widgets," try changing the filter to "All."

BTW, I am not sure I would call it an oddity (step 5) because that seems to be the way Sonar has been done at least since Sonar 3. Back in the day before I used soft synths, when creating multitrack recordings the way input echo/thru functioned seemed intuitive (at least to me). Lay down a line (separate track from other lines), mute playback of a recorded line, test other lines live, unmute to listen to interaction of previously recorded line and live overlays, etc. At that point there were options to undo previously recorded lines, make a new track for an overlay, etc. Perhaps with the addition over the years of different record modes, take lanes, the extensive use of soft synths, etc. my simplistic method makes the input echo/thru behavior seem less intuitive. Technological complexity can do that. Perhaps you want to request an option, something like "[ ] On track mute, always suppress input echo to external gear." Or perhaps the Mute-Solo-Record button array could have its own border to convey they relate to tracks and there could be some Input Echo/Thru buttons within a different border. If I understand why you are calling the behavior an "oddity" perhaps options like these (if possible) might help you and others. Just a thought. Just in case its not clear, I don't think one work flow is "better" than any other; ideally, we should all have what works best for us. One of the things I have appreciated about SONAR/Cakewalk is its flexibility. So if there is the possibility of adding optional work flow preferences, I think that's consistent with the history of the software. Clarification: Which insert soft synth method did you use? I have discovered that sometimes the methods [of inserting soft synths] used make a difference. Sorry I didn't emphasize that in the original post. What I mean was: How did you insert the soft synths you tested? For example, (a) from the Insert Menu, (b) by right clicking in the track area, (c) by dragging an instrument from the Browser, (d) from the Synth Rack, etc. I don't think your results would be different based on which method you used to insert each soft synth (it shouldn't), but I was wondering which method you used. Footnote: I try different things out when other people mention them because it helps me to make better use of the software. For example, while exploring your observations, I got an idea (and tested it) on how to use a particular soft synth/sampler I have that can have up to 19 output buses from a single instance of the VSTi. If I can make it work the way I want, that might mean I can make a smooth workflow transition--from developing tunes using my old school hardware to porting the tunes to the VSTi (same manufacturer and basic synth engine as the hardware) and possibly only needing a laptop to play out (a long time goal of mine). So, thanks for raising this issue!!

Regarding step 6 above: Which insert soft synth method did you use? I have discovered that sometimes the methods used make a difference. Not sure if it does here, but I was just wondering about this. Thanks.

Over the past several months I have been working on designing some personal Workspaces [formerly Lenses]. For the past week I have been using a something I got from another user--locked screen sets. It seems to be helping me to move things around in a project and then return to my desired visual arrangement. Not sure if this will work for you (if you haven't tried it yet), but maybe. Workspaces are global and Screen sets are per project,. So, in several projects I have saved my preferred initial screen set in slot 01. and locked it. I also make an unlocked copy in another slot so if I tweak it, I have both the original locked version and the one I last had prior to saving the project. I am still experimenting but thought this might be useful. BTW, I trying to figure out where the width of the control bar (collapsed or expanded) gets restored from--or if there is a bug (sometimes it gets restored properly; sometimes I have to manually expand it and then collapse it). I usually just use the default track icons, so I just tested this by changing two if my icons. Depending on which Workspace I chose, either the track icons were shown or hidden. If shown, the new ones were there. It seems to me that specific track icons are saved with different projects, not screen sets or Workspaces. Now that you mentioned this issue, maybe I will start using custom icons.

I don't use them, but I have Sonar 3 and Sonar 8.5 installed on my Win 10 PC. I have to shovel more snow, but if no one else tests those in the meantime, I am interested. I don't remember which version does what in which way(s). I just let my ||: eyes-brain-ears-brain-hands :|| bio-feedback mechanism do its thing as best it can. Earlier today (based on your observations) I also tested for the effects of record-armed mode, counting down period, and midi recording for the PRV keyboard and note display (as well as for the echo/thru to ext gear path when the track is muted and the midi input track level leds). With the Sonar 3 and Sonar 8.5 tests, that should represent a good sample of versions. If not, I think I still have more versions on my XP PC. Uh Oh. Its snowing as hard as it did yesterday and overnight into today. ? (An hour or so later) Initial Results re: SONAR 3: track echo/thru (midi input echo on & auto thru modes) work as expected: (1) usb keyboard -> external sound module [track mute is irrelevant for this test; not testing recorded track data, just midi input echo/auto thru]. (2) when recorded, notes get placed into PRV in real time; PRV keyboard doesn't show usb keyboard key presses as I believe that feature came later, IIRC. (3) midi data does not seem to trigger track leds in any condition (and I didn't see an option to make this happen). (4) midi-track-i/o-channeling functions as expected; usb keyboard on midi channel 2 (a) is echoed to external gear midi channel 2 (b) except when forced to a specific midi channel by the track i/o routing and (c) in both cases, the data gets recorded as midi track 2 data. Tentative Conclusion: I expect if I were to test other post SONAR 3 versions, the track echo/thru would function the same way when routed to external gear--except for any new options or features that might have been added. Footnote: It took longer than I expected to remember where things were in the pre-X SONARs.