Re: [ubuntu-studio-users] Questions about production
Hi all maybe a bit off topic, but i'm interested in getting some advice on a 'simple cheap' USB audio device any tips? my requirements are these : - 1 stereo output (or 2 mono), ideally 2x 6.3mm mono jack (or cinch) - preferably with cable (so not the 'dongle' type of audio device) - inputs : dont really care, but 2x 6.3mm jack inputs would be nice - cost : really low ;-) - latency : approx 10ms will do - supported in linux OOTB maybe something like the behringer ucg 102? ( http://www.behringer.com/EN/Products/UCG102.aspx) all tips are welcome grtz Thijs 2014-07-29 9:20 GMT+02:00 Shubham Mishra mishrashubham2...@gmail.com: OH!, i forgot to mention my opinion of USB mic's.. personally, i think they are great if they meet your needs.. they are one trick pony uni-tasking devices.. for example, you may be able to get a nice USB audio device and a nice actual mic for not much more cost than a decent USB mic, and those 2 things are *much* more versatile.. if you have a USB mic, for example, and you later decide to purchase a nicer preamp, you cant use it.. the USB audio device can also provide a nice instrument input, and be used as a fully functioning sound card.. so, for my money, i consider a USB mic to be a little bit of a wasted investment, unless the user is *only* doing something like a podcast, or only speech or one channel at a time with a mic.. good luck Thanks for the advice. Yeah, getting a dedicated audio interface sounds promising. Like you said, the hardware needs to support linux properly. Normally that wouldn't be an issue since I can easily find out from the internet which interfaces are linux compatible, getting them is more of a problem. E-commerce where I live, is a mess; Amazon US has everything though, but shipping will cost me a fortune. So that just leaves running around audio shops and picking up the right stuff. I'm a bit low on cash these days anyways, so I'll get the mic and the interface later. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/ mailman/listinfo/ubuntu-studio-users -- follow me on my Audio Linux blog http://audio-and-linux.blogspot.com/ ! -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Wed, Aug 6, 2014 at 10:27 AM, Thijs van severen thijsvanseve...@gmail.com wrote: Hi all maybe a bit off topic, but i'm interested in getting some advice on a 'simple cheap' USB audio device any tips? my requirements are these : - 1 stereo output (or 2 mono), ideally 2x 6.3mm mono jack (or cinch) - preferably with cable (so not the 'dongle' type of audio device) - inputs : dont really care, but 2x 6.3mm jack inputs would be nice - cost : really low ;-) - latency : approx 10ms will do - supported in linux OOTB maybe something like the behringer ucg 102? ( http://www.behringer.com/EN/Products/UCG102.aspx) all tips are welcome I use one these http://www.roland.com/products/en/UA-25EX/ after much reading on different linux forums. It should be possible to get a used one very cheap. /Jimmy -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
Sorry couldn't reply earlier. Got stuck all day in an emergency in the lab and just dozed off after getting home. On 27-Jul-14 5:07 PM, Ralf Mardorf wrote: You could disable wlan, just for testing purpose, even after we ensured that the snd driver has got the second high priority, right after the clock, testing this could be useful. Hmm.. setting the cpu scaling to performance and turning of wlan seems to have done the trick. I can now have 10.7 ms latency without getting xruns (haven't tested under heavy load conditions but this is a huge improvement). I'll update after doing something more intensive. Thanks for the help! Mish -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
in this scenario, where the machine is the sound source, or the software synth, you will need lower latency for that to feel like an actual instrument.. for me, i want under 12ms latency for this.. ideally, 5 to 8.. i personally dont want to incite an argument about latency and what is needed, or usable, or adequate, but rather, encourage you to, as i did, set the scenario up, and decide for yourself what latency is acceptable to you for live software synth instruments. if i had an internal audio device only, i would go ahead and assume the latency i will have will be unacceptable for this purpose.. a work around would be, connect the midi unit to the machine, and record the midi data, but, if the midi keyboard is more than a controller and has *any* internal sounds, use the internal sounds on the actual keyboard to monitor while tracking the midi data into the computer.. this will get you the same end result, with the compromise of not hearing exactly what you want while recording, but, hearing an instrument played in realtime.. after tracking the midi data into the machine, you can then process the midi data however you like... routing the midi data to whatever software instruments, and to whatever audio effects.. Yes, the keyboard does have its own synth with a line out, although the sounds are somewhat limited. Not being able to listen to the sound I want seems a little weird at first. But I guess I'll get used to it if I do it more often -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
OH!, i forgot to mention my opinion of USB mic's.. personally, i think they are great if they meet your needs.. they are one trick pony uni-tasking devices.. for example, you may be able to get a nice USB audio device and a nice actual mic for not much more cost than a decent USB mic, and those 2 things are *much* more versatile.. if you have a USB mic, for example, and you later decide to purchase a nicer preamp, you cant use it.. the USB audio device can also provide a nice instrument input, and be used as a fully functioning sound card.. so, for my money, i consider a USB mic to be a little bit of a wasted investment, unless the user is *only* doing something like a podcast, or only speech or one channel at a time with a mic.. good luck Thanks for the advice. Yeah, getting a dedicated audio interface sounds promising. Like you said, the hardware needs to support linux properly. Normally that wouldn't be an issue since I can easily find out from the internet which interfaces are linux compatible, getting them is more of a problem. E-commerce where I live, is a mess; Amazon US has everything though, but shipping will cost me a fortune. So that just leaves running around audio shops and picking up the right stuff. I'm a bit low on cash these days anyways, so I'll get the mic and the interface later. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, Jul 27, 2014 at 3:37 AM, Shubham Mishra mishrashubham2...@gmail.com wrote: Hello People. After a long time I finally got around to try and record something. I have a fresh install of Ubuntu Studio 14.04 up and running and I have fiddled around with some of the programs and tried to do some stuff but I'm running into some problems. Note I am not only new to linux audio but new to audio recording in general so please bear with me if some of the questions sound stupid. At the moment I'm using my midi keyboard which is hooked up with a USB cable and I'm only going to do midi stuff right now although I'm planning to get a microphone later for vocals. So here we go 1. I seem to be running into xruns a lot (one every 2-3 minutes) and the settings which I have to bring jack so I don't get any dropouts at all brings the latency up to 40ms which is too high. I'm running this on my relatively old laptop using the built in sound card, which has a first gen i3 and 3 GB RAM. Now I have absolutely no idea about what kind of hardware is recommended for audio recording, so is this much enough? Because if it is, then I'm probably doing something wrong. I do have a desktop with a much better processor which I may have to use then, but no dedicated sound card. you could be running into more issues with the hardware you have not supporting linux, or not supporting the work flow you are doing. on *any* internal audio device, if i can get 40ms latency, im comfortable with that. internal audio devices like that are not intended for audio production. regardless of the machine you end up using, even just adding a simple USB audio device that is under $80us can drastically improve your setup, in latency, and functionality, such as adding a mic preamp, or a proper line in for instruments. I have Realtime enabled in JACK and enabled memlock in Ubuntu Studio controls. What else can I do reduce the latency? I have left the priority setting in qjackctl at default. Should I change that to something? 2. Is it ok to use rakarrack effects while recording or should I monitor just a clean signal and then apply effects later? I mean, does the extra processing add significant load to the CPU or are we talking on completely different scales here? Same with zynaddsubfx; should I use that while recording? I read somewhere that apparently it is not real time safe. on older hardware, i dont do the effects in realtime like that on the way in. if i have 40ms latency, i dont even monitor with the software like that.. if i dont need to monitor in realtime, i dont. if i, for example, am recording a guitar, i'll have the amp or acoustic instrument in the room, live.. i'll put a mic on the amp or the instrument, and record. monitoring basically live with my actual ears, not the computer. in this case, the latency of the hardware literally doesnt matter. if i want effects, i'll add them in externally in this scenario, still, not using the machine to monitor. if i want to overdub, there are things in place in ardour that are supposed to adjust for the latency.. i will play the recorded track, and listen while tracking a new track, monitoring the already recorded track from the machine, and the live instrument im recording now with the analog source instead of after the software. in both of those scenarios, there is no benefit to monitoring after the software so i dont. if i wanted to, i would get hardware that supports lower latency. this does not necessarily mean faster CPU. i used to get sub 2ms with firewire on a pentium4 with a gig of ram. the firewire device was capable and supported linux well.. 3. For monitoring while recording, is it better to route the midi signal through qtractor to the synth or to connect the keyboard directly to the synth? in this scenario, where the machine is the sound source, or the software synth, you will need lower latency for that to feel like an actual instrument.. for me, i want under 12ms latency for this.. ideally, 5 to 8.. i personally dont want to incite an argument about latency and what is needed, or usable, or adequate, but rather, encourage you to, as i did, set the scenario up, and decide for yourself what latency is acceptable to you for live software synth instruments. if i had an internal audio device only, i would go ahead and assume the latency i will have will be unacceptable for this purpose.. a work around would be, connect the midi unit to the machine, and record the midi data, but, if the midi keyboard is more than a controller and has *any* internal sounds, use the internal sounds on the actual keyboard to monitor while tracking the midi data into the computer.. this will get you the same end result, with the compromise of not hearing exactly what you want while recording, but, hearing an instrument played in realtime.. after tracking the midi data into the machine, you can then process the midi data however you like... routing the midi data to
Re: [ubuntu-studio-users] Questions about production
10.7ms for the audio signal in - computer processing - audio out rout are usable for software monitoring, but it already is not very pleasant. Btw. it's the lowest I can get with my prosumer and professional sound cards. A longer delay IMO can't be used anymore. An analog mixing console IMO is very helpful to bypass software monitoring, some audio cards also provide an alternativ solution for the monitoring, but as Mike already mentioned, you have to imagine what it does sound. Musicians usually own external gear too, even if I will use a software delay, for the monitoring I could use an external 19 effect. IWO to give tips and tricks, we need to know what exactly you want to do and what your budget is. A cheap analog mixer could be helpful for monitoring and provides a mic preamp. But what exactly is cheap? ;) Buy a cheap this and a cheap that and in the end cheap becomes much money. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
[ubuntu-studio-users] Questions about production
Hello People. After a long time I finally got around to try and record something. I have a fresh install of Ubuntu Studio 14.04 up and running and I have fiddled around with some of the programs and tried to do some stuff but I'm running into some problems. Note I am not only new to linux audio but new to audio recording in general so please bear with me if some of the questions sound stupid. At the moment I'm using my midi keyboard which is hooked up with a USB cable and I'm only going to do midi stuff right now although I'm planning to get a microphone later for vocals. So here we go 1. I seem to be running into xruns a lot (one every 2-3 minutes) and the settings which I have to bring jack so I don't get any dropouts at all brings the latency up to 40ms which is too high. I'm running this on my relatively old laptop using the built in sound card, which has a first gen i3 and 3 GB RAM. Now I have absolutely no idea about what kind of hardware is recommended for audio recording, so is this much enough? Because if it is, then I'm probably doing something wrong. I do have a desktop with a much better processor which I may have to use then, but no dedicated sound card. I have Realtime enabled in JACK and enabled memlock in Ubuntu Studio controls. What else can I do reduce the latency? I have left the priority setting in qjackctl at default. Should I change that to something? 2. Is it ok to use rakarrack effects while recording or should I monitor just a clean signal and then apply effects later? I mean, does the extra processing add significant load to the CPU or are we talking on completely different scales here? Same with zynaddsubfx; should I use that while recording? I read somewhere that apparently it is not real time safe. 3. For monitoring while recording, is it better to route the midi signal through qtractor to the synth or to connect the keyboard directly to the synth? 4. On an unrelated note, how do sfz files work? Are they sort of like sf2 files, which I can just load up on Qsynth or something? 5. For the microphone, is it ok get a USB microphone? I heard that it's messy handling multiple sound cards with jack. If yes, then what is the best way to connect a microphone? Thanks Mish -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 13:07 +0530, Shubham Mishra wrote: 1. I seem to be running into xruns a lot CPU frequency scaling is the first one under suspicion, so run $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor Assumed the output shouldn't be performance for all CPUs, then run $ echo -n performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor /dev/null 2. Is it ok to use rakarrack effects while recording or should I monitor just a clean signal and then apply effects later? That depends on what you want to get and to the horsepower of your machine. It can't harm to use rakarrack, to play with the wanted sound, but at the same time to record the clean signal, so you could fine tune the used effect late. Same with zynaddsubfx; should I use that while recording? I read somewhere that apparently it is not real time safe. Use it while you're playing, not only for recording. It is rt safe, what ever that should mean. Consider to use yoshimi, it's the successor. By the preferences of both synth, you can select the sound quality, less good sound quality, less DSP load. 3. For monitoring while recording, is it better to route the midi signal through qtractor to the synth or to connect the keyboard directly to the synth? Rout it through qtractor, there's no need to double connect to the synth. 4. On an unrelated note, how do sfz files work? Are they sort of like sf2 files, which I can just load up on Qsynth or something? I don't know, but perhaps linuxsampler can use those files. Qsynth is the frontend for fluidsynth. I guess fluidsynth can't handle thsoe files. Qsampler is one of the frontends for linuxsample. Perhaps there's a PPA providing linuxsampler or maybe the KXstudio repositories provide it. Debian and Ubuntu unlikely will provide it, regarding to a licence issue. https://www.linuxsampler.org/ Start learning to compile it on your own ;). 5. For the microphone, is it ok get a USB microphone? I heard that it's messy handling multiple sound cards with jack. If yes, then what is the best way to connect a microphone? Assumed your sound device has got a microphone input, then better use this one. Btw. please give more information about your hardware. CPU, RAM, sound devices. Post the output of $ aplay -l $ arecord -l If possible don't use USB MIDI, it has got the tendency to increase MIDI jitter, IOW the timing might become audible less good, OTOH if you quantise using a sequencer, this might be unimportant. The best thing is to use PCI(e) MIDI, or use parallel port MIDI, usually only available by old PCs. For MIDI out from the computer to external synth, never ever use USB, since than the quantisation can't fix the jitter, only the other way, keyboard to computer could be usable, but also could cause trouble. For using external MIDI synth, I recommend to use a kernel-rt instead of the lowlatency kernel. Regards, Ralf -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
What are your jackd, resp. QjackCtl settings? Periods/Buffers should be 2, if possible, but sometimes 3 is needed, other sizes make no sense. Frames/Period depends on your hardware combination ;), the lower you can go, the better ;). 48 KHz is the preferred Sample Rate for studio usage, lower sample rates aren't good and higher sample rates usually are only good to get lower latency for stage usage. Just a few devices aren't optimised to 48 KHz, if so using another sample rate could be useful for studio usage too. When using Qtractor for audio recording, changing the Frames/Period between recording and mixing does cause an serious issue. The latency correction will not be corrected and Qtractor already hasn't a good latency correction, if you stay with the same latency. It's a trick to record with low latencies, less effects, playing not all tracks = less DSP load and to mix with higher latencies, when all tracks and effects are needed. You shouldn't try to do this with Qtractor, at least not with the versions I used. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
We need also the output of $ /etc/init.d/rtirq status e.g. to find out, what USB port you should or shouldn't use, assumed a port should share the IRQ with your sound device. We also could see if the real time priorities are ok. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
Hello, Other points have been dealt with, but I might have some ideas about the last ones. 4. On an unrelated note, how do sfz files work? Are they sort of like sf2 files, which I can just load up on Qsynth or something? SFZ files are just what you say, a sort of like sf2 files (compression algorithms may differ), that can be played with some players, although I have not tried them with Qsynth as yet. I play them on Win. software and they sound well. There might be a question of property rights though. 5. For the microphone, is it ok get a USB microphone? I heard that it's messy handling multiple sound cards with jack. If yes, then what is the best way to connect a microphone? As far as I have tried, it is possible but messy or complicated to deal with multiple sound cards, especially different ones, with Jack. The best way to connect a microphone is simply on a good sound interface, where it is made for. I mean : input 1 or whatever is microphone input. Then you may have to think about what soundcard or interface, keeping in mind it has to be useable with Linux/Ubuntustudio and your computer with its possibilities and limits. See the ALSA wiki pages about that and for a list of compatible sound devices. I have a RME UCX that works very well, but it's expensive and needs a good powerful PC. I used a multimix USB4 before and might be a good choice as prices go. Anyway, get a good quality microphone if you want to get good sounds, and think about it as a whole : microphone+sound device+computer, as the sound you will get will be dépendent on the weakest piece of equipment. regards, Jean -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 11:32 +0200, Jean HUBER wrote about sound devices. I want to add, that even an integrated sound device likely provides a low quality mic preamp. There are good Envy24 PCI cards for less money available at Ebay, prosumer, but the analog section unlikely comes with a mic preamp, so at least a cheap analog mixer or cheap mic preamp is needed too. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
Am Sun, 27 Jul 2014 13:07:32 +0530 schrieb Shubham Mishra mishrashubham2...@gmail.com: a first gen i3 and 3 GB RAM. This is plenty of computing power for audio. A Pentium-M 1.4GHz with 2 GiB RAM was plenty, too. My current laptop is a Core2Duo (OK, with 8 Gig, but those are not in use for audio production) and can work with a project in Ardour with about 20 tracks plus buses and effects all over the place (EQ, comp, reverb ... sometimes a amp/speaker simulation, too) just fine. You'll find that CPU load is not that high, unless you go for extremely low buffer sizes (below 128 or so). The crucial point is to have the system properly configured and to avoid bad luck with certain hardware that just won't work properly. Even frequency scaling with the 'ondemand' governor is no problem with my Core2Duo (also with the Pentium M back then). It might be a problem for you, though, but I actually doubt it. I suspect some software issue interfering with the operation of your gear. Especially if the xruns are regular. A fresh install of Ubuntu Studio _should_ not feature the usual suspects, though. 5. For the microphone, is it ok get a USB microphone? I heard that it's messy handling multiple sound cards with jack. If yes, then what is the best way to connect a microphone? Multiple sound cards are possible, but it should be avoided for simple setups, especially if the cards are not linked to a common clock (I run two Firewire devices that are in sync via S/PDIF). An USB microphone is a separate sound card. Best aquire a normal analog microphone and plug it into the same sound card that offers the MIDI interface. If your keyboard only has USB, not an actual MIDI port, then you could try a USB mic for cost-effectiveness, but you'd be more happy with an audio interface that handles both the data from the MIDI keyboard and the microphone. On the other hand ... I do wonder if there is a sync problem between a MIDI-only USB device and an audio USB device at all (apart from the jitter that Ralf refers to and which can but doesn't have to be a problem you encounter). When MIDI only does input, then the clock is ... you?! I'm not sure about the timing in the protocol ... but does it actually make a difference to have unsynced devices in this case? A question for the audience;-) In any case: Getting two devices into a JACK setup is more work than getting one device in there. Plus, a separate analog microphone can have other uses (on stage, in a different studio). Alrighty then, Thomas signature.asc Description: PGP signature -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 11:51 +0200, Thomas Orgis wrote: Am Sun, 27 Jul 2014 13:07:32 +0530 schrieb Shubham Mishra mishrashubham2...@gmail.com: a first gen i3 and 3 GB RAM. I didn't notice that this info already was provided. This is plenty of computing power for audio. Indeed, I own an AMD 2.1 GHz dual-core, 4 GiB RAM, RAM, CPU load, DSP load aren't an issue, anyway, chipsets and ugly Linux drivers could be a PITA. [rocketmouse@archlinux ~]$ arecord -l List of CAPTURE Hardware Devices card 0: HDSPMx579bcc [RME AIO_579bcc], device 0: RME AIO [RME AIO] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: EWX2496 [TerraTec EWX24/96], device 0: ICE1712 multi [ICE1712 multi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: EWX2496_1 [TerraTec EWX24/96], device 0: ICE1712 multi [ICE1712 multi] Subdevices: 1/1 Subdevice #0: subdevice #0 10.7 ms is the best latency provided by the PCI Envy24 cards (ICE1712) to get no xruns, such a card is around 30,-€ at Ebay, it's prosumer quality. The professional PCIe RME HDSPe AIO costs more than 500,-€, recommended by a LAD member, but it's not usable with Linux. It can't go under 10.7 ms and even with that latency or even a higher one, there are tons of xruns. hdspmixer shows input for all 8 ADAT channels, but routed to jackd are only 2 of the 8 channels. IOW for input and output only 2 of the 8 ADAT channels do work. The card isn't broken and the developer of the driver claims that I'm a liar. You need good luck, not only good hardware! On the other hand ... I do wonder if there is a sync problem between a MIDI-only USB device and an audio USB device at all I can not speak for USB audio devices. For PCI/PCIe it should be the best to use one and the same sound card for MIDI and audio, but since for serious MIDI work with external MIDI gear we need several MIDI outputs, it's impossible to use just the MIDI interface(s) provided by the audio card. Sync between the card I use for audio and the cards I use for MIDI is the same good/bad as for audio and MIDI using the same card. Even for PCI/PCIe cards MIDI jitter is an issue. IT seems to interact with the audio latency, the lower the latency, the better the audio to MIDI and MIDI to MIDI sync. A note to the OP, this MIDI sync issue only is important, if you're using external MIDI synth. But since you're using Qtractor, there's another sync issue, in loop play mode audio and MIDI tracks get out of sync after a few loops, this does effect internal, virtual synth too. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
Thanks for the help Running what you gave shows ondemand for all cpus. My jack settings are attached. @admin : please ignore the previous message i sent $ aplay -l output List of PLAYBACK Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: MID [HDA Intel MID], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 $arecord -l output List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ /etc/init.d/rtirq status output PID CLS RTPRIO NI PRI %CPU STAT COMMAND 80 FF 90 - 130 0.0 Sirq/8-rtc0 75 FF 80 - 120 0.0 Sirq/16-ehci_hcd 77 FF 79 - 119 0.0 Sirq/23-ehci_hcd 79 FF 75 - 115 0.0 Sirq/1-i8042 78 FF 74 - 114 0.0 Sirq/12-i8042 47 FF 50 - 90 0.0 Sirq/9-acpi 152 FF 50 - 90 0.0 Sirq/40-ahci 372 FF 50 - 90 0.0 Sirq/18-ips 439 FF 50 - 90 0.1 Sirq/17-wlan%d 3497 FF 50 - 90 0.0 Sirq/42-mei_me 3498 FF 50 - 90 0.0 Sirq/43-snd_hda_ 3571 FF 50 - 90 0.0 Sirq/44-i915 3791 FF 50 - 90 0.0 Sirq/41-eth0 3 TS - 0 19 0.0 Rksoftirqd/0 26 TS - 0 19 0.0 Sksoftirqd/1 31 TS - 0 19 0.0 Sksoftirqd/2 36 TS - 0 19 0.0 Sksoftirqd/3 As for the ports, I will have to use a USB midi for now since my laptop has neither PCI midi nor firewire ports. But I won't be sending anything to the keyboard anyways. Only take the signal from the keyboard [Splitter] AudioConnectView\sizes=266, 88, 266 MidiConnectView\sizes=34, 20, 34 AlsaConnectView\sizes=34, 20, 34 PatchbayView\sizes=34, 20, 34 InfraClientSplitter\sizes=12, 12 [Geometry] qjackctlMessagesStatusForm\x=430 qjackctlMessagesStatusForm\y=388 qjackctlMessagesStatusForm\width=516 qjackctlMessagesStatusForm\height=278 qjackctlMessagesStatusForm\visible=false qjackctlSessionForm\x=848 qjackctlSessionForm\y=71 qjackctlSessionForm\width=511 qjackctlSessionForm\height=428 qjackctlSessionForm\visible=false qjackctlConnectionsForm\x=387 qjackctlConnectionsForm\y=288 qjackctlConnectionsForm\width=594 qjackctlConnectionsForm\height=286 qjackctlConnectionsForm\visible=false qjackctlPatchbayForm\x=2 qjackctlPatchbayForm\y=71 qjackctlPatchbayForm\width=750 qjackctlPatchbayForm\height=369 qjackctlPatchbayForm\visible=false qjackctlMainForm\x=371 qjackctlMainForm\y=186 qjackctlMainForm\width=479 qjackctlMainForm\height=100 qjackctlMainForm\visible=true [Program] Version=0.3.10 [Presets] DefPreset=(default) [Options] Singleton=true StartJack=false StopJack=true StartupScript=false StartupScriptShell= PostStartupScript=false PostStartupScriptShell= ShutdownScript=false ShutdownScriptShell= PostShutdownScript=false PostShutdownScriptShell= StdoutCapture=true XrunRegex=xrun of at least ([0-9|\\.]+) msecs ActivePatchbay=false ActivePatchbayPath= MessagesLog=false MessagesLogPath=qjackctl.log BezierLines=false TimeDisplay=0 TimeFormat=0 MessagesFont=Droid Sans,10,-1,5,50,0,0,0,0,0 MessagesLimit=true MessagesLimitLines=1000 DisplayFont1=Droid Sans,12,-1,5,75,0,0,0,0,0 DisplayFont2=Droid Sans,10,-1,5,50,0,0,0,0,0 DisplayEffect=true DisplayBlink=true JackClientPortAlias=0 ConnectionsIconSize=0 ConnectionsFont=Droid Sans,10,-1,5,50,0,0,0,0,0 QueryClose=true KeepOnTop=false SystemTray=false StartMinimized=false DelayedSetup=false ServerConfig=true ServerConfigName=.jackdrc ServerConfigTemp=false QueryShutdown=true AlsaSeqEnabled=true DBusEnabled=true AliasesEnabled=false AliasesEditing=false LeftButtons=true RightButtons=true TransportButtons=true TextLabels=true BaseFontSize=0 [Defaults] PatchbayPath= MessagesStatusTabPage=1 ConnectionsTabPage=0 SessionSaveVersion=true [Settings] Server=/usr/bin/jackd ServerName= Realtime=true SoftMode=false Monitor=false Shorts=false NoMemLock=false UnlockMem=false HWMon=false HWMeter=false IgnoreHW=false Priority=0 Frames=1024 SampleRate=48000 Periods=2 WordLength=16 Wait=21333 Chan=0 Driver=alsa Interface= Audio=0 Dither=0 Timeout=500 InDevice= OutDevice= InChannels=0 OutChannels=0 InLatency=0 OutLatency=0 StartDelay=2 Verbose=false PortMax=128 MidiDriver=seq ServerSuffix= [History] ServerPrefixComboBox\Item1=/usr/bin/jackd ServerPrefixComboBox\Item2=jackd ServerPrefixComboBox\Item3=jackdmp ServerPrefixComboBox\Item4=jackstart ServerNameComboBox\Item1=(default) InterfaceComboBox\Item1=(default) InterfaceComboBox\Item2=hw:0 InterfaceComboBox\Item3=plughw:0 InterfaceComboBox\Item4=/dev/audio InterfaceComboBox\Item5=/dev/dsp InDeviceComboBox\Item1=(default) InDeviceComboBox\Item2=hw:MID,0 InDeviceComboBox\Item3=plughw:0 InDeviceComboBox\Item4=hw:0 InDeviceComboBox\Item5=/dev/audio OutDeviceComboBox\Item1=(default) OutDeviceComboBox\Item2=hw:0 OutDeviceComboBox\Item3=plughw:0
Re: [ubuntu-studio-users] Questions about production
So I should get an external audio interface which has a mic preamp and midi in and not use onboard card at all? On Sunday 27 July 2014 03:02 PM, Jean HUBER wrote: SFZ files are just what you say, a sort of like sf2 files (compression algorithms may differ), that can be played with some players, although I have not tried them with Qsynth as yet. I play them on Win. software and they sound well. There might be a question of property rights though. Hmm.. then I'll check linux sampler -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 16:23 +0530, Shubham Mishra wrote: $ /etc/init.d/rtirq status output PID CLS RTPRIO NI PRI %CPU STAT COMMAND 80 FF 90 - 130 0.0 Sirq/8-rtc0 75 FF 80 - 120 0.0 Sirq/16-ehci_hcd 77 FF 79 - 119 0.0 Sirq/23-ehci_hcd 79 FF 75 - 115 0.0 Sirq/1-i8042 78 FF 74 - 114 0.0 Sirq/12-i8042 47 FF 50 - 90 0.0 Sirq/9-acpi 152 FF 50 - 90 0.0 Sirq/40-ahci 372 FF 50 - 90 0.0 Sirq/18-ips 439 FF 50 - 90 0.1 Sirq/17-wlan%d 3497 FF 50 - 90 0.0 Sirq/42-mei_me 3498 FF 50 - 90 0.0 Sirq/43-snd_hda_ Please post the output of $ grep RTIRQ_NAME_LIST /etc/default/rtirq Your sound device doesn't share it's IRQ, but it has got a bad priority. The rtirq default is to care about snd drivers, but Ubuntu Studio has got the tendency to use current lowlatency kernels, but stay with outdated rtirq scripts, that don't fit to the kernel. Please also post the output of $ sudo apt-cache policy rtirq-init $ uname -rm On Sun, 2014-07-27 at 16:24 +0530, Shubham Mishra wrote: So I should get an external audio interface which has a mic preamp and midi in and not use onboard card at all? Not necessarily! But one step after the other, first we need to find out why you experience xruns. You set up the CPU frequency scaling to performance? -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
I'm to lazy to read your attachment, lease post the output of $ cat .jackdrc -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
You could disable wlan, just for testing purpose, even after we ensured that the snd driver has got the second high priority, right after the clock, testing this could be useful. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
These are the jack settings /usr/bin/jackd -p128 -dalsa -dhw:0 -r48000 -p512 -n2 -Xseq On Sunday 27 July 2014 04:47 PM, Ralf Mardorf wrote: On Sun, 2014-07-27 at 16:23 +0530, Shubham Mishra wrote: $ /etc/init.d/rtirq status output PID CLS RTPRIO NI PRI %CPU STAT COMMAND 80 FF 90 - 130 0.0 Sirq/8-rtc0 75 FF 80 - 120 0.0 Sirq/16-ehci_hcd 77 FF 79 - 119 0.0 Sirq/23-ehci_hcd 79 FF 75 - 115 0.0 Sirq/1-i8042 78 FF 74 - 114 0.0 Sirq/12-i8042 47 FF 50 - 90 0.0 Sirq/9-acpi 152 FF 50 - 90 0.0 Sirq/40-ahci 372 FF 50 - 90 0.0 Sirq/18-ips 439 FF 50 - 90 0.1 Sirq/17-wlan%d 3497 FF 50 - 90 0.0 Sirq/42-mei_me 3498 FF 50 - 90 0.0 Sirq/43-snd_hda_ Please post the output of $ grep RTIRQ_NAME_LIST /etc/default/rtirq RTIRQ_NAME_LIST=rtc snd usb i8042 Your sound device doesn't share it's IRQ, but it has got a bad priority. The rtirq default is to care about snd drivers, but Ubuntu Studio has got the tendency to use current lowlatency kernels, but stay with outdated rtirq scripts, that don't fit to the kernel. Please also post the output of $ sudo apt-cache policy rtirq-init $ uname -rm rtirq-init: Installed: 20130909-1 Candidate: 20130909-1 Version table: *** 20130909-1 0 500 http://in.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status and 3.13.0-32-lowlatency x86_64 Not necessarily! But one step after the other, first we need to find out why you experience xruns. You set up the CPU frequency scaling to performance? Yes it's set to performance now. I get almost the same number of xruns, a bit less may be. However DSP load seems to have gone down from 50% to 20%. I'll record again in the evening after a system restart with the frequency scaling at performance and see how many dropouts i get. Thanks Mish -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 17:40 +0530, Shubham Mishra wrote: These are the jack settings /usr/bin/jackd -p128 -dalsa -dhw:0 -r48000 -p512 -n2 -Xseq ^^ wrong /usr/bin/jackd -dalsa -dhw:0 -r48000 -p512 (or -p128) -n2 -Xseq $ grep RTIRQ_NAME_LIST /etc/default/rtirq RTIRQ_NAME_LIST=rtc snd usb i8042 that's good, but seemingly ignored $ sudo apt-cache policy rtirq-init $ uname -rm rtirq-init: Installed: 20130909-1 Candidate: 20130909-1 3.13.0-32-lowlatency x86_64 Perhaps the rtirq script doesn't fit to the kernel or something else is fishy. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
On Sun, 2014-07-27 at 14:50 +0200, Ralf Mardorf wrote: On Sun, 2014-07-27 at 17:40 +0530, Shubham Mishra wrote: These are the jack settings /usr/bin/jackd -p128 -dalsa -dhw:0 -r48000 -p512 -n2 -Xseq ^^ wrong /usr/bin/jackd -dalsa -dhw:0 -r48000 -p512 (or -p128) -n2 -Xseq -p maximum-number-of-ports My apologies, it's ok ;). -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Questions about production
Hello, I think yes, that would ensure trouble-free working of both audio and midi together. Best regards, Jean Le 27/07/2014 12:54, Shubham Mishra a écrit : So I should get an external audio interface which has a mic preamp and midi in and not use onboard card at all? On Sunday 27 July 2014 03:02 PM, Jean HUBER wrote: SFZ files are just what you say, a sort of like sf2 files (compression algorithms may differ), that can be played with some players, although I have not tried them with Qsynth as yet. I play them on Win. software and they sound well. There might be a question of property rights though. Hmm.. then I'll check linux sampler -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
