Jump to content
Inthorns

Just Updated from X3...w/ New Tracking Issues

Recommended Posts

'ello everyone, I'm new(ish) in these parts. 

As far as all things Cakewalk go, I'm a bit of a 'legacy act' -Lolz

I've just switched from Sonar X3 to the bandLab outfit, which seems real nice in comparison, but as fate would have it (always), I'm 'busting my knuckles' already.

Everything seems good and well, other than the driver config/settings. When I set it to ASIO, which is the proper mode for my get up, I don't see the proper inputs. The input selection window doesn't look right, I don't have the same 64 i/o's as before, and only show only 3. When I pick a 'lesser' driver mode, I see my input options as I'm supposed to, and can attempt to track, but pops and clicks abound (even with a buffer/latency increase).

 

I'm running a Win 8.1 x64, i7 Quad 3.4, 8g

Antelope Orion Studio HD

I was tracking just fine in Sonar X3, fyi.

Any help you fine folks can offer is MUCH appreciated!

You know how it goes... of course I'm at the tail end of a tune.

And if I can re-track the scratch bass line minus the crotchety clicks, she just might be a banger !!

 

Thank you kindly good people,

                                                    Ron

Share this post


Link to post
Share on other sites
8 hours ago, Bruno de Souza Lino said:

Update your Antelope drivers?

Good call. Somehow, that hadn't dawned on me. :D

Trying it now (fingers crossed).

Grazie!

Share this post


Link to post
Share on other sites
2 hours ago, bdickens said:

NEVER update in the middle of a project.

Too late for that! Not to worry though, I enjoy the hurdles. They make me a better 'runner'. -Lolz

13 hours ago, Inthorns said:

Good call. Somehow, that hadn't dawned on me. :D

Trying it now (fingers crossed).

Grazie!

Driver/firmware update didn't help anything.  Probably didn't hurt though either.

I cracked the code after my shift last night!

It was the silliest thing 😆 . . .

I had recently checked out a MAGIX Samplitude demo, and during install it added a 'Magix generic low latency ASIO driver' that it seemed to default to when choosing ASIO as my driver mode. In the selection window it was checked, and all of my Antelope I/Os were greyed out (generally meaning they are not an option, in the old X3 anyway), so it appeared that I couldn't check the Antelope I/Os,  which of course I tried, to no event.  Eventually, I simply unchecked the Magix driver, and then my Antelopes became an option. In X3 you could select several different I/O sources, which I guess you cannot do in its newer iteration(?). Annnnnd that's where they threw me :D

Fortunately (for now), that's a wrap!

Thanks for the chimes fellas,

                                                            Ron            

Edited by Inthorns
typo

Share this post


Link to post
Share on other sites

I've also noticed that some Steinberg demos install a generic low latency ASIO driver that can try to replace your interface's ASIO driver in the DAW.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, abacab said:

I've also noticed that some Steinberg demos install a generic low latency ASIO driver that can try to replace your interface's ASIO driver in the DAW.

Cubase does this, regardless of it being a demo or the full version.

  • Like 2

Share this post


Link to post
Share on other sites

Generic drivers can be a problem any time a factory driver is present.

Many of these drivers are repacked versions of ASIO4All.

None of them are true ASIO drivers.

They are all software wrappers for other Windows audio drivers.

 

Cakewalk reads

HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

from the registry to find out which drivers are installed.

There should be at most one ASIO driver for each audio interface.

  • Like 2

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...