User 905133

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.

Hmmm. Had to get out a scope to "hear" it. ?

I have had similar experiences. With the introduction of Sonar X1, there was much re-learning needed from the way I had done things in numerous pre-X versions. Finally with Cakewalk by Bandlab, I have been working on teaching myself many of the new features and changes introduced in Sonar X1 and since.

Note to self: See this as being possibly related. UPDATE [2020-06-27] related to the thread referenced: (1) The interception of midi data as explained by @msmcleod for a different problem (re: pedal CC data) appears to be unrelated to the problem in this thread (re: remote control of the Inspector-based Arpeggiator). So the solution for that problem doesn't help here. (2) However, a generalized observation made then seems to be related--specifically, the "usual" behavior of remote control midi seems to be either unintentionally or quasi-intentionally intercepted via automation/automation lanes. [This was suggested in a thread related to an issue a user had with automation, though IIRC it was removed because it was off-topic to the original problem.] [emphasis added]

When you replied to my suggestion that you look at the event list, I assumed that you had done that; but, now I am not sure. I raise this because when I tried Mark's suggestion with this: no CC 64 events (On or Off) were recorded. However, without redirecting the sustain pedal, they were. (1) Had you looked? (2) If you had, were there CC 64 events recorded? I ask because I have been trying to diagnose what might be a bug related to MIDI Remote Control and the Inspector-based Arpeggiator and this issue seems to be related.** **Briefly (without rehashing the whole issue), although the Shift-key interception per Mark's comment did not produce a midi event,*** it did allow me to latch an Arpeggiator with the foot pedal! (It doesn't solve the problem I have been working on, but it points to something that might be related to a possible bug.) ***Clarification, CC 64 on/off (1) did not place sustain events into the event list for the designated arp track, (2) did not trigger changes in the arp's latch state as displayed, but quite surprising (3) did latch the the arp!!!!!

Alternative option to solve the problem removed