No Asio device found for my Line6 X3 Live

[GuitarSlinger]

This may be completely unrelated but since the last line6 update for toneport, I can't even get a green light on my toneport if my headphones are plugged into my soundcard. Strange. Have you guys tried rolling back to different drivers? Is it possible to use a previous version of Riffworks?

[mickeymix]

This may be completely unrelated but since the last line6 update for toneport, I can't even get a green light on my toneport if my headphones are plugged into my soundcard. Strange. Have you guys tried rolling back to different drivers? Is it possible to use a previous version of Riffworks?

You mean Guitarport don't you?

[GuitarSlinger]

No I have a UX1, I think it is on its last legs. The USB is held in place by a couple of picks wedged under the cord, otherwise it don't work at all. My X3 on the other hand works perfectly.

[mickeymix]

Ah....ok I have UX2 .....was just curious...... sorry me gonna butt out now. I wish I could help the lads .........I just can't help thinking that it's something small that's being overlooked........

[unsurx]

Hey Unsurx did you find a solution to the NO ASIO thing that riffworx is doing ?

My solution for the moment is above :
I just power off my Tascam before lauching RW.
After I can power on the Tascam and i use without problem RW, the Pod and the Tascam together.
Look at your RW log file, maybe some indications inside...

[rpinon69]

Lickman wrote:

Are we the the only 3 peeps that have a Riffworks not recognizing our hardware? Please feel free to write about it so we can petition Sonoma to do something to help us little guys out with this. For me the problem became apparent almost 2 months ago.

Hello
I have recently begun to have a problem were RiffWorks tell me it encountered an unexpected error and shuts down. If I try to relaunch it does not recognize my POD Studio UX2 unless I reboot. I think Sonoma should investigate and gives us some help.

This in an addition to the problem I'm having with RiffCast. When I launch RiffCast within RIffWorks the window pops up and I check the box enter my password and I receive the message Incorrect username and password. I have contacted support and they have assured that it is just the wacky servers that the new servers will be better. When? So until then I guess suck it up!!!!

[GuitarSlinger]

Hello
I have recently begun to have a problem were RiffWorks tell me it encountered an unexpected error and shuts down. If I try to relaunch it does not recognize my POD Studio UX2 unless I reboot. I think Sonoma should investigate and gives us some help.

For this part of the problem you should be able to simply reach behind the Pod Studio(Toneport) and disconnect the usb for 10 seconds. Reattach it and start riffworks. It beats restarting the PC. Basically when riffworks crashes the driver gets dumped, reattaching refreshes it.

[rpinon69]

GuitarSlinger

Thanks for the tip I will keep that in mind when it happens again. Even though I am new(a few months) issues didn't start until I upgraded from T4 to Standard which was about 2 weeks ago. I enjoy using this product very much and I understand things happen especially with hardward, software, etc....

Thanks

[jwross]

Here is your problem:

1906139962 : ASIOSetSampleRate returned error: 1906313948 :

You have locked your sample rate (which is definitely the right thing to do). Probably set it to 96k. Riffworks appears to ONLY work at 44.1k (CD resolution). This is kind of a drag, but it makes sense. Riffworks is a scratchpad, it isn't a professional recording tool. And locking to 44.1 would make it LOTS easier to code, no dithering, etc.

So go to the ASIO control panel of whatever your interface is, and unlock the sample rate, or you could probably lock it at 44.1k.

Note: Audio hardware in windows locks to the sample rate of whatever passes through it, so you should have all system sounds, beeps etc. turned off, because you record a beautiful take at 96k, then windows runs an 8k beep through and your system tries to play 96k recording through an 8k opening and it's Alvin and the Chipmunks.

Hope this helps.

[rpinon69]

Here is your problem:

1906139962 : ASIOSetSampleRate returned error: 1906313948 :

You have locked your sample rate (which is definitely the right thing to do). Probably set it to 96k. Riffworks appears to ONLY work at 44.1k (CD resolution). This is kind of a drag, but it makes sense. Riffworks is a scratchpad, it isn't a professional recording tool. And locking to 44.1 would make it LOTS easier to code, no dithering, etc.

