alfawig seeking weta besters: herding debian cats for $$$
-
- KVRAF
- Topic Starter
- 9123 posts since 6 Oct, 2004
First signs of impending linux version doom: a 147 meg .deb file.
(Reaper is about 9 meg)
Second sign, 64 bit only.
Third sign: based on ubuntu.
Fourth sign, the servers were buried, with a new version
released in minutes
Now, the nuts and bolts of it, is that BS takes over
the linux jackd server, but still fails to find the midi input
from perhaps the most ubiquitus and rock solid combination
of midi keyboard, and pci soundcard known to linux.
On the same 64 bit system, it took minutes to install the
64 bit wine, choose the correct wineasio.dll
install the windows version of the infamous R,
drag&drop a hefty vst folder, and begin enjoying
the Diva Magic Flute preset, sounding precisely twice as good
as on a lowly 32 bit system
And R glady shares the jackd server, with all the other
linux audio apps at hand. Bitwig-Studio, not so much:
"ATTENTION: The playback device "hw:M2496,0" is already in use. The following applications are using your soundcard(s) so you should check them and stop them as necessary before trying to start JACK again:
BitwigStudioEng (process ID 4039)"
There is actually a vast linux userbase in just Germany,
Spain, and european university culture in general.
I find it shocking that such a slack hand has been applied.
Far better to have waited 6 months, even a year,
and funded a competitive linux release,
and perhaps sold a very nice stack, a few months down the road.
Linux users able to i/o midi and audio with bitwig linux version,
please post your distro, kernel, java version, soundcard,
motherboard/cpu, and pertinent steps that may have been needed.
There is still hope, still time left on the clock
Cheers
(Reaper is about 9 meg)
Second sign, 64 bit only.
Third sign: based on ubuntu.
Fourth sign, the servers were buried, with a new version
released in minutes
Now, the nuts and bolts of it, is that BS takes over
the linux jackd server, but still fails to find the midi input
from perhaps the most ubiquitus and rock solid combination
of midi keyboard, and pci soundcard known to linux.
On the same 64 bit system, it took minutes to install the
64 bit wine, choose the correct wineasio.dll
install the windows version of the infamous R,
drag&drop a hefty vst folder, and begin enjoying
the Diva Magic Flute preset, sounding precisely twice as good
as on a lowly 32 bit system
And R glady shares the jackd server, with all the other
linux audio apps at hand. Bitwig-Studio, not so much:
"ATTENTION: The playback device "hw:M2496,0" is already in use. The following applications are using your soundcard(s) so you should check them and stop them as necessary before trying to start JACK again:
BitwigStudioEng (process ID 4039)"
There is actually a vast linux userbase in just Germany,
Spain, and european university culture in general.
I find it shocking that such a slack hand has been applied.
Far better to have waited 6 months, even a year,
and funded a competitive linux release,
and perhaps sold a very nice stack, a few months down the road.
Linux users able to i/o midi and audio with bitwig linux version,
please post your distro, kernel, java version, soundcard,
motherboard/cpu, and pertinent steps that may have been needed.
There is still hope, still time left on the clock
Cheers
-
- KVRian
- 508 posts since 9 Feb, 2012
I haven't gotten around to demo'ing it yet, but I think that's a by-product of apparently being written mostly in Java.glokraw wrote:First signs of impending linux version doom: a 147 meg .deb file.
(Reaper is about 9 meg)
The 2 premier Java desktop/workstation apps are Eclipse and Netbeans, and both of those are buggy as hell and painfully slow even after years of contribution from IBM, Sun, Oracle etc... thanks to Java's legendary enterprise-grade "write once, debug everywhere" technology.
From what I've seen, Bitwig still seems to have an awful lot of bugs even after being years late and then the 4-month punt from release date announcement to release date. I sincerely hope they get it all working smoothly (especially on Linux), but I'm really starting to have my doubts.
I think any computer not capable of 64-bit operation is probably not capable of running Bitwig adequately anyways, given that Java apps use about 100x as much memory as C/C++ apps you're going to need more than 2GB of process memoryglokraw wrote: Second sign, 64 bit only.
-
- KVRAF
- Topic Starter
- 9123 posts since 6 Oct, 2004
Looks like uncompressed, 180 meg, out of 300, are in the JRE folder,
and a couple of jar files.
At least they put it all in /opt, instead of doing the
tornadic debris field installation like Native Instruments.
DP had it manually installed in Fedora, before the ink was dry.
How are the electro-tracks coming for the Pydaw trance/dance CD?
Seventy minutes per CD, you should be getting into some good
mastering territory by now. That first release is the important one.
Better a couple months later than desired, than half-baked and gooey
and a couple of jar files.
At least they put it all in /opt, instead of doing the
tornadic debris field installation like Native Instruments.
DP had it manually installed in Fedora, before the ink was dry.
How are the electro-tracks coming for the Pydaw trance/dance CD?
Seventy minutes per CD, you should be getting into some good
mastering territory by now. That first release is the important one.
Better a couple months later than desired, than half-baked and gooey
-
- KVRian
- 508 posts since 9 Feb, 2012
That was another reason I stopped using Windows and started rolling my own. The 24-48 hour install of NI Komplete and it's content library (95% of which is useless for making real music with) gets old when you're someone who regularly reinstalls his OS.glokraw wrote: At least they put it all in /opt, instead of doing the
tornadic debris field installation like Native Instruments.
It's actually coming along really well, thanks for askingglokraw wrote: How are the electro-tracks coming for the Pydaw trance/dance CD?
Seventy minutes per CD, you should be getting into some good
mastering territory by now. That first release is the important one.
Better a couple months later than desired, than half-baked and gooey