Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DAWproject: Open exchange format for DAWs

github.com

Post reply on HN
Print view View original

21–30 of 93 posts

Re: DAWproject: Open exchange format for DAWs

#21

Post by londons_explore »

gravitronic wrote: post #17
elihu wrote: post #16

One thing I'd like to see is native support for some notion of pitch other than 12-tone equal temperament. Looking at their example, I see this: ...which looks like it's basically just a representation of the underlying midi. One way they could represent other pitches is for "key" to allow a floating point value rather than an integer. So, for instance, 65.5 would be a quarter-tone (50 cents) above note 65. According…

At this layer of note information, fact is the data will be either sent to a MIDI device or a plugin as a MIDI event, so you might as well keep it in the native format and not convert to a frequency.

I feel like we're only months/years away from software and file formats being obsolete for this for this sort of thing, and instead songs are composed by humming a tune to ChatGPT and have it add all the other instruments, some nice vocals, and output the MP3.

If you want to make changes, you give ChatGPT the MP3 file and say "switch out the trumpet for a piano and make the singer a guy".

Re: DAWproject: Open exchange format for DAWs

#22

Post by thrtythreeforty »

conradfr wrote: post #20
CharlesW wrote: post #19

If the goal is widespread industry adoption, I'd recommend the approach of extending a professional, standards-based interchange format already supported by major DAWs: AAF. https://en.wikipedia.org/wiki/Advanced_Authoring_Format https://www.loc.gov/preservation/digital/formats/fdd/fdd0000...

The README extensively references AAF.

Indeed. This is a Bitwig project. I think the default for Bitwig engineering should be "assume extreme competence."

Re: DAWproject: Open exchange format for DAWs

#24

Post by steve1977 »

lagniappe wrote: post #15
ckbishop wrote: post #9

Bitwig is quickly becoming my favorite DAW. Big fan of how they develop software.

Bitwig knocked it out of the park coming out the gate with Linux support. Can't say I'm surprised though, it's made by the original team that made Ableton Live.

Bitwig was founded by people who were previously working for Ableton. Some longer, some less long.

But they were not the original team that made Live, that is a bit misleading.

Re: DAWproject: Open exchange format for DAWs

#26

Post by johnnyworker »

londons_explore wrote: post #21
gravitronic wrote: post #17

Earlier quoted context omitted.

At this layer of note information, fact is the data will be either sent to a MIDI device or a plugin as a MIDI event, so you might as well keep it in the native format and not convert to a frequency.

I feel like we're only months/years away from software and file formats being obsolete for this for this sort of thing, and instead songs are composed by humming a tune to ChatGPT and have it add all the other instruments, some nice vocals, and output the MP3. If you want to make changes, you give ChatGPT the MP3 file and say "switch out the trumpet for a piano and make the singer a guy".

As someone who makes music as a hobby that's about as enticing as outsourcing sex. I don't care if the machine can do it better.

Re: DAWproject: Open exchange format for DAWs

#27

Post by unshavedyak »

johnnyworker wrote: post #26
londons_explore wrote: post #21

Earlier quoted context omitted.

I feel like we're only months/years away from software and file formats being obsolete for this for this sort of thing, and instead songs are composed by humming a tune to ChatGPT and have it add all the other instruments, some nice vocals, and output the MP3. If you want to make changes, you give ChatGPT the MP3 file and say "switch out the trumpet for a piano and make the singer a guy".

As someone who makes music as a hobby that's about as enticing as outsourcing sex. I don't care if the machine can do it better.

That's an interesting point. I don't get much value from art personally (not that i don't see why people value it, i do!), so the idea of AI generated art isn't disgusting to me.

Music however.. i adore music. A big (but not essential) thing i love about music is the story that got the artist to that point. Pain, joy, emotion is transferred. Yea, often it's not essential so maybe AI Music has a place in my life, but easily 60% of my music is loved partly, if not heavily, because of the emotions that got the artist to that point.

I too am not interested in outsourcing this.

Re: DAWproject: Open exchange format for DAWs

#28

Post by IndySun »

lagniappe wrote: post #15
ckbishop wrote: post #9

Bitwig is quickly becoming my favorite DAW. Big fan of how they develop software.

Bitwig knocked it out of the park coming out the gate with Linux support. Can't say I'm surprised though, it's made by the original team that made Ableton Live.

"Bitwig ... founded by Claes Johanson, Pablo Sara, Nicholas Allen and Volker Schumacher. Our experience in the computer music software industry includes Ableton, where we were all part of the development team behind the successful music software Live ... "

Re: DAWproject: Open exchange format for DAWs

#29

Post by unshavedyak »

sctb wrote: post #18
dmicah wrote: post #11

It would be nice if Bitwig would support existing plug-ins formats like AU.

Do you encounter many AU-only plugins? From what I can tell, the limitations of VST/AU/AAX are more pressing and Bitwig are working to address that with CLAP: https://u-he.com/community/clap .

Man i hope more people (plugin developers too) embrace CLAP or something open. I'm writing a Rust program and i really want to allow for Modart's Pianoteq plugin and VST just makes it feel so difficult.
Post reply on HN