So go to the ASIO control panel of whatever your interface is, and unlock the sample rate, or you could probably lock it at 44.1k.

Note: Audio hardware in windows locks to the sample rate of whatever passes through it, so you should have all system sounds, beeps etc. turned off, because you record a beautiful take at 96k, then windows runs an 8k beep through and your system tries to play 96k recording through an 8k opening and it's Alvin and the Chipmunks.

Hope this helps.

jwross

Default Sample Rate 44100Hz
Defualt Bit Depth 16 bit
Buffer Size 512

Never been changed these are the setting set when the software was installed. The only other sample rate option is 48000 so I'm not sure what you mean. I am using a Pod Studio UX2.

Thanks

[jwross]

I was replying to the original poster. I'm sure his Tascam is set to a fixed sample rate.

Your issue is very different. You have the software crashing, then it can't find the hardware, as I understand from your post. I'd wager your issue is that the actual connection to the UX2 is lost, so Riffworks is right, and there is no hardware (check that with a sequencer after a crash). Grabbing the Sonoma log would tell you about it. Kudos to Sonoma for providing a log file, most Windows/Mac software tries as hard as possible to pretend we are too stupid to read a log file. Do you find these crashes after you use sound in another application (or web browser) then return to Riffworks? Or get a beep or some windows sound that Riffworks didn't make? I bet you do.

JR

[d3drocks]

are you on 64 bit?
Line6 always has a different set for 64 bit windows

[zapartan]

I just wanted to add to this that I am having the same problem with my Pod XT Live. It works fine in Line 6 Edition, but T4 tells me I have no ASIO devices and gives me the splash screen with links to purchase one. The log file actually says I have three ASIO devices. The only difference I have seen is that the Line 6 Edition disables anything but Line 6 hardware.

In my case I have a USB Samson Condenser Mic and my NVIDIA sound card ASIO drivers in addition to my POD XTL. So deduction would say that one of those drivers is causing Riffworks to not validate the POD XTL before it gets the inputs loaded. I am inserting each log file so you can see the differences I am seeing. esn modified of course.

76602132738 : L6TWX hwInfo - asioname:ASIO PODxt Live esn:1xxxxx1 firmware:17956864 driver:50594662
76602256746 : TWX Error -7 : (Code 00000000) Success.
76608701587 : 1 Allowed Devices: 76608701617 : ASIO PODxt Live 76608701625 :
76608701638 : ConfigureBays
76608701646 : mFileLooper
76608701740 : mLooperBay
76608701762 : mInputBay
76608701907 : DPickupApp::InstallDriverBay
76608701940 : DAsioBay::Setup
76608701949 : DAsioBay::FillDeviceList
76613681137 : DAsioBay: number of installed drivers = 3
76613681164 : DAsioBay: Driver name = ASIO PODxt Live
76613711581 : DAsioBay loadAsioDriver OK
76613712161 : DAsioBay: ASIOInit OK - driver version: 50594663
76613712188 : DAsioBay: ASIOGetChannels OK
76613712196 : DAsioBay: InputChannels = 2
76613712204 : DAsioBay: OutputChannels = 2
76613712217 : DAsioBay: Driver name = NVIDIA ASIO
76613712224 : DAsioBay: L6ed Ignoring NVIDIA ASIO
76613712233 : DAsioBay: Driver name = Samson ASIO Driver
76613712241 : DAsioBay: L6ed Ignoring Samson ASIO Driver
76613712253 : DAsioBay::SetDeviceByName ASIO PODxt Live
76613712262 : DAsioBay::SetDevice 0
76613719329 : DAsioBay: Driver name = ASIO PODxt Live loaded
76613719816 : DAsioBay: Buffer sizes min:256 max:4096 pref:512
76613719840 : DAsioBay::CreateBuffers
76613719850 : DAsioBay : ASIOCreateBuffers with inputChannels = 2
76613719858 : DAsioBay : ASIOCreateBuffers with OutputChannels = 2
76613719866 : DAsioBay : ASIOCreateBuffers with size = 512
76613767476 : kAsioSupportsTimeInfo
76613767777 : ASIOGetLatencies : InputLatency = 780 latency = 17 msec
76613767805 : ASIOGetLatencies : OuputLatency = 1561 latency = 35 msec
76613767813 : DAsioBay::GetChannelInfo
76613767896 : ASIOChannelInfo input: 0 16 Input 1
76613767931 : ASIOChannelInfo input: 1 16 Input 2
76613767964 : ASIOChannelInfo output: 0 16 Output 1
76613767997 : ASIOChannelInfo output: 1 16 Output 2
76613768006 : DAsioBay::PopulateInputChannelList
76613768014 : input 0 Input 1
76613768026 : DAsioBay::SetInputChannel 0 Input 1+Input 2
76613768034 : DAsioBay::PopulateOutputChannelList
76613768042 : output 2 Output 1
76613768052 : DAsioBay::SetOutputChannel 0 Output 1+Output 2
76613768061 : DLooperBay::SetDriverBay
76613788023 : DAsioBay::SetInputStereo

