User 905133

(1) That's 98% vague. I know you know how to open executables, but you provided no information on how far you got, assuming you opened the program, ran it, navigated to where your cakewalk project files are, and opened one of them. Are you saying that ProjectScope showed you the tracks in the file, but not the names of the instruments you used? Are you saying when you double clicked on a *.cwp file, Cakewalk didn't boot and didn't try to open it? (2) Did you put the names of the instruments in the tracks in when made the projects? Did you use Sonar/Cakewalk's "Notes" to document your project? Just so you know, even though I downloaded ProjectScope previously, I downloaded it again to verify that the download still works. Where I used the name of an instrument in the track name, its there. Where I wrote Notes, they are there. As for Plug-Ins, so far as I can see from the *.cwp files I tested with ProjectScope, that panel only includes FX plug-ins, not soft synths. If you used *.ins files and were looking for a program that would open up the correct *.ins file and dereference / look up the bank / patch assigned in the track widgets, I don't see ProjectScope as having that ability. Not sure if that's what you mean by "it doesn't do anything, just sits there open."

In terms of hardware synths, some have CCs hard coded to specific synth engine parameters as msmcleod noted while other hardware synths have an open architecture allowing many/most CCs to be assigned to any available parameter. Usually the manufacturer's documentation spelled all this out. Some software synths also spell this out, too. In addition, with hardware different controllers (knobs, buttons, sliders, pedals, etc.) can be mapped to different CCs. Some software synths allow users to map incoming controllers/parameters to different functions/parameters; some are "hard coded." Some manufacturers have been good about making MIDI implementation easily available; some have been meticulous in the details they provide; some have even made it easy to understand. While the basic MIDI Implementation sheet is a good starting point, the additional documentation can be invaluable. Mapping CCs to parameters can be done in different places along the data route, including (as msmcleod noted) within a DAW. Other software along the data route can also be used.

Goes back to antecedents of synth-pop with Dell Shannon (Runaway) , The Tornados (Telstar) , Delia Derbyshire (Dr. Who Theme), and others.

See also: https://www.bleepingcomputer.com/news/security/chinese-hackers-abuse-vlc-media-player-to-launch-malware-loader/

While I do have some Workspaces that have a full-sized Console on Monitor 2, my "Narrow Strip Test" was done with Views on a single monitor. I will try tweaking one of my Workspaces with a full-sized Console on Monitor 2 to see if that fails to get saved and restored properly. 2022-04-11 Update: Took the "Narrow Strip Test" Workspace; tweaked it to have a full-size Multi-Dock with the Console on Monitor 2; verified narrow strips (track, bus, output) work consistently with several different projects. I call it "Narrow Strip - D on Mon 2" (D = Dock). Duplicated the lens [copied & renamed via Windows], then converted all the strips to wide and saved the Workspace. I call it "Narrow [W] Strip - D on Mon 2." Did lots of loading of files and switching of Workspaces. So far results have been consistent. Testing was done on a PC with a duo Core processor. Not sure if more cores would introduce glitches in the restoring of Workspaces properly. I have the option to "Apply Workspace on Project Load" checked. Not sure that would make a difference. Since people have their own work flows, I am not sure this is worth more time. Since each PC is different and since there are so many variant workflows, it might be impossible to isolate specific factors that would account for our different experiences.

On 3/7/2022 I created a test Workspace I called "Narrow Strip Test." Immediately afterward, I tested it with various recent and older *.cwp files. I was going to mention this, but I forgot. So I just tested it again. We all have difference experiences, but in my experience, when I load projects I do get narrow strips. Also, when I add new tracks (instrument, soft synths, audio, or MIDI) or busses, they get added in as narrow strips. Not doubting your experiences; just saying I have gotten different results. Not sure why, but it might be worth trying to figure out why. I am very much aware that sometimes things work on my PC that don't seem to work on others' PCs. But I am curious to know if I will get the same results (all narrow tracks) with project files others have done on their PCs. If they show up as all narrow strips on my PC, I can (1) post my Narrow Strip Test Workspace if you want to try it and/or (2) try to reconstruct what I did to create the Workspace. I tend to test many things to add to my personal knowledge base.

I'd also want full vst3s with all parameters properly named and exposed so they can be manipulated via external controls, including program change and bank switching plus the dynamic voice allocation as found in VIP. Oh yeah, I'd also want them to be 100% compatible with all the expansion packs. ? Almost forgot: At least 4 audio outs, preferably more.

Yes. I recognized that. I was trying to call attention to an overly complicated solution in hopes that the forces around here that make the decisions about what to spend their time improving would see the value in a streamlined method like you proposed. I guess it wasn't clear that I was endorsing your idea. Sorry if that wasn't clear from my post. I will try to fix it. Just to be clear, last June I felt it was way too time consuming to be able to find specific data types in the event list, but I recognized at the time that there was little chance that the Event List would be given any attention.

I remember using a filter in conjunction with the Event List. For example, let's say you use controllers in a range from 21 to 26 (or 71 to 73) you could find them more easily. Using this method will leave black rectangular cells in the left-hand column for the desired controllers. At the time of that post I specifically remember thinking it would be nice to have this functionality built into the Event List management system. But I didn't suggest it because (1) most Cakewalk users seem to be more interested in manipulating audio data, not midi data and (2) the devs seem to have plenty of more important stuff to do. However, there seems to be an increased interest in midi these days. I would love to see a redesigned edit filter tied in with the Event List if its possible and if its a now deemed to be a reasonable use of development time. Perhaps targeted filter-by-type dialogs or fly-out menus, radio dials, check boxes, etc. based on each specific data type?

