Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Music Media Software Linux

New MusE Release, A Step Toward The Linux Studio 250

spamatica writes "In these times when multimedia on Linux seems to be on a roll, it's my pleasure to break the news that one of the most powerful midi/audio sequencers on Linux, MusE, has just had a new release. This release is a major milestone featuring things such as Jack-transport and win32/VST-Instrument support. Moreover it has been much improved concerning usability, stability and functionality. The Linux-based studio is looming ever closer -- in fact, it's here!"
This discussion has been archived. No new comments can be posted.

New MusE Release, A Step Toward The Linux Studio

Comments Filter:
  • Exciting.. (Score:2, Insightful)

    by superhoe ( 736800 )
    .. all I need now is to get my professional audio card to actually work under Linux.
    • Re:Exciting.. (Score:5, Informative)

      by abe ferlman ( 205607 ) <bgtrio@nOspAm.yahoo.com> on Monday July 19, 2004 @08:19AM (#9736825) Homepage Journal
      My Delta 1010 works just fine, as does my Turtle Beach USB MIDI adapter.

      Your Echo Darla, Gina, Layla or RME Hamerfall card would be supported by ALSA as well, among others. Linux audio may have issues, but a lack of professional sound cards that work is not one of them.
      • According to ALSA's own page, they don't support my professional sound card. [aardvarkaudio.com]

        A lack, maybe not, but they don't support everything, and for most people they won't be willing to buy a new card for Linux compatability.

        Also, as another poster here said: we really do want manufacturer drivers, so we have a throat to slit when it fails to work, or when there's some obscure conflict.
        • perhaps someday there will be a sufficiently large market to support a service industry supporting free software drivers and you'll have someone to blame if you need to. Until then we're forced to choose between a company's desire to protect its reputation and the ability to use free software thereby avoiding lockin/no source code/etc. I understand we choose different sides of this divide, but I hope one day we won't have to choose.
        • Re:Exciting.. (Score:5, Insightful)

          by zerblat ( 785 ) <<es.cibuks> <ta> <sanoj>> on Monday July 19, 2004 @09:16AM (#9737156) Homepage
          Actually it's the other way around, Aardvark doesn't support ALSA. Had they supplied the ALSA people with sufficient specs, I'm sure your Q10 would be working in Linux right now. Have you contacted Aardvark and told them that you would be interested in support for ALSA?
        • Re:Exciting.. (Score:3, Insightful)

          by Ricdude ( 4163 )
          As with any OS, you must check the hardware compatibility lists before purchasing hardware and expecting it to work. The point is you *can* buy pro quality cards to work under linux. Whether or not you choose to or not is up to you. Personally, I tend to buy hardware that works on Linux and Windows. I had fun once with a hardware modem that didn't work under Windows until I downloaded the right driver (via Linux). There are very few things that can't work well on both. I make a point of buying hardware
        • Send them an email, ask them to support Linux, etc.
          They don't have to write the driver themselves. Often, a company will sit on their card's specs and not release them to the open source community. This will prevent a free driver to be written.
    • Yeah, I was talking to a sound professional this weekend actually, who has his own studio running mostly on Mac with a few PCs. What's holding Linux back in the studios is (1) lack of familiar professional mixing/software (one app doesn't cut it, they need a whole suite of very full-featured, professional apps and utilities), and (2) hardware support for the piles of miscellaneous equipment that gets used all the time. The newer hardware is all digital, and there are linux drivers for a very small percent
  • Finally, (Score:5, Insightful)

    by Lispy ( 136512 ) on Monday July 19, 2004 @07:24AM (#9736617) Homepage
    I can put my old Atari 1040ST to rest. No, seriously, this is another killerapp that kept some of my friends from switching to Linux so far. I am really curious if it is competitve enough and easy to use for all those Apple switchers.
    • I suspect if it's really that good it'll get ported to OS X anyway, many othr GPL apps of this kind (Think AudaCity) get ported eventually.
    • Re:Finally, (Score:2, Insightful)

      I can put my old Atari 1040ST to rest. No, seriously, this is another killerapp that kept some of my friends from switching to Linux so far.

      I'm curious: you do know that Cubase exists on Windows and Macintosh, right? Heck, you even have the choice of using Cakewalk or DP on those platforms.

      What's this Atari ST nonsense? I can't decide whether you're trolling, or you're such a hysterical Windows and Mac hater that you're willing to not use anything but your Atari until something's available for Linux...
      • Re:Finally, (Score:5, Interesting)

        by Threni ( 635302 ) on Monday July 19, 2004 @07:48AM (#9736709)
        > What's this Atari ST nonsense?

        So you know little about audio software, right? Cubase on the ST was more stable and usable 12 or more years ago than the same software under Windows. I gave up trying to get accurate, fast hihats on my PC, instead using Cakewalk (which is inferior to Cubase in practically every other way). Cubase on the ST is rock solid, with out-of-the-box midi support, and many studios still use it. You're suggesting people upgrade from STs just because they're old? Why? That's just not how things work once you get out of the PC industry. People upgrade because there's a point to it, or because they have to, not just because they can.
        • Cubase on the ST was more stable and usable 12 or more years ago than the same software under Windows. I gave up trying to get accurate, fast hihats on my PC, instead using Cakewalk (which is inferior to Cubase in practically every other way).

          Couple of things...
          Cubase from 12 years ago is nothing like Cubase of today, ST or Windows. They do very different things, although MIDI has always been there. If you want what Cubase offers today, there's no way to get an ST to handle everything it does. You

      • I agree with the poster, I owned an Atari ST and an Amiga, and now both are rusting away in the Garage because everything they can do can be done on modern hardware with modern operating systems faster and better.

        If you really insist on booting your OS off a 720k floppy and waiting another 3 minutes for your application to come up, then being limited to 100k for a sample then who am I to stop you...
        • Re:Finally, (Score:3, Interesting)

          by tolan-b ( 230077 )
          The Atari ST has very low MIDI latency. Also, the OS is on firmare, so you don't have to boot off floppy.
        • limited to 100k for a sample

          Some of us aren't totally enamoured by software synths and samplers. I'd rather use hardware devices (analogue preferably), and just use the computer as a sequencer and patch editor/librarian.

          • If you do that, then why do you need the kind of timing ST owners blather on about? There are outboard sequencers that would do you just fine.
            • If you do that, then why do you need the kind of timing ST owners blather on about? There are outboard sequencers that would do you just fine.

              I don't need anything out of the ordinary when it comes to latency. The main reason I use the ST instead of a hardware sequencer, is the better interaction via mouse, monitor and keyboard. Saying that, I do have an ancient Roland MC-300 sequencer that I use for live stuff (it's a rugged little beastie).

              • I was thinking more along the lines of one of the modern sequencers that can accept sequence data from a PC; edit on a good interface, dump it to the hardware sequencer for timing reasons. But if you want the better interaction, but don't have special timing needs, why not upgrade from the ST?

                I don't know. All my current live stuff is about as far away from sequenced as you can get (improvised, nothing pre-recorded and nothing pre-planned), so it's been a while since I've had to fight with a sequencer.
                • I was thinking more along the lines of one of the modern sequencers

                  I borrowed my brothers Akai MPC a while ago, and it was a very nice piece of equipment. I couldn't justify the cost of one for myself though, as I'd never use half the features. I'm also hopeless at sampling, so I'd end up using third party libraries.

      • Re:Finally, (Score:5, Informative)

        by LizardKing ( 5245 ) on Monday July 19, 2004 @08:05AM (#9736770)

        What's this Atari ST nonsense?

        I still use Steinberg Pro-24 (the forerunner to Cubase) on an Atari ST. It is far more stable than any version of Cubase that I have used on a PC. I don't own a Mac, but I do hear that recent versions of Cubase have been rock solid on that operating system. So if I upgraded that would be they way I'd go. Then again by the time I can afford a decent Mac, Rosegarden (http://www.rosegardenmusic.com/) may have reached a stable release ...

        As for the poster below who talks about booting from a 720Kb floppy, my ST has a SCSI hard drive, and boots in seconds.

        • Amen. I still use Bars and Pipes on the Amiga. Not anywhere near so stable as Pro-24, but it just suits the way I like to work.

          The people saying you should junk the old hardware and software which help you work are idiots. Making music isn't like compiling code - a faster computer doesn't necessarily make you more productive.

          When a person creates, the tools they use are important. Some people like oil paints, some like acrylics. Some people like Pro-24, some like Cakewalk. Some like digital, some like an
      • Re:Finally, (Score:2, Informative)

        by Anonymous Coward
        Timing on the ST had nothing to do with the OS. I'm not sure of the particulars, but the MIDI clock was a Integer mutiple of one of the base hardware clocks, that's why it's rock solid, no rounding of floating point numbers like you get these days.
        The same chip is still being used in brand new broadcast timecode generators right now.
    • I would Band in the Box, a crappy old tool that does what the musician *really* needs. From a usability perspective it may be bad, from a usefulness perspective it is unrivaled
    • I can put my old Atari 1040ST to rest.
      Why should you?
      Now is the time to port MusE to Linux/m68k [linux-m68k.org] on Atari ST! :-)

  • if they made a live distro outof it, then it would help people change. do people want to dump windows before even trying the software: no
  • by Saven Marek ( 739395 ) on Monday July 19, 2004 @07:28AM (#9736629)
    This is where Apple has traditionally worked, and it's been a strong position for them.

    While the market isn't big, it is fiercely loyal and worth money to them. Now that Linux based solutions can compete and strip away that advantage, Linux too will embed itself more concretely in the mindset of Yet Another Subculture.

    Heh. Why would you now spend $50k on a mac recording studio when you can get a Linux based one for the cost of cheap 2nd hand hardware?. Revolutions baby...

    The Nets Biggest Adult Anime Gallery's [sharkfire.net]
    • by proj_2501 ( 78149 ) <mkb@ele.uri.edu> on Monday July 19, 2004 @07:31AM (#9736642) Journal
      well, there are reasons to avoid cheap 2nd hand hardware for a studio. if you can't get low latency or a low noise floor out of your sound card, or if you can't get linux drivers for the card, what's the point in saving money?

      also, there's no ableton live for linux, which is key in my book :)
      • by Anonymous Coward
        oh cripes. 90% of the noise floor in a studio is the equipment before the computer.

        the Mackie mixers that are typical in home studios have almost a 5 db hiss sitting there with all controls potted all the way down. (5db from silence not from the bizzare zero db refrence that is so prevalent in audio.) then you have how your cables are run, the low end microphones you are using as well as the noise levels coming out of the guitar's, effects pedals, the keyboards and synth modules themselves (alesis = high
      • It's still not necessary to spend the big apple-style bucks to build a studio on linux if the software is there. You can buy 24 bit 96 khz four channel audio cards with linux support for under $250 each - I can't remember who makes them, though, because I don't have that kind of money to spend on sound cards anyway :)
        • MAudio [m-audio.com]

          You're probably thinking about Audiophile 2496, or maybe even the Delta 1010LT.
          Still, the "big" Delta 1010 (not the LT) is perhaps better, since it has balanced analog. But it's more expensive (about $600).
    • This is where Apple has traditionally worked, and it's been a strong position for them.

      This may just be my experience, but I've found that in the UK studios are more likely to have PC's than a Mac. however, in the States the opposite appears to be true. I haven't seen an Atari ST in a professional studio since 1996 though ...

    • "Why would you now spend $50k on a mac recording studio when you can get a Linux based one for the cost of cheap 2nd hand hardware?."

      Because the most you will be spending on a Mac Based Recording Studio will *NOT* be in the computer hardware. If you have $50k in a studio, I can guarentee that at most, a tenth of that is going to be on the computer.

      $3k for the highest performing Mac...maybe another $2k for the monitor. Thats $5k right there.

      And its well spent because it works out of the box. I don't kn
  • ardour? (Score:3, Interesting)

    by MancunianMaskMan ( 701642 ) on Monday July 19, 2004 @07:29AM (#9736637)
    anyone know how this compares (quality-wise, cpu-hunger-wise, functionality-wise) to ardour [ardour.org].

    I can't try it out because my pII-233 is a bit weak...

    • Re:ardour? (Score:3, Informative)

      Ardour is a hard disk recorder. Muse is a MIDI sequencer with some support for audio tracks. They are not competitive, but complementary.
    • There is only one tool to compete with: http://www.pgmusic.com/bandbox.htm It is a user-centered product, not for professionals, for musicians. It features everything musicians really need.
    • Ardour is more Pro Tools, sound tweaking tool, as MusE is full audio/midi sequencer. I guess in future Ardour and MusE could be in battle for good meaning, but Ardour is more really for sound tweakage. I'm really getting more and more excited about Linux pro audio, as I have Ice1712 based (ALSA drivers fully support this cipset) sound card from Terratec EWS88MT. It rocks. And Jack and Ardour shows big improvements. Of coarse, there are still long road ahead for fully user friendly Linux audio studio which
    • Muse is comparable with Rosegarden, not with Ardour.

      Muse and Rosegarden are sequencers (MIDI and stuff), while Ardour is a DAW (digital multitrack sound recorder).
  • by Zorilla ( 791636 ) on Monday July 19, 2004 @07:35AM (#9736654)
    We can all troll that Linux still has trouble supporting sound, decent system-wide hardware MIDI beyond KDE's aRTs MIDI (or a really nice software wavetable synth like WinGroove's), more-than-2 channel support for sound, and difficulties playing DVDs and WMV9 systems (which still seems impossible for the video portion even if the WMA2 stream plays), but I think this could be a push for improvements to all of the above.

    (Wow, that was just one sentence)
  • by djcapelis ( 587616 ) on Monday July 19, 2004 @07:46AM (#9736700) Homepage
    The slashdot effect is starting on the poor site and the database only allows 32 connections at one time... so I figured it would be best to post a copy of the news summaries that it digs out of the database: .7 and .7-PRE4 don't have much changed in the way of news. .7-PRE3

    # Configuration and customization

    * Shortcuts for 'arrowing around' in arranger added
    * changed default start behaviour to open default.med template
    * Lots of new icons ;-)
    * A proposal for MusE logo (tell us what you think!)
    * Autodetect of browser for help system

    # MusE general:

    * FluidSynth: added support for drum patches
    * MusE now will not start if RTC is not available.
    * show one more measure in pianoroll and drum editor
    * list editor: implemented input mode for program change messages

    # Fixed bugs:

    * fixed: pitch bend handling and import fixed
    * fixed: 'edit - delete track' hangs MusE - bug
    * fixed: routing for stereo LADSPA plugins used in mono strips
    * fixed: midi import problems
    * auxSend chorusSend and reverbSend enabled in midi mixer strip if corresponding controllers are added
    * implemented 'Add New Controller' in list editor / edit controller
    * midi controller values now saved in .med file
    * updated roland-XP30.idf instrument definition
    * And a number of other bugs fixed (and added?)
    * Also check the TODO for currently known issues. .7-PRE2

    # Custom guis for plugins work again
    # Splash screen
    # LADCCA/LASH support updated
    # Cleaned up shortcuts
    # Single key shortcuts for edit tools
    # Update marker list on tempo change
    # Allow adding markers from the ruler with shift-click
    # Metronom now sends proper note off events
    # Clip list editor deaktivated
    # After loading of template, treat current project as 'untitled'
    # Song format changed due to bugfixes
    # Shortcuts to bug reporting tool and homepage from help menu
    # Updated AboutBox
    # Fixed QT version check in m4/qt.m4
    # And a number of other bugs
    # Check the Changelog for a complete list of changes.
    # Also check the TODO for currently known issues.
  • Me alone? (Score:3, Insightful)

    by ceeam ( 39911 ) on Monday July 19, 2004 @07:53AM (#9736728)
    Who else has read the title as SusE? This miscapitalization is silly.
  • by no longer myself ( 741142 ) on Monday July 19, 2004 @08:03AM (#9736764)
    I've missed messing around with MIDI since I left MS Windows, but this still looks a little too tricky for a convert like me...

    ~~~ Requirements (paraphrased)
    - QT: Qt 3.2.0 or above
    - ALSA 0.9.x or newer (cvs)
    - gcc 3.x.x
    NOTE: you _must_ compile MusE with the same compiler you used to compile QT
    - libsndfile 1.0.1 (current 1.0.4)
    - Linux kernel with rtc (RealTimeClock) driver (device /dev/rtc)
    - JACK
    - fluidsynth-1.0.3 (formerly known as iiwusynth)
    - of course: a soundcard and/or some midi gear
    - (if you compile from cvs:) automake 1.7 and autoconf 2.54

    I don't even know "JACK", and just looking over these things I'd have to update every single one of these requirements except for the ones I don't even have installed in the first place. I guess I won't be installing this for a while... :-(

    Sadly all my boxes have that on-board AC97 audio, and it has no hardware MIDI support at all. Otherwise, ALSA does a great job, and I never needed to configure anything for wave output. Just no MIDI.

    (Side note: I never could get things like TiMIDIty to work right either... Guess, I'm just not quite geeky enough... yet.)
    • Wait till it comes out for your distro. Proprietary software is often written and packaged in the same company and they release nothing until installer etc. etc. is ready. Open source programs are often written and packaged by different persons, and the first person considers the program "released" when the tarball's ready.

      Midi really ought to work though - even if you're not "geeky". What distro are you using?
    • If you happen to be using it or don't mind switching. You just need to set urpmi up to use alternative sources (you should always do this immediately).

      Take a look: rpm.nyvalls.se [nyvalls.se]

      To add this as root type:

      urpmi.addmedia thacs.rpms http://rpm.nyvalls.se/10.0/RPMS with hdlist.cz

      to add PLF and some other useful ones:

      urpmi.org/easyurpmi/ [urpmi.org]

      Looks like thac has already packaged Muse 0.7.0 along with a load of other sound related software. Good stuff. :)

  • Rosegarden (Score:4, Interesting)

    by javilon ( 99157 ) on Monday July 19, 2004 @08:08AM (#9736781) Homepage
    How does Muse compare to Rosegarden [rosegardenmusic.com]?
    • Re:Rosegarden (Score:5, Informative)

      by Chris Cannam ( 8406 ) on Monday July 19, 2004 @09:52AM (#9737338)
      > How does Muse compare to Rosegarden?

      Well, they're both audio and MIDI sequencers for Linux. They both support outboard MIDI gear, native Linux ALSA soft synths, and audio and transport synchronisation through JACK. Both look and feel somewhat like the big sequencers for other platforms. Both use Qt for their GUIs, though Rosegarden also uses the KDE libraries. I happen to think Rosegarden has the more polished GUI, but I'm biased (see disclaimer at bottom).

      Both support arbitrary numbers of MIDI and audio tracks, with audio mixing and routing capabilities. Both support LADSPA effects plugins, of which there are hundreds available free. Both can (with some work!) be made to use VST effects through vstserver [notam02.no]. MusE can host VST instruments with libfst using Wine; either of them can drive VST instruments hosted separately using jack_fst [linuxaudiosystems.com]. None of these VST solutions is currently at all easy to configure and build, but see here for more information [djcj.org]. Rosegarden is implementing the DSSI synth API [sf.net] and will probably ultimately use a DSSI wrapper for VST instruments. Rosegarden can also be run without audio support if you only want MIDI or score, whereas MusE always requires JACK.

      My rather fuzzy impression of the difference in "feel" between them is that MusE feels like it came more from a studio/MIDI gearhead background, Rosegarden more from a composition background. MusE is a bit further ahead with things like instrument plugins, audio routing (send/returns etc) and automation. Rosegarden places a lot more emphasis on the score editor, whereas the one that used to be in MusE was actually removed completely for the 0.7 release.

      Rosegarden is a somewhat bigger and more complicated program than MusE (c 200K lines of code vs 130K LOC), which you may see as good or bad depending on whether the extra code happens to do stuff you want or not. They're both written in C++, should you happen to care.

      On the subject of soundcard support: the usual quick answer is "it's probably supported unless it's FireWire or made by MOTU". In particular the current M-Audio, Terratec and RME semi-pro gear mostly works fine, as well as most consumer cards. The lack of FireWire audio device support currently is a pain though. Anyway, see the ALSA soundcard matrix [alsa-project.org] for detailed information.

      (Disclaimer: I am a Rosegarden developer and, although I track MusE CVS, I have never actually managed to get MusE 0.7 to build because I don't have the right libraries and autotools. So do take all this with a pinch of salt.)

      • Out of curiosity why are MOTU cards not supported? A friend of mine uses a 24-channel I/O card of theirs, and I was just wondering.
  • Yes but does it support loadable and selectable Soundfonts with my SBLive! Value?
  • Yes, but... (Score:4, Funny)

    by Ed Avis ( 5917 ) <ed@membled.com> on Monday July 19, 2004 @08:35AM (#9736909) Homepage
    Does it run on SuSE?
  • My problem with MusE is that it has a Steinberg-style interface. I'm not proficient enough with a MIDI keyboard to use it for any serious work and trying to write a song with Steinberg's and MusE's mouse-based note input facilities is a nightmare.

    Trackers, on the other hand, were designed to be nicely usable with only a keyboard and mouse, but ever since Impulse Tracker died I haven't found one to my liking.

    I know of many trackers for Linux and Windows, but all of them are too unstable, their developme

  • Close, but no cigar (Score:3, Interesting)

    by iamdrscience ( 541136 ) on Monday July 19, 2004 @08:42AM (#9736944) Homepage
    Good MIDI support, sequencers and virtual synths are all great stuff, but there is one hugely crucial element to "the linux studio" that's missing, and that's support for professional sound cards.

    It's always been a bit of a trick to get sound working on Linux, but it's always getting easier too and most desktop oriented distros (i.e. Mandrake, Redhat, Suse) make it no problem in most cases, but there is really zero support for most of the established professional audio interfaces (i.e. Motu, Audigy, etc.). I've had a few friends adventurous to consider playing around with Linux audio programs, but when they ask if their $200 (and up) interfaces don't work and the best I can do is point them to the O'Reilly book on writing Linux drivers, it's (understandably) a real turn-off.

    In summary: If anybody out there has the time and knowledge and is looking for a project, this is a great one. Work on writing drivers for the upper-crust interfaces. I'm sure there are even a few nerds out there willing to lend you their cards so that they can get a driver for it.
    • [...]but there is really zero support for most of the established professional audio interfaces (i.e. Motu, Audigy, etc.).

      The problem is that Motu haven't been willing to release necessary documentation. Audigy? Are you talking about Creative Labs's SoundBlaster Audigy? And using it in the same sentance as professional?

      There is support in ALSA for decent audio hardware from e.g. RME (who have been very supportive of the ALSA developers), M-Audio, Echo and others. The problem is that many of the hardware

    • How is this the problem of the audio application?

      It's definitely a problem for linux audio in general, but it's a little unfair to use it as a point against MusE.
      Are you saying that they should give up until every MOTU card is supported out of the box on Linux?

      Hell, even if SBLive! was the only audio card supported, then this application (and the other audio projects that seem to be maturing these days - JACK, Rosegarden, LADSPA, Ardour, etc) is still a great step forward for Linux audio.

      You're not going
    • A Sound Blaster Audigy is not a pro sound card (and that's a non-issue anyway because ALSA has working drivers for it anyway). A pro sound card is something like an M-Audio Delta 1010[-LT] or an RME Hammerfall which both have working drivers.

      It's a lot of the low-end pro sound cards that aren't supported. Bug the manufacturers about releasing specs to the ALSA developers and maybe that problem will go away.

    • but there is one hugely crucial element to "the linux studio" that's missing, and that's support for professional sound cards

      FWIW I have Audigy up and running, but that's hardly a card I'd call professional. So lets see... ALSA [alsa-project.org] currently supports several RME cards (with ADAT I/O), several M-Audio cards (most of which are 200$ and up) and some cards from SEK'D and Echo, for example. Granted this is not by any means a complete selection of pro audio cards, but you can get a pro card that'll work with Linux i

    • by Lumpy ( 12016 ) on Monday July 19, 2004 @10:36AM (#9737724) Homepage
      I've had a few friends adventurous to consider playing around with Linux audio programs, but when they ask if their $200 (and up) interfaces don't work and the best I can do is point them to the O'Reilly book on writing Linux drivers, it's (understandably) a real turn-off.

      Of course, you're being an ass to them by playing the elitest RTFM! game.

      Linux supports a WIDE range of professional sound recording cards. if you would have actually searched instead of acting like a snide know-it-all to your friends you would have known this....

      Here, I'll help you...

      Alsa sound card matrix. [alsa-project.org]

      it shows support for the Sonorus medi/o and studi/o professional 24 channel recording cards.

      Oh look it supports the RME hammerfall card 52 recording channels at 24bit resolution.

      There are lots more supported, I leave it up to you to find the rest in the link above.

      I strongly suggest you actually learn about the ALSA support of professional soundcards and the PRO MIDI interfaces.... the midiman usb midi devices are also well supported and used extensively by professionals. Handing out advice to people when you do not know the facts only spreads bad information.

      and as always, find out what is supported and then go buy it. buying something at random and then hoping it is supported is always a silly thing to do.

  • This [music123.com] usb midi device to connect your midi keyboard works excellent in Linux. The module is snd-usb-audio. I've done all the midi-type applications (rosegarden, NoteEdit, etc) and this midi/usb works great. Plugged it in and it works.

    Just wanted to make a post in case others might be interested.

    • Just wanted to make a post in case others might be interested.

      Well, in that case: my newest toy, a Korg Triton Extreme [korg.com] works too. It has a built in USB-MIDI interface and you can access the compact flash slot as usb-storage (the EX must be in usb-storage mode). I had to patch usbquirks.h in alsa to get it to work, but the changes have been added to CVS.

      FWIW, I also have a Radium 61 key [maudio.co.uk] and a Midisport [maudio.co.uk] (this device is sold under many names) working just fine in Linux.

      So, yeah, Linux audio isn't that p
  • by theManInTheYellowHat ( 451261 ) on Monday July 19, 2004 @10:03AM (#9737430)
    There is a great deal of work that should be reviewed by anyone concidering Linux sound / video production and I am supprized that someone has not mentioned it yet.

    Planet CCRMA [stanford.edu] is awesome! This is such a good start for everyone who says "I am not geeky enough to get {insert package here} working". I suspect that the FC2 iso's are close to coming out, the ones for FC1 are excelent. You basicly install FC and then there is a kernel iso and an app iso which installs most of the known linux sound apps. The mailing list is also quite active and the people very helpful.

    Strong work from Fernando Lopez-Lezcano!!!

  • by Zebbers ( 134389 ) on Monday July 19, 2004 @10:18AM (#9737579)
    I've used the cakewalk line of programs for years now and it's one of the few reasons I still run windows on one of my boxes....are there any replacements?

    I have a dedicated box for it, so its highly unlikely Id ever switch unless it was as polished as CW.
  • The Linux-based studio is looming ever closer -- in fact, it's here!"

    Great. But why would any pro or semi-pro studio migrate from the ProTools and OS X solution they almost certainly already have?

    I think it's great that Linux supports tools powerful enough that they could conceivably be used to run a recording studio, but realistically I don't expect market penetration to be significant.
  • From the screenshot I see one thing immediately that I absolutely can't stand: little volume knobs that you have to "turn" with the mouse pointer. There cannot be a more lame widget to try to use in a mouse-based user-interface. Sure you can probably use the scroll wheel.

    The entire interface looks cluttered and not well-suited for use along side our current GUI apps. There are reasons why certain things are and aren't done in GUIs. We can't always make our programs look just like the physical objects

All seems condemned in the long run to approximate a state akin to Gaussian noise. -- James Martin