[02:08] okay [02:08] len-dt: its like very static? [03:49] len-dt: whats the best way to record guitar? [03:49] Whatever gets the sound you want [03:50] Last bit I did, I used a vocal mic (at 2020) to record an acoustic, and ran the electric direct. [03:51] I added effects to the guitars after I had most of my tracks for mixdown. [03:52] That can be a bit limiting because one plays different depending on how the sound is [03:53] But it does give a nice clean track that any effect will work on. [03:54] FloatingGoat, When I say direct in... that means through a preamp... not direct to sound card. [03:55] The pre amp I used is the one in a Mackie 1604 mixer. [03:56] Still, lots of records made with an SM57 in front of the guitar amp too. [03:57] Depends what kind of sound you want. [03:58] Use your ears... make 5 or 10 tracks doing it every way you can think and keep what sounds best for the song you are doing. [03:59] If I use more than one guitar track I try to do each one different. [04:00] Use different guitars, mics, amps, effects etc. [04:00] okay [04:01] i pretty much did it the way you said [04:01] i recorded my acoustic through [04:01] my mic and the electric through the not mic [04:01] I mean like [04:01] if its a two minute song [04:01] should I play guitar for two minutes and thats the track? [04:02] the same thing for two minutes? [04:02] Whatever sounds right for the style of music and gets what the song is trying to say across. [04:02] Music is about communication. [04:04] Take Neil Young... Old Man Vs Hey Hey, My My [04:05] They are saying two completely different things and are two different styles. [04:10] yeah? [04:14] Hey music is art, some paint with oils and others watercolours.... and some with film [04:15] There is no such thing as a set of rules... just do this and it will work... unless you are doing vocal gymnastics for Idol [04:17] What do you do on stage? start with that. [04:18] Then listen... maybe you will get an idea to change something... so try it. If it sounds better keep it. Don't be afraid to try things. [04:20] The nice thing about a computer tracker is that you can have lots of tracks, mute the ones you aren't using and they won't load the computer down [04:24] Listen with your eyes closed, Does every sound support the vocal or the instrument solo? Or does something distract? [04:24] There is nothing wrong with recording something and deciding not to use it later. [05:31] yeah i guess [05:31] it just takes time and effert [07:25] VLC is giving me flickering. very minute flashes... [08:36] how can i play video files in vlc [10:15] http://www.linuxdsp.co.uk [10:21] Hi I am trying to make puredata work with Jack with no luck. Every time I select "jack" in puredata, puedata locks up completely. [10:22] jablo: Did you try starting jack first? [10:23] And if that still doesn't work, try this in a terminal (after starting jack): pd -jack [10:24] You can even do: pd -jack channels 2 -alsamidi [10:24] I start jack with qjackctl fist, yes. I'll try your command lines, need to do some "kill"s first though. [10:24] Ah, sorry. -channels [10:27] 1) Start jack; 2) pd -jack -channels 2 -alsamidi; 3) Pureadta window shows up with a big "Audio Error". [10:28] Still - setting dsp and making a small "osc~ 440" --> "dac~" gives sound. [10:28] So I'd say - thanks for your help. [10:28] Apparently I need to start puredata from the command line. [10:31] jablo: Did you make sure to choose number of inputs and outputs when choosing jack from the pd menu? [10:32] jablo: Also, don't forget that even if you have a low latency with jack, you'll need to set pd's latency low too, for the non-audio operation (such as midi) [10:32] Yes and no - puredata locks up as it displays the jack audio configuration menu [10:32] jablo: Which OS and release is this? [10:34] Ubuntu Studio, Ubuntu 12.04.1 LTS, uname 3.2.0-23-lowlatency [10:34] x86_64 [10:36] jablo: You might like to try pd-extended instead. https://launchpad.net/~eighthave/+archive/pd-extended [10:36] ICE1712 - Hoontech SoundTrack Audio DSP24 [10:36] Ok I'll try and look at that. [10:36] Those are older, but should work [10:36] There's also the beta of pd-extended.. [10:37] I'm still trying to get the pd patch you or (who was it?) sent me the other day, to detect sound and trigger a bass drum from hydrogen [10:37] jablo: Ah, yeah. That was me [10:38] Well, pd vanilla should do that well enough. [10:38] There's something weird about the jack interface only when starting it. [10:39] Since I got sound out of puredata through jack when starting it on the command ... [10:39] pd-extended includes loads of extra libs, as well as having a more pleasant look [10:40] jablo: You need to make sure alsamidi is enabled. If you don't see pd in qjackctl alsa midi tab, enable the alsamidi from the pd menu [10:40] When running the patch, you want to have dsp on, and needless to say, the audio and midi ports properly connected [10:41] After making sure it works, you'll want to reduce latency as well [10:41] When I load the patch - seems that puredata locks up again. The window with the flow is unresponsive, can't move things around. [10:41] Cant' open puredata audio preferences [10:41] so - something isn't working well [10:42] jackd latency is 2.9ms [10:42] 64 sample blocks [10:42] Try reducing jack latency [10:42] Just for testing [10:42] The patch has a auto dsp on [10:42] After starting pd, before opening the patch, try turning dsp opn [10:43] killling things and retrying... brb [10:45] just starting puredata (on the command line, with jack aleady started), puredata continuously spits out: [10:45] damn cutn'paste not working [10:46] watchdog: signaling pd... [10:46] Jack: JackClient::ClientNotify ref = 3 name = pure_data_0 notify = 3 [10:46] Jack: JackClient::kXRunCallback [10:46] Jack: JackClient::ClientNotify ref = 3 name = pure_data_0 notify = 3 [10:46] Jack: JackClient::kXRunCallback [10:46] What's jacks latency at now? [10:46] still 2.9ms [10:47] Try reducing it just for seeing if pd will start. Also, did you set latency before in pd settings menu? [10:47] If not, all is fine [10:47] I tuned on dsp, then load patch. Puredata locks up before the patch is loaded. [10:48] yes i checked that pd latency (block size) is 64 like jack [10:48] You can set blocksize also from the commandline. pd --help gives you an idea [10:49] I'd try with a much larger blocksize to see if it will start [10:49] On both jack and pd [10:49] ok. [10:51] I run pd with 64 frames myself, but I don't use vanilla pd [10:51] 512 - seems to be working a bit better [10:52] Afte the patch loads, shouldn't the window be alive - ie, I should be able to highlight, click and move the blocks aoround? [10:52] You need to be in edit mode for that [10:52] YES! [10:52] Ctrl + E [10:52] I am SO new to puredata. Hate it. I'm a programme, not a mouser :) [10:53] *programmer [10:53] Hmm. I don't see puredata in jacks midi pane. [10:54] There's no jack midi for pd [10:54] So, you'll find it in alsa midi [10:54] If you enabled alsamidi, that is [10:54] Ok, let me be precise here: I see puredata in jack "audio" pane, but not in jack "MIDI" pane nor in jack ALSA pane. [10:55] Woups, now it's there [10:55] Ahha. So - I should be ready to hook up Ardour --> puredata --> hydrogen. [10:56] And get a decent drum bass sound whenever my badly recorded bass drum sounds. [10:56] With 512 sample blocks, probably a bit time skewed - but that's for later. [10:56] The [bonk~] object works pretty well without any arguments, but it can be tuned. To see help for objects, just right-click and choose help [10:57] Thanks. Yes. I'll get some tea, play around with this and possibly be back. [10:57] You are very helpful. [10:57] np [10:58] Other question - are you guys using ubuntu studio? and using -generic, -lowlatency or -realtime kernels? [10:58] I use -lowlatency [10:59] k [10:59] Haven't used an -rt since Ubuntu Natty [10:59] -generic was completely unusable to me. even with i think 1024 block i got more noise than sound [11:00] I was on puredyne 9.10, based on Ubuntu 9.10, which had an -rt kernel in the main repo. That one was pretty ok. Since 11.04 I started using -lowlatency instead. Those kernels are actually a bit better on performance [11:01] I mean, the ones on 11.04 and perhaps 11.10 [11:01] That's what I read too. [11:01] Here's a howto I made on building an older -lowlatency kernel on a newer release https://help.ubuntu.com/community/BuildOldLowlatency [11:03] I haven't yet prepared a production system for my pd patches, which are quite extensive and used with our band. I will probably want to try the older kernel [11:03] I only tried it quickly when I made the howto, and it seemed more responsive [11:03] I just grabbed a -lowlatency i had in synaptic package manager [11:03] Since 12.04, there's a lowlatency in the main repo [11:04] But, we were testing kernels already a year earlier [11:04] Ah. [11:04] 2.6.37 was very nice, but 2.6.38 was the first to support the rtirq script [11:05] Another piece of -rt that has gotten into the main kernel source [11:06] HEY, puredata is doing something to my sound. [11:07] theree's a "velocity" thingie that changes values in step with the music! [11:08] Not sure what you mean [11:09] I connected ardour (bass durm track) to the puredata patch. And started playback in ardour. [11:09] The noteout is given a message: note 30, velocity $1. Velocity is based on the volume that [bonk~] object [11:09] Missing words there, but you get the point [11:09] Yes that's what I figured. So, since the velocity object moves, puredaata hears the sound, pocesses it... DOES something. [11:09] hooking up to hydrogen now. [11:09] It doesn't do anything with the sound. It only outputs midi [11:10] There's no audio out on the patch [11:10] Nono fine, I want a midi signal into hydrogen. [11:10] Yes. There'a a small blinking "midi in" thing now in hydrogen... now... sound... [11:11] AND it's actually hooked up to the bass drum... wow. [11:14] Amazing. [11:14] Hydrogen is playing the bass drum now. [11:14] Sound awful though [11:15] But that's the hydrogen drum set AND filtering in bonk~. Wow wow wow. [11:17] jablo: Another thing you can do, if you want to be more advanced, is used pd as the sample player [11:17] But, that'll make you need to learn how to make pd patches [11:18] You get a bit more control, but I gather that is probably not needed in your case [11:20] A gate on the drum track has fixed this for now. [11:21] jablo: [bonk~] has more options in it's right outlet. You might want to look into that. [11:21] Amazing - now I have the sound of a hydogen bass drum synchronously playing with our recorded track [11:22] Thanks - I'll definitely look into this. This is a fabbatastic proof of concept! [11:23] Going to use this trick and make an updated set of music-minus-one mixes for the band. Wee hee :-D [11:26] bonk~ help says something about it working on 256 sound samples at a time. So probably one sholdn't set jack block size lower thatn 256 [11:45] jablo: Nah, it works on lower setting too [11:45] As I said, I use it at 64 [11:46] pd's internal block size is 64 by default, I believe. This may not be related to audio latency [11:46] Try reducing latency using the -audiobuf in ms instead [11:47] Or, data latency, not audio latency. Audio latency is controlled by jack [12:18] Ailo, I have one more queestion. What I have now with the bonk~ puredata ptach is very useful. It does, however, at times generate some extra spurious notes (bleeding from snare drum into bass drum mike). So I would like it to limit the number of notes it outputs. [12:18] and threshold setting comes to mind. But I don't understand the help - do I add a box called threshold, or ... ? [12:24] jablo: You either create the object with arguments, like [object arg1 arg2] [12:24] jablo: Or, you give it messages, using the message object. [12:25] jablo: Adding a message is done either from the edit menu, or Ctrl + 2 [12:25] You can type whatever you want in a message, and that will be outputted from its outlet to anything its connected to, when you click it [12:26] so if i add messgae, and type "thresh 2.5 5" that should do something to bonk~ ? [12:26] oh yes, the help displays the same icon as message. oh. [12:26] Yea [12:26] (as I said: I'm a pogrammer, not a mouser/guie'er. sry.) [12:28] Thanks. [12:29] In the patch you have, there were two messages. One for the [noteout] object, and one to start pd. Anything after ";" in a message is sent somewhere, in this case "pd". The first word in the list identifies where it's sent [12:29] One to start dsp, sorry [12:29] Ah, i was wondering what the "loadbang" --> "; pd dsp 1" was for. [12:30] There are the [send] and [receive] objects. You can use those too [12:31] I must say - it's really working extremely well. Just using you patch and some fiddling with the low pass + aggressive gating on the sound track, hydrogen does exactly what it should, and feeding back into ardour all sound samples are nicely lined up. Timing is perfect. [12:31] I use the [bonk~] object with a couple of trigger pads. Beats the hell out of any midi drum I've tried [12:32] Ha. I have never really combined computer + music (my 2 great hobbies, and computers my work too). [12:33] I can see where you could do some really neat things... controlling... yeah, well, anything - just from your music. [12:33] [clip 0 127] just makes sure the output from [bonk~] is within the midi velocity range. Variables in messages, like [30 $1( will be filled with whatever you push it. [12:34] It doesn't take a lot of time to whip something up on pd, creating both midi, audio and gui interfaces [12:35] jablo: If you want to find out more, I suggest looking into the manual in the help browser [12:36] Well, the part that's called "Pure Data" in the manual, is what I mean [12:37] in the browser, not the manual. Jeez [12:37] Anyway, I'm going cyclink. First day with no wind for ages [12:38] have a nice trip. [12:42] jablo: One good pointer is to use the [print] object a lot. Connect anything to print, and you see the output in the console [12:42] Ok, going now [18:27] hello :D [18:27] have troubles with jack and D-Bus [18:28] cannot connect to socket, can't find some useful infos on the web [18:33] pandoras: Standard Ubuntu Studio install? [18:33] If you started jack, and it failed before, it could be running. The default setting for qjackctl is to start jackdbus [18:33] To kill jackdbus, do: killall -9 jackdbus [18:33] alio, yes [18:34] mom [18:34] Sometimes stopping jack does not stop jack. When that happens, you have to kill jack in order to start it again [18:35] This is a bug with qjackctl and jackdbus on Ubuntu 12.04 [18:35] ok, ps -e | grep jack list anyway some running processes [18:36] so, nothing is running, try again [18:37] doesn't work [18:37] If that didn't help, try also restarting pulseaudio. I usually just kill it, and it respawns [18:37] pandoras: Make sure qjackctl is set to use a device you know works [18:38] So, I do: killall -9 jackdbus, killall pulseaudio. And then try jack again. [18:38] pandoras: What kind of device are you using with jack? [18:39] ok, now its running [18:40] the standart-device was (default) and not hw:2 [18:40] pandoras: Every time you boot, the devices might shift order [18:40] im using a PCI-Terrasoniq TS-22 Studio-card [18:40] ailo, should only happen, when a new device plugged in [18:40] pandoras: No [18:41] The devices are not listed in order [18:41] The order can change at each boot [18:41] pandoras: If you want to make sure qjackctl is always set to use the card you like, use the name, instead of the number. [18:42] If I do: cat /proc/asound/cards [18:42] i had a roommate, and his xsever was not working anymore, because he has set the fix BUS-ID for the card. [18:42] This is my device: 2 [M66 ]: ICE1712 - M Audio Delta 66 [18:42] In qjackctl, I write: hw:M66 [18:42] Instead of hw:2 [18:43] 2 [PCI ]: ICE1724 - Terrasoniq TS22 PCI [18:43] Terrasoniq TS22 PCI at 0xec00, irq 18 [18:43] that means only type "PCI" as setting? [18:43] hw:PCI [18:44] Try that. Should work. You type it in manually [18:44] thx, very useful to know [18:44] i figured out how the midi controlers of my keyboard with Ardour works :D [18:46] do you know if yoshimi does support midi-mapping-controller? [18:46] I've never tried using midi devices to control ardour, but I assume it's mostly about assigning the right midi ctrl value, and channel to whatever you want to control [18:47] Never heard of midi-mapping-controller [18:47] i mean put a midi controller to any parameter [18:48] I think qmidiroute might be helpful, if you can't create a template, or save settings in the program you want to use [18:48] zynAdd/Yoshimi is so amazing and kickass [18:48] sad that important features are missing [19:41] ailo, kthxbye