Jump to content

User 905133

  • Content Count

  • Joined

  • Last visited

Everything posted by User 905133

  1. There are a number of options in Cakewalk for saving the size and position of windows. We all have different preferences and opinions based on our workflows. Some options I use: (1) maximize/dock floating windows [or un-collapse, depending on the window] and save the project, (2) save a screenset to slot 1 [or another one], and (3) use workspaces [Note: "None" as a Workspace should restore your UI to the last used configuration. Also, Screensets work on a per project basis; Workspaces work globally--from project-to-project]. (1) (2) (3) Assuming your file is a Cakewalk file (e.g., *.cwp), probably the easiest to to maximize (image 1 above) the floating window and resave it. If it is a *.mid file (as in your example), you can maximize it and save it as a Cakewalk (*.cwp) file. If you are doing this regularly with midi files (e.g., *.mid) you might want to use a workspace (image 3 above) that has a non-floating track view window. [For example, I just tested opening *.mid files with a custom Workspace and with the Advanced Workspace. Both allowed me top open midi files into a non-floating track view window automatically.] This way you won't have to re-save each file as a Cakewalk file. I am sure there are other methods; these are just some I would use as a plain old user. I hope they help.
  2. I thought this was odd, so I checked. I seem to have None as an input option.
  3. Footnotes: https://www.loc.gov/preservation/digital/formats/fdd/fdd000119.shtml lists both .mid and .midi . It looks like they based it on http://filext.com/ . Though smf is listed in the The File Extension Source data base as Standard MIDI File, several other file format evidently also use smf . The Library of Congress digital preservation document does not include the .smf extension as a standard for preserving midi files. Also, it looks like opening *.midi files via several methods will be supported in the next official Cakewalk release.
  4. Good to know; thanks for the clarification.
  5. Will *.midi and *.smf be treated the same way under all circumstances? Just curious.
  6. User 905133

    View Event list

    If you are using the Basic Workspace, try "None" or one of the others.
  7. Based on my experience with several other failed Windows 10 update attempts, the so-called "Rollback" did not restore my pre-failed update settings. On several occasions the most obvious signs were BSODs mostly coming from my usb 2x2 midi interface drivers, but sometimes others related to my PCI audio card drivers. In fairness to Windows 10, these are older devices that Windows 10 might not have current drivers for--even though they work when I install the manufacturer's drivers manually. On several occasions I have uninstalled the devices and the drivers (even checking "hidden devices and deleted the drivers that might be there). Also, I suspect that in my case part of the issue is that I have multiple 2x2 midi interfaces from the same manufacturer. On several occasions I have re-connected and reinstalled them one-by-one (with a PC reboot in between). That seems to work to prevent BSODs, until after an "ordinary" Windows 10 update. I have never been sure if Windows' Compatibility Telemetry (or some other "protect-the-consumer-from-him-or-herself" process says, "I don't like this device and/or driver)" and changes my system. 😛 So I usually just assume its my older PC and devices. But when I see others with somewhat similar experiences, maybe its not just my system.
  8. You might have noticed that some software plug-ins, etc support microtonal / alternate tunings via scala.
  9. moot details deleted; footprint reduced since fix will be fixed in final release
  10. Removed: After reading the following clarification of the original post, any additional discussion of ways to record CCs as I tried to bring up would not help.
  11. I wanted to do follow-up on this because one of my long-term to-do sets of projects is to port and update some of my older tunes from a hardware sequencer (backed up as *.mid files) into Cakewalk. So, thanks for asking about this--it gave me a convenient opportunity to move one step closer! 🙂 Results will be different based on a number of things, especially the files you are opening, but in case it helps, here are two screen shots. (1) shows the result of placing file 2 after file 1. Here I have zoomed in all the way. (2) shows the result after file 3 has been placed after file 2. The zoom is almost all the way out. I look forward to the recommendations of others on this process. (1) (2)
  12. Yes, I understood you wanted the files one-after-the-other. (Apologies for using "concatenate." My bad. 😞 ) In my test, I used files with multiple tracks. I did not juggle the different clips on the different tracks to line them up. So, if a bass part were on track 3 in file 1, on track 7 in file 2, and track 2 in file 3, I did not drag them around, duplicate them and reassemble them into my own bass track, etc. It should be easy to do in Cakewalk. Since I don't generally do this, I will defer to others who do and to others who know the relevant links in the online documentation and the correct pages in the Reference Guide. I just jumped in because I saw you wanted to place the files end-to-end, knew I could do it with audio files, and wanted to quickly test to see if it could also be done with *.mid files.
  13. EDITED: I don't remember trying this with midi files, but with *.wav files I want to concatenate, I zoom in as tightly as I can, put the now time at the end of one file, and then drag the file in after it (that is, where the now time is). I will test this shortly to see if this also works with *.mid files. I will report my results either way (works/doesn't work). I tested with the method with PTN loops and with entire midi files. It works. I placed the Now Time cursor at the end of one file (in the Track View) dragged the second file to where it lined up with Now Time cursor. (That is, I released the mouse button when the file being dragged was directly on top of the Now Time cursor. I did this both from Cakewalk's Media Browser and a third party file navigation tool I use.
  14. Very true! It would be easy enough to have a limited, dedicated workspace with the larger "Scrabble-for-Juniors" I, O, C, B, P icons but the normal-sized track control buttons just for the times I am setting those. Thanks for leading me to this option-for-aging-eyes.
  15. Thanks for testing & confirming that. I have looked for possible settings that might be affecting this, but have not found anything. Its a shame IMO, because I really like the arpeggiator. Maybe someone else knows a secret setting.
  16. I have used a momentary contact foot pedal plugged into a usb/midi keyboard and the knobs on the keyboard. They work fine for other functions, just not the arpeggiator functions. It is clear that the midi is going to where I want (latch, on/off, etc.) because the virtual button changes its state (lit/unlit), but not the function itself. I will try again with octaves.
  17. @kzmaier Have you ever gotten the Inspector-based arpeggiator functions to respond properly to remote control midi commands?
  18. @Astra-Ios Several months ago I explored the Inspector-based Arpeggiator. I really liked it a lot and was building a custom template. Unfortunately, I was never able to get midi learn to work the way I wanted. (I am still not sure if it is a bug or just user error.) Depending on what you want to do, it might meet your needs. In my experience, if you don't mind using a mouse for turning the arps on and off, latching them and un-latching them, etc. they seemed to work fine. The problem I had was that via remote midi, the virtual buttons changed (lit/unlit), but the functions did not change based on remote midi commands. Other than that, I thought they were quite flexible. http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Recording.17.html
  19. I see that there used to be skins for z3ta+ 1.5 on the internet, but I can't find any links for skins that still work. My guess is that the one in the video (and posted above) is a skin. (I like it, too; so, I looked for it but couldn't find it.)
  20. Is this from Z3t+ 1.5 or a newer version (or an earlier version)? Perhaps they are the initials of the sound developer? (Just a guess.) In 1.5 there is a bank that says . Maybe BT stands for BigTone? Speculation verified by Canopus. See below.
  21. Interesting idea. I thought resizing images would cause problems for the UI's stability so I never tried it. But as my eyes continue to age I might explore expanding the size of frequently used / hard to read elements. More research needed. Intuitively I suspect that trying to enlarge the buttons so they match the double sized icons won't work, but based on your suggestion its worth it to me to try. EDIT: Suspicion confirmed:
  • Create New...