Now T4

41272180245 : mLooperBay
41272180297 : mInputBay
41272180477 : DPickupApp::InstallDriverBay
41272180720 : DAsioBay::Setup
41272180733 : DAsioBay::FillDeviceList
41272186121 : DNetworkServerConnection::ConnectToServer ping SUCCESS
41272235358 : DAsioBay: number of installed drivers = 3
41272235389 : DAsioBay: Driver name = ASIO PODxt Live
41272247207 : DAsioBay loadAsioDriver OK
41272247712 : DAsioBay: ASIOInit OK - driver version: 50594663
41272247728 : DAsioBay: ASIOGetChannels OK
41272247736 : DAsioBay: InputChannels = 2
41272247744 : DAsioBay: OutputChannels = 2
41272247757 : DAsioBay: Driver name = NVIDIA ASIO
41272249000 : DAsioBay loadAsioDriver OK
41272249405 : DAsioBay: ASIOInit returned -1000 for NVIDIA ASIO
41272249418 : DAsioBay: Driver name = Samson ASIO Driver
41272250398 : DAsioBay loadAsioDriver OK
41272250729 : DAsioBay: ASIOInit OK - driver version: 1
41272250745 : DAsioBay: ASIOGetChannels OK
41272250754 : DAsioBay: InputChannels = 2
41272250762 : DAsioBay: OutputChannels = 0
41272250780 : DAsioBay::SetDeviceByName ASIO PODxt Live
41272250789 : DAsioBay::SetDevice 0
41272632712 : DLooperBay::SetDriverBay

That's it. It never says ASIO driver loaded even though it checked each one and said they were ok. I suspect this line "DAsioBay: ASIOInit returned -1000 for NVIDIA ASIO" So I am going to see if I can update the NVIDIA ASIO as I really don't know how to remove without removing all of my system drivers.

I wish there was a way to tell T4 to ignore the drivers I don't want to use. At least I could see which of the other two are causing the problem.

That is what I am doing to try to figure it out. Hopefully that can help someone else trouble shoot as well. I'll post an update if I fix it.

[zapartan]

Now an update to the above. I started by getting rid of the NVIDIA ASIO driver as I thought that was my problem due to the message in the log. Once I had deleted the nvasio.dll and deleted the entries out of the registry, I launched T4 again with the same results. That made it clear that the problem was the Samson ASIO driver for my USB condenser microphone.

I then uninstalled the Samson drivers and now it works great.

At least now that I know the problem I can find out how to get my mic working later. From Samson's website I found the C01U has a 16-bit, 48K sampling rate, but can work at lower sampling rates. The error log did not give the sampling rate error, so I did not think that was the problem. Maybe if I can figure out how to drop it to 44.1K it will work.