User 905133

If it were me, I might be offended, and blow up and swear etc. in the privacy of my own home. ? Or I might just shrug it off. I don't know since I don't post my music. Or, I might reply with a "thank you for telling me; you might be interested to know the forum interface allows anyone to ignore anyone else; I won't be offended if you choose to use that to skip over my posts." I think writing about it and asking others' thoughts is a good response, too, if that fits who you are. I just hope that it doesn't inspire expressions of anger and hostility, retribution, etc. There's too much of that in the world for my tastes and I hate to see it in this community of Cakewalk users. Thanks for asking.

Thanks!! I haven't narrowed it down but I did get the Windows folder hierarchy to work properly (left pane of Media Browser) both in a floating window and the multi-dock. Thanks also to LoopJunkie for prompting my exploration of the Media Browser in new ways. So much for having left it docked on the right for ages!! I am already thinking of ways to tweak my workflow! Never too late for an old dog Cakewalk User to learn new tricks!!!! ?

By any chance is there another setting deselected? I get the same results as before with "Window Layouts" deselected. Perhaps, something also needs to be done with saving a non-locked current Screen set? Thanks. AHA!!!!! Doing something with Screen sets seems to be involved. I also (1) selected Screen set 1, (2) made sure it was unlocked, and (3) re-saved the project since screen sets are per project. I am not sure which change allowed the hierarchy to be retained, but it seems to involve Screen sets.

ooops. was intending to do a PM.

I will assume you are not using the Media Browser docked on the right or left and unless I am missing something (like a setting/parameter),** I confirmed you you found. Perhaps Cakewalk resorts to what Windows tells it? Maybe one of the experts in the ins and outs of Cakewalk can tell us? UPDATE: This probably doesn't help, but when I clicked on the + in the folder above the left panel, it took me to the folder above the level of the clips in the right panel. UPDATE: **See Promidi's comment and related discussion

In my limited experience, when rebooting Cakewalk, Workspaces restore the visual configure as the Workshop was stored (as opposed to the last visual configuration used). On a current project, I have started to explore saving a "CURRENT" Workspace when I shut down the project for the day. So far, that seems to return me to a "last state before shut down" visual configuration. Maybe that will work for you (and others). 100% Opinion Here: If you have not worked with creating and saving Workspaces, I highly recomend reading the Reference Guide, On-line Documentation, the New Features posts, esp. where Lenses as renamed as Workspaces, and the comments people have posted--esp. from the people who know Cakewalk inside and out, but also from the people who have experienced some frustrations. (If someone wants to reply saying, "Workspaces should be simple enough to use intuitively, without having to read up on them," trial and error also works. Trust me--I have done enough of it, and I have also appreciated the wisdom of others here!)

Ages ago I lived in Allentown, PA for a year, not too far from Macungie, PA--home of the Allen Organ Company. I had heard about a computer music keyboard they had and having been interested in college in any possible potential to connect a computer up a synthesizer (such as a Moog), I arranged for a visit with the person who did the album showcasing the RMI Keyboard Computer. It was a great tour/demonstration/explanation!! To me, it was esp. amazing to see the ability to slide in a punch card and to have the organ play the sound that was coded on the card! I think midi had already come out, so I asked if it had (or could have) the ability to use midi. Unfortunately at the time, the reply was, "We don't speak midi." As I understand it, the Allen Organ Company eventually did get on board with midi.

Texture!!! Reminds me . . . I still have the manual for Prism 1.0 (c) 1989--also pre-Windows 3.1 and with an amazing GUI! "For IBM-PC's, compatibles, and Yamaha C1 Music Computer."

Not sure if this is part of the problem (i.e., if you successfully copied new sound sets, but they just don't seem to be available) , but I recall with some of those old soft synths a function key (maybe F5) needed to be pressed to repopulate the patch selection menu with newly added patches.

Thanks for the suggestions @Base 57and for the mini-videos demonstrating them @msmcleod . I anticipate that this technique will be very useful with a current project--making a set of oral history recordings much more listener-friendly.

Thank you for the reply!! For me, your issue seems to be related to the kind of issue I have seen--namely, that in some very definite instances, midi data does not seem to be going where it is supposed to go (and therefore doesn't do what it is supposed to do). Coupled with the fact that Mark's suggestion points to a way that midi data can be intentionally intercepted from going where it normally goes, it seems to me possible that something in the software could also be intercepting midi data unintentionally** so that it doesn't do go where it should (and therefore doesn't do what its supposed to do). **or quasi-intentionally, that is intended for some functionality, and coincidentally preventing it from going to other functionality

Two of the things I thought about asking for with regard to my use of the staff view (i.e., formal feature requests as opposed to points in discussions) are: (1) to have the tools back within the Staff View window/pane/multi-dock and (2) a split multi-dock (or separate/multiple floatable docks/panes) so we can have both the Staff View and the Event List visible/accessible at the same time instead of having to jump from tab to tab in the multi-dock. I imagine that some people who also use the PRV extensively might benefit from these abilities, too. For me, I tend to enter note data in with a midi/usb keyboard and edit them, though sometimes I enter notes directly on the staff. So, I am wondering, what things would help you editing with the Staff View?

Thanks for chiming in on this. It makes sense. Just to clarify, I like and appreciate the new functionality. So far as I am concerned, these continuing improvements are great!!!

Hi. Welcome. I have a question about the line I emphasized above. Was it (1) Cakewalk by Bandlab (a Windows program) that started or (2) the web-based Bandlab app (which works in Chrome, not FF, as far as I know)?

Thanks for chiming in with these details. Just to be clear, I like flexibility. I am not sure, but from the little testing I did last night, the Track(s) number seemed to insert those many instances of the soft synths I tried, though not each in its own folder. Maybe it is "Synth Instances?"

removed

removed

removed as it referred to a prior discussion before this early release.

Can you uncheck the orange buttons under "Advanced" in that section? UPDATE: I will check now--what soft synth are you using?

I saw this and thought it was optional--for those people who wanted new behavior (multiple instrument tracks as either stereo or mono) if softsynths allowed for that. Hmmmm. You have my curiosity; will have to look at this tomorrow. Clarification: This is only about the new "Instrument Track per Output" feature in the Early Release.

I remember! Also, I remember C-64 MIDI!!! Commodore asm routines!!!! Mondo fun!!! - when programming was easy! ?

Thanks for the update! Based on how useful I I have found Z3ta+fx over the years, I hope that between the Surge people and the Cakewalk people, it can be made to work in Cakewalk. Thanks also for the others with fx plug-ins.

I would prefer midi features to be fixed, esp. remote control midi of the Inspector-based arpeggiator.

You have inspired me to see if I still have TouchDAW on my tablet and to test it on my PC. I test drove it a few years ago with a lap top and have long forgotten about it. Thanks for the reminder!

This interests me because I have been working on writing/tweaking in part via Staff View. I have not gotten to the point of using it in mixing, recording, etc., so have not considered the track level issue--yet. Thanks for the clear steps in the Workaround section which seems to me to also serve as the steps to try to reproduce the issue.