[04:08] <VelhoP4> hello frie3nds!
[04:09] <VelhoP4> Im running UbuntuStudio on a live DVD, trying to connect FA-66. It has ffado pre/installed, but what should I do next, to make the system recognise this sound board_
[04:09] <VelhoP4> ?
[04:17] <holstein> VelhoP4: literaly nothing
[04:17] <holstein> VelhoP4: have you learned to set jack up on *any* device?
[04:17] <holstein> have you looked at..
[04:17] <holstein> !proaudio
[04:27] <VelhoP4> holstein, Ive read it and follow it
[04:27] <VelhoP4> still no sucess >*
[04:28] <holstein> VelhoP4: so, you have *not* setup jack with the internal audio device? or *any* device
[04:28] <holstein> VelhoP4: i suggest, unplug the edirol, and set jack up with the internal device
[04:28] <holstein> otherwise, in qjackctl, you will see the driver "firewire" under the driver drop down in the "setup" area
[04:28] <holstein> you select the firewire driver, and click "start"
[04:30] <VelhoP4> holstein, and whats the interface? default?
[04:31] <holstein> VelhoP4: for what?
[04:31] <VelhoP4> i also have plughw0 and hw0
[04:31] <holstein> VelhoP4: using the firewire driver?
[04:31] <holstein> VelhoP4: i'll *literally* try them all.. since there are just a few, and the labels can be wrong
[04:31] <VelhoP4> holstein, for the firewire driver. for edirol fa-66
[04:31] <holstein> VelhoP4: you only have the one firewire device, so, "default" should be it
[04:32] <holstein> VelhoP4: but, as i said before, you can have issues with the chipset
[04:32] <holstein> VelhoP4: you havent stated your firewire chipset
[04:32] <VelhoP4> holstein, how to resolve the chipset problem?
[04:32] <holstein> VelhoP4: yo udont
[04:32] <holstein> VelhoP4: but, do you have a chipset problem?
[04:33] <holstein> VelhoP4: the "chipset problem" is, the chipset manufacturer doesnt support linux.. you cant make them support linux
[04:33] <holstein> VelhoP4: what chipset do you have?
[04:33] <holstein> VelhoP4: you can run lspci and share the output
[04:33] <holstein> !paste
[04:34] <VelhoP4> holstein, i dont know. how can i discover the answer to that question?
[04:34] <cfhowlett> VelhoP4, at the purchase point, you have to ensure you've selected a linux-friendly hardware.  after purchase hacking is a lot more painful than pre-purchase planning
[04:34] <holstein> VelhoP4: by opening a terminal and typing the text from above.. "lspci", then, you press the enter key on your keyboard, and you can copy paste that into a pastebin
[04:35] <VelhoP4> holstein, thank you so much for your patience
[04:36] <holstein> VelhoP4: sure.. we're here :)
[04:36] <holstein> no problem
[04:38] <VelhoP4> http://paste.ubuntu.com/9352332/
[04:39] <holstein> VelhoP4: i dont see it listed..
[04:39] <holstein> VelhoP4: not very hopeful.. do you see it? cfhowlett ?
[04:40] <VelhoP4> holstein, im running ubu7ntustudio on a live dvd. dont knoiw if that matters
[04:41] <holstein> VelhoP4: nope
[04:41] <holstein> VelhoP4: are you sure the firewire is enabled in the bios?
[04:42] <VelhoP4> cfhowlett, right now I have this Edirol fa-66 and would like to use it with linux, if possible. if i cant do it, iIll considering buying a supported sound card. But, from what I read, this sound card is full supported
[04:42] <VelhoP4> holstein, not sure
[04:43] <VelhoP4> holstein, the bios, you mean BEFORE the OS?
[04:43] <holstein> VelhoP4: correct.. the machine will have to have the hardware enabled
[04:43] <VelhoP4> or is there any bios inside linux?
[04:43] <VelhoP4> holstein, well, it works with windows
[04:44] <holstein> VelhoP4: ok.. but, you can confirm that its on, by checking again in windows, to be sure, or looking in the bios settings
[04:45] <holstein> VelhoP4: *if* the firewire hardware is not present, and supporting linux, then the firewire device wont work
[04:45] <holstein> VelhoP4: are you using an 14.04 live CD?
[04:50] <holstein> this, among other things, is why i suggest *not* taking all this on at once
[04:50] <holstein> i say, unhook the firewire audio device, and get jack running on the internal device
[04:54] <VelhoP4> holstein, that, i get working!
[04:55] <holstein> VelhoP4: im sorry i dont clearly understand what you are saying
[04:55] <holstein> VelhoP4: are you able to use jack and configure it to run on the internal audio device?
[04:55] <holstein> VelhoP4: can you, for example, route something like yoshimi over jack on the internal audio device?
[05:01] <VelhoP4> holstein, im rooting a Calf plugin after Ardour, wich is reproducing a track. and its working with my internal sound board. FA-66 is connected, but dont know how to make it work
[05:03] <holstein> VelhoP4: and you *cant* make it work, if your firewire device doesnt show up
[05:03] <holstein> VelhoP4: if your hardware doenst promise you that it will work with linux, then you can have a challenging time
[05:03] <holstein> what would i do? take the device to a machine with a supported texas instruments firewire chipset, boot the live iso, test the edirol
[05:04] <holstein> VelhoP4: i ask again, are you using ubuntustudio 14.04 live?
[05:04] <holstein> VelhoP4: i suggest 14.04 and *not* 14.10..
[05:05] <VelhoP4> holstein, ubuntustudio 14.04 live
[05:06] <holstein> VelhoP4: what im saying is, since you *dont* see your firewire device when you run "lspci", then, you will *never* see *any* firewire devices..
[05:06] <VelhoP4> holstein, the problem is there i dont know were to find the firewire
[05:06] <holstein> VelhoP4: sure. its *not* there, friend
[05:06] <holstein> VelhoP4: it doesnt have to work with linux.. you were not promised that it would
[05:06] <holstein> VelhoP4: but, that will be necessary *before* *any* firewire devices show up in linux for you
[05:07] <VelhoP4> holstein, ah, get it! but what does full support means, then?
[05:07] <holstein> VelhoP4: we are *not* talking about the edirol
[05:07] <holstein> VelhoP4: as i said, you can literally unhook it
[05:07] <holstein> VelhoP4: we are talking about the *actual* firewire on the device
[05:07] <holstein> VelhoP4: on your compupter
[05:07] <holstein> computer*
[05:08] <holstein> VelhoP4: i you have a firewire hard drive, for example, you can plug that in, and it also, will *not* work.. since, the firewire device on your computer is not supporting linux
[05:08] <holstein> VelhoP4: this is a prerequisite to the edirol, or *any* firewire device working
[05:09] <holstein> VelhoP4: it would be like, taking a USB stick and plugging it in in windows and *not* having the USB drivers installed for the motherboard USB hub
[05:09] <holstein> VelhoP4: the USB stick in that scenario would *not* work, but that is not related to the USB stick
[05:10] <VelhoP4> holstein, hmm. Im using a PCM cia - i think thats whats called - to connect the firewire cable
[05:10] <holstein> VelhoP4: ok
[05:10] <VelhoP4> holstein, i dont have a firewire input built in my laptop
[05:10] <holstein> VelhoP4: when you bought the thing, it *never* stated "linux support".. so, it doesnt have to work with linux.. they never promised you it would
[05:10] <VelhoP4> maybe thats why liunux cant see the soundboard?
[05:10] <holstein> VelhoP4: no.. that *is* *exactly* *why*
[05:10] <holstein> VelhoP4: thats what im saying, friend
[05:11] <holstein> VelhoP4: if you mean, the edirol, when you say "sound board", then, *yes*.. thats what i mean
[05:11] <VelhoP4> holstein, so Edirol FA-66 works under linux or not?
[05:11] <holstein> VelhoP4: the firewire PCI card will *need* to work *before* *any* firewire will work
[05:11] <holstein> VelhoP4: i am not edirol or edirol support
[05:11] <holstein> VelhoP4: ubuntustudio is doing nothing to prevent that edriol from working with it
[05:12] <holstein> VelhoP4: will it work? i dont have one here to say, first hand
[05:12] <holstein> VelhoP4: i looked at the official ffado site and linked to you where they state the edirol is fully supported
[05:12] <holstein> VelhoP4: you *cant* confirm that, since, you dont have firewire on your computer that supports linux
[05:12] <VelhoP4> holstein, ah!
[05:12] <holstein> VelhoP4: step one, as i said, get firewire that works in linux
[05:13] <holstein> VelhoP4: i have several texas instrument chipsets for just that occasion
[05:13] <VelhoP4> holstein, got it!!
[05:13] <holstein> VelhoP4: as i also said, instead of buying that, go to a machine with a firewire chipset and test the edirol, first hand
[05:13] <holstein> *if* it works, you can get a texas instruments chipset
[05:14] <VelhoP4> holstein, im using a dual boot machine, fa-66 works fine on windows 7
[05:14] <holstein> VelhoP4: sure, and that doesnt mean *anything*
[05:15] <holstein> VelhoP4: when you bought all that hardware, you *were* promised driver support for windows..
[05:15] <holstein> VelhoP4: all that means is, the hardware is likely functional..
[05:15] <holstein> VelhoP4: if you dont see the firewire chip in lspci, then you will *never* get *any* firewire devices in linux on that machine
[05:16] <holstein> VelhoP4: details can help me help you
[05:16] <VelhoP4> holstein, since this adventure is takingt me more time then what ive expected, i will install ubuntustudio, and play with if through my laptop internal sound board, that works fine
[05:16] <holstein> VelhoP4: what pci firewire card do you have?
[05:16] <VelhoP4> holstein, let me check
[05:18] <VelhoP4> holstein, this one http://www.lindy.co.uk/components-tools-c7/add-on-cards-c308/firewire-c311/firewire-card-2-port-expresscard-34-p3339
[05:18] <holstein> VelhoP4: so, you can see Chipset: Texas Instruments XIO2200A
[05:19] <holstein> VelhoP4: they are typically well supported
[05:19] <VelhoP4> holstein, <3
[05:19] <holstein> VelhoP4: i say, try booting the live CD, with the firewire card *out*.. and put it in after boot
[05:19] <holstein> pull it out and put it back in right now, and try "lspci" again
[05:20] <VelhoP4> gonna do that right now, just a moment
[05:22] <VelhoP4> holstein, you mean reboot everything and then do the lspci?
[05:22] <holstein> VelhoP4: i mean, *literally* experiementing in every way
[05:22] <holstein> VelhoP4: i would pull the card *right* *Now*, and put it back in..
[05:22] <holstein> leaving it out for about 20 seconds or so
[05:22] <holstein> then, i would run lscpi..
[05:23] <holstein> if i dont see it, i reboot with the card out. and wait til the machine is booted, and put it back in after its booted, and run lspci
[05:23] <holstein> i want to see the device listing a texas instrument chipset in a terminal in lspci
[05:24] <VelhoP4> holstein, so, i must find the text TEXAS INSTRUMENT with the lspci?
[05:25] <holstein> VelhoP4: friend.. its like this. that device will need to work in linux before anything you plug into it will
[05:25] <holstein> VelhoP4: its that simple.. now, making that happen can take *any* amount of fiddling around..
[05:26] <holstein> VelhoP4: a team of professionals worked for what could have been years, making sure all of your hardware worked out of the box and well in windows.. you are taking that responsibility on yourself when running linux, since, no one has promised you linux support
[05:26] <VelhoP4> holstein, got it!
[05:26] <holstein> VelhoP4: what do i do? i literally try *everthing*
[05:27] <VelhoP4> holstein, i can be patient. i really want edoril fa/66 to work on my linux system
[05:27] <holstein> boot with out the thing.. boot with the thing.. take the thing out.. try another thing to isolate if its the thing or not that is causing the issure, or if its the other thing
[05:27] <VelhoP4> holstein, yes, i understand
[05:27] <holstein> VelhoP4: again, we are not talking about the edirol, at all
[05:28] <holstein> im talking about the pciexpress card
[05:28] <VelhoP4> holstein, yes, we are talking about the pcmcia firewire adapter
[05:28] <VelhoP4> holstein, im newbie, but im not that dumb, lol
[05:29] <VelhoP4> holstein, I dont know how to thank you, you re being so supportive
[05:29] <holstein> im not saying you are dumb.. im just clarifying..
[05:29] <VelhoP4> thank you so much for not leaving me alone, and giving me your hand on this
[05:30] <VelhoP4> holstein, thank you for all you patience, and making an efford to understand my awfull english when Im sleepy
[05:31] <holstein> sure. but, i do need to run.. you can try #opensourcemusicians or #xubuntu #ubuntu for the expresscard support..
[05:31] <holstein> cheers!
[05:31] <holstein> and good luck...
[05:31] <VelhoP4> holstein, cheers!!
[19:50] <VelhoP4> hello folks! ive just installed UbuntuStudio in my dualboot laptop. I noticed there are Extra Applications in each menu. were can I find detail info about whats included?
[19:51] <VelhoP4> included with the Extra Applications, I mean
[19:51] <holstein> VelhoP4: pretty much any package manager.. or you can search online
[19:51] <holstein> i like synaptic for a GUI Package manager..
[19:51] <delt> VelhoP4: i just type in a terminal: apt-cache search [package name]
[19:51] <holstein> also, here..
[19:52] <VelhoP4> holstein, Ive searched online and found no info. thats why im asking here
[19:52] <holstein> !info yoshimi
[19:52] <delt> !info zynaddsubfx
[19:52] <delt> !info zynaddsubfx-dssi
[19:52] <holstein> VelhoP4: sure.. and we are doing our best to help you.. try one of the few suggestions above, or tell us how what you searched online failed...
[19:54] <VelhoP4> holstein, thanks! I thi8nk im getting it
[19:55] <delt> this is weird.... on this machine qjackctl doesn't show a menu from the system tray / notification area.... it just shows a small line, like the rest of the menu isn't appearing....
[19:56] <holstein> delt: i would check the settings and make sure i have it set to be shown there, then, i would try as a different user, and try launching from the terminal to see error messages..
[19:56] <VelhoP4> these Extra Apps are just additional packages I can get from synaptic
[19:56] <holstein> VelhoP4: i dont know what you are asking about..
[19:57] <delt> http://www.deimos.ca/miscjunk/qjackctl-glitch.png
[19:57] <holstein> VelhoP4: you can ask about any particular application by name
[19:57] <delt> holstein: it looks like this ---> http://www.deimos.ca/miscjunk/qjackctl-glitch.png
[19:57] <holstein> delt: that looks as i would expect.. expecially if i had resized my panel
[19:57] <VelhoP4> holstein, lol, nevermind, I got the answer I needed
[19:58] <delt> uh? the little grey line is at the outside of the panel
[19:58] <holstein> ok
[19:58] <VelhoP4> !info ardour
[19:58] <holstein> delt: just keep configuring,and trying the suggestions above
[19:59] <holstein> delt: i'll find that compositing can effect that sort of UI element
[19:59] <VelhoP4> !info ardour3
[19:59] <holstein> i mean,for me, 'if it aint broke', i dont fix it
[19:59] <delt> holstein: that little grey line appears instead of the menu
[19:59] <holstein> VelhoP4: you can query the bot, as well
[19:59] <VelhoP4> holstein, how so?
[19:59] <holstein> delt: ok.. so, any mesages when launching from the terminal? does it happen as another user?
[20:00] <delt> also, quick suggestion for the ubuntustudio distribution: set the default xfce font to "Ubuntu", it looks really nice :D
[20:00] <holstein> VelhoP4: i use "/q ubottu "
[20:00] <delt> anyway, back to this qjackctl thing....
[20:00] <delt> holstein: my laptop is running the exact same setup, with no problems.
[20:00] <holstein> delt: you would file a wishlist bug, or email the dev list
[20:00] <holstein> delt: sure.. so,are we talking about the laptop?
[20:00] <delt> nope.. this bug appears on the desktop machine
[20:01] <delt> disabling compositing doesn't seem to fix the problem...
[20:01] <holstein> delt: the suggestions above are for the *same* machine.. start qjackctl from the terminal and see error messages,and try as another user, to see where the issue is
[20:01] <VelhoP4> holstein, that command doesnt seem to work on xchat... nothing appears
[20:01] <holstein> delt: sure.. you are assuming a few things. that, its a bug, and that its broken
[20:01] <holstein> VelhoP4: you can typically right click on the nick and query it, or try "/query ubottu "
[20:02] <holstein> https://toxin.jottit.com/xchat_help_commands
[20:02] <delt> holstein: starting qjackctl from a terminal, no output ... compositing disabled in window manager, still getting just a little grey line instead of the menu.
[20:02] <holstein> delt: and, as another user?
[20:02] <delt> it's not such a HUGE issue, since running qjackctl again pops up the window.
[20:03] <delt> that's what i'm going to try next.
[20:03] <VelhoP4> holstein, cool! thanks
[20:04] <vlt> Hello. It’s 2014 – so what do I want to use for basic non linear video editing? I have several different sources (1280p/720p h.264, DV ...), want to arrange them on tracks on the timeline, create (sub)titles and edit audio levels. I tried openshot but I haven’t figured out how to move a whole bunch of clips around. Any idea what to use?
[20:04] <delt> ok, i'm in the guest account... trying now
[20:05] <delt> enabling system tray icon in qjackctl
[20:05] <holstein> vlt: i like kdenlive, but, it realy just depends on what fits your needs.. i would try kden and the cinellera ppa.. and lightworks is a commercial option
[20:05] <delt> same bug happens: just the little grey line.
[20:05] <holstein> pitivi
[20:06] <holstein> delt: sure. but, as you say, its not happening on the other box, so, why assume its a bug?
[20:06] <delt> compositing on or off, makes no difference
[20:06] <holstein> delt: i mean, its an issue, correct? a bug would be something i can reproduce, and something you can on your other machine
[20:07] <delt> ok, so we know the problem isn't caused by something in my ~
[20:07] <holstein> delt: what would i do? look for and apply updates.. look at my sources for relevant PPAs such as kxstudio ones.. i would then look for a bug, and file one, and try and get someone to confirm it, after i confirm it on my other machine
[20:07] <vlt> holstein: Thank you. I’ll try kdenlive first.
[20:07] <delt> vlt: also check out cinelerra, iirc it's not in the ubuntu repos, you have to add their ppa
[20:08] <holstein> http://www.techdrivein.com/2013/09/top-5-video-editors-for-ubuntu-linux.html
[20:08] <delt> holstein: maybe uninstall and reinstall qjackctl? 2 sec i'll just log back into my normal account
[20:08] <holstein> thats the cinelerra ppa i referenced.. https://launchpad.net/~cinelerra-ppa/+archive/ubuntu/ppa
[20:08] <holstein> delt: i already said what i would do..
[20:09] <holstein> that could be a fix.. but, you really dont know what the issue is yet
[20:11] <vlt> delt: Thanks.
[20:24] <delt> holstein: you mentioned resizing the panel might cause this problem... how would that be?
[20:25] <holstein> delt: when i misunderstood the issue
[20:26] <delt> oh....
[20:42] <VelhoP4> Is there any advantage on installing UbuntuStudio 64 vs 32 bit? I just discovered one disadvantage: I cant install the package dssi-vst
[20:43] <holstein> VelhoP4: you cant do what? why?
[20:44] <VelhoP4> holstein, !info dssi-vst
[20:44] <VelhoP4> !info dssi-vst
[20:45] <VelhoP4> holstein, -  (Only available for i386)
[20:45] <holstein> VelhoP4: you can run 32 bit apps on 64bit
[20:45] <holstein> VelhoP4: you have to stop saying "cant" and assuming.. and just ask how..
[20:46] <holstein> http://howtoubuntu.org/how-to-install-a-32bit-program-in-64bit-ubuntu for example
[20:46] <holstein> these days, if a machine can to 64bit, i install 64bit on it.. if it has 4gb's of ram..
[20:48] <holstein> now, hosting windows vst's in 64bit may be a problem, but, thats not related to linux at all
[20:48] <holstein> anyone can make *anything* they want for linux.. its all open
[20:48] <holstein> if they dont, then, you have to do your own support
[20:49] <holstein> if windows VST's were a deal breaker for me, id run windows.. if i wanted to try them in linux, id use 32bit