dantarbill

There's a number of (somewhat scary) steps... Run the "TranzPort_Win_Setup_1.5.0.exe" installer in Win7 compatibility mode... Right click .exe. Select properties. Select compatibility tab. Check Run this program in compatibility mode for: and select Windows 7 from drop down. Note that you’re supposed to disconnect the USB interface/dongle thingy before the install. You'll probably get the "A driver cannot load this device" complaint... TranzPortx64.sys (C:\Program Files\TranzPort) A security setting is preventing this driver from loading. You’ll need to adjust your settings to load this driver. https://support.microsoft.com/en-us/windows/a-driver-can-t-load-on-this-device-8eea34e5-ff4b-16ec-870d-61a4a43b3dd5 …suggests turning off the memory integrity setting. (This has scary "you could screw things up" warnings.) Make sure TranzPort_64.dll finds it way into the "Shared Surfaces" directory (noting that only 64 bit is now supported by SONAR). You should have a SONAR_and_TranzPort_v1.3.3.pdf doc in your collection of downloads from Frontier that walks you through the rest of the setup under "SONAR Setup". There might be some missing steps here. I tried to document everything as I went through it though. Lemme know if this works for anyone.

Sorry to cross post this (from General Music Discussion/Gear), but I've managed to get an ancient Frontier Tranzport to work with SONAR 2025.11 under Windows 11 Pro. Details are available under General Music Discussion/Gear.

Ah!! It's working!! If anyone wants further details or assistance, reply here!

I'm taking a stab at this on a new Win11 machine after finally retiring its 14 year old Win10 progenitor. I ran the installer (TranzPort_Win_Setup_1.5.0.exe) in Win7 compatibility mode. I also turned off the memory integrity setting. There's still some things missing yet...which I'll try today. Has anyone else gotten the Tranzport to work on Windows 11 or am I still alone here?

I've had a Yamaha 01V for the last 25 years...but it is aging out. My plan is to replace it with an A&H SQ-5. Part of that fantasy is to use the SQ-5 as a controller so I can at least record fader moves on existing material. I also have a lot of time on my hands and years of software engineering experience, so I could conceivably do some AZ Controller configuration. What is the current state of AZ Controller and what would I have to do to get it to work with an SQ-5?

This is kinda related to the previous PSYN II question... I have a large number of legacy projects that use the ancient DXi plugin DR-008 from Fxpansion. Is there a way to get this to run in the current (64 bit) Sonar 2025? I'm not sure that it's a registry issue, since I'm seeing this all over in my registry. The way it works is weird and kinda hinky...but it's a hard dependency in a lot of projects.

Not sure I can speak to "better or worse than Guitar Rig" but I can say that I like and use Studio Devil's Virtual Bass Amp Pro.

Yeah...set the Wayback to 2004... I have an old project that's using an ancient DXi softsynth called PSYN II. I've got the dll (dated 09/08/2006) along with it's .chm file. There used to be a way to get this installed into the registry. Would this still work if I did?

Thanks...I needed that!

I guess I'm admitting that I've been using way too many synth factory patches, since I'm just now running into this... I've made changes to an Applied Acoustic Systems synth patch hosted in Sonar. When I try to use the keyboard to rename the patch, the keys activate the standard Sonar shortcuts instead. How do you bypass the shortcut behavior so you can type in patch names in the synth UI's editor? Thanks

