inputs suddenly stopped working

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi. My midi and audio inputs both suddenly stopped working! Nothing wrong with the sound card (Audiophile 2496) or midi interface, as both work fine in energyXT. I've tried restarting the computer and T2, resetting ASIO and midi ports, opening old edits and new ones. Can't reinstall right now, as I cannot access the download page due to the server error (see another thread).
Any ideas?

Post

Shite the same thing just happened to me.
Got an Audiophile 2496 too.

HELP !

Post

install file is in the tracktion 2 folder!!!

probley @
c:\program files\tracktion2\setup\tracktionsetup.exe

install it ontop of its self & report back with more info if you can

Subz

Post

if you ever experience an input that is not working... consider lube... :-o

Post

DUDE strike TWO what kaboodle has fallen into your kitchen?! dang!

Post

This mysteriously happened to me one day too, but I have an Aardvark Q10. I did have one input and when I looked in T's settings, the input names were very strange:
Aardvark 3,4 Input 1 Enabled
Aardvark 3,4 Input 2
Aardvark 3,4 Input 1
Aardvark 3,4 Input 2
Aardvark 5,6 Input 1
Aardvark 5,6 Input 2

(I tried to enable the other multiple inputs with no success.)

It should look like this:
Aardvark 1,2 Input 1 Enabled
Aardvark 1,2 Input 2 Enabled
Aardvark 3,4 Input 1 Enabled
Aardvark 3,4 Input 2 Enabled
Aardvark 5,6 Input 1 Enabled
....etc, etc.

I figured my Aardvark had crashed and decided to reboot. After reboot, I restarted the device, in Tracktion, and everything seemed back to normal. But, that was only a coupla weeks ago, so my fingers are still crossed.
Anti-aliasing is for "synthmonk%ys".

Post

Tried to reinstall just now, everything is seemingly back to normal.

Post

This happened to me with my Creamware Pulsar too. I reinstalled the Creamware software *and* Tracktion 2.0.1.13, and the problem went away. But then it reappeared, and I reinstalled the Creamware software to fix it. Things stayed OK for two sessions, then I had to do it again. This was a week and a half ago, and things have been fine since then.

No idea why this would occur.

Post

I had something similar with the latest drivers for the Emu 0404 - worked for a while but then nothing worked (although in my case it appeared to be a system-wide problem not just Tracktion). Reinstalling the previous driver version cured it.

Post

0 problems here with firepod (so far), intensive recordings, etc as well

RONC

Post

I reinstalled T2 but noticed the "end to end" was not enabled.

Enabling it has resolved the issue.

Pretty simple ...

Post Reply

Return to “Tracktion”