When I got the e-mail about the one-year anniversary sale on Cherry Audio's "Eight Voice," I search by that name and not seeing the deal announced, made a post which included links to some videos. I then learned that Larry had indeed announced it. (See his forum link posted above.) For my needs and uses, I agree with the positive assessments posted above. It is my daily "go-to" soft synth to test that my PC's audio is setup properly. Noodling with it at the start of every day warms me up. It might not meet everyone's needs, so I would encourage others considering spending from $15.95 to $19 to take a look at some of the resources linked here:

Thanks for the DJ Swivel video. I actually had picked it up as part of a "StayCreative Free Plugin Bundle (Ozone Elements & DJ Swivel Spread)" a year ago and finally installed it last month. I played with it a little, but it is nice to hear from DJ Swivel explaining it!! I already discovered how the dial can make audio sound mono varying shades of wide, so its nice to learn from his tips.

I am also biased wrt the PSP Ultimate Bundle Larry mentions. I generally only use a handful of the PSP VM modules, but the Ultimate Bundle (link to pdf) is a very handy collection of 37 VM modules and is at an amazing price. FYI (for those unfamiliar with Voltage Modular): PSP's VM modules can be set up in an instance of VM within Cakewalk (kind of like a Voltage Modular FX Rack).

https://store.cherryaudio.com/bundles/eight-voice-synthesizer https://www.pluginboutique.com/products/7433 https://www.jrrshop.com/cherry-audio-eight-voice ADDENDUM: See Larry's post linked below and under "Cherry Audio Oberheim SEM and Ultimate Voltage Modular" for some GROUP discounts available. Some people love it, some people hate it, some people are in the middle. JMO: You might want to try the demo to hear if it meets your musical needs. TIP: Its available at a number of places, so you might want to wait to see which one works best for you based on loyalty currency, purchase perks, etc. No need to rush into this. https://docs.cherryaudio.com/cherry-audio/instruments/eight-voice/getting-started BIAS: At the start of the day, to verify that my audio PC, Windows 10 Audio Services, audio interface, etc. have booted properly, Cherry Audio's "Eight Voice" is my go to synth. Noodling on it a bit warms me up. I have no financial or personal interest in sharing the info here. What others have said here in the Cakewalk Forum: https://discuss.cakewalk.com/index.php?/search/&q="Eight Voice"&quick=1

Nahhhh. Zappa wrote notes on staves. It looks more like a Xernakis score (or someone of his ilk).

But there is value in reading these threads. I just wish that people had stopped the OP bashing. For me, the added bashing just added fuel to the fire that had been pissed on and was mostly put out just so the fire could could be rekindled.

Come on. Are you trolling here in an attempt to inspired a political debate and try to get yet another thread closed? Well, OK, then. I'll take the bait for a "good" cause: Like "they" told Viet Nam War opponents, long-haired hippies, etc. who in the late '60s and early '70s didn't like what "the government" was doing, "Why don't you move to Russia?" ? BTW, that's a rhetorical question--no answer needed.

LOL. Now I have to ask: @Pilutiful Were you only upset that Track View switched to a midi track and its OK with you if it gets switched to another type of track? To be clear, any time I click on the the small track icon to open up a synth's UI, that track gets chosen. If I was working on a different track, I then have to go back to it. But maybe by "different track" the OP really meant "the same track?" ?

I figured it out. You were pointing to vertical meters.

AHA! Evidently you were pointing to the vertical meters.

I also did some additional fiddling with the Synth Rack and different insertion modes/property settings. Depending what the OP wants to do, choosing just the "First Synth . . . . " or "All Synth . . . . " output options (not split/simple/midi options) MIGHT be what the OP wants. When I chose just those options ^^^ and had an Audio Track highlighted/selected, clicking those those synths didn't move them away from the Audio Track of choice. HOWEVER, when I added a MIDI Track and pointed it to one of those soft synths, the solution falls into the 99% unwanted behavior category. Fun speculation, and I learned a lot more about options for using the Synth Rack. Still not sure what the OP's needs are and if any of this will help. Maybe we will get some clarity on this? Or maybe the devs have a crystal ball that is better than mine.

I listed both (instrument track or MIDI track) because I tested several things, including a hybrid instrument track, a split instrument track, and a midi source only track. (I think we are saying something similar, though). More problematic for me is that the OP has not stated what the goal is for clicking on the Synth Rack and what the workflow is that creates the 99% figure. For example, let's say the OP routinely (almost exclusively) uses non-hybrid instrument tracks and does some editing on the non-MIDI potion in the track view, but then clicks on and turns the knobs in an expanded Synth Rack.** When I did this, in 100% of my tests earlier, the associated MIDI track was selected in the track view. If that's what the OP does, I believe the OP is correct (the associated MIDI track gets selected and it is a workflow distraction) but just didn't explain the reason for the request. However, we just don't know the OP's workflow, if there is a better solution than clicking on the Synth Rack, etc. **By the way, if this is what the OP does, I would have suggested the option of using MIDI Learn to assign a knob, slider, etc. to control the virtual control in the Synth Rack. I didn't mention this earlier because the OP hasn't stated the reason for clicking on the Synth Rack and therefore might be totally irrelevant. Anyhow, since this is a feature request, I'm done trying to read the OP's mind.

At first I was wondering why the OP was clicking in the Synth Rack without wanting to have an associated track (instrument track or MIDI track) selected in the track view. So I played with the Synth Rack a bit in different ways than I usually use it. In at least 99% of the times I have used the Synth Rack, I don't have an issue with an associated track being selected, but workflows differ. It might be helpful if the OP gave more details on how the Synth Rack is being used (i.e., why click on it if you don't want to do something with the associated track?).

FAMOUS LAST WORDS, Or: Lessons from "Goodbye" threads: Lesson (from the OP of the above): Not only are they good reading, but maybe they should be required reading before someone posts an "I'm done with Cakewalk!!!!!" post. ?