mettelus

More an FYI since it is not stated outright on the PB sale, but Vielklang is "Discontinued but supported through 2024." I was sort of surprised that this is being sold.

When you mentioned Guitar Tracks Pro, are you working with old .wrk files? One idea that comes to mind is open those old files first, then "Save As..." with CbB with a new name to a .cwp file. Test that out with one of them first and retry what you have been doing to see if that helps. I am not sure of your system specs, but it could very well be a system configuration issue. I would try the above first to see if that does anything for you before digging deeper into things.

Type "Services" into the Windows search bar and open that app. You can maximize that window that pops up if too small. Sort the services by name (click on the top of the first column to sort), and scroll down to "PreSonus Hardware Access Service." If you right click that you can stop it there. Also, that should be set to "Manual" for Startup Type so that it only opens when you start the Universal Control. If that is set to "Automatic," right click that, select "Properties" and set Startup Type to "Manual" in the center of that window. A lot of Windows services default to "automatic" which is unnecessary if not in use.

Either closing the app in the task bar (right click -> Quit) or hitting CTRL-Q with the Universal Control window open and active will exit the app. It does not stay resident in memory. Once closed you should be able uninstall/re-install per the above.

Are you doing that with new tracks you created or the imported tracks? The only thing that comes to mind is if this is done to an imported track is there may be FX/routings present that are giving CbB grief. There are cases (where you cannot simply use older FX) that need just the track content (audio/MIDI) shift-dragged into the new track and "mixed from scratch."

I think the biggest hurdle for me personally when getting acclimated to Take Lanes was paying attention to the cursor as I was moving around clips. The smart cursor has several actions embedded into it, so zooming in a smidge while learning controls made it much simpler. Pay attention to where you are hovering and what the cursor looks like before taking "action" on clips. Once you force yourself to work through it a few times, it does become a very fast method to work with takes.

Not sure if you got this resolved, but also be sure to set either set something else as your Windows default playback device, or remove the driver manually (and restart). For Windows, the manual method should be similar to what Focusrite advises to remove their Mix Control app (the "For Windows" section near the bottom). IIRC, there was an update to the Universal Control in November about a week after I began testing it that resolved the only issue I had with the app. You definitely do not want conflicting installs running even if you need to remove both of them and install the new one from scratch. Quick Edit: One big advantage of the Universal Control is it includes the FAT Channel from Studio One, so you can process signals before they are written to disk. I think I saw a reference that they are not ASIO drivers, but they most definitely are (and rather capable ones at that). I was running them through multiple apps simultaneously and the only app that took exception to these shenanigans was Melodyne. Melodyne stand-alone literally had a heart attack doing this, but no issues otherwise.

Can you specify your workflow with this? Definitely start simple... if you highlight a single track on the left side of the Track View, right click it, then "Save as Track Template..." it should save as a .cwx file to the Track Templates folder. Then if you right click an empty area of the left pane of the Track View and select "Insert from Track Template->" that name should appear in the second list that pops up for you. Are you getting pop up information for the crash occurring? This is specific to Track Templates, not Project Templates.

^^^^ It is exactly like the link in the OP reads... if someone steals your user name/password they would also need to steal your phone to get access to your account (if you set up SMS as your authentication method). Banks are pretty much forced to do this now because stealing passwords is so rampant. It is more often used when a monetary transaction can be made (i.e., you have a credit card/account on file), but is definitely there to help verify that the person logging in is really them.

Yikes, "about $2 billion, is swiped annually"... pretty lucrative scam.

In addition to the above, also bear in mind that you can create track templates that include multiple tracks - they are not limited to only one track (almost like a mini-"project template"). As you flesh them out, you will get a feel for what you want for tracks, FX, buses, you want to be inserting as you work. In essence, it is really building projects from the ground up based on existing needs (via inserts), rather than top down via a massive project template which may consume resources that may or may not be used for the given situation (requiring removals). Realize that this is an iterative process, so as you go you may find that you get to the point that you have created a project while working that may be suitable as good project template as well. No harm, no foul. It is really more working with actual material (why I shy away from a project template out of the chute) and being consistent with track/bus routings as you go.

