Hi to all, I'm trying to run Battery3 with Wine, but I'm experiencing some problems. 1. When I launch Battery (command line) I see these messages: --- fixme:win:RegisterDeviceNotificationW (hwnd=0x50062, filter=0x32fcb0,flags=0x00000004) returns a fake device notification handle! JackActivationCount::Signal value = 0 ref = 5 JackActivationCount::Signal value = 0 ref = 5 fixme:shell:IDropTargetHelper_fnShow (0x141b90)->(0) fixme:shell:IDropTargetHelper_fnShow (0x141b90)->(1) --- After these lines, I see a lot of: fixme:shell:IDropTargetHelper_fnShow (0x141b90)->(0) fixme:shell:IDropTargetHelper_fnShow (0x141b90)->(1) that appears continuously even if I'm not playing. When the JackActivationCount line appears, a XRUN occurs. 2. When the GUI is visible, it increases a lot the CPU's usage (from 2% to 15%) and the numbers of XRUNS. If I hide the GUI(or a part of it), XRUNS still occurs, but less than before. 3. If I play a lot of cells in short time, I often hear clicks and pops, and XRUNS occurs. I also notice that jack's CPU usage goes from 7% to 50%. Is there anything that I can do to improve the perfomance and eliminate clicks, pops and XRUNS? I'm using Wine 1.2.2, WineASIO 0.8, linux-rt 2.6.31.11, rtirq, on a 64bit Ubuntu 10.04. Sorry for my bad english, Thanks!
Hi, I have Battery3 installed..(actually all of N.I Komplete) i wouldn't expect that plugin to be "lite" on resources, it's not. it has a number FX, and multi-layered sounds, as well as some other non-cpu-lite features ~ like it's gui. i only experience xruns with that application, sometimes when starting, and usually on exit. Otherwise, it runs perfectly fine. - this is using my ubuntu 10.10 64-bit (quad-core). I am using wineASIO 0.9.0 (beta), with Jack2, wine 1.3 (actually "wine-rt"). ~ from the KxStudio repositories... However, on my laptop (coreduo) battery3 does cause some xruns. usually when switching drumkits, and if my CPU and DSP load are really high, during playback, i may also experience xruns. also, I had to revert my Battery3 install, as a recent update that added some features, seem to make the plugin less stable and reliable under wine on my machine. (including more xruns) 1.You might want to use wine-rt, and specify proper priorites for battery3 and see if that helps... 2.one way of reducing xruns on my laptop, was to disable SMP support in Battery3's "options" section. 3.You also could limit how many outputs Battery has, i think by default it will have 8 or 16 - which may also be giving you more xruns. 4.You may also want to adjust the DFD stuff in battery. The xruns could be because of a slow-disk too? or.... 5.if you happen to be using a slower machine, i wouldn't bother with Battery3. Instead, i would ditch it for a mmore minimal sampler such as "specimen" or "linuxsampler". You can take all of the Battery3 drum sample librairies from your ISO/or hard-disk, and map them in either program. then you will be using more like 4% CPU even when playing many multi-layered sounds at once. This is actually what i do... why bother wasting large amounts of CPU on a task, that really should take very little cpu? there's my cents, hope it helps jordan
Hi Jordan, thank you for the advices! I wiped out my Ubuntu installation and now I have a fresh Ubuntu 10.04 with Kxstudio's ppa (wine-rt 1.3.9, wineASIO 0.9.0, jack2). You told me that you had to rollback your Battery version, which version you have now? 2. What is exactly SMP support? I can't be able to find it. 3. Ok, I reduced to one stereo output for testing. 4. I don't use DFD: I load all the samples in memory. I'll make another test, Thank you! Nicola
Hi, I've just tested all the things you wrote in your previous posts.> I am running 3.1.1 - I believe the upgrade that i had was 3.1.4I tested 3.0.6 and 3.1.1, without SMP, with just one stereo output and no DFD. The enviroment of test was a Ubuntu 10.04 with kernel 2.6.31.11-rt and all the infos that I found here http://wiki.linuxmusicians.com/doku.php?id=system_configuration I made 2 tests: one with rtirq and the other without it. With rtirq the priorities were:> > ps -eLo rtprio,cls,pid,pri,nice,cmd | grep "FF" | sort -r > - TS 6801 19 0 grep --color=auto FF > 99 FF 3 139 - [migration/0] > 99 FF 27 139 - [watchdog/1] > 99 FF 17 139 - [posixcputmr/1] > 99 FF 16 139 - [migration/1] > 99 FF 14 139 - [watchdog/0] > 99 FF 13 139 - [posixcputmr/0] > 90 FF 730 130 - [irq/8-rtc0] > 85 FF 966 125 - [irq/19-ohci1394] > 80 FF 3833 120 - [irq/22-HDA Inte] > 75 FF 682 115 - [irq/16-uhci_hcd] > 75 FF 670 115 - [irq/18-ehci_hcd] > 74 FF 692 114 - [irq/18-uhci_hcd] > 74 FF 675 114 - [irq/23-ehci_hcd] > 73 FF 707 113 - [irq/18-uhci_hcd] > 73 FF 702 113 - [irq/19-uhci_hcd] > 72 FF 687 112 - [irq/21-uhci_hcd] > 71 FF 697 111 - [irq/23-uhci_hcd] > 70 FF 4785 110 - /usr/bin/jackd -P70 -dalsa -dhw:0 -r44100 -p128 -n2 -Xseq > 65 FF 6692 105 - .wine/drive_c/Programmi/Native Instruments/Battery 3/Battery 3.exe > 50 FF 596 90 - [irq/17-pata_jmi] > 50 FF 562 90 - [irq/19-ata_piix] > 50 FF 552 90 - [irq/19-ata_piix] > 50 FF 541 90 - [irq/16-ahci] > 50 FF 4051 90 - [irq/16-nvidia] > 50 FF 4019 90 - [irq/28-eth0] > 50 FF 190 90 - [irq/9-acpi] > 49 FF 9 89 - [sirq-tasklet/0] > 49 FF 8 89 - [sirq-block/0] > 49 FF 7 89 - [sirq-net-rx/0] > 49 FF 6 89 - [sirq-net-tx/0] > 49 FF 5 89 - [sirq-timer/0] > 49 FF 4 89 - [sirq-high/0] > 49 FF 26 89 - [sirq-rcu/1] > 49 FF 25 89 - [sirq-hrtimer/1] > 49 FF 24 89 - [sirq-sched/1] > 49 FF 23 89 - [sirq-tasklet/1] > 49 FF 22 89 - [sirq-block/1] > 49 FF 21 89 - [sirq-net-rx/1] > 49 FF 20 89 - [sirq-net-tx/1] > 49 FF 19 89 - [sirq-timer/1] > 49 FF 18 89 - [sirq-high/1] > 49 FF 12 89 - [sirq-rcu/0] > 49 FF 11 89 - [sirq-hrtimer/0] > 49 FF 10 89 - [sirq-sched/0] > 1 FF 31 41 - [events/1] > 1 FF 30 41 - [events/0] > 10 FF 6695 50 - /usr/bin/wineserver >While without rtirq were:> > ps -eLo rtprio,cls,pid,pri,nice,cmd | grep "FF" | sort -r > - TS 5020 19 0 grep --color=auto FF > 99 FF 3 139 - [migration/0] > 99 FF 27 139 - [watchdog/1] > 99 FF 17 139 - [posixcputmr/1] > 99 FF 16 139 - [migration/1] > 99 FF 14 139 - [watchdog/0] > 99 FF 13 139 - [posixcputmr/0] > 70 FF 4785 110 - /usr/bin/jackd -P70 -dalsa -dhw:0 -r44100 -p128 -n2 -Xseq > 65 FF 4861 105 - .wine/drive_c/Programmi/Native Instruments/Battery 3/Battery 3.exe > 50 FF 966 90 - [irq/19-ohci1394] > 50 FF 730 90 - [irq/8-rtc0] > 50 FF 719 90 - [irq/1-i8042] > 50 FF 718 90 - [irq/12-i8042] > 50 FF 707 90 - [irq/18-uhci_hcd] > 50 FF 702 90 - [irq/19-uhci_hcd] > 50 FF 697 90 - [irq/23-uhci_hcd] > 50 FF 692 90 - [irq/18-uhci_hcd] > 50 FF 687 90 - [irq/21-uhci_hcd] > 50 FF 682 90 - [irq/16-uhci_hcd] > 50 FF 675 90 - [irq/23-ehci_hcd] > 50 FF 670 90 - [irq/18-ehci_hcd] > 50 FF 596 90 - [irq/17-pata_jmi] > 50 FF 562 90 - [irq/19-ata_piix] > 50 FF 552 90 - [irq/19-ata_piix] > 50 FF 541 90 - [irq/16-ahci] > 50 FF 4051 90 - [irq/16-nvidia] > 50 FF 4019 90 - [irq/28-eth0] > 50 FF 3833 90 - [irq/22-HDA Inte] > 50 FF 190 90 - [irq/9-acpi] > 49 FF 9 89 - [sirq-tasklet/0] > 49 FF 8 89 - [sirq-block/0] > 49 FF 7 89 - [sirq-net-rx/0] > 49 FF 6 89 - [sirq-net-tx/0] > 49 FF 5 89 - [sirq-timer/0] > 49 FF 4 89 - [sirq-high/0] > 49 FF 26 89 - [sirq-rcu/1] > 49 FF 25 89 - [sirq-hrtimer/1] > 49 FF 24 89 - [sirq-sched/1] > 49 FF 23 89 - [sirq-tasklet/1] > 49 FF 22 89 - [sirq-block/1] > 49 FF 21 89 - [sirq-net-rx/1] > 49 FF 20 89 - [sirq-net-tx/1] > 49 FF 19 89 - [sirq-timer/1] > 49 FF 18 89 - [sirq-high/1] > 49 FF 12 89 - [sirq-rcu/0] > 49 FF 11 89 - [sirq-hrtimer/0] > 49 FF 10 89 - [sirq-sched/0] > 25 FF 4861 65 - .wine/drive_c/Programmi/Native Instruments/Battery 3/Battery 3.exe > 20 FF 4861 60 - .wine/drive_c/Programmi/Native Instruments/Battery 3/Battery 3.exe > 1 FF 31 41 - [events/1] > 1 FF 30 41 - [events/0] > 10 FF 4864 50 - /usr/bin/wineserver >With those configurations, and thanks to your advices, the results was pretty good. XRUNS occured only when I opened/closed Battery, and the CPU never went over 16%! The only annoying thing was a strange vibration in the built-in reverb. But, in the end, you were right: it's better to use a native sampler because it'is more stable and cpu-optimized. I'm happy that I can use Battery3 on GNU Linux, but in the (near) future I'm planning to switch to a native sampler, maybe Hydrogen... So thanks again for your help :-)
Why are the servers down? I wanna play WoW!!
On Tue, Feb 22, 2011 at 9:53 PM, fanlynne <wineforum-user at winehq.org> wrote:> Why are the servers down? I wanna play WoW!!why are you asking in a thread, which has nothing to do with WoW??? our discussion is about the use of VSTs in Wine, not about video games under wine. Furthermore, what does Wine have to do with the WoW servers being down??!! jordan