| View previous topic :: View next topic |
| Author |
Message |
bender24 Junior Jammer

Joined: 08 Nov 2006 Posts: 19
|
Posted: Wed Nov 08, 2006 3:02 am Post subject: Tascam US 122 issue |
|
|
Hallo,
I've just tried the jamstix demo version and like it very much. But before I buy, I need an answer about the following issue:
Can anybody confirm, that when using Tascam US 122 interface as sound card and loading jamstix as VSTi in any host (Steinberg Cubase SE1, Tobybear Small Host), the system (XP SP2) crashes severely?
This don't happens with other sound cards.
The US 122 works well with nearly all other VSTi.
Does anybody know a workaround?
Regards
Michael |
|
| Back to top |
|
 |
Doc Moderator

Joined: 26 Feb 2005 Posts: 663
|
Posted: Wed Nov 08, 2006 7:04 am Post subject: Re: Tascam US 122 issue |
|
|
| bender24 wrote: | Hallo,
I've just tried the jamstix demo version and like it very much. But before I buy, I need an answer about the following issue:
Can anybody confirm, that when using Tascam US 122 interface as sound card and loading jamstix as VSTi in any host (Steinberg Cubase SE1, Tobybear Small Host), the system (XP SP2) crashes severely?
This don't happens with other sound cards.
The US 122 works well with nearly all other VSTi.
Does anybody know a workaround?
Regards
Michael |
Hi Michael!
Sorry I don´t have the Tascam US 122...
What I can´t imagine is how your problem could relate to Jamstix but not to the host you´re using.
Is everything configured properly? Latency? |
|
| Back to top |
|
 |
Ralph [RZ] Site Admin

Joined: 02 Jan 2008 Posts: 13332
|
|
| Back to top |
|
 |
bender24 Junior Jammer

Joined: 08 Nov 2006 Posts: 19
|
Posted: Fri Nov 10, 2006 8:37 pm Post subject: |
|
|
The DEP settings were allright from the beginning. I tried half a day several things. With no success:
- no reboot
- no starting up with another soundcard
- no starting up with another ASIO-driver
- no loading of another vsti prior to the jamstix
helped me out of that. Loading jamstix with the US122-ASIO-driver causes a bluescreen.
The only thing that helps is to load the jamstix vsti with another ASIO-driver (direct-x or another) and then switch to the US122-ASIO-driver. This will fix the behaviour until the next reboot. You can even end the sequencer and start it again - no problem.
Does anybody have an explanation for that? I know that many people don't like the US 122 sound card because of driver problems. But I had no problems until now and I think, it has to do with implementation of the USB-driver in conjunction with the programs driver interface.
Regards
Michael |
|
| Back to top |
|
 |
darcyb62 Jamologist

Joined: 24 Mar 2005 Posts: 188
|
Posted: Thu Nov 30, 2006 5:40 pm Post subject: |
|
|
I had a lot of problems with the US-122 and I retired it quite some time ago. The 1st issues had to do with interrupt sharing on an older pc. When I dug into stuttering problems I was having I found out that my USB, video, network and internal audio were all sharing the same interrupt. Disabling the network and audio drivers helped for a bi but I had to update my system before I was really functional.
I still found the us122 drivers buggy and Jamstix seemed to exacerbate the problem. The more samples being loaded the more often I would run into problems. Using the low memory settings and freezing tracks helped significantly as did using higher latencies but earlier this year I dumped the US122 for a Presonus Inspire and things have been humming since.
The other issue I had with the US122 was sound bleeding from the output back to the input. I was able to live with driver problems but once I noticed the sound bleeding issues, that was it.
With the performance I see on the Inspire I doubt that I would ever go back to a USB unit. _________________ darcyb62 |
|
| Back to top |
|
 |
|