Quick synopsis here first, if you take a single track, you will add 3dB each time you double it. So if they were all identical and participating equally you will get roughly +18dB when summing 64 tracks (+15dB for 32 tracks). Basically every track would need to be roughly -18dB (when initially mixing) to not sum over 0dB at the end. When talking signals, signal-to-noise ratio is king, so as long as you do have enough difference between them to process the signal properly you won't destroy anything by lowering/raising gain alone, but it will affect thresholds of (existing) FX if done willy nilly and can also bring up the noise floor. If you have the mix doing what you want, there is no reason you cannot lower the gain at the final output. It is much akin to the end user adjusting their volume knob, which you cannot control anyway. You could also lower the bus gains similarly (-9dB for 8 "identical" busses), but as you delve deeper to track level it will affect the mixing decisions/FX already made. The advantage of being inside the DAW and working with floats is they will not digitally clip, so definitely try the master output first and then work backwards if needed.

This is probably the preferred method to use anytime an FX isn't included in the instrument itself. Melda Production has a number of FX in their free MFreeFXBundle (with both a vibrato and tremolo). Depending on your application, another thing to consider with track FX are ones that are able to sync to the DAW tempo so they will musically fit the piece.

Check out this thread in the Computer forum, it has a pretty comprehensive list of system checks to consider. The other thing to check specifically for your situation is that the sample rate/bit depth in the universal control match the project settings. If using that interface with multiple applications (i.e., it is a default output in Windows Sound Settings - see below, as this is something you really do not want if feasible), the first app that uses it will lock the sample rate/bit depth. I got my first experience with Universal Control last fall, and unlike most every other ASIO driver, it will connect to multiple apps at different sample rate/bit depths. On my system that inserted a noticeable latency hit, but otherwise functioned fine. However, it didn't tell me (actively) that it was doing it, and it might do more than just insert latency on other machines. A one-time thing I do with interfaces is go into Windows Sound Settings and explicitly tell Windows to use the RealTek chip as the default audio device (with the interface connected/visible). You also want both "exclusive control" boxes in Windows Sound Settings unchecked for devices so that Windows isn't running the show with how things are being used.

Be sure to also consider using track templates (for your situation that would be highly preferable to me over a project template). As you get into a groove of structure and workflow, track templates can be saved (and re-saved as you update them) to include all of the "standard" nuances of FX, busses, sends, etc. With a new project, you can drag the old cwp/wrk files from the media browser to "populate" the new project, then add track templates as needed to accommodate what the old project entails and shift-drag audio from the old tracks to the new ones. As you polish up tracks that will be used again, be sure to save/update track templates as you go.

You just need to have a plugin that accepts side chains (like the Sonitus ones) on one track and insert a send from the track you want as the side chain to that plugin. Although the graphics are slightly different, the mechanics are pretty identical to newer versions of SONAR/CbB. Even side chain videos from newer SONAR/CbB versions (is hard to find videos from old SONAR versions) will cover what is involved.

In addition to the above, overdub recording generally references recording a new track while listening to (monitoring) previously recorded ones. Be sure to record the new material on new tracks, so your track count will go up for each instrument you record. What you have described is overwriting, not overdubbing.

If you scroll down on that description it says it will use a USB-C cable connection for MIDI as well, which is probably preferred over BT. Amazon has a very liberal return policy (and a coupon on that product to boot), so you can always test it out and return it if it doesn't fit your needs. I have zero experience with any of these. The first pic in the product description made me laugh though... the product is HUGE, and they shrank the poor kid to the left of it.

