ASIO not working (ultralite PC)
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
ASIO not working (ultralite PC)
So I just got my ultralite and i'm trying to use it in both FL studio and abelton live and all the drivers work except for the ASIO drivers. I can hear audio in the headphones when I turn on the asio drivers but nothing comes out of the speakers. any ideas?
Which output pair are you using to feed your speakers?
Assuming you are using Main Outs to feed your speakers, if you are assigning track(s) to Outputs 1-2 (Phones 1-2 on the UltraLite) in Live, you will not hear anything out of the Main Outs. Because the Main Outs on the UltraLite is a discrete output pair, meaning it does not mirror any other output pairs.
Try assigning track(s) to the Main Outs (outputs 11-12 in Live).
Assuming you are using Main Outs to feed your speakers, if you are assigning track(s) to Outputs 1-2 (Phones 1-2 on the UltraLite) in Live, you will not hear anything out of the Main Outs. Because the Main Outs on the UltraLite is a discrete output pair, meaning it does not mirror any other output pairs.
Try assigning track(s) to the Main Outs (outputs 11-12 in Live).
thanks that seems to have been my problem......now any ideas for FL studio 6? i don't know if that program has that sort of control.ALTOIDS wrote:Which output pair are you using to feed your speakers?
Assuming you are using Main Outs to feed your speakers, if you are assigning track(s) to Outputs 1-2 (Phones 1-2 on the UltraLite) in Live, you will not hear anything out of the Main Outs. Because the Main Outs on the UltraLite is a discrete output pair, meaning it does not mirror any other output pairs.
Try assigning track(s) to the Main Outs (outputs 11-12 in Live).
thanks for that tip, fixed that problem but now i've encountered a new one.ALTOIDS wrote:In FL Studio:
1. Go to View/Mixer
2. Select the Master Fader.
3. Locate OUT option on bottom right-hand corner of the Mixer window.
4. Switch Phones 1-2 to Main Outs 1-2.
FL is nearly unusable. songs that ran fine with my m-audio firewire audiophile play so glitchy its impossible to work on them. i've tried setting my sampe buffer as high as possible but its still just crunchy glitchyness. anyone out there actually using this card with FL?
On the other hand its running ableton great even with my HUGE live set.
Hi,
I'm puzzled to hear this because I intended to buy the Ultalite for using mainly with FL Studio.
You should try this. It worked for so many soundcard, and sometime it work better than using the drivers provided with a sound card.
www.asio4all.com
I guess that most people with souncard problems should give a try to this driver. It add some time to your tweaking and debugging but in the end, it may be your only solution, so ....
Please let us know about your success using FL Studio and UltraLite
Thanks
I'm puzzled to hear this because I intended to buy the Ultalite for using mainly with FL Studio.
You should try this. It worked for so many soundcard, and sometime it work better than using the drivers provided with a sound card.
www.asio4all.com
I guess that most people with souncard problems should give a try to this driver. It add some time to your tweaking and debugging but in the end, it may be your only solution, so ....
Please let us know about your success using FL Studio and UltraLite
Thanks
i've tried asio4all and it doesn't make any improvement.
i've been going back and forth with FL tech support so we will see if anything comes of that, but last night i formatted my machine and it definatly improved the playback of FL. Its been at least a year since my last format which is usually about when my system starts to get a bit bogged down.
I can definatly say this card isn't running FL as well as my m-audio firewire audiophile in asio mode but its definatly usable now. my next plan of a attack is to hit up motu tech support (though they haven't responded to my email from 4 days ago yet) and see if they have plans for a driver update or something soon.
anyone know how motu is about fixing something like this that could be driver related?
i've been going back and forth with FL tech support so we will see if anything comes of that, but last night i formatted my machine and it definatly improved the playback of FL. Its been at least a year since my last format which is usually about when my system starts to get a bit bogged down.
I can definatly say this card isn't running FL as well as my m-audio firewire audiophile in asio mode but its definatly usable now. my next plan of a attack is to hit up motu tech support (though they haven't responded to my email from 4 days ago yet) and see if they have plans for a driver update or something soon.
anyone know how motu is about fixing something like this that could be driver related?
Here's a few questions that may help to track the problem.
When you say that it's not as well as the Audiophile FW, you mean the latency will be higher for a same CPU usage (or higher CPU usage for same latency), or you mean the less functionnality ?
Have you totally uninstalled the Audiophile FW drivers and apps ?
Are you using a Laptop ?
What OS and what SP are you using ? Have you tried any FW patches for windows ?
What is the RPM of your HardDrive ?
Does your HD containing your audio is the same as the one with your OS and softwares ?
What kind of Firewire card or chipset do you use ?
DId you tried with the power supply and powered via FW ? Same problems in both cases ?
Are you having glitches when playing back or only when you record a new track while listening to the previous ?
Are you able to record a track without loosing sync, and without introducing glitches or noises in your new track ?
When
When you say that it's not as well as the Audiophile FW, you mean the latency will be higher for a same CPU usage (or higher CPU usage for same latency), or you mean the less functionnality ?
Have you totally uninstalled the Audiophile FW drivers and apps ?
Are you using a Laptop ?
What OS and what SP are you using ? Have you tried any FW patches for windows ?
What is the RPM of your HardDrive ?
Does your HD containing your audio is the same as the one with your OS and softwares ?
What kind of Firewire card or chipset do you use ?
DId you tried with the power supply and powered via FW ? Same problems in both cases ?
Are you having glitches when playing back or only when you record a new track while listening to the previous ?
Are you able to record a track without loosing sync, and without introducing glitches or noises in your new track ?
When
i'd say probably CPU usage...hard to say as I don't have the audiophile hooked up now. I just know when I used the audiophile I was able to play this song smoothly (for the most part, it was occasionally glitching). But basically now its just glitchy so bad you can't listen to the parts of the song that have a lot of fx and vsts going on.sonidos wrote: When you say that it's not as well as the Audiophile FW, you mean the latency will be higher for a same CPU usage (or higher CPU usage for same latency), or you mean the less functionnality ?
I have completly formatted the system to make sure the old card wasn't causing the problem.sonidos wrote: Have you totally uninstalled the Audiophile FW drivers and apps ?
Are you using a Laptop ?
What OS and what SP are you using ? Have you tried any FW patches for windows ?
What is the RPM of your HardDrive ?
Does your HD containing your audio is the same as the one with your OS and softwares ?
What kind of Firewire card or chipset do you use ?
DId you tried with the power supply and powered via FW ? Same problems in both cases ?
Are you having glitches when playing back or only when you record a new track while listening to the previous ?
Are you able to record a track without loosing sync, and without introducing glitches or noises in your new track ?
When
Yes its a laptop
Running Windows XP, was on SP2 just read about the fix for speeding up firewire, tried it, didn't work....tried uninstalling SP2 didn't fix the problem either.
external FW harddrive 7200 rpm daisy chained through the MOTU
the HD only contains my music source files and samples. my OS and software is on the main computer HD.
Firewire card - Texas Instrument OHCI Compliant IEEE 1394 Host Controller
Since the FW hookup is a 4 pin hookup I'm unable to use bus power so its all been with the MOTU plugged in.
The glitches are when i play back old completed songs, haven't experimented enough to figure out more than that.
I've also noticed that when the computer beeps or when it starts up and intro sound plays there is a fraction of a second bit of glitchy sounding audio. like its having a hard time when it is playing those sounds.
any help would be great!
Maybe that what you ask of your laptop is simply too much for most of soundcards (supposing that FW Audiophile had better and more stable drivers than the normal)...? Let's see :
What is your system like ? (Laptop brand and model, CPU, RAM, internal HD rpm)
What is your song (the one that glitches) like ? (number and types of tracks...bitrate, sampling rates, types of FX...softsynths ?)
If you disable a few tracks, or better, if you delete some audio tracks and then save the song under a new version, close FL Studio and then reopen and reload this "light"version, are you having more stability ?
If you do the same with VST or DX plugins or synths, does it help ?
I noticed that there are a few synths or a few VST that are quite boggy, or sometime they won't cause crash or noise during mixdown, but will simply ask WAY TOO MUCH cpu for what they do. And as much as I remeber, they were ok with some drivers, and extremely cpu-heavy on some others. And sometime bypassing them is not sufficient, they must be totally removed from the song.
Another idea : The problem could be the bandwidth limitation of the FireWire. If you have glitches with, lets say a "light" 8 tracks version of your song, and you think your internal HD should be able to handle that amount of data streaming, move your tracks to your internal HD and reopen the light-8-track version using tracks that are on your internal HD.
I do not know how many tracks an internal HD can handle usually as I do not do multitrack recording from my laptop, but...
The thing you can do to be sure that it is not the FW bandwidth that cause glitches, try to find the lowest number of audio tracks were your audio have dropouts (using FW HD), and supposing it's 8, try with those 8 tracks transferred on your internal HD. If there is no dropout, then it means that you should try to move your external HD on a different port (USB 2.0, second onboard FW port, or best, a PCMCIA FW Card).
Another tips :
in "control panel", "system", "advanced", "performance", "advanced", choose background services instead of programs...as strange as it may seem, windows treat VST and such sound processing units as a background service, while the graphic interface is program...the position of the knobs of your VST plugins for exemple will be updated more slowly, but there will be far less glitches as the priority wll have been moved to audio.
have you tried the usual FW tips like removing the laptop battery and running only on AC, or the inverse, running only on battery, no AC plugged ?
disabling the onboard soundcard and network and modem ports in the BIOS ?
do you use this laptop for internet ? Anti-Virus or firewall ?
I wish I could buy this unit and be able to run FLstudio flawlessly on it, so I will try to help the best way I can...Any news from MOTU tech yet, Scottfro ?
What is your system like ? (Laptop brand and model, CPU, RAM, internal HD rpm)
What is your song (the one that glitches) like ? (number and types of tracks...bitrate, sampling rates, types of FX...softsynths ?)
If you disable a few tracks, or better, if you delete some audio tracks and then save the song under a new version, close FL Studio and then reopen and reload this "light"version, are you having more stability ?
If you do the same with VST or DX plugins or synths, does it help ?
I noticed that there are a few synths or a few VST that are quite boggy, or sometime they won't cause crash or noise during mixdown, but will simply ask WAY TOO MUCH cpu for what they do. And as much as I remeber, they were ok with some drivers, and extremely cpu-heavy on some others. And sometime bypassing them is not sufficient, they must be totally removed from the song.
Another idea : The problem could be the bandwidth limitation of the FireWire. If you have glitches with, lets say a "light" 8 tracks version of your song, and you think your internal HD should be able to handle that amount of data streaming, move your tracks to your internal HD and reopen the light-8-track version using tracks that are on your internal HD.
I do not know how many tracks an internal HD can handle usually as I do not do multitrack recording from my laptop, but...
The thing you can do to be sure that it is not the FW bandwidth that cause glitches, try to find the lowest number of audio tracks were your audio have dropouts (using FW HD), and supposing it's 8, try with those 8 tracks transferred on your internal HD. If there is no dropout, then it means that you should try to move your external HD on a different port (USB 2.0, second onboard FW port, or best, a PCMCIA FW Card).
Another tips :
in "control panel", "system", "advanced", "performance", "advanced", choose background services instead of programs...as strange as it may seem, windows treat VST and such sound processing units as a background service, while the graphic interface is program...the position of the knobs of your VST plugins for exemple will be updated more slowly, but there will be far less glitches as the priority wll have been moved to audio.
have you tried the usual FW tips like removing the laptop battery and running only on AC, or the inverse, running only on battery, no AC plugged ?
disabling the onboard soundcard and network and modem ports in the BIOS ?
do you use this laptop for internet ? Anti-Virus or firewall ?
I wish I could buy this unit and be able to run FLstudio flawlessly on it, so I will try to help the best way I can...Any news from MOTU tech yet, Scottfro ?
I'll try your suggestions this week as I have to get to work now but this is what MOTU said to me.
Thank you for writing.
Are you running Windows XP SP2? What type of FW card are you using?
Our FW interfaces under Windows are only 100% compatible on FW cards
that use a Texas Instrument or Lucent chip set.
NEC, VIA, or simply OHCI compliant are not compatible chip sets.
There are also issues with SP2's 1394 driver. MOTU recommends using SP1.
if you go on unicornnation there's a topic called All motu firewire
users using xp sp 2 or something... first it says the sp 2 1394 driver
is flawed and it reduces bandwidth from 400 Mbps to 100 Mbps.... so
there is a little applet to reinstall the sp 1 driver on the microsoft
site and also there is another link to just get the driver and do it
yourself.... it also says that DEP must be shut off by going into the
c:\boot.ini file and changing the last line from "/NoExecuteBlahblah"
to "/Execute"... this has made a WORLD difference...... no more pops
squeaks that aren't a result of pushing the computer too hard (this was
happening before and i know what not to do to avoid it...)
where i found this in unicornation:
http://www.motunation.com/forum/viewtopic.php?
t=4810&highlight=firewire
and the microslop applet:
http://support.microsoft.com/kb/885222/en-us
Check to see if you have a shared IRQ number with the onboard Sound
card and FW card. Disable the onboard sound card within the BIOS. IRQ
settings or Power management can be the cause of high pitch output and
stuttering.
Disable Wireless Internet networking.
Make sure the graphics card and FW card run on their own IRQ (disable
unused USB2 nodes).
Battery Polling:
Some PC machines will have an issue where the FW bus has been
interrupted. This is usually due to the ACPI. On windows you can't fix
this ACPI, but in many cases work around it. On some laptops this is
due to Battery polling. Try disabling the battery driver in device
manager. This will fix the high pitch output ( only an issue in SP2),
but leaves you with your PC that switches off when the battery runs out
rather than gracefully shutting down.
Regards,
Garrick Sanderson
MOTU Tech Support
Thank you for writing.
Are you running Windows XP SP2? What type of FW card are you using?
Our FW interfaces under Windows are only 100% compatible on FW cards
that use a Texas Instrument or Lucent chip set.
NEC, VIA, or simply OHCI compliant are not compatible chip sets.
There are also issues with SP2's 1394 driver. MOTU recommends using SP1.
if you go on unicornnation there's a topic called All motu firewire
users using xp sp 2 or something... first it says the sp 2 1394 driver
is flawed and it reduces bandwidth from 400 Mbps to 100 Mbps.... so
there is a little applet to reinstall the sp 1 driver on the microsoft
site and also there is another link to just get the driver and do it
yourself.... it also says that DEP must be shut off by going into the
c:\boot.ini file and changing the last line from "/NoExecuteBlahblah"
to "/Execute"... this has made a WORLD difference...... no more pops
squeaks that aren't a result of pushing the computer too hard (this was
happening before and i know what not to do to avoid it...)
where i found this in unicornation:
http://www.motunation.com/forum/viewtopic.php?
t=4810&highlight=firewire
and the microslop applet:
http://support.microsoft.com/kb/885222/en-us
Check to see if you have a shared IRQ number with the onboard Sound
card and FW card. Disable the onboard sound card within the BIOS. IRQ
settings or Power management can be the cause of high pitch output and
stuttering.
Disable Wireless Internet networking.
Make sure the graphics card and FW card run on their own IRQ (disable
unused USB2 nodes).
Battery Polling:
Some PC machines will have an issue where the FW bus has been
interrupted. This is usually due to the ACPI. On windows you can't fix
this ACPI, but in many cases work around it. On some laptops this is
due to Battery polling. Try disabling the battery driver in device
manager. This will fix the high pitch output ( only an issue in SP2),
but leaves you with your PC that switches off when the battery runs out
rather than gracefully shutting down.
Regards,
Garrick Sanderson
MOTU Tech Support
sonidos wrote:Maybe that what you ask of your laptop is simply too much for most of soundcards (supposing that FW Audiophile had better and more stable drivers than the normal)...? Let's see :
What is your system like ? (Laptop brand and model, CPU, RAM, internal HD rpm)
What is your song (the one that glitches) like ? (number and types of tracks...bitrate, sampling rates, types of FX...softsynths ?)
If you disable a few tracks, or better, if you delete some audio tracks and then save the song under a new version, close FL Studio and then reopen and reload this "light"version, are you having more stability ?
If you do the same with VST or DX plugins or synths, does it help ?
I noticed that there are a few synths or a few VST that are quite boggy, or sometime they won't cause crash or noise during mixdown, but will simply ask WAY TOO MUCH cpu for what they do. And as much as I remeber, they were ok with some drivers, and extremely cpu-heavy on some others. And sometime bypassing them is not sufficient, they must be totally removed from the song.
Another idea : The problem could be the bandwidth limitation of the FireWire. If you have glitches with, lets say a "light" 8 tracks version of your song, and you think your internal HD should be able to handle that amount of data streaming, move your tracks to your internal HD and reopen the light-8-track version using tracks that are on your internal HD.
I do not know how many tracks an internal HD can handle usually as I do not do multitrack recording from my laptop, but...
The thing you can do to be sure that it is not the FW bandwidth that cause glitches, try to find the lowest number of audio tracks were your audio have dropouts (using FW HD), and supposing it's 8, try with those 8 tracks transferred on your internal HD. If there is no dropout, then it means that you should try to move your external HD on a different port (USB 2.0, second onboard FW port, or best, a PCMCIA FW Card).
Another tips :
in "control panel", "system", "advanced", "performance", "advanced", choose background services instead of programs...as strange as it may seem, windows treat VST and such sound processing units as a background service, while the graphic interface is program...the position of the knobs of your VST plugins for exemple will be updated more slowly, but there will be far less glitches as the priority wll have been moved to audio.
have you tried the usual FW tips like removing the laptop battery and running only on AC, or the inverse, running only on battery, no AC plugged ?
disabling the onboard soundcard and network and modem ports in the BIOS ?
do you use this laptop for internet ? Anti-Virus or firewall ?
I wish I could buy this unit and be able to run FLstudio flawlessly on it, so I will try to help the best way I can...Any news from MOTU tech yet, Scottfro ?
Just to be sure I'm reposting this snippet from the link you gave above :
"A tech support from MOTU did respond to me today to tell me that the only problem with Travelers on SP2 has to do when there are more than one device."
It's sad to hear this, as multitrack recording can be quite limited from a 4200rpm HD.
Let us know the maximum amount of track you're able to play and record with the internal hard drive.
"A tech support from MOTU did respond to me today to tell me that the only problem with Travelers on SP2 has to do when there are more than one device."
It's sad to hear this, as multitrack recording can be quite limited from a 4200rpm HD.
Let us know the maximum amount of track you're able to play and record with the internal hard drive.
I'm going to have the ultralite in just a few days, and the first thing I will test is Fruity Loops compatibility.
So we will see if it's your setup is the problem or if it really is the Ultralite that do not like FL.
Scottfro, could you keep us aware of what is happening with your ultralite ?
Thanks
Ralph
So we will see if it's your setup is the problem or if it really is the Ultralite that do not like FL.
Scottfro, could you keep us aware of what is happening with your ultralite ?
Thanks
Ralph