Hallo,
Mark Knecht hat gesagt: // Mark Knecht wrote:
> On Sun, 28 Nov 2004 22:09:17 +0100, Frank Barknecht <fbar(a)footils.org> wrote:
> <SNIP>
> >
> > Nobody can steal free software, because they already own it. (As long
> > as they follow the rules as stated in the GPL etc.)
>
> This is so patently untrue I cannot imagine how you got here.
>
> GPL == GP License
>
> Nothing under GPL is 'owned' by me. It is 'licensed'. I didn't create
> it so I don't have any rights other than those granted me. If you own
> something you can do anything you want with it simply because you own
> it. If it is licensed you must follow the terms of the license
> specifcally because the real owner only grants you the rights in the
> license.
Well, that's what I wrote: As long as you follow the license, you can
do everything you want with it. The free software licenses are
designed in a way, that you can do everything, that does not try to
take away the right to do everything with the software from other
users. Even the original "owner", the autor of the software, cannot
take away these rights once he released a piece of code under a libre
license. In this way he is as much an "owner" as you are. (He is more
"owner" in the case that he wants to double license his code under a
non-free licens, but then this piece of code is not free software
anymore. He still cannot take back the code he already had set free.)
I am not strictly talking "law" here. But e.g. the FSF is working on
freeing software from owners (Why Software Should Not Have Owners,
[1]) by giving authors the same rights as users (and thus making them
"owners", too, in a way)
[1] http://www.fsf.org/philosophy/why-free.html
Ciao
--
Frank Barknecht _ ______footils.org__
On Mon, 2004-11-29 at 01:32, Mark Knecht wrote:
> On Mon, 29 Nov 2004 03:19:14 +0100, Marek Peteraj <marpet(a)naex.sk> wrote:
>
>
> > > ???? RME never 'supported' the card under Linux. The 'supported' the
> > > developers by providing technical info. I did not purchase the card
> > > because of RME telling me it would be OK to use the card under Linux.
> > > They never stated such things.
> >
> > Unfortunately they did. To quote a part of their response:
> > "> [linux-audio-dev] RME is no more
> >
> > Complete BS. We have and will support Linux/Alsa as before. The only
> > excluded product is the Fireface."
> >
> > Marek
>
> Well, I don't know exactly what you're calling BS
No no you don't understand, i was quoting RME. I had a discussion with
them on their forum.
Marek
On Mon, 2004-11-29 at 00:58, Mark Knecht wrote:
> On Mon, 29 Nov 2004 02:25:09 +0100, Marek Peteraj <marpet(a)naex.sk> wrote:
> > On Sun, 2004-11-28 at 21:31, Mark Knecht wrote:
>
> >
> > One nice example. Korg 1212 i/o, worked under win98, doesn't under winXP
> > because korg does not provide support for it. There is an alsa driver
> > for it now(and specs), so basically the life of that card is extended to
> > eternity.
> >
> > There are more such damn good reasons for open source drivers. People
> > just don't shout too loud. :)
>
> Fair enough. There are companies here in Silicon Valley that take over
> 'end of life' chip designs and manufacturer them for a while to help
> customers, but there isn't much money in it most of the time, just as
> there is probably no financial reason for Korg to support that card. I
> didn't like it when DigiDesign said they weren't going to continue to
> support the 001 forever and I was forced into buying an 002 or going
> away from Windows. Unortunately there was no other platform that
> maintained my music investment as well so I stuck with Digi.
>
> That's the nature of technology. It gets outdated. Not too many
> companies making buggy whips anymore either...
>
> >> However how did Marek end up being an RME customer when
> > > there was (as far as I know) never any support for this device under
> > > Linux, nor anyone even really saying there would be?
> >
> > Actually not quite, it seemed as if there would be support, Thomas
> > wanted to do the driver. I just invested too much trust in RME. My
> > fault.
>
> And I am very sorry about that.
You don't have to be.
> It is a disappointment I'm sure.
> You're a long ways away. If it was more practical I'd probably buy the
> unit from you. I have uses. I'm sure others will too. You'll sell it
> and get good money. Chalk the loss up to learning and
> remember..."Trust, but verify".
Agreed. It was a lesson to learn. Thanks for your 'heads up' :)
>
> >
> > > In my case I Was
> > > told that supporting the HDSP 9652 would be a non-issue based on the
> > > DigiFace working. It turned out to be true, but then again it took
> > > about a year to become really useful to me, and even today doesn't
> > > work as well as it does under Windows. How did he end up with this
> > > device and in this position?
> > >
> > > I somehow don't think this is RME's fault...
> >
> > If RME did the drivers for your HDSP 9652 then you could directly
> > contact them and ask them for support. I'm sure Thomas would help you
> > aswell if he had the card, and that's the problem. In such case claiming
> > that they do support alsa is just plain unfair.
>
> ???? RME never 'supported' the card under Linux. The 'supported' the
> developers by providing technical info. I did not purchase the card
> because of RME telling me it would be OK to use the card under Linux.
> They never stated such things.
Unfortunately they did. To quote a part of their response:
"> [linux-audio-dev] RME is no more
Complete BS. We have and will support Linux/Alsa as before. The only
excluded product is the Fireface."
Marek
On Sun, 2004-11-28 at 21:31, Mark Knecht wrote:
> On Sun, 28 Nov 2004 15:20:33 -0500, Lee Revell <rlrevell(a)joe-job.com> wrote:
> > On Sun, 2004-11-28 at 12:06 -0800, Mark Knecht wrote:
> >
> >
> > > > Fine with me. If I shelled out for RME hardware I better be able to
> > > > call RME for support, same as on any other OS. You get what you pay
> > > > for, right?
> > >
> > > Sure, but when you buy it and the box says 'Requires Mac OS X or
> > > Windows XP' then as a buyer I have to respect that. I cannot expect
> > > them to support Linux when it wasn't advertised that it works on
> > > Linux. RME has given me GREAT support under Windows and I expect that
> > > this will not change. They are a great company. I own two cards and
> > > wouldn't hesitate to buy another if I was going to set up another
> > > Windows box.
> >
> > Yeah, I was referring to an Nvidia like scenario, where they don't
> > release open drivers, but release closed Linux drivers of comparable
> > quality and the same support as the Windows driver.
>
> Sure, I get it. However I think you and plug in a close source RME
> card driver and happily use it if it was available. I think Marek,
> Frank and others do not feel this way. I had no second thoughts about
> putting an NVidia controller in my dad's Linux box even though I used
> ATI up until then. My experience using both is no that different, but
> for me it's not political.
>
> Am I wrong when I think this desire is particularly European in
> nature? I'm so Open Market driven, especially when it comes to
> technology, that I hardly seem to understand this oter POV. However, I
> am interested.
One nice example. Korg 1212 i/o, worked under win98, doesn't under winXP
because korg does not provide support for it. There is an alsa driver
for it now(and specs), so basically the life of that card is extended to
eternity.
There are more such damn good reasons for open source drivers. People
just don't shout too loud. :)
>
> >
> > Of course I would be pretty annoyed if they just drop Linux completely,
> > for the same reasons as others in this thread - they have a relationship
> > with the community at this point. But I don't think they would be that
> > stupid. After all pissing off hundreds of potential customers is just
> > as bad an idea as giving valuable IP to the competition.
> >
>
> Darn straight. However how did Marek end up being an RME customer when
> there was (as far as I know) never any support for this device under
> Linux, nor anyone even really saying there would be?
Actually not quite, it seemed as if there would be support, Thomas
wanted to do the driver. I just invested too much trust in RME. My
fault.
> In my case I Was
> told that supporting the HDSP 9652 would be a non-issue based on the
> DigiFace working. It turned out to be true, but then again it took
> about a year to become really useful to me, and even today doesn't
> work as well as it does under Windows. How did he end up with this
> device and in this position?
>
> I somehow don't think this is RME's fault...
If RME did the drivers for your HDSP 9652 then you could directly
contact them and ask them for support. I'm sure Thomas would help you
aswell if he had the card, and that's the problem. In such case claiming
that they do support alsa is just plain unfair.
Marek
I haven't posted anything in a while, but I'm sure some of you remember
I made a few claims over the summer. Fear not, things are moving along.
Anyhoo, I had a spark of inspiration and banged out a little sort of folk tune
tracked with ardour. Audacity as a front end for LAME. Still getting my ears
calibrated to a subpar monitoring system so forgive the buried vox and any
tubbyness.
4 tracks.
1 scratch guitar & vocal (the limiting factor)
1 bassline
1 vox overdub
1 keyboard
http://65.125.227.61
click the title header for a link
l8r
J
Hi all:
I've been thinking some more about a prototyping/development board (not
a production board) for a free open multi-channel firewire audio interface.
The objective would be to keep initial development time and costs down
even at the expense of pushing component costs slightly up.
Here are my very rough, version 0, not-fully-thought-out thoughts:
~ Use off-the-shelf asics for the firewire link and physical layers
~ Use a small-ish xilinx spartan 3 fpga for the rest of the "signal
path" logic
~ Use a microchip dsPIC for everything that's off the "signal path"
~ Leave A/D, DA converters (or dig audio I/O) etc entirely off the board:
Just provide headers for adding them on a sub-board later.
There's a block diagram here:
http://www.sjenkins.pwp.blueyonder.co.uk/fwboard/block01.png
Some notes:
1. The smaller spartan 3 fpgas are supported by the free, downloadable ISE
WebPACK software.
2. The PCI block in the fpga doesn't need to be that fancy or versatile.
It just
needs to handle the one TI component fast enough to get data in and out of
its FIFOs on time plus the occasional (much less time-critical) interactions
between the dsPIC and the link layer. It doesn't need to do this stuff
as fast
as possible - there's nothing else on the PCI bus to contend the bandwidth -
it just needs to do it fast enough.
3. The dsPIC never, ever touches the audio data. The converter interface
engine directly handles all transfers between the link-layer fifos and
its own
buffering. It also directly handles any other time-critical interactions
with
the link layer.
4. The dsPIC does everything else: It...
~ stores and programs the fpga configuration data
~ performs all non-time-critical interactions with the link layer and, via
the link layer, with the driver.
~ initialises the converter interface engine ready for whatever formats of
audio I/O may be about to start
~ stores user configuration data
~ handles any LEDS, switches, pots, encoders, LCDs or whatever might
go on an interface front panel.
~ does any non-time-critical control of an analog I/O subboard. (eg if
analog
monitoring were implemented the dsPIC would do the necessary switching).
~ could handle a first-cut implementation of MIDI, although this might
better be migrated to the fpga.
Comments?
Cheers
Simon
I'm proud to announce a new stable release of Hydrogen Drum Machine!!
Features:
__General__
* Very user-friendly, modular, fast and intuitive graphical interface based
on QT 3.
* Sample-based stereo audio engine, with import of sound samples in .wav, .au
and .aiff formats.
* Support of samples in compressed FLAC file.
__Sequencer and mixer__
* Pattern-based sequencer, with unlimited number of patterns and ability to
chain patterns into a song.
* Up to 64 ticks per pattern with individual level per event and variable
pattern length.
* 32 instrument tracks with volume, mute, solo, pan capabilities.
* Multi layer support for instruments (up to 16 samples for each instrument).
* Ability to import/export song files.
* Unique human velocity, human time and swing functions.
* Multiple patterns playing at once.
__Other__
* JACK, ALSA and OSS audio drivers
* ALSA MIDI input with assignable midi-in channel (1..16, ALL).
* Import/export of drumkits.
* Export song to wav file.
* Export song to midi file.
Changes:
* New ALSA driver
* New french tutorial and manual page (thanks to Pierre 'AlSim' Chapuis)
* Bug fix
Download:
http://hydrogen.sourceforge.net
Vote hydrogen at the italian open source contest!
http://hydrogen.sourceforge.net/HowToVote.html
Happy drumming! :^)
--
Alessandro <Comix> Cominu
http://hydrogen.sf.net
e-mail: comix(a)despammed.com
Icq: 116354077
Linux User # 203765
Along with Common C++, I also made available the first release of the
new and much improved stand-alone (no longer requires GNU Common C++)
version of the GNU Common C++ Audio class framework; "ccaudio2". This
new framework, in addition to being more portable and fully endian aware
than it's predecessor (it builds and runs on platforms as varies as
GNU/Linux, various BSD's, OSX, and W32) also includes a new stand-alone
utility, "audiotool", which can do various basic manipulations with
audio files, and a revised system for supporting audio codecs as
plugins. ccAudio2 still needs additional work, particularly in support
of .mp3 and .ogg audio containers, and in getting additional codecs working.
We also had a w32 installer built using GNU GPL licensed "inno setup"
builder which installs all three class libraries together, along with a
new class reference manual, for those using a freedom challenged platform.
The one place all these things can be found together at the moment is:
http://sourceforge.net/project/showfiles.php?group_id=1523&package_id=41672…