I am really not sure why pricing this year was changed. Updates for Pro had always been $50 from the previous version, but for v7 it is $75. The pre-release is also something that they never did before and seemed to be open to everyone for $30. I would have missed that myself if it hadn't been posted in here, and I am not sure if it being open to everyone was a fluke or intentional.

Google has had this for years. If they cannot track you, they pop that up incredibly often (and seems even more often when using special search command operators, even when not on a VPN).

I just did a quick scan in Rebelle's forum for "Moho" and this post popped up. Rebelle (since v3) uses a PSD compression that most other apps cannot interpret properly, but it can be turned off in preferences (the first post is more informational since the second post was added to fix this). Quick edit: I just did a quick check of this and those psds seem to open fine in other apps now, although there is still a disclaimer (when saving in Rebelle 7) that "Pigments used are not recognized by Photoshop, so they may not display accurately." That said, when importing new layers from other apps it is safer to import only the new layers and leave the originals intact (i.e., do work in the other apps on new layers when feasible).

The selection aspect is the actual problem, since the NumPad is the standard numerical data entry medium (banking, engineering, you name it). If the contents of a field are selected with any keystroke on that pad, then the very next entry overwrites the contents. I just checked the keyboard shortcuts and the Num - is not bound, so that behavior is scripted into the app and cannot be undone (Windows default behavior is to enter a -, go figure). When someone is doing data entry, they are not expecting those keys to select the contents of the field as they go and it will cause issues for people either focused on the NumPad itself (me 99% of the time) or reading a data sheet as they are typing. I cannot think of any other program where if I select the contents of a data field (intentionally) and either hit Backspace or just start typing that it doesn't take all of the characters that I type, let alone overwrite something I know I typed.

Yeah, there are a lot of apps available with layer functionality and psd export to use out there. Oddly enough, a Rebelle 7 psd export will import to Photoshop itself, just not other apps which I typically use. My workaround thus far has been to open them with Photoshop (CS5.5 version) then re-save them with a new name with "Max compatibility" checked. This strips out the info tags for the new Rebelle 7 features that seem to give non-Photoshop apps a heart attack, so Moho opens those "re-saves" fine then. Unfortunately, that particular workaround isn't available to everyone (without a subscription to CC that they might not necessarily need otherwise).

Quick resource post for this guy. Lost Marble posted a very nicely presented and segmented video course on YouTube (sans ads, which absolutely rules) that can be found here. With the manual for Moho 14 switching to a wiki-style format (no pdf), the video course may be a quicker alternative to learning Moho 14. **** Side note for people who have been playing with graphics bundles posted recently. Most programs allow saving into psd formats, and using layers allows for much quicker jump-starts with animation tools. Unfortunately, Rebelle 7 still has issues with saving as psd formats due to all of the new goodies, so layers need to be extracted separately. Although Rebelle 7 warns you that psd formats "may not display properly" in other programs, I have found the new layers types added with Rebelle 7 make them unreadable for transfer as a psd file. Hopefully that one will get ironed out in the coming months. The issue with Rebelle and psd formatting is addressed a few posts down in this thread. It is due to psd compression that is being used and can be shut off in preferences.

I found what it is, and part of it is due to my typing speed. Using Normalization Amount as an example, if you clear that entry cell then hit the - key on the NumPad, it steps down integer values with each keypress, but also selects the field contents with each iteration. If not watching that cell when clearing it, the - changes the contents to -1.0 (highlight selected) and following it with a 3 will overwite the -1.0 with a 3 (which is then not selected). So when clearing the cell contents and typing "-3" then looking back up, I only was seeing 3 and wondering where the - went. The only way to input numbers, for example -3.5 for Normalization amount, you need to hit - then mouse click the field to deselect the "selection" and change them that way. I am very much in the habit of clearing a field and just typing what I want in there, but typing "-3" will yield "3" if not paying attention. Also note, the selection behavior only occurs when using the - on the NumPad. When using the number row, the "selection" behavior does not occur, so you can type in -3 and it takes as -3.