Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'driver'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • FBV Controllers (MKII / 3)
    • M5
  • Amplifiers
    • Powercab
    • Catalyst
    • Spider V
  • POD
    • POD Go
    • Pocket POD
    • POD Express
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay/XD-V Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

  1. I am experiencing lots of crashes with the POD Go ASIO driver in Windows using Ableton Live 11. Recording goes fine until you switch off the power of the POD Go. That will almost always result in a fatal blue screen of death. So I'm suspecting a driver fault. Does anyone else have similar problems?
  2. Some users have reported getting an error message when installing Line 6 product drivers on Windows 10 or 11. The error message will mention that Line 6 drivers are not being recognized or are being blocked after installation. The best workaround for this is to disable Memory Integrity under Windows security settings. You can find this feature under Windows Security > Device Security > Core Isolation details. See this article from Microsoft for further details: https://support.microsoft.com/en-us/windows/device-protection-in-windows-security-afa11526-de57-b1c5-599f-3a4c6a61c5e2 This is a known issue to our team, and for now the best option is to disable Memory Integrity as a work-around. We will continue to monitor this issue for our driver releases.
  3. Hi everyone, I installed the latest Line 6 HX Stomp Driver2 (Version 1.97.0.2) for Windows 10. When I try to start a recording session on Ardour, the HX Stomp is recognized, I can select the drive ASIO... but then when I start the session Ardour crashes... Has anybody have any issues with the HX Stomp, a DAW on Windows and the latest driver(s) ? Thanks Vincent
  4. Background Apple has recently pivoted away from using Intel-based CPUs with its computers, instead favoring the Apple Silicon processor, also known as the M1 Chip. Both Intel and Apple Silicon systems run on macOS 11.0 Big Sur. As it stands, some Line 6 products are not fully supported on computers using Apple Silicon processors, so we cannot offer technical support for those products installed on M1 systems at this time. We highly encourage you to check with the manufacturers' websites of your music system’s hardware and software for M1 compatibility. Workaround on M1 Systems NOTE: Any workarounds offered are not official solutions. Issues experienced with workarounds offered cannot be addressed until official support is offered. Starting with Big Sur macOS 11, Apple introduced Rosetta v2, which allows applications to run in an emulated mode. Rosetta runs automatically with our software that is NOT a plugin. To use Rosetta with our plugins, locate your DAW in the Applications folder. Use command ⌘+I and check the “Open in Rosetta” box. You may have to rescan your plugins afterwards. Testing Applications and plugins tested (latest versions) on M1 systems running macOS 11.0 Big Sur: Helix Native: working as expected on DAWs running under Rosetta Echo Farm 3.0: working as expected on DAWs running under Rosetta Amp Farm 4.0: working as expected on DAWs running under Rosetta POD Farm 2 (Plugin): working on DAWs running under Rosetta, but takes a few seconds to appear after adding an instance of the plugin POD Farm 2 (Standalone): working as expected Ampeg SVT Suite: working as expected on DAWs running under Rosetta HX Edit: working as expected POD Go Edit: working as expected Powercab Edit: working as expected POD HD500 Edit: App launched properly, device was unable to connect POD HD500X Edit: App launched properly, device was unable to connect POD Pro X Edit: App launched properly, device was unable to connect Spider Valve Mk II Edit: working as expected Spider V Remote: working as expected Spider IV Remote: working as expected Workbench HD: working as expected Line 6 FBV Control: working as expected Line 6 Updater: working as expected Line 6 License Manager: installs as expected, yet devices do not populate in Line 6 License Manager. There is currently an open bug for this issue. Tested and available: M1-compatible Hardware Audio Drivers for: Helix Helix LT Helix Rack HX Stomp HX Stomp XL POD Go POD Go Wireless POD HD POD HD Pro POD HD Pro X POD HD500 POD HD500X Hardware Audio Drivers for most TonePort/POD Studio products (see below for exceptions) Will not be updated to support Silicon-based systems: StageScape: Audio Driver POD X3: Audio Drivers, Editors, Updaters, Control Panel app and License Manager POD XT: Audio Drivers, Editors, Updaters, Control Panel app and License Manager TonePort UX8: Audio Drivers, Updaters, Control Panel app and License Manager TonePort/POD Studio KB37: Audio Drivers, Updaters, Control Panel app and License Manager POD HD300/400 Line 6 Monkey
  5. Hello, bought a brand new HX Stomp. It won't connect to my pc (Windows 7 x64). Problems found: - USB Audio Device has a driver problem. - HX Stomp doesn't have a driver. Are the driver available for download somewhere? None of the software provided, in the Downloads section of Line6's webpage, are able to "see" my HX Stomp.
  6. Hi, just switched to a Macbook m1 Pro. HX Edit HX Stomp all fine. Issue I, I cannot change the sample rate. Is fixed in Audio Devices. All my cubase projects are pitched up now (nice speed boost for metal, though :-) ) I have installed Line 6 Helix Driver 1.5.0.dmg. But no change here. What do I missing. Thanks, Marco
  7. Changes to macOS Security Policy With Silicon processor computers running macOS Big Sur or greater, Apple has changed their security policy. These machines no longer allow third party drivers to be installed in the manner that they previously had. Driver installs now require the macOS security settings to be lowered before installation. As Silicon is still new to everyone, we expect to see bug fixes, changes and optimizations to macOS Big Sur and possibly subsequent macOS releases over the coming months. With that, the Silicon driver install process may change as well. As such, we encourage you to update your Silicon machine to the latest Big Sur version, which is currently 11.6, before installing drivers. Changing Security Settings Apple’s guide to changing security settings on a Silicon Mac are found at: https://support.apple.com/en-lk/guide/m … 8f7291/mac · Shut down your Mac · Press and hold the power button until you see "Loading startup options …". Your Mac will boot into Recovery mode. · Click Options (the gear icon), then click Continue · In macOS Recovery, you may need to choose your account and click Next. Enter the password and click Continue. · In the top menu go to Utilities...Startup Security Utility · Select the system on which you want to install the Driver. If the disk is encrypted with FileVault, click Unlock, enter the password, and then click Unlock. · Click Security Policy, choose Reduced Security and check the option to allow user management of kernel extensions from identified developers · Click OK. Enter the password for your account and click OK. · Restart your Mac from Apple menu Rosetta Installation When installing the Line 6 driver from the downloaded dmg file, you may be prompted to install Rosetta. · If so, click “Install”. Enter your password when requested. · If you see “System Extension Blocked”, go into System Preferences...Security and Privacy, click the lock, enter your password, click Unlock, and choose Allow. · Restart your Mac. Driver Removal It is advised that no programs are open, especially programs that may require the kext that is about to be removed. 1. In Finder, locate the kext file that is to be removed. Kext files are located in Library/Extensions. Keep this finder window open. 2. Open Terminal. Type the following command followed by the pathway of the kext that you would like to remove. Type without the quotes: "sudo kmutil unload -p /Library/Extensions/<Kext Name>". (ex. "sudo kmutil unload -p /Library/Extensions/L6Helix.kext") and click enter. 3. Enter your password. There should be no message after this. 4. Go to the finder window that was left open in step 1 and remove the kext file to the trash. You will be prompted to enter your password. 5. Restart your computer. 6. Go to Library/Extensions in finder and verify that the kext file is no longer in the extensions folder. If you see a message in Terminal (after Step 3), chances are there is another program open operating in the background that may interrupt the command. If so, restart your computer - verify there are no applications open and begin steps 1-6 again.
  8. i tried to follow the tutorial on youtube : https://www.youtube.com/watch?v=OIeJjy9Ruro&t=184s&ab_channel=Line6Support But at 6 minutes when he showed what could happen , it did not show what i was experiencing . my clip light weren't going back and forth And my light meters did not light up . nothing was lighting up despite following the tutorial to this point . I tried to reinstall pod farm and the drivers multiple times but it did not work. (but i guess there is an issue with the drivers ) If anyone can help me i will be very thankfull
  9. Hi everyone! First of all, I am from Argentina, sorry for my english. Here is my problem: I have purchased a Helix Floor the last week. Everything was going OK with the product until I tried to connect the pedal to my desktop PC (Windows 10) using the USB output with the aim of edit my presets easily (its a little bit tedious to do it manually having the possibility to do if from my PC). The problem is I am not able to do anything using my PC because as soon as I connect the USB cable, the OS says "DRIVER IS UNAVAILABLE"... that is, HELIX appears in my SETTINGS as a KEYBOARD but with that legend below (DRIVER IS UNAVAILABLE). Has anyone has the same problem in the past? As far as I know, my Helix has the last Firmware installed (3.11.0), so, thats not the problem as I read in several topics. Thanks a lot to everyone!!! GABRIEL
  10. Hello All, I'm new to Helix and I've spent a little time playing with the Helix (with firmware 3.11) as a USB audio interface attached to my Mac M1 mini (running macOS Big Sur 11.4). All is well when I stick to a sample rate of 48000kHz but I would like to able to change the sample rate, so I tried to install the Line 6 Helix Driver (1.1.0.) for Mac, which says it should allow sample rates of 44.1kHz, and 96kHz. However, although the driver seems to install ok (the .kext file appears in the /LIbrary/Extensions folder), the Helix Audio device does not allow me to change the sample rate. Has anyone else encountered this problem and has found a way around it? Maybe I'm best to just record from the analog outs to my Mac via my existing interface. Thanks for any help, Dave
  11. macOS 10.13/10.14/10.15/11.4 has implemented an additional security layer for kernel extension drivers, such as the Line 6 audio drivers. After the Line 6 device is connected, the customer must open the Security Control Pane and accept the Line 6 driver in order for the device to be recognized. Typically, but not always you'll see this message when your driver gets blocked, or is not available for use with your DAW: However, sometimes the driver gets blocked and the message won't appear. Your driver and hardware simply won't work. In either case, you'd need to approve the driver in System Preferences > Security & Privacy: Additional information about this change can be found at https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 For some cases if the "Allow" button does not change anything, or the "Allow" button does NOT disappear after clicking. Please try these steps: Go into: System Preferences > Keyboard > Shortcuts > Select 'All Controls'. Then: Go back to System Preferences > Privacy & Security > Press 'Tab' until 'Allow' is selected > Press 'Spacebar'. Note: the Privacy & Security page may need to be unlocked before 'Tab' will work.
  12. i have updated my line 6 UX1 to the latest driver 4.2.7.7 from 4.2.7.6 but when i go to "Line 6 audio-MIDI devices settings" i cannot change the bit depth or buffer size. when i select another size or bit rate, it just reverts back to default. the previous update did not do this. i have uninstalled all line 6 drivers and updated to the new one. i had no luck so i reverted back to the previous update. i would like to update this thing! please help!
  13. Summary Check the Pod HD ASIO driver is not performing Sample Rate Conversion without you being aware of it. Remove easy potential sources for stutter. Background I had been plagued by the commonly-reported Pod HD-related blue screens (BSOD) on my Win 10 desktop, particularly when working with my DAW, Reaper. I have reached a point where my setup is now stable. Over recent weeks I've had four recording sessions without bluescreens whilst maintaining a USB connection. In this post I'm intending to document what I did, what was effective and what was ineffective. I see many frustrated posts about this issue. Sometimes people seem to be replacing or returning their Pod HD, which is a shame. I have not seen Sample Rate Conversion problems being talked about in the trouble shooting posts I read, so I hope this helps someone. Workarounds or ineffective configurations I tried - Ignoring USB and going direct to my other interface (as I have one). Obviously this works, but the sound quality did not seem as good as the USB connection to me. I'm not saying I can hear the extra DAC/ADC step, but it's another spot where you have to get the levels right, and you need two cables if you want stereo. My other interface only has two channels and I wanted to keep a mic in the other one. So, if you are really stuck this works fine, but was not great for me. - Disabled Selective USB Power Down. You will see other references to this step. It did not reduce BSODs for me on its own. I did leave this setting disabled in my final configuration, though, so it may be a factor. - Using the rear USB vs the front USB. This does have some logic to it as the front USB ports on a desktop tend to be a hub, so if the rears are not then things have been simplified. Using a Rear USB did not make a difference for me. - USB2 vs USB3. Simply swapping to USB2 was not enough for me, but I have continued to use a USB2 port in the stable configuration, so could be a factor. If you have USB2 ports available I think it make sense to use them, as the Pod HD was, I think, designed before the USB3 standard was introduced. - Different combinations of allowing the Pod to be or not to be the audio device used by Windows as default made no difference for me. - Disabling Windows System Sounds on its own made no difference for me, but I have continued to leave them off in the stable configuration, so could be a factor. After trying those solutions I found the official Line 6 advice on USB troubleshooting here: https://line6.com/support/page/kb/recording/computer-audio-set-up-and-troubleshooting/usb-audio-troubleshooting-r443/ and set about eliminating sources of stutter which seem to be less-well handled by the Pod HD driver stack when compared with the driver for my Focusrite Saffire 6 USB audio interface. I noticed that Reaper was reporting that the Pod driver was operating at a 44.1 kHz sample rate, despite the Windows Sound Control Panel settings being set to 48kHz sample rate and Reaper being set to use whatever the hardware was using. Checking the Line 6 Audio-Midi Devices App confirmed the same thing, and the Sample Rate Converter light in that app was on. I went through all the parts of the end to end system where I could set the sample rate and made sure all were aligned to the same settings (48kHz, 24 bit). There are four places I checked and aligned: 1) Windows Sound Control Panel/Playback tab/Line 6 POD HD Device Properties/Advanced/Default Format -> Set to 24bit, 48000 Hz (Studio Quality) 2) Windows Sound Control Panel/Recording tab/Line 6 POD HD Device Properties/Advanced/Default Format -> Set to 24bit, 48000 Hz (Studio Quality) 3) Reaper/Audio Device Settings -> Request Sample Rate to 48000 4) On the Pod itself, under the IO settings there is a setting for the sample rate of the S/PDIF interface. This name suggests it has nothing to do with the USB output, but I made sure it was set to 48Khz too. Annoyingly, I can't remember what the default was, so I can't remember if I changed this. After step 3 Line 6 Audio-Midi Devices App now reports no Sample Rate Conversion happening and Reaper also reports 48kHz operation. I also shut down some unnecessary audio-using apps (Skype, Google Music Manager and Steam) and removed the Windows System Sounds. I felt these were easy and prudent steps to take. I felt from the Line 6 article the general advice was to remove sources of noise and stuttering, so where I could remove potential sources easily for me I did so. I did not at any time remove my existing Focusrite Saffire 6 USB interface and its driver, so in my case at least the Pod is able to co-exist with other ASIO drivers. Note that the Focusrite wasn't being used as Reaper doesn't provide the option to use two ASIO devices at the same time, but was plugged in and powered on. I have not taken the time to isolate the single factor that has made a difference for me, however the BSODs did seem to clear up once I had got the Pod ASIO driver operating in 48 kHz sample rate instead of doing Sample Rate Conversion. I don't yet know why it was stuck operating at 44.1 kHz, as nothing before or after it was asking for that and I had not changed defaults. Furthermore, when I was trying to force it back to 44.1 to isolate the fix for this post it stubbornly refused to return to that rate. At this point I have arrived at a stable setup for me so I am unlikely to spend more time characterizing the cause, but will report back if I find something. I'd say it is likely others have this problem as I don't change defaults for this sort of thing. Effective Configuration - Disabled Selective USB Power Down - Disabled Windows System Sounds - Shut down unnecessary apps that use audio - Ensured Windows Sound Control Panel properties for Playback and - Recording on the Pod are set to 24bit, 48000 Hz - Reaper/Audio Device Settings -> Request Sample Rate to 48000 (key step for me) - Using front panel USB2 port I am sure not all of these steps are quite necessary for me, but wanted to share as completely as I could. General guidance, summary observations and speculations Clearly, reading the official advice at https://line6.com/support/page/kb/recording/computer-audio-set-up-and-troubleshooting/usb-audio-troubleshooting-r443/ is good practice. I've internalized that article as "you have to be as kind to the drivers for the Pod HD as you can". For me that meant getting over a Sample Rate Conversion that was happening, which I speculate takes extra cycles in the driver stack, introduces more potential error conditions and makes it more susceptible to stutter conditions. I am not sure why the driver was choosing to operate at 44.1 Khz instead of 48 Khz, but I have been able to force it to 48 Khz operation with Reaper. Removing unnecessary Sample Rate Conversion feels like good practice in any case. Getting the USB connection stable has been a big plus for me. The clarity of my recordings is better, I have stereo, so things sound fuller, it is easier to set levels and hear changes. It makes me feel like I need Helix Native less. Happy days :-) DM
  14. Hi. I have a problem. Maybe someone has the answer. Since i use my PodGo, i have a lot a crakles and noise in my DAW. If i change my buffer size (extra small or extra large) it change nothing. My cpu is right (17% used) I had a PodHD before with the same computer and the same DAW and the problem was not there. So, it seems to come from the Podgo driver. It occurs only within the daw (cubase 10)... Thank you... and the last uptade is done (version 1.12)
  15. If you've installed a Line 6 driver and the device will not subsequently connect, it is possible that the driver is disabled by the system. How to check if the software is disabled by the system: • Click on the Apple symbol in top-left corner of the screen and go to "About this Mac -> Overview ->System Information -> Disabled Software”. • If there is disabled software, it will be presented with a 10-digit software ID and a file descriptor, similar to "VCN535JA6Y - com.line6.driver.xtaudio" • Take a screen shot or write down the ID (in this example it’s VCN535JA6Y – yours might be different). How to enable software that is disabled by the system: • Uninstall the drivers: https://line6.com/support/page/kb/recording/computer-audio-set-up-and-troubleshooting/how-to-uninstall-line-6-drivers-from-mac-osx-r85/ • Reboot to recovery, holding down Command-R while restarting. • From Menu -> Utilities, open Terminal and type the following (replacing the system ID with yours): “spctl kext-consent disable” “spctl kext-consent add VCN535JA6Y" (replace the VCN535JA6Y with yours if different) “spctl kext-consent enable" • Reinstall the driver. • Open System Preferences -> Line6 Audio-Midi devices and plug the device into the Mac. The device should appear in a few seconds.
  16. I have problems on an older Mac Pro with the MacOS OS-X Lion 10.7.5 The latest driver is shown as 7.3.7 but no matter how I install it (via the monkey or manually) the driver neither does update in the monkey ("update selection") nor let me connect the POD via HD Edit or the licence manager. HD Edit crashes on directly start. The licence manager shows the computer as activated but no device. The driver is shown as outdated even if the POD is not connected. Of cause I tried to uninstall the driver via the uninstall-tool and to restart the mac. Of cause I have tried 2 different USB cables (both working on another machine). I have tried everything & several times… no luck!
  17. I have a POD HD500 that i have just recently bought. I have previous experience with this pedal, but have never run into an issue like this one. I will do my best to explain this without getting anyone confused. I have 2 Computers. A custom build and a factory built Dell. The POD HD500 drivers will not properly install on my custom built PC, but install perfectly fine on the factory built Dell. The custom built computer is my primary computer and the one I am wanting to use for recording. This issue is very odd to me because i have previously had a friends HD500 connected to the custom built pc for 3 months and it worked fine. I haven't made any changes to the computer since then. I have tried installing the drivers as administrator, tried every USB port (which all work fine for any other devices). My PC recognizes the POD HD500 in the device manager, but is not recognized in Line 6 Monkey or HD500 Edit. I am at a loss and would appreciate any helpful advice.
  18. Hi at all!!! I have a problem with the amplifi tt drivers. I have already installed line 6 updater and updated to the latest version but when I start line 6 updater does not recognize the amplifi tt and as a result do not recognize it as sound card and I can not use cubase to record. what can I do? I have seen that many have encountered the same problem I followed all the directions but still did not go. Is there anyone who can help me ??? Please
  19. Base info: System: macOS Mojave 10.14.2 Hardware: MacBook Pro 2016, Line 6 Pod X3 Pro Line 6 driver version: 7.6.8 Line 6 Monkey version: 1.78 Line 6 License Manager version: 1.13 Line 6 Monkey does not recognize installed driver and connected device, same as License Manager. However Pod is avaiable in System Preferences as Audio-MIDI Device and works perfectly with Pod Farm 2.59. Because of problem with License Manager i cant use full version of Pod Farm. On Windows laptop everything works like a charm (via usb 2.0 and usb-c connectivity). Any ideas what is wrong with License Manager on macOS Mojave?
  20. This is my elaboration on Round Trip Latency of Helix hardware used as audio interface based on research on closed fb group https://www.facebook.com/photo.php?fbid=10156514192780269&set=pcb.1077888115728194&type=3&theater&ifg=1 This topic is hardly relevant if you are monitoring direct. Helix hardware latency is 1,8ms from AD/DSP/DA (measured for one DSP Path), no matter what buffer or sampling frequency you pick. If you use another interface for monitoring/recording it is not relevant neither. It is 2,70 firmware time. OSX - you have a choice of two drivers: 1. Multi sampling rate Core Audio driver. You get the lowest latency of 15ms using 32 samples buffer but this seems not to be stable (tested on 8th gen i7) . Safer buffers of 64, 128 samples are at 20ms range. 2. Class Compliant 48kHz driver at 64 samples buffer gives 8ms RTL. EDIT: I do not know if 8ms RTL is REPORTED by the driver or it can be REAL RTL. Windows - you have a choice of two drivers: 1. Supplied ASIO driver. Here are my figures for Round Trip Latencies: 21ms on "Small" 128 samples buffer@48kHz 17ms on "Extra Small" 64 samples buffer@48kHz 15ms on "Small" 128 samples buffer@96kHz 10ms on "Extra Small" 64 samples buffer@96kHz - but this setting is unusable because of artifacts. Bad news for virtual instruments players are 3/4 of RTL is on the output side. 2. ASIO4ALL driver - it is rather overlay for WDM driver, not compatible with Pro Tools. Round Trip Latencies are: 5ms at 128 samples buffer@48kHz 3ms at 64 samples buffer@48kHz 3ms at 128 samples buffer@96kHz Good news or virtual instruments players are buffers are 50/50 input/output. EDIT: I have proven that they are in fact REPORTED RTLs. They are fake numbers! I made my Windows tests using using Reaper (64bit), desktop Windows 10 PC with 3th gen i5 CPU, 16GB RAM. Reaper session was loaded with 5 Hx Native instances. CPU usage was monitored with Windows Task Manager and for the same 128 buffers on both drivers was at 30%. 7ms pictured vs mine 5ms is because I switched off additional 32 samples buffers used for latency compensation in ASIO4ALL (for aggregating devices?) Some pictures to back it up:
  21. I need help for my iMac Sierra, I can't download the driver for run my line 6 ux1. When I start installing the driver they don't work.... can anyone help me pls
  22. Hi. I'm getting up-to-speed on integrating my new Helix Floor into my Cubase 10 recording rig. Here is the experience I'm having with the Helix connected to my computer via USB: In Cubase I open a project which was created before I even owned the Helix. IOW, this saved project could have no idea about Helix or the Helix ASIO driver. However, what I find is that the Helix ASIO driver is now the Cubase ASIO driver, putting me in a position where I do not recognize the names of the audio inputs and outputs as previously in use. Now, strangely (probably by design!), things do seem to "work" - I can record my guitar into Cubase and can play back my prior recorded tracks and hear them. The thing is, I have no idea what is really going on - why I'm even able to hear things, how the guitar is getting in and the pre-recorded audio is getting out. IOW, I suppose I just don't understand sufficiently how ASIO/audio works in Cubase, and especially how things change when the Helix is connected. My past history is using the Cubase with my MOTU 2408 mkII interface (which I do understand well), and also (more recently) using Cubase with my Motif XS keyboard and the Firewire ASIO interface (which causes the Motif to "take the place" of the MOTU 2408 mkII). Is there someone who has this all straight in their head who can write come words of enlightenment here that will help me to fully grasp the situation? Or, can someone point me to Helix ASIO driver docs which would explain it? If so, many thanks!
  23. A quick note that I hope might be useful to others. I bought a Helix LT this week. The driver software loaded fine onto a couple of laptops but I couldn't get it to install on my main Windows 7 PC. The Helix showed up as a device in "Devices and Printers" but was reported by WIndows as unusable and that the driver had failed to load. It appears that my copy of Windows had loaded a generic USB device driver instead of the L6 software. Anyway, after several fruitless exchanges with L6 support, I found the fix myself. You need to go to the Helix device shown in Device Manager, click on Properties, click on Driver, tell it to "Update Driver" and install the driver manually from the folder: Programs (x86)/ Line6/ Tools/ Driver2 Archive/ Helix. Windows will identify the ".inf" file in that folder as the correct driver. Click on that and you should be good to go. I suspect it's an unusual problem inasmuch as one of my laptop installs was also Win 7 and went perfectly smoothly. Nevertheless, I hope this may help someone. Now I can get back to trying to get the Helix to play nicely with my DT25.......... Andy
  24. Francais Deutsch Once you have installed Line 6 Monkey and the applicable drivers for your Line 6 device, you will be able to assign your USB capable device as the sound card for your computer. See the following instructions for assigning your Line 6 device as a sound card for your Mac computer: Select the "Apple dropdown" menu, then select "System Preferences" Select "Sound" in the Hardware section Select "Input", then select your Line 6 device in the Sound Playback dropdown menu (This example uses the Guitarport). Select "Output", then select your Line 6 device in the Sound Playback dropdown menu (This example uses the Guitarport). Close the window. Be sure that your speakers and/or headphones are connected to your Line 6 device (rather than the computer's sound card). Ein Line 6 Gerät als Sound Karte für Ihren Mac Computer zuweisen Nachdem Sie Line 6 Monkey und alle nötigen Treiber für Ihr Line 6 Gerät installiert haben können Sie ein USB-Gerät von Line 6 als Sound Karte für Ihren Computer zuweisen. Wenn Sie Probleme bei der Installation von Monkey oder den Treibern haben besuchen Sie bitte folgende Webseiten: Line 6 Monkey: Installation und F.A.Q. Installation von Treibern für Ihr Line 6 Gerät Folgen Sie den anschließenden Anweisungen um Ihr Line 6 Gerät als Sound Karte zuzuweisen: Im Apple Menu, klicken Sie "Systemeinstellungen". Wählen Sie dann "Ton" in der Kategorie "Hardware" aus. Klicken Sie oben "Eingabe" an und wählen Sie dann das Line 6 Gerät aus der Liste. Wir benutzen für unser Beispiel GuitarPort. Klicken Sie dann oben auf "Ausgabe" und wählen Sie wieder das Line 6 Gerät aus. Wir benutzen für unser Beispiel GuitarPort. Schließen Sie das Fenster. Verbinden Sie nun Ihre Lautsprecher und/oder Kopfhörer mit dem Line 6 Gerät anstelle der sirekten Verbindung an Ihren Computer. Assigner un appareil Line 6 comme carte de son de votre ordinateur Mac Si vous avez installé Line 6 Monkey et les pilotes pour votre appareil, vous pouvez assigner votre appareil USB comme carte de son pour votre ordinateur. Si vous avez des problèmes d'installation de Line 6 Monkey ou des pilotes, visitez ces sites: Installation et F.A.Q.: Line 6 Monkey Installation des pilotes pour l'appareil Line 6 Suivez les instructions suivantes pour assigner l'appareil Line 6 come carte de son: Cliquez "Préférences Système…" dans le menu Apple. Cliquez l'icône "Son" dans la catégorie "Matériel". Sélectez "Entrée" et choisissez l'appareil Line 6. Nous utilisons "GuitarPort" pour cet exemple. Sélectez "Sortie" et choisissez l'appareil Line 6. Nous utilisons "GuitarPort" pour cet exemple. Fermez la fenêtre. Assurez-vous que vos haut-parleurs et/ou écouteurs sont connectés à l'appareil Line 6.
  25. When I updated the osx to 10.13.14 the UX1 stopped starting at startup, no lights red or green. opening Monkey it says that there are no drivers installed so I proceed with the installation that seems to install them but after restarting the computer Monkey keep saying that no driver are installed. I also noticed that some days after some hours that the computer is on suddenly the UX1 gives me the green light without any kind of action by myself, some other days nothing happens the whole day. Anyone have a suggestion on how to make it work again?
×
×
  • Create New...