Goddammitalltohell!!!!! @^%@^@% Jamlab piece of @#%^

[Roland Saul]

Ok, total novice at Soanr, 6 Studio, got it working, figured out my routing, figured out the plug-in, all great, got french friggin horns and violins galore.

All running thru an M-Audio Audiophile 24/96, ALL working great.

UNPLUGGED/Disconnected my usb keyboard, also an M-audio keystation.

Loaded the drivers/software for the Jamlab, which is a simple 1/4" to usb adapter, it gets recognised when I plug it in just fine. Problem is, no sound at all. Every single frickin audio/midi/ anything device in the chain is just fine except for Jamlab.

Routing is just fine. Guitar signal is fine up until where it enters the Jamlab, then it's gone, can't even monitor with the headphone jack on the Jamlab.

Tried the guitar thru a pre-amp to the Jamlab, no go.
Straight from guitar to Jamlab, no go.

In sonar, AGAIN, everything is fine, BUT, when I go to the drivers tab of the audio options, all of the drivers are enabled (or at least listed) except for the Jamlab drivers, which are listed, but I can't "check" them to enable them. Asio/MME drivers, no difference. i use the Asio drivers for the soundcard, AND the Installer for the Jamlab SAYS it's installing ASIO drivers, WHICH show up but are "unavailabe" in Sonar.

Uninstalled, reinstalled with "new" (same) drivers from M-Audio website. Same thing.

I'm not the most patient guy in the world. If I dont' figure this out, it's gonna get "fixed" in about 5 minutes with a pipe wrench.

At no time during this are any other usb devices installed. The sound card routing is perfect and functional in all parts except for !@#$%smokin son of a #$%^ piece of @$% @$%in Jamcocksmokin Lab.

Ok, rant over, maybe a stupid Sonar novice mistake, but I figured I should be able to hear something loooong before the signal gets to Sonar anyway.

 

[dachay2tnr]

It certainly appears relatively simple and straightforward. However, the spec sheet says it's compatible with ASIO 2. I'm not sure if Sonar is ASIO 2 compatible, but maybe that's the issue. Have you tried switching to WDM drivers?

Also, the M-Audio site notes that it doesn't work with Windows Media Center Edition. Not sure what OS you are running, but I guess that could be an issue if you are running WMCE.

The headphone issue puzzles me however. I'm not sure if the headphone feed is directly off the input signal, or whether it is from a signal returned from the computer. If it is monitored off the input signal, then the unit would appear to be "dead." Since it appears to be getting its power from the USB, are you sure the USB port you have it plugged into is functional.

OTOH, if is is monitored via a return signal, it would seem you need a functional software host. Did you try it with the software that was included with the unit. If it works with that, then it would appear to be a Sonar issue. If it doesn't, than it would more likely seem to be a hardware issue.

 

[Roland Saul]

Thanks for the input. Turns out the "host" software, GT Player Express, needs the Jamlab to be the only USB Audio device connected, which I tried to no avail, but ALSO needs to be running BEFORE the Jamlab is plugged into the USB port. The software gives warnings on install that it hasn't passed the Windows logo testing, which I suspect means they never paid the money to have the software fully tested to conform to the XP API set.

All well and good, except the signal is so weak that even with the "input" AND "output" controls on GT Player cranked to the red zone, the signal is barely visible on the meters. It is still audible thru the phones, but not thru the computer. Further, there is no level control for the phones leading me to believe that they are upstream from any PC functions.

ALL audio and signal parameters are easily monitored by anything else other than Jamlab up to that point. There is perfect signal going in, and crap coming out, with no way that I can find to boost the gain or output from the unit.

Further to THAT, the USB port monitor hangs and does not register the connection immediately. like the other usb devices on my system work. Sometimes, it takes 3 MINUTES to give the little "buh-BEEP" that you get for a USB connect/disconnect.

This is just crappy software and/or crappy hardware. Regardless of whether or not Sonar supports the same ASIO version, the GT player software has a VERY hard time determining that the Jamlab has been just plugged in.

I appreciate your response, man, but I'm still pissed after reading the "Plug in/Rock out" logo on the box, and struggling with crappy , cheesy , buggy, useless, putrid, ancient Druid Death Software for two hours and getting nowhere.

 

[warble2]

Whatafrickincrazysituationyouhavehere!!@#!@@@@@#@!!!!

 

[Roland Saul]

Ok the phones are downstream from the soundcard AND the GT software, which I can now hear only on the headphones, even though I THINK the routing is still ok, after many changes. There have been in fact so many changes that I have to admit I don't have a clue what I'm doing.

So I am going to retract all the bad stuff I said about Jamlab, and try a few things tonight. I have read good reviews on it, and also a few really bad reviews on it, mainly by people having the same problem as I am. Hopefully it's a simple error because I'm such a halfwit with all this newfangled hippy drug music software. Otherwise it's pipe wrench time.