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
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
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
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
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
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 OutDev
[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
