brundlefly

With four bars showing in the PRV, 8th notes are quite large, even on my laptop. 'Fine-tuning' 8th start times/durations is pretty easy at that zoom level. I must be missing something...?

Could be done pretty quickly with a little batch scripting, but I think we should make IK Dev do it.

Cool. Let me know when you're done re-saving them all, and I'll ping you an e-mail address. ?

Sweet. Resisted the urge to pick up bx_oberhausen at $49.99, but taking another$25 off put it firmly in no-brainer territory.

Yeah, makes me wonder if saving changes from ST3 would not have broken the authorization. I didn't stop to look and see what was in the modded files to make them so much larger.

@Noel Borthwick what should we expect when using plugins that induce a lot of PDC?

Checked out loading multis in Syntronik. Turns out part of what I was missing is that you have to click in the center of of the browser/selection field within the Multi Panel. If you click on the layers icon at the left end, you get no dropdown - not very intuitive. So I can see and load multis, but the ones I edited in Sampletank to set all layers to channel 1 and re-saved now throw an "Instrument not authorized' error for each layer in Syntronik. I found a thread referencing this on KVR, but it implied this would only happen if you edited the individual instruments and/or changed names, and tried to share it with another user. I didn't change anything but the channel assignments, so it's not really clear what's going on here, but I'm guessing that reinstalling the relevant sound set will fix it. Fortunately I only modded a handful of multis. Not cool that making such a minor edit breaks the authorization. No crashes here, yet, but IK not making a really good first impression on me, otherwise. EDIT: Extracted the Syntronik_Multis.zip file, and manually copied just the 4 affected .st3m files back over my significantly larger, modded ones, and Syntronik is happy to load them now. EDIT 2: Just out of curiosity, I manually modified the MIDI channel tag for the second 'part' in the XML-style .st3m file using a text editor (note that part and channel numbering starts at 0), and it loads to Sampletank with the correct behavior, and still loads to Syntronik as well.

If using onboard sound as an audio interface, make sure the Input/Source in the soundcard's mixer applet is set to something like 'Mic/Line In' as opposed to 'Stereo Mix' or 'What U Hear' which will record from the output so you capture everything being played back.

So opening a project from the other PC breaks MIDI input functionalty in all projects that were working after re-install/update? That's pretty weird. And you've confirmed it's an input problem not an echo problem - you can't record any input with a track set to omni? Check Preferences > MIDI > Playback and Recording to ensure Notes and Controllers are enabled for recording at a minimum. And Driver Mode is MME, not UWP? What does the MIDI device config look like on the other PC? I would compare the TTSSEQ.INI files between the two machines, and look for changes to it that might be happening between re-installing and opening the project that breaks things.

Thanks abacab, I figured it might be something like that. Still finding my way around the UIs, and haven't been through the Syntronik manual yet. Thanks for confirmation on the layer-channeling issue. Will have to ping IK about that.

To avoid further hijacking of Joe Bradford's post about Sampletank crashing, I decided to post this separately. I was playing around with Syntronik 'patches' loaded in Sampletank, and found that some patches were silent above a certain velocity. After some head-scratching I figered out that the higher velocity samples were loaded into a second layer that was assigned to channel 2 by default. Specifically, there are several 12-velocity bass patches that consist of two 6-velocity layers using high-velocity and and low-velocity sample sets. Subsequently, I found other patches with as many as 4 layers with only the first one sounding because layers 2, 3, and 4 were on channels 2, 3, and 4. This seems like a major patch-programming oversight...? I was curious what the situation would be for the same patches in Syntronik, but when I looked at the basses, I found that the browser only offered the two 6-velocity patches separately, not the two-layer 'multis'. Likewise, a 4-layer keyboard patch in Sampletank had only the single layer for which the patch was named in Syntronik though it's capable of layering up to 4 sounds, I believe. So... why isn't Syntronik seeing its own multis? I haven't yet installed any of Smapletank's sound sets, so everything it's seeing is from the Syntronik installation. P.S. In the course of looking into this, I figured out that all of Syntronik's synth UIs are just a re-skinning of the Sampletank's 'Edit Instrument' UI, sometimes with different scales on a control, but with equivalent range and increments. And since it uses the same set of built-in effects, a given patch sounds essentially identical in the two 'synths'. Curiously, though, when I tried to get them to null, aside from minor differences due to unsynced LFOs and such, I found that Syntronik was consistently rendering audio 48 samples (1ms) later than Sampletank when playing via live MIDI or recording audio in real time. I didn't get around to comparing the rendering of existing MIDI. Just thought I would share this insight for the benefit of anyone who might be curious about whether there's any difference between loading Syntronik and loading its patches in Sampletank. To me, the big advantage of using Sampletank is that you don't have to deal with the pointless (other than cool-factor) graphical rearrangement of the editing UI for the 'different' synths that are assocated with sample sets from their respective hardware cousins. You can just learn Sampletank's UI, and be done with it.

I'm almost certain the issue is Remove DC Offset. Disable it, and make an extended multitrack test recording. I think you'll be fine.

Newly added port enabled (checked) in Preferences > MIDI > Devices? Or is the problem that it doesn't show up there?

