[04:02] <coelebs> so i started to work on midi looper in pure data
[04:03] <coelebs> now i can record and erase all cc data on sequences that have predefined length
[04:04] <coelebs> need to find decent midi metronome patch and work out undo and it's ready
[05:25] <niko__> hi
[05:25] <Unit193> Howdy.
[05:26] <niko__> looking for some help
[05:26] <niko__> trying to make a toneport UX1 Line 6 work
[05:26] <niko__> ...
[05:27] <niko__> found some topics on web
[05:27] <niko__> but nothing works
[05:28] <niko__> has someone a suggestion?
[05:28] <niko__> newbee on ubuntu
[05:29] <niko__> ok
[05:29] <niko__> thanks anyways
[05:40] <Unit193> Well.
[05:48] <niko__> hi
[05:48] <Unit193> Howdy.
[05:48] <Unit193> (Not a bot, don't ask.)
[05:51] <niko__> OK
[05:52] <niko__> Can I ask you some help?
[05:52] <Unit193> I can't help you with that question though.
[05:53] <niko__> I am new to Ubuntu and try to install my external soundcard
[05:53] <niko__> but it does not work...
[05:55] <Unit193> That one runs fast.
[17:45] <cyborg_> help needed with setting usb midi devices and drivers
[17:46] <cyborg_> they are not working out of the box per se
[17:50] <cyborg_> need help getting drivers loaded for usb midi controllers
[17:50] <cyborg_> can anyone assist
[17:51] <zequence> cyborg_: Which device is it?
[17:51] <zequence> If has generic midi support, no special drivers are needed
[17:51] <zequence> generic usb support, that is
[17:52] <cyborg_> i got a second had openlabs dbeat. the controllers that i need help with are the drum pads mixer and possibly editor
[17:52] <cyborg_> mainly druim pads and mixer
[17:52] <cyborg_> i see it in lsusb
[17:52] <cyborg_> and even usbview
[17:53] <holstein> but, not in alsa or midi tab's of qjackctl connect, correct?
[17:53] <cyborg_> yes correct
[17:54] <holstein> is the device connected through a hub? i would not connect it through a hub, but direct, and through other live CD"s on other hardware til i see it in qjackctl
[17:55] <holstein> i'll try other usb ports, and i'll also check it in a supported operating system
[17:55] <cyborg_> i've  looking around and not able to find a oem driver or firmware
[17:55] <holstein> i mean, if its second hand, you are even assuming the device is functional.. you can waste time with it and its DOA
[17:56] <holstein> cyborg_: sure.. its likely that you were not promised or provided official linux support.. which is why im saying, testing in windows or osx can help you see if the device is acutally functional
[17:57] <cyborg_> it was working fine with the original hardware and software and i've been told that there are no special drivers for the controllers and mapping and such takes place in ableton
[17:58] <holstein> cyborg_: i personally dont trust what i am told. i like to see it in action, and if you havent, you are assuming
[17:58] <holstein> cyborg_: there are likely not special drivers needed for OSX, which is what is being referenced there.. but, you wont know til you look first hand
[17:58] <cyborg_> i know the guy i got it from very well and seen it work.
[17:58] <holstein> cyborg_: you can waste many hours fiddling around, if the device is damaged
[17:59] <holstein> cyborg_: im not saying anyone is lying to you, friend.. things break, and if you havent seen it working, that is a possibility, is all
[17:59] <cyborg_> however that was with the installation of windows
[18:00] <holstein> cyborg_: so, if you can say, *right now, the device works from windows*, and windows is supported, then its safe to say the hardware is functional. just make sure you can say that, or you are potentially wasting time
[18:00] <holstein> i only say that from experience..
[18:00] <holstein> otherwise, as i suggested, i'll try live CD's, and make a note of the kernels that support, if they do.. i'll try on different usb hardware and motherboards
[18:01] <cyborg_> cool thanks for looking out. but i am sure it works
[18:01] <holstein> cyborg_: from what you stated above, im not
[18:01] <holstein> cyborg_: and, its *not* working.. but, its up to you..
[18:02] <holstein> cyborg_: have you tried other  machines with a live CD? are you using a hub? have you tried plugging after boot? and before boot?
[18:03] <cyborg_> okay so i am really trying to get a usb mid driver to be assigned to it since the descriptors that are listed in the firmware are not allowing ubuntu to do its magic and automatically assign the driver
[18:03] <holstein> cyborg_: assigning it will come later.. try and just get the device working
[18:03] <holstein> cyborg_: do you have a usb hub?
[18:03] <cyborg_> no hub it is a a direct connection to the motherboard header
[18:04] <holstein> cyborg_: have you tried other motherboards? other machines?
[18:05] <holstein> its also nice to just try a  fresh system from live CD.. to remove your install from the equation.. usb devices, as zequence and i state, typically just work, out of the box..
[18:05] <cyborg_> the device turns on.  the device is seen in lsusb, another motherboard/system has beentried but it was running ubuntu as well
[18:06] <holstein> cyborg_: but, was it running the same version of ubuntu? same kernel? im suggesting trying different kernels with different drivers.. easily done from live CD's
[18:06] <cyborg_> well im ahaving an issue with an m-audio oxygen 8 that wont show  up in jack or alsa
[18:06] <holstein> cyborg_: choose one of the devices at a time, and work kwith it
[18:06]  * krokus is away (Linux is culture.)
[18:06] <holstein> cyborg_: but, my maudio is plug and play, and the oxygen is as well
[18:07] <holstein> cyborg_: so, i suggest, work with a liveCD that removes your configs and operating system from the equation, and go from there..
[18:08] <cyborg_> okay  ive tried on 12.04lts, 10.04, 14.04lts 64bit, studio 14.04, and studio64bit 14.04
[18:08] <cyborg_> live cds and freshinstalls
[18:09] <holstein> they are *all* ubuntu, though.. and im talking more specifically about 2 things. removeing you and your config from the equation, and trying *other* kernels for other potential support
[18:09] <holstein> 64 vs 32bit likely wont break support for a device like that..
[18:09] <holstein> at least, not in my experience..
[18:09] <cyborg_> so for instance try puppy, or fedora
[18:10] <holstein> cyborg_: i specifically suggested avlinux.. but, i have 12.04, 14.04, and i'll try the daily for 14.10, though, its not supported..
[18:10] <holstein> but, its likely  not the issue that a newer kernel will support the device.. its more likely just a configuration breakage, or something specific about the device that just doesnt work in linux
[18:11] <cyborg_> is avlniux a debian based distro
[18:11] <holstein> i mean, its not promised to work in linux.. but, the maudio should
[18:12] <holstein> finding someone with that specific hardware running in linux would be nice.. since you can just ask them, first hand, what is needed
[18:12] <cyborg_> yeah it would
[18:13] <holstein> in some cases, a normal firmware update that could be easily done in windows or osx could break linux support for the device
[18:13] <cyborg_> it would lead you to beleive that it is possible since it is based on a pc anyway
[18:13] <holstein> cyborg_: but, even if i had that *same* device, its not guranteed that it would have the same chipsets.. and have the same support in linux
[18:14] <cyborg_> the chipset in the device or the motherboard
[18:35] <cyborg_> hello anyone there
[18:37] <holstein> cyborg_: yes
[18:38] <holstein> cyborg_: the chipsets im referencing are in the device, but, they can be anywhere, and change.. all the company has to do is what they have promised.. and that is, provide a windows or osx driver.. not provide the chipset information, or drivers for linux
[18:40] <cyborg_> okay i got that
[18:40] <cyborg_> but i have seen where some have loaded drivers for their devices and got them to work on ubuntu
[18:44] <cyborg_> i think i need help with solving how to bind the built in drivers in ubuntu to the devices and maybe then it will work in ubuntu
[18:47] <holstein> cyborg_: i disgree
[18:47] <holstein> cyborg_: you cant "bind" anything that is not showing up
[18:48] <holstein> cyborg_: i would work on determining what you need to support the device.. which one are we talking about specifically? the maudio should just work.. and it does, correct?
[18:48] <cyborg_> they are showing up
[18:48] <holstein> cyborg_: they?
[18:48] <cyborg_> in lsusb, usbview, tree
[18:48] <holstein> cyborg_: i mean, in jack, specifically.. not lsusb..
[18:49] <cyborg_> okay so how do i get it to show in jack if the hardware is showing up on the machine
[18:49] <holstein> cyborg_: well, the fact is, it  may not be possible
[18:50] <cyborg_> my moto is nothing is impossible
[18:50] <cyborg_> i really dont want to go back to windows
[18:50] <holstein> cyborg_: sure. i didnt say impossible, what i mean is, the manufacturer is welcome and encouraged and able to provide you support for the device.. but, if they dont..
[18:51] <cyborg_> there is free lifetime support to the original purchaser of the unit
[18:51] <holstein> cyborg_: sure.. but, not for linux
[18:51] <cyborg_> I am not the original purchaser
[18:51] <holstein> cyborg_: nothing is broken here.. everything is working as advertised
[18:52] <holstein> the issue is, why is it not working in linux? and how are you going to make it work? and determine if its supposed to or able to work? knowing that the company can always make it work, utimately, but may not choose to
[18:54] <cyborg_> lthey do not support linux at this time
[18:54] <cyborg_> i am trying to do something different
[18:55] <holstein> cyborg_: right. something that is not supported
[18:55] <holstein> cyborg_: i suggest, focus on the maudio.. mine literally works when i plug it in. fully up to date 14.04 ubuntu installation.. and *any* other linux i have used it with.. out of the box
[18:55] <holstein> cyborg_: is the maudio working? and showing in jack? in alsa and/or midi?
[20:47] <cyborg_> still.... loking for help with usb midi controller drivers
[20:48] <holstein> cyborg_: no, you are not.. you are looking for help running linux on the machine.. the dbeat hardware specifically.
[20:49] <holstein> its different.. the way you ask above looks like you have a dbeat, and you are connecting it to linux, which is not the case.. you are running linux on that actual hardware and you ned *general* support for it. for everything
[20:51] <cyborg_> its an intel core 2 duo running at 3ghz 4gb ram 1tb hdd ubuntustudio 14.04 64bit
[20:51] <cyborg_> linux is running fine
[20:52] <cyborg_> i can use any normally supported devices with it
[20:52] <holstein> cyborg_: no its not.. you are not getting device support in linux for what youare asking  support with
[20:52] <holstein> cyborg_: then, what is not working?
[20:52] <cyborg_> however i just want to use the hardware that is built into it
[20:52] <holstein> cyborg_: ok.. and what hardware is that?
[20:53] <holstein> cyborg_: you can lspci and lsusb or anything else you feel a volunteer may find helpful..
[20:55] <cyborg_> did you not get the pastebin?
[20:56] <cyborg_> pastebin = http://pastebin.com/ar2cE7wy
[20:56] <cyborg_> holstein,  output of lsusb
[20:56] <holstein> cyborg_: you didnt put the pastebin in this channel, friend
[20:57] <holstein> cyborg_: that was a different channel. you can also try asking properly in #ubuntu, but, i think what you will find most benificial is running other kernels on that hardware
[20:57] <cyborg_> i put it in #kxstudio originally
[20:57] <cyborg_> when gordonjcp was attempting to help
[20:58] <holstein> cyborg_: right and the link you give still isnt working, and it was just for lsusb..
[20:58] <holstein> http://pastebin.com/ar2cE7wy is dead
[20:58] <holstein> !paste
[21:02] <cyborg_> http://pastebin.com/KFzeWGgv
[21:03] <cyborg_> do you see it now
[21:04] <cyborg_> holstein,
[21:04] <holstein> cyborg_: no. i still only see lsusb
[21:04] <holstein> cyborg_: and i still see a belkin hub connected
[21:04] <cyborg_> what do you want to see
[21:05] <holstein> cyborg_: i would open a terminal, and run "lspci, lsusb, aplay -l, arecord -l" literally anything i think a volunteer would need..
[21:05] <cyborg_> I am not disconnecting the belkin hub
[21:05] <holstein> cyborg_: you should
[21:05] <holstein> cyborg_: i suggested it first thing.. why would you not?
[21:06] <cyborg_> holstein, it is a non-issue (the Hub)
[21:06] <holstein> cyborg_: its relevant, friend..
[21:06] <cyborg_> it is how my kvm is connected
[21:07] <cyborg_> holstein,  or rather my key mouse/ touchinterface
[21:07] <holstein> this is how you will get the most help.. by having information ready in a pastebin.. and unplugging all unessential hardware and trying other kernels with live CD's
[21:08] <cyborg_> ive done that same result
[21:08] <cyborg_> different machine diff ver of kernel  same result
[21:08] <holstein> cyborg_: yeah? how did the avlinux kernel support the hardware? whats the output of lspci and aplay  -l from avlinux?
[21:09] <holstein> cyborg_: not different machine.. *that* machine
[21:10] <cyborg_> not installed any more
[21:10] <holstein> cyborg_: i *never* suggested installing it
[21:11] <holstein> what i suggest is, running different kernels live, and see how those commands list and recognize the hardware
[21:11] <holstein> cyborg_: live, meaning, yyou dont need to install them
[21:21] <cyborg_> holstein, here is the output of "lsusb -d 1471: -v | less" "lspci" and "aplay -l" http://pastebin.com/cLRm1qQU
[21:21] <cyborg_> http://pastebin.com/cLRm1qQU
[21:22] <cyborg_> do u c it
[21:22] <holstein> cyborg_: ok.. so just do that for a few other kernels
[21:22] <holstein> and, id try and keep it simpler
[21:23] <cyborg_> look i want to get it working on this installation
[21:23] <holstein> i mean, literally open the terminal.. run "lspci" "lsusb" "aplay -l" "arecord -l" and pastebin that
[21:23] <holstein> cyborg_: look?
[21:24] <holstein> cyborg_: im offering troubleshooting steps that can aid you in getting it working in that installation
[21:24] <holstein> cyborg_: if you wanted to just install a binary and have full working system, the company that made the device can and is welecome to provide that.. but they are not.. so, you will need to do some work on your own
[21:25] <cyborg_> i dont have the time / patience to try forty different version just to get the same results all over again.  (im exagerating but  u catch my drift)
[21:25] <holstein> cyborg_: you can try a more populated channel, like #ubuntu ..or a mailing list
[21:25] <holstein> cyborg_: this will take both time and patience.. much of both
[21:27] <cyborg_> i guess what im saying there is no need for the troubleshooting steps if it worked on a fresh install of windows and is physically connected the same way
[21:27] <holstein> cyborg_: windows support is irrelevant
[21:28] <cyborg_> same hardware just different OS
[21:28] <holstein> cyborg_: the company paid a team of professionals to provide that support... and officially extend that to you.. they are welcome and able to provide the same support for linux.. but dont
[21:29] <holstein> cyborg_: take the machine, and try installing osx on it for example.. you would have a similar sistuation.. or android for that matter..its just not made with linux support in mind nor provided
[21:30] <holstein> the fact that window works on it doesnt mean linux will.. windows, stock, out of the box, doesnt work on the hardware either.. its the drivers the manufacturer provides that support it
[21:30] <cyborg_> if I were the original owner of the unit then they would give me the support. but...since i am not they will not provide me with support especially under linux
[21:31] <holstein> cyborg_: no, they wouldnt.. they dont provide support for linux.. not support not drivers
[21:31] <cyborg_> ok so is there a way to force a driver to load for a specific device
[21:31] <holstein> cyborg_: there is not such thing as support for that device in linux, though, linux is not preventing that.. but, there is little it can do to actively facilitate it
[21:31] <holstein> cyborg_: yes.. there is a way to "force a ddriver to load" . the manufacturer would create and support the driver, andit would work
[21:32] <holstein> cyborg_: what do you do in windows to force the drivers to load?
[21:33] <cyborg_> windows has a wizard for that
[21:33] <cyborg_> easy
[21:33] <holstein> cyborg_: ok.. load the wizard that the company provided for windows
[21:33] <cyborg_> or edit the registry
[21:33] <holstein> cyborg_: the company made that wizard for windows.. is there not one from them for linux?
[21:34] <holstein> if not, thats why you are having such an issue.. there is little windows is doing to support the device .. the manufacturer provides that
[21:34] <cyborg_> they didnt provide that and it is unavailable to unregistered users of their products
[21:34] <cyborg_> i am not the original/registered owner
[21:34] <holstein> cyborg_: no.. its unavailable in general, friend. they do not provide a tool for driver support in linux
[21:34] <holstein> cyborg_: linux is not supported
[21:35] <cyborg_> go4rdon was more optimistic than this
[21:36] <holstein> cyborg_: sure.. and im not saying it cant be supported.. im realistic.. there is not "driver loader" built into linux here.. nor is there one you can get from the company
[21:37] <holstein> this would be just like downloading or buying windows8 and trying to run it on that machine.. or osx.. its just not intended to run them, so the company doesnt provide drivers.. that doesnt mean you cant get it working, but you have to be willing to troubleshoot and spend time and effort
[21:38] <cyborg_> it is a normal computer!!!!!!
[21:38] <holstein> cyborg_: i never said anything to the contrary, friend
[21:39] <holstein> cyborg_: but, many "Normal computers" cant run linux.. because they do not have driver support from the manuracturer
[21:39] <cyborg_> windows NT, XP, 2000, VISTA, WIN7, Win8 can all run on it
[21:39] <holstein> cyborg_: great.. why is that?
[21:40] <holstein> cyborg_: did the company promise they would? by providing driver support?
[21:40] <cyborg_> ok fine
[21:40] <holstein> cyborg_: if they did, you can ask them to do the same for linux.. but, if not, you'll have to do some testing
[21:41] <cyborg_> i did some searching and found where someone was able to reassign a driver to a different device of a different kind to get more functionality using ubuntu.  so how much different is that from what i am trying to do other than
[21:42] <holstein> cyborg_: for that specific hardware?
[21:43] <cyborg_> holstein,  YES!!!  testing that is what I want to do. but I also want to test by binding drivers or editing scripts.  is there help for that
[21:43] <holstein> cyborg_: share what you have, friend..
[21:43] <cyborg_> holstein, http://lwn.net/Articles/143397/
[21:44] <holstein> cyborg_: where is it stated that this pertains to your hardware?
[21:44] <cyborg_> nowhere
[21:45] <cyborg_> however the pricipal should be the same
[21:45] <holstein> cyborg_: so, when i ask "for that specific hardware?: above, and you reply in caps with "YES!!!", its actually *not* for that specific hardware? then?
[21:45] <cyborg_> principal
[21:45] <holstein> cyborg_: the principil there is, there is something to support the device.. you dont have that here.. you havre *different* *hardware* .. and a much newer kernel, where that is not needed as much
[21:46] <cyborg_> 14.04lts 64bit
[21:46] <holstein> cyborg_: that link is for an older kernel, and for other hardware.. it has little relevance for your situation.. since you dont know what to bind, or if you can, or need to bind anything
[21:47] <holstein> cyborg_: i would be using the avlinux 32bit kernel.. and a 12.04 live, and 14.10 live.. as well as 14.04.. all 32bit, likely
[21:47] <holstein> live*
[21:47] <holstein> so that i can be nimble, and check hardware support..
[21:48] <holstein> that link is not for you..
[21:48] <holstein> "One new feature in the 2.6.13-rc3 kernel release, is the ability to bind and unbind drivers from devices manually from user space. Previously, the only way to disconnect a driver from a device was usually to unload the whole driver from memory, using rmmod."
[21:48] <holstein> you have no drivers to bind, or unbind.. you dont konw what , if anything, from the kernel supports the device yet
[21:48] <cyborg_> i need 64bit for the amount of ram that will be installed.  whats the use of fixing it on a platform that will not be used
[21:49] <holstein> cyborg_: it doesnt matter what you need, in the end, friend.. im talking about the steps you need to do to test..
[21:49] <holstein> cyborg_: none of this is a "Fix".. nothing is broken
[21:50] <cyborg_> okay
[21:50] <holstein> its not a shortcoming of linux or that system that linux doesnt run on it.. and its not broken.. its all working as advertised and promised
[21:52] <cyborg_> so if they intentionally made it invisible to linux but not to windows
[21:53] <cyborg_> is there a way to bind the snd-usb-midi driver to it
[21:54] <holstein> cyborg_: sure.. where is the driver that the manufacturer provided?
[21:54] <holstein> cyborg_: or the specs that allow us to communicate with the device they have made?
[21:54] <holstein> cyborg_: they are not intentionally blocking it from linux friend.. they are just not providing support for linux.. they never promised they would
[21:57] <cyborg_> i need help binding a driver to a device.
[21:58] <cyborg_> there no windows drivers available
[21:58] <cyborg_> it is class compliant but linux doesnt see it
[22:00] <holstein> if its class compliant, it should just work
[22:01] <cyborg_> but has the wrong class listed