Jump to content

Sam Stalos

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

4 Neutral
  1. Just to follow up, my issue with Win 10 20H1 has been resolved. I went back to Microsoft yesterday (7/16/21) and there was a new update to Win 10 with the word "critical" in it's name. (2021-07 KB5004237) I let the computer do its thing and it took about 20 minutes to install and reboot. I should have tested the DAW at that time to verify that the bug was fixed, but when I opened Cakewalk I saw Cbl had issued the new update (2021.6 Build 053) MSMCLEOD mentioned, and I installed that version right away. Everything works. There's something MSMCLEOD mentioned about One Drive. I deliberately avoided activating One Drive on my DAW, and so my updates may have been uncoordinated when I was caught in the initial 20H1 Win 10 update just a day earlier. (I also noticed that in June, the previous update was labeled 20H2, which if memory servers, verifies that update versions and builds do not necessarily adhere to numerical order. Regardless, if you pay attention to the Win 10 update versions, 20H1 now seems to be cooperating with Cakewalk just fine, or vice versa.
  2. I can only confirm that Windows 10 Update 21H1 is a bust. I've been running elaborate tempo maps every day for a week and everything has been working smoothly. But this afternoon, I accidentally updated to Win10 21H1 19043.1083. What a mess. I keep the DAW off line and avoid updating as much as possible, but eventually Win 10 will go into update mode before I can catch it. I'm running Cakewalk 2021.06, Build 050. 1. .wav files don't appear in the Cakewalk project folder, i.e. in the Audio folder associated with the .cwp Project Folder. That Audio folder is completely blank. But those files will appear using Windows Explorer. If you try to open the .wav file with a double click, the computer may lock up. I didn't play with this quirk long enough to test the variables. So you can do a mix down, or render just a track or two, and even Export a complete mix, and everything is fine. And save like crazy every chance you get. But the next time you open Cakewalk, those files are not to be found using the normal commands in Cakewalk. 2. If you save an open .cwp file in Cakewalk , that file name will not appear as an option the next time you boot Cakewalk. That is, the file name will not appear in the Recent Projects menu of the Start Screen. 3. You can find the .cwp file using the Open menu in Cakewalk, and it may--or may not -- boot, and it may work for a while. But even if you save that .cwp file frequently while working on a project, it will not appear as a Recent Project once you close and reopen Cakewalk again. I expect an extortion letter to arrive any day now offering to return control of my DAW. Then Win 10 will work with BitCoin like a champ.
  3. Thank you so much for the clear explanation. Have an extra glass of Belhaven on me.
  4. Versions prior to 2021.04, e.g. 2020.098, had a feature labeled "Step" in the "Insert Series of Tempo Changes" menu that does not show up in my upgraded version of Cakewalk. (Photo attached.) I would always set the Step Command to .01 when doing tempo mapping, and everything from Sonar 5 to 2020.098 has worked great. This Step feature eliminated the stair-stepping effect that occurs when changing tempos that were not simply abrupt, immediate shifts to a new tempo. I interpreted the Step command as controlling the resolution of the math involved in making minute changes to tempos over time, and I always reset the Step to .01 with the acknowledgement that this change placed more calculating stress on the CPU... but I never had any problems. The readout calculations would appear resolved to .001. I have been working with polytemporal music for the past 14 years, which involves simultaneously changing tempos in several different instruments over an extended period of time. The changes are likely to involve a gradual "shifting" to a new tempo, and are to be accomplished as smoothly as possible. In the composition stage, I obviously work only with MIDI, which has, so far, never stressed my CPU. I also use an external hardware sampler, SPDIF, and an internal sound card to keep the processing clean and reduce latency, although I now assume I could probably shift to the Instrument-Softsynth/VST/USB approach without introducing latency problems. At present, the MIDI tracks -- once rendered to audio -- are then incorporated into other time-based media (such as video and visual timing mechanisms), which means that maintaining the highest precision is important. It's been visually difficult to check for stair-stepping using the new Tempo Mapping system because of restrictions on display real estate. I have always used Cakewalk in the past because of its "full page" Tempo Mapping view and extremely malleable approach. Is there a way to get back to minimizing stair-stepping by incorporating a Step command in these newer version? On page 390 of the Reference Guide, I found a topic called Tempo Map Decimation, and I don't know if it is relevant to my question. Apparently, the Tempo Map Decimation can be reset to 3 different values. It involves making a modification to the cakewalk.ini file. But before I do that, I wanted to make sure I understood the consequences of making such a change. I don't understand how the tolerance being set to 1/16, 1/32 or 1/64 could be as precise as reducing the Step resolution to .010 or .001. A reduction in the Step value to .010 or .001 would seem to be more precise than a reduction to 1/64 of the beat (note) value. And is the reliability of the calculations not affected by the base tempo of the composition, e.g. resolving the tolerance to a tempo working around at 80 BPM verses one working around 200 BPM? I'm starting to run some tests with the new track-view/node envelope system. If any has worked through this resolution problem, or if I can get some feed-back on the elimination of the Step option, I would appreciate hearing from you. Thank you for your response.
  5. I would like to test the changes to tempo mapping features contained in the new 2021.04 Build 27.04.0.3175 version before updating from my current Win 10 version, 2021.01 Build 098, 64 bit. My primary use of Cakewalk involves the manipulation of tempo maps. In a previous post, user Stefan Gorej asked about setting up a “roll-back” copy of the current version before downloading and installing the new 2021.04 version. Noel responded with a link to the current release notes on this new version. @Štefan Gorej ... You can roll back by following the instructions in the current release notes. When I followed Brothwick’s link, it seemed to suggest that the roll-back procedure to a version not involving BandLab Assistant could be made by simply logging in under a new name (basically establishing another account), and then downloading the latest 2021.04 version, which does not involve using BandLab Assistant. That would be fine. I just want make sure I understand this correctly. When the new 2021.04 version is installed, the older version would be left intact, and one would then have two versions of Cakewalk on the computer. If this is correct, should I save my older projects to the .cwb format and import those .cwb files into the new version, or would that be unnecessary? Please verify.
  6. Sure enough. Win 10 published a new build (Version 1903 build 18362.900) and everything now works. I did make a dump file but decided not to send it in having been through this before. I'm sure Cakewalk has enough bugs to fix without absorbing Microsoft's load. I just wanted to document the consistency of this problem for those who get caught by the next Win 10 update .
  7. Previously used .cwp files in Cakewalk now lock up after just 23 seconds of playback or recording after updating to version 26.05.0.039 of Cakewalk and updating Win 10 to build OS 18362.900 of Win 10 version 1903. I am running on Xeon processors working at 3.07 GHZ with 12 Gig of RAM. After Cakewalk abruptly locks up, I cannot shut it down via the Red X at the top right corner or open the File Menu to Close properly. In fact, no menus will open once Cakewalk freezes. I have to use Task Manager in Win 10 to close Cakewalk. As expected, once Cakewalk is shutdown via Task Manager, it will not open again; but when I try to shut down the computer I encounter another problem. Following the shutdown of Cakewalk, I cannot shutdown Win 10 via a Left click on their Start Icon on the bottom left. In fact, no menus appear via a left click on that Start icon, not even the obnoxious thumbnail listing of all the programs available on the computer. I can however exit Win 10 via a Right Click on the Search Bar adjacent to the Start Icon. Both Win 10 and Cakewalk by Bandlab were updated this week of July 1, 2020. Prior to updating, Cakewalk by Bandlab had been working fine for many months, but I have seen this phenomenon before, and it always seem to be linked to concomitant updating. Trying to research and fix the issues during the in-between-re-update-time is a total loss, and I have learned to sit back and wait for subsequent fixes to come down the pipe weeks later. But then, how is this a productive tool for composing music? Deadlines and commitments are abandoned, which makes the use of such unreliable tools a fools choice. Why did this updating stumble not occur with earlier versions of Sonar and Windows software, or did it and I just didn't notice? It makes Cakewalk as a midi sequencer on an orange screen under DOS seem like an advantage. At one time Microsoft published that it was possible to simply go back to an earlier version of Win 10 under their Settings Menu, but I see that this option has been removed. To combat the updating issue, I have learned to keep my DAW offline. But eventually, when pressured by Microsoft, and when seeing new updates available from BandLab, I give in and update both programs at the same time, hoping they have worked out their mutual bugs. But this time, they have not. I can open and use Sibelius on the same computer without any problems, and have done so after this last updating fiasco. There is some responsibility toward fixing this problem on my part, which is to report these bugs when they occur... and to recognize that it is impossible for software developers to consider every possible configuration of hardware that now exists, especially in the PC world. I tried adopting the Apple approach about 12 years ago, but what an expensive joke that was. And so I am registering my official "bug report" at this time. It would help to know that I am not alone, or insane, or unreasonable, and that COVD-19 hasn't mutated to a version that eats magnetic code on the SSD disk in my computer. Please advise.
  8. Thanks to David Baay and 905133 for responding, and thanks to 905133 for catching my mistake. Take the rest of the day off. Everything is working fine now. The Widget Filter, eh? When you step away from this technology for several years, the jargon fades, and I needed an expert to bring me back into the game. If you hover the cursor over most panels/buttons/menus headings in the Track View of Cakewalk's layout, a brief description of the function of that button/menu will appear in the "Help Module" panel on the right side of Track view. But nothing appears when the cursor hovers over the Widget Filter, not that I would have understood the meaning of "All, Custom, Mix, FX or I/O." Your clarity and experience were much needed. Thank you again.
  9. Midi assignment problem. I have two different .cwp songs using Band Lab’s Cakewalk (BLC-latest update as of 12/3/2019), but I am achieving different results with each song when trying to use an external midi sampler (EMU-Virtuoso 2000.) Both songs are on the same computer using the same BLC software. The Midi Preference settings for both songs are shown in the attached photos, where the 2495 Audiophile card (Delta AP Midi) is included and routed to Emu's Virtuoso sampler, which is assigned to Channel 1. See midiTrack27.png, midiTrack28.png and midiTrack5.png. The settings are identical for both songs. I can’t remember how I configured the first .cwp song, the one that works perfectly and created with an earlier version of Sonar -- what small, obscure button I pushed, what small menu I unchecked/checked. In the first song, the one created in an earlier version of Sonar, the midi output from BLC to my 2496 Audiophile card (Delta AP MIDI) in Win 10 (using the 24-bit version of the Win 7 driver), assigns Channel 1 to the legacy sampler (EMU’s Virtuoso 2000). The Virtuoso hardware is assigned to Channel 1 via the Preferences menu shown in MidiTrack5.png. The Virtuoso hardware comes with an instrument definition file, which BLC uses to categorize the hundreds of different samples in the Virtuoso hardware via a series of dropdown menus in the Track View, i.e. patches and banks, as shown in midiTrack21.png thru midiTrack22, 23 and 24.png Everything in this first song works just as anticipated, and operates just as it did in an earlier version of Sonar on Win 7. This first song continues to perform flawlessly in BLC. But that second song, the one I just recently created in BLC... The second song (.cwp file), with all the same parameters and menu settings as above, does not show the same series of drop-down menus in the Track View. See the comparison of the drop-down tracks for the first song in midiTrack8a.png and the second song in midiTrack2a.png. What magic button did I fail to push to make the Midi Track output menus of this second song stop proliferating as in the first song, so that Channel 1 becomes assigned to the Virtuoso hardware? The Input drop-down menus of both songs are identical: None (checked). The first midi Output menus for both songs are identical and read: Delta AP Midi (checked). But that’s where the similarity ends. In the second song, there is no further proliferation of the Output menus which would allow me to designate Channel 1 as going to the Virtuoso sampler. In the second song, the one not working correctly, I can see that the BLC midi output reaches the Virtuoso hardware. There’s a midi input light on the hardware that blinks with each midi note that arrives, and it’s blinking correctly. And for some reason it is locked onto a piano sample by default, and I’m unable to change that assignment. In the second song, under the Insert menu, a selection of the Bank/Patch Change menu shows Output 1 and Channel 1, Bank Select Method set to "Normal," nothing in the Bank slot, and an Acoustic Grand Piano selected in the Patch slot. I can change the Bank slot to one of the Virtuoso Banks, click Okay, but it won’t hold this new setting. If you come back to the same menu, it has reset itself. The Virtuoso hardware uses the “Normal” bank selection method, and this selection appears in all the subsequent menus and settings in BLC. The Add Instrument menu under the Insert Menu only shows the Cakewalk TTS-1 software and does not allow me to alter that selection. There are a series of detailed instructions on midi assignments at BLC’s Cakewalk Documentation website starting at www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x200B8, which I’ve read and re-read. No luck. Other than cloning the first song, eliminating everything but the midi track each time I want to assign midi to this Virtuoso sampler, what are my options? What am I missing? Any suggestions greatly appreciated.
×
×
  • Create New...