Oddly enough...I really like the new "flat" interface. (I can't speak for "Next" though.) I've been on all the variations since the Cakewalk DOS sequencer just prior to version 2.0. This one makes me smile the most.

Ok...I've found the key sequence that does the Screen Lock function on my Logitech wireless keyboard. However, this doesn't seem to be enabling the functionality that I'm talking about. Does anyone ELSE recall the function I'm talking about? The proof that this has been enabled will be that the "Mixing Down Audio" progress bar will come up in its own window that you can then relocate at will.

I've got Insert, Print Screen and Pause/Break. No Scroll Lock. Besides...this is the same keyboard I've used for years. I don't recall that it was a key sequence that did the trick. It was something I did in the Sonar UI that would keep it from updating graphics in plug ins and such. It would also put the "Mixing Down Audio" progress bar in its own window that you could then drag onto another screen so I could put it up in a corner somewhere and see it while doing something else. What WAS that?

Pause and Scroll Lock are new to me. I'll give those a shot. What I was doing before did something to stop or collapse the whole UI and presented the render progress bar as a separate little window of its own.

I used to do mixdowns of live multi-track performances regularly. (Like...weekly...or more.) I've since had to take a break for a year and move from the left coast to the right coast. I've also updated from 2023.09 (build 075) to 2025.02 build 077. There used to be a thing that I would do to speed up the render that (I think) kept Sonar from updating all the graphic elements in the UI. I can't remember now what that was. Who remembers what that is...or has become in the new update? Thanks

Does anyone have recent experience with using an Allen & Heath SQ series mixer as a control surface? I'm seeing references to using AH-MIDI-Control using the HUI protocol, but it may be that this only maps the faders (which would still be nice). 'Twould be even better if it sent data to the scribbles strips. Any comments are welcomed.

The template in question is post ProChannel, so at least that won't be an issue.

Is there any possibility of problems using a Project Template that I've been building on since Sonar was first introduced? Should this all be backwards compatible with 2024.12?

I have a number of legacy (32 bit) projects that were built using the old Session Drummer 3 (SD3). Trying to use that MIDI data with Addictive Drums 2 (AD2) is yielding poor results. Trying to use SD3 doesn't work because it claims to not be installed correctly. It would appear that the SD3 content is actually there, because there's a SessionDrummer.dll file dated 09/12/2013 in my 32 bit VST(i) path... C:\Music\Plugins\VSTi\32\Cakewalk\Session Drummer 3 ...as well as a Contents sub folder with Kits, Patterns and Programs. What's odd is that I also still have Session Drummer 2 from previous versions...and it works without issues. I guess this comes down to 2 different questions... What was the last Sonar release that included Session Drummer 3? (And/or how do you get it reinstalled) How do you make drum mapping work to make SD3 MIDI content work with AD2? Thanks for your help.

I have a number of legacy (32 bit) projects that were built using the old Session Drummer 3 (SD3). Trying to use that MIDI data with Addictive Drums 2 (AD2) is yielding poor results. Trying to use SD3 doesn't work because it claims to not be installed correctly. It would appear that the SD3 content is actually there, because there's a SessionDrummer.dll file dated 09/12/2013 in my 32 bit VST(i) path... C:\Music\Plugins\VSTi\32\Cakewalk\Session Drummer 3 ...as well as a Contents sub folder with Kits, Patterns and Programs. What's odd is that I also still have Session Drummer 2 from previous versions...and it works without issues. I guess this comes down to 2 different questions... What was the last Sonar release that included Session Drummer 3? (And/or how do you get it reinstalled) How do you make drum mapping work to make SD3 MIDI content work with AD2? Thanks for your help.

Is anyone out there not using a mixer in their setup and just using Input Echo to monitor with FX? Thanks

For many years, I had been using a Yamaha 01v and ADAT as my audio interface. This let me use the 01v’s FX to “wet down” the monitor mix in the headphones to keep vocal clients (mostly me) warm and happy. I’ve since started using a Cranborne 500R8 rack as my interface (better preamps and more than 18 bit ADC’s). The problem is, in order to wet the monitor mix, I have to turn on the Input Echo. I thought I could live with the comb filtering caused by the latency…but then I tried it with a “not me” client, and she wasn’t having it. I’ve come up with a hack to get around it. I’m taking a signal from the vocal pre’s insert and feeding it back to the mixer and using that to monitor and wet the signal. However…I’m wondering why I’m hearing the flangey, comb filtery thing in the first place. Am I somehow getting the early vocal signal mixed into my monitoring chain, or is that just happening “in my head” as it were? Does everyone using Input Echo just live with this, or is there something wrong with the way I’m routing stuff? My current setup shows 1.5 ms (64 sample) buffers (44.1 kHz) for a round trip of 6.4 ms. (Version 2024.02)

iZotope RX! (Standard is fine. You don't need the uber expensive Advanced edition.) It will seem like an expensive way to solve a limited problem, but after you have it, you'll wonder how you did without it. Gates can work too...but there's a lot of work involved in getting it dialed in right...and it doesn't deal with the veil of noise under the signal.

I've checked and rechecked... Any settings I make in "Selection after single split:" do NOT change the default behavior. It always acts as if I have "None" selected as the default behavior. Same is (was) true for the "Default Fade-In Curve>" and "Default Fade-Out Curve>". Ah HA!! I found it! The problem was that I had "Auto Crossfade" selected. That caused what I'll consider unintuitive behavior where it applied the Crossfade defaults when I split. I'm not sure if I had changed the "Auto Crossfade" selection or that behavior had changed with the new update...but I'm back in business.

Sorry...you're right. It's just S for Split and K for clip mute.