Started browsing Syntronik instruments in Sampletank. Quickly encountered one that would not load due to missing files. Checked my installation, and found that some sound archives had downloaded to the wrong folder (due to an issue with the IK download defaulting to a previously used directory when downloading multiple files at once), and I missed a couple. No problem, but I'm curious that instruments that aren't installed are listed in the browser. I guess some master list gets installed with the Syntronik product regardless of whether you've actually installed the sound files...?

Check if the keyboard ports have been taken over as a Control Surface.

Remove DC Offset is not enabled by default, and has been known to cause exactly this issue in the past. Defnitely disable it, and I think you won't see this issue again. Other settings look fine. ThreadSchedulingModel=1 is the default, and fine for your Core2Duo. 2 optimizes for quad cores and above. 3 has proven problematic for many users, and is not recommended at this time.

Maybe side-effect of having the 'Basic' Workspace' enabled? Try setting Workspace to 'Advanced' or 'None' (access to everything with no predefined views). Beyond that, maybe give exact steps you're using to start a project, and upload a screenshot or two showing the problems.

Usually a MIDI track is dedicated to driving a single instrument/sound. Although it is possible to have events with different channels driving different instruments of a multi-timbral synth from the same track, it makes it very difficult to keep track of things and compose/edit efficiently. For a single instrument (or a drum synth that has a different kit piece on every note number), you will sometimes have different harmonic parts/lines/voices that you'd like to isolate for editing/mixing/arrangement purposes which you can do by using multiple 'Lanes' of a track (Shift+T to show lanes). The 'Inline' PRV that your screenshot is showing is for the 'parent' track using only one lane. If you use multiple lanes, you can display an inline PRV for each. The separate 'main' PRV that you get by double-clicking that icon in the upper right corner of the clip (or Alt+3 or Views > Piano Roll View) lets you see all lanes of one or more tracks, but will not let you easily differentiate parts/lanes within a single track, except by enabling 'Hide Muted Clips' in the PRV's View menu and temporarily muting clips in lanes that you don't want to see. Nevertheless, that's where most of us do our detailed MIDI editing because it has more editing capabilities and display options. There's a lot more to understand, depending on how you ultimately choose to work, but that should help get you started, or at least know what question to ask next or what part of TFM to R. ;^)

If files are missing, Cakewalk will pop up a dialog prompting you to locate them. If you don't get any warnings, then audio clips referencing those files were deleted from the project (or never existed) before it was saved. Deleting a clip does not delete the file, so those files it should still be available to re-import unless you *did* in fact whack them via Windows Explorer. I suggest you run the Cakewalk Audio Finder utility (Utilities > CWAF Tool) and let it search your all you drives. It will show 'Missing' files that projects are referencing but were not found, 'Orphaned' files that are no longer referenced by any project, and 'Referenced' files that are used by one or more project files. After executing 'Find', you can click on a'Referenced' or 'Missing' file to see what projects are referencing it it, or click on a project to see what files it references. If clips were inadvertently deleted from one or more projects, the previously associated audio files should show as Orphaned. Depending on what else you have on your PC, and how you set up CWAF, a lot of the 'Orphaned' files may be .WAV files that are unrelated to Cakewalk. See post #5 in the below thread for a 'primer' I wrote on how I use it: http://forum.cakewalk.com/Clean-Audio-Folder-still-broken-I-see-m3023320.aspx#3023681

Sounds like the problem from back in Platinum era with 'Remove DC Offset During Record' in Preferences > Audio Playback and Recording. As I recall, it was fixed at some point, but maybe still manifests in some cases. That, or did you maybe enable the experimental 'Aggressive' ThreadSchedulingModel=3 in AUD.INI (Preferences > Audio > Configuration File)?

I usually have Follow Snap Settings enabled, but just tried fixing at 1/8, and it persisted after save/close/re-open as expected. My guess is you're using a Workspace, and need to resave it. I currently have Workspaces set to 'None' so per-project settings reign.

WASAPI Exclusive mode is probably the best place to start for onboard sound users as it's full supported by the Bakers. That said, I was initially suspicious about the possible involvement of ASIO4ALL in this issue as well, but the faulting module is Sampletank, and I would not expect that loading samples would affect the audio driver state.

I should, unless maybe you have Transport Seeking Stops Playback enabled in that same options menu.

Have not browsed extensively, and I've mostly been playing with Syntronik inserted directly rather than loading via SampleTank. Will try using ST4 some more. I only installed the VST3. As I recall, you have to unhide VST2s with the checkbox, then also un-Exclude them individually, and then you can Exclude the VST3 if you don't want to see it.

New one on me. Hard to imagine it would affect one some project unless those affected projects all shared a common ancestor, with lurking corruption. Can't really think of anything that would cause that otherwise or any procedure that might 'break the spell' other than things you have probalby already tried like archive/unarchive, delete/undo, solo/unsolo the whole project from the mix module or by quick-grouping, etc. Maybe save as a bundle, and open it from a new location...? If the problem was really precipitated by installing Studio One, I would wonder if maybe it overwrote the a version of the C++ runtime library that CbB was using or something like that You might try re-installing Cakewalk. But many of us have Studio One as well, and no problems with CbB.