No date as been suggested, other than "soon".  There is one outstading 
major issue we have not resolved -- 554//560 whic are aspets of the same 
deep issue.  Plus a few less important ones.

==John


On Mon, 8 Feb 2016, Rory Walsh wrote:

> I think the last release was at the end of September.There have been some
> great improvements made since then!
> 

I think one of the main roadblocks is that we want to get a Windows64 package ready as well. Not sure
how that is at the moment.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
> 
> Soon is good enough for me. 
> 
> On 8 February 2016 at 14:26, jpff  wrote:
> No date as been suggested, other than "soon".  There is one outstading major issue we have not resolved -- 554//560 whic are aspets of the same deep issue.  Plus a few less important ones.
> 
> ==John
> 
> 
> 
> On Mon, 8 Feb 2016, Rory Walsh wrote:
> 
> I think the last release was at the end of September.There have been some
> great improvements made since then!
> 
> 

Can you provide a Csound + Cabbage installer for Windows then? We could release that (instead of a Csound + CsoundQT).


========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
> 
> As it stands, thanks to the work of Steven, it's pretty trivial to create a 64bit version for Windows. I have to double check, but as far as I can remember his MSYS2 build is not missing much from the current Windows package. In fact, his MSYS2 build will also generate 32bit binaries too. I'm happily using them for both my Cabbage packages. I can easily throw together an installer for Csound64. But I'm afraid I don't have time to work on building a 64bit version of CsoundQT.   
> 
> On 8 February 2016 at 16:17, Victor Lazzarini  wrote:
> I think one of the main roadblocks is that we want to get a Windows64 package ready as well. Not sure
> how that is at the moment.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
> >
> > Soon is good enough for me.
> >
> > On 8 February 2016 at 14:26, jpff  wrote:
> > No date as been suggested, other than "soon".  There is one outstading major issue we have not resolved -- 554//560 whic are aspets of the same deep issue.  Plus a few less important ones.
> >
> > ==John
> >
> >
> >
> > On Mon, 8 Feb 2016, Rory Walsh wrote:
> >
> > I think the last release was at the end of September.There have been some
> > great improvements made since then!
> >
> >
> >

WinXound does not make the cut for a realtime-capable IDE, as it does not have API integration, etc.
We would need CsoundQT then.

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Feb 2016, at 12:57, Rory Walsh  wrote:
> 
> I'd rather go with WinXound and Csound. I would like to continue to distribute Cabbage outside of the main Csound project because I release newer versions of Cabbage a lot more frequently than Csound releases. So if I release a bug fix for Cabbage I won't be able to update the Csound installer that it ships with until the next release date. I just think it's cleaner to distribute it separately. I won't have to build WinXound as it doesn't use the Csound API. So any version of WinXound will run any version of Csound. What do you think? 
> 
> On 9 February 2016 at 08:21, Victor Lazzarini  wrote:
> Can you provide a Csound + Cabbage installer for Windows then? We could release that (instead of a Csound + CsoundQT).
> 
> 
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
> >
> > As it stands, thanks to the work of Steven, it's pretty trivial to create a 64bit version for Windows. I have to double check, but as far as I can remember his MSYS2 build is not missing much from the current Windows package. In fact, his MSYS2 build will also generate 32bit binaries too. I'm happily using them for both my Cabbage packages. I can easily throw together an installer for Csound64. But I'm afraid I don't have time to work on building a 64bit version of CsoundQT.
> >
> > On 8 February 2016 at 16:17, Victor Lazzarini  wrote:
> > I think one of the main roadblocks is that we want to get a Windows64 package ready as well. Not sure
> > how that is at the moment.
> > ========================
> > Dr Victor Lazzarini
> > Dean of Arts, Celtic Studies and Philosophy,
> > Maynooth University,
> > Maynooth, Co Kildare, Ireland
> > Tel: 00 353 7086936
> > Fax: 00 353 1 7086952
> >
> > > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
> > >
> > > Soon is good enough for me.
> > >
> > > On 8 February 2016 at 14:26, jpff  wrote:
> > > No date as been suggested, other than "soon".  There is one outstading major issue we have not resolved -- 554//560 whic are aspets of the same deep issue.  Plus a few less important ones.
> > >
> > > ==John
> > >
> > >
> > >
> > > On Mon, 8 Feb 2016, Rory Walsh wrote:
> > >
> > > I think the last release was at the end of September.There have been some
> > > great improvements made since then!
> > >
> > >
> > >
> >

A 64-bit build certainly benefits me as I can then run a 64-bit JVM to
run Blue.  For Java and Python, I imagine it's a pain to have both a
32-bit and 64-bit runtime installed.

I think from the experiences of getting Csound building with MSYS2,
both 32-bit and 64-bit, it seems like it shouldn't be difficult to get
CsoundQT building.  It'd be nice as a long-term goal to have a
PKGBUILD script working to both build Csound and CsoundQT, which would
leverage pacman to download all dependencies to build and install the
system for a developer.  That would make it fairly easy then to fully
automate everything for building a Csound installer.

On Tue, Feb 9, 2016 at 9:13 AM, Rory Walsh  wrote:
> The question is why we need a 64bit build for Windows at all. The only
> Csound frontend that I can think of to benefit from it would be the csound~
> object in Max. But the last time I looked it wasn't possible to build 64-bit
> objects for Max/MSP using GCC.
>
> Anyone building 64bit applications can easily build it themselves thanks to
> Steven's work with MSYS2.
>
> On 9 February 2016 at 13:03, Victor Lazzarini 
> wrote:
>>
>> WinXound does not make the cut for a realtime-capable IDE, as it does not
>> have API integration, etc.
>> We would need CsoundQT then.
>>
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 9 Feb 2016, at 12:57, Rory Walsh  wrote:
>> >
>> > I'd rather go with WinXound and Csound. I would like to continue to
>> > distribute Cabbage outside of the main Csound project because I release
>> > newer versions of Cabbage a lot more frequently than Csound releases. So if
>> > I release a bug fix for Cabbage I won't be able to update the Csound
>> > installer that it ships with until the next release date. I just think it's
>> > cleaner to distribute it separately. I won't have to build WinXound as it
>> > doesn't use the Csound API. So any version of WinXound will run any version
>> > of Csound. What do you think?
>> >
>> > On 9 February 2016 at 08:21, Victor Lazzarini 
>> > wrote:
>> > Can you provide a Csound + Cabbage installer for Windows then? We could
>> > release that (instead of a Csound + CsoundQT).
>> >
>> >
>> > ========================
>> > Dr Victor Lazzarini
>> > Dean of Arts, Celtic Studies and Philosophy,
>> > Maynooth University,
>> > Maynooth, Co Kildare, Ireland
>> > Tel: 00 353 7086936
>> > Fax: 00 353 1 7086952
>> >
>> > > On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
>> > >
>> > > As it stands, thanks to the work of Steven, it's pretty trivial to
>> > > create a 64bit version for Windows. I have to double check, but as far as I
>> > > can remember his MSYS2 build is not missing much from the current Windows
>> > > package. In fact, his MSYS2 build will also generate 32bit binaries too. I'm
>> > > happily using them for both my Cabbage packages. I can easily throw together
>> > > an installer for Csound64. But I'm afraid I don't have time to work on
>> > > building a 64bit version of CsoundQT.
>> > >
>> > > On 8 February 2016 at 16:17, Victor Lazzarini
>> > >  wrote:
>> > > I think one of the main roadblocks is that we want to get a Windows64
>> > > package ready as well. Not sure
>> > > how that is at the moment.
>> > > ========================
>> > > Dr Victor Lazzarini
>> > > Dean of Arts, Celtic Studies and Philosophy,
>> > > Maynooth University,
>> > > Maynooth, Co Kildare, Ireland
>> > > Tel: 00 353 7086936
>> > > Fax: 00 353 1 7086952
>> > >
>> > > > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
>> > > >
>> > > > Soon is good enough for me.
>> > > >
>> > > > On 8 February 2016 at 14:26, jpff  wrote:
>> > > > No date as been suggested, other than "soon".  There is one
>> > > > outstading major issue we have not resolved -- 554//560 whic are aspets of
>> > > > the same deep issue.  Plus a few less important ones.
>> > > >
>> > > > ==John
>> > > >
>> > > >
>> > > >
>> > > > On Mon, 8 Feb 2016, Rory Walsh wrote:
>> > > >
>> > > > I think the last release was at the end of September.There have been
>> > > > some
>> > > > great improvements made since then!
>> > > >
>> > > >
>> > > >
>> > >
>> >
>

I think as Steven does that a 64 bit build of Csound is necessary, and
more so than the 32 bit build. The 64 bit CPU architecture is now the
norm and Csound will benefit from this in many ways on all platforms.

About CsoundQt or Cabbage or any other front end, I think that it
should be up to the authors of such systems whether they want to
maintain them within the Csound repository or not. But if they do, the
build should be managed as part of the regular Csound build system.

Csound is now arguably the most powerful Music N system, but this
advantage could be lost if Csound becomes too difficult to maintain or
to build.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Tue, Feb 9, 2016 at 9:29 AM, Rory Walsh  wrote:
> I was gong to suggest consolidating CsoundQT into the main Csound package,
> but I think this is a better idea.
>
> On 9 February 2016 at 14:21, Steven Yi  wrote:
>>
>> A 64-bit build certainly benefits me as I can then run a 64-bit JVM to
>> run Blue.  For Java and Python, I imagine it's a pain to have both a
>> 32-bit and 64-bit runtime installed.
>>
>> I think from the experiences of getting Csound building with MSYS2,
>> both 32-bit and 64-bit, it seems like it shouldn't be difficult to get
>> CsoundQT building.  It'd be nice as a long-term goal to have a
>> PKGBUILD script working to both build Csound and CsoundQT, which would
>> leverage pacman to download all dependencies to build and install the
>> system for a developer.  That would make it fairly easy then to fully
>> automate everything for building a Csound installer.
>>
>> On Tue, Feb 9, 2016 at 9:13 AM, Rory Walsh  wrote:
>> > The question is why we need a 64bit build for Windows at all. The only
>> > Csound frontend that I can think of to benefit from it would be the
>> > csound~
>> > object in Max. But the last time I looked it wasn't possible to build
>> > 64-bit
>> > objects for Max/MSP using GCC.
>> >
>> > Anyone building 64bit applications can easily build it themselves thanks
>> > to
>> > Steven's work with MSYS2.
>> >
>> > On 9 February 2016 at 13:03, Victor Lazzarini 
>> > wrote:
>> >>
>> >> WinXound does not make the cut for a realtime-capable IDE, as it does
>> >> not
>> >> have API integration, etc.
>> >> We would need CsoundQT then.
>> >>
>> >> ========================
>> >> Dr Victor Lazzarini
>> >> Dean of Arts, Celtic Studies and Philosophy,
>> >> Maynooth University,
>> >> Maynooth, Co Kildare, Ireland
>> >> Tel: 00 353 7086936
>> >> Fax: 00 353 1 7086952
>> >>
>> >> > On 9 Feb 2016, at 12:57, Rory Walsh  wrote:
>> >> >
>> >> > I'd rather go with WinXound and Csound. I would like to continue to
>> >> > distribute Cabbage outside of the main Csound project because I
>> >> > release
>> >> > newer versions of Cabbage a lot more frequently than Csound releases.
>> >> > So if
>> >> > I release a bug fix for Cabbage I won't be able to update the Csound
>> >> > installer that it ships with until the next release date. I just
>> >> > think it's
>> >> > cleaner to distribute it separately. I won't have to build WinXound
>> >> > as it
>> >> > doesn't use the Csound API. So any version of WinXound will run any
>> >> > version
>> >> > of Csound. What do you think?
>> >> >
>> >> > On 9 February 2016 at 08:21, Victor Lazzarini
>> >> > 
>> >> > wrote:
>> >> > Can you provide a Csound + Cabbage installer for Windows then? We
>> >> > could
>> >> > release that (instead of a Csound + CsoundQT).
>> >> >
>> >> >
>> >> > ========================
>> >> > Dr Victor Lazzarini
>> >> > Dean of Arts, Celtic Studies and Philosophy,
>> >> > Maynooth University,
>> >> > Maynooth, Co Kildare, Ireland
>> >> > Tel: 00 353 7086936
>> >> > Fax: 00 353 1 7086952
>> >> >
>> >> > > On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
>> >> > >
>> >> > > As it stands, thanks to the work of Steven, it's pretty trivial to
>> >> > > create a 64bit version for Windows. I have to double check, but as
>> >> > > far as I
>> >> > > can remember his MSYS2 build is not missing much from the current
>> >> > > Windows
>> >> > > package. In fact, his MSYS2 build will also generate 32bit binaries
>> >> > > too. I'm
>> >> > > happily using them for both my Cabbage packages. I can easily throw
>> >> > > together
>> >> > > an installer for Csound64. But I'm afraid I don't have time to work
>> >> > > on
>> >> > > building a 64bit version of CsoundQT.
>> >> > >
>> >> > > On 8 February 2016 at 16:17, Victor Lazzarini
>> >> > >  wrote:
>> >> > > I think one of the main roadblocks is that we want to get a
>> >> > > Windows64
>> >> > > package ready as well. Not sure
>> >> > > how that is at the moment.
>> >> > > ========================
>> >> > > Dr Victor Lazzarini
>> >> > > Dean of Arts, Celtic Studies and Philosophy,
>> >> > > Maynooth University,
>> >> > > Maynooth, Co Kildare, Ireland
>> >> > > Tel: 00 353 7086936
>> >> > > Fax: 00 353 1 7086952
>> >> > >
>> >> > > > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
>> >> > > >
>> >> > > > Soon is good enough for me.
>> >> > > >
>> >> > > > On 8 February 2016 at 14:26, jpff  wrote:
>> >> > > > No date as been suggested, other than "soon".  There is one
>> >> > > > outstading major issue we have not resolved -- 554//560 whic are
>> >> > > > aspets of
>> >> > > > the same deep issue.  Plus a few less important ones.
>> >> > > >
>> >> > > > ==John
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > > On Mon, 8 Feb 2016, Rory Walsh wrote:
>> >> > > >
>> >> > > > I think the last release was at the end of September.There have
>> >> > > > been
>> >> > > > some
>> >> > > > great improvements made since then!
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >
>> >
>

Just my 2c on this.
Since Cabbage includes a csound.exe, it can potentially create hard to
find errors for an end user. As happened this week for a student in my
class. When running Csound from the commandline, he got an error about
a missing dll (libgcc_s_seh-1.dll), and we plundered quite a bit
before resolving the issue. He also had Cabbage (32 bit) installed,
and I tried to rename the Cabbage dir to eliminate any interaction
between the two. Still the same error. In the end I had him rename the
Csound6 dir and try to run Csound on the command line, and the csound
command could still be found. At that point I realized there must be
yet another version of Csound lying around somewhere, and indeed, he
also had Cabbage64.
I think that if such a thing occurs on an inexperienced user's system
and they have no help sorting it our, the result might be that the
user decides Csound "does not work". So it would be very valuable if
the packaging we choose minimize the potential for such random
interaction between different Csound versions on the same system.

2016-02-09 13:57 GMT+01:00 Rory Walsh :
> I'd rather go with WinXound and Csound. I would like to continue to
> distribute Cabbage outside of the main Csound project because I release
> newer versions of Cabbage a lot more frequently than Csound releases. So if
> I release a bug fix for Cabbage I won't be able to update the Csound
> installer that it ships with until the next release date. I just think it's
> cleaner to distribute it separately. I won't have to build WinXound as it
> doesn't use the Csound API. So any version of WinXound will run any version
> of Csound. What do you think?
>
> On 9 February 2016 at 08:21, Victor Lazzarini 
> wrote:
>>
>> Can you provide a Csound + Cabbage installer for Windows then? We could
>> release that (instead of a Csound + CsoundQT).
>>
>>
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
>> >
>> > As it stands, thanks to the work of Steven, it's pretty trivial to
>> > create a 64bit version for Windows. I have to double check, but as far as I
>> > can remember his MSYS2 build is not missing much from the current Windows
>> > package. In fact, his MSYS2 build will also generate 32bit binaries too. I'm
>> > happily using them for both my Cabbage packages. I can easily throw together
>> > an installer for Csound64. But I'm afraid I don't have time to work on
>> > building a 64bit version of CsoundQT.
>> >
>> > On 8 February 2016 at 16:17, Victor Lazzarini 
>> > wrote:
>> > I think one of the main roadblocks is that we want to get a Windows64
>> > package ready as well. Not sure
>> > how that is at the moment.
>> > ========================
>> > Dr Victor Lazzarini
>> > Dean of Arts, Celtic Studies and Philosophy,
>> > Maynooth University,
>> > Maynooth, Co Kildare, Ireland
>> > Tel: 00 353 7086936
>> > Fax: 00 353 1 7086952
>> >
>> > > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
>> > >
>> > > Soon is good enough for me.
>> > >
>> > > On 8 February 2016 at 14:26, jpff  wrote:
>> > > No date as been suggested, other than "soon".  There is one outstading
>> > > major issue we have not resolved -- 554//560 whic are aspets of the same
>> > > deep issue.  Plus a few less important ones.
>> > >
>> > > ==John
>> > >
>> > >
>> > >
>> > > On Mon, 8 Feb 2016, Rory Walsh wrote:
>> > >
>> > > I think the last release was at the end of September.There have been
>> > > some
>> > > great improvements made since then!
>> > >
>> > >
>> > >
>> >
>
>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://flyndresang.no/

... that was on windows btw...

2016-02-10 9:21 GMT+01:00 Oeyvind Brandtsegg :
> Just my 2c on this.
> Since Cabbage includes a csound.exe, it can potentially create hard to
> find errors for an end user. As happened this week for a student in my
> class. When running Csound from the commandline, he got an error about
> a missing dll (libgcc_s_seh-1.dll), and we plundered quite a bit
> before resolving the issue. He also had Cabbage (32 bit) installed,
> and I tried to rename the Cabbage dir to eliminate any interaction
> between the two. Still the same error. In the end I had him rename the
> Csound6 dir and try to run Csound on the command line, and the csound
> command could still be found. At that point I realized there must be
> yet another version of Csound lying around somewhere, and indeed, he
> also had Cabbage64.
> I think that if such a thing occurs on an inexperienced user's system
> and they have no help sorting it our, the result might be that the
> user decides Csound "does not work". So it would be very valuable if
> the packaging we choose minimize the potential for such random
> interaction between different Csound versions on the same system.
>
> 2016-02-09 13:57 GMT+01:00 Rory Walsh :
>> I'd rather go with WinXound and Csound. I would like to continue to
>> distribute Cabbage outside of the main Csound project because I release
>> newer versions of Cabbage a lot more frequently than Csound releases. So if
>> I release a bug fix for Cabbage I won't be able to update the Csound
>> installer that it ships with until the next release date. I just think it's
>> cleaner to distribute it separately. I won't have to build WinXound as it
>> doesn't use the Csound API. So any version of WinXound will run any version
>> of Csound. What do you think?
>>
>> On 9 February 2016 at 08:21, Victor Lazzarini 
>> wrote:
>>>
>>> Can you provide a Csound + Cabbage installer for Windows then? We could
>>> release that (instead of a Csound + CsoundQT).
>>>
>>>
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>> > On 8 Feb 2016, at 16:23, Rory Walsh  wrote:
>>> >
>>> > As it stands, thanks to the work of Steven, it's pretty trivial to
>>> > create a 64bit version for Windows. I have to double check, but as far as I
>>> > can remember his MSYS2 build is not missing much from the current Windows
>>> > package. In fact, his MSYS2 build will also generate 32bit binaries too. I'm
>>> > happily using them for both my Cabbage packages. I can easily throw together
>>> > an installer for Csound64. But I'm afraid I don't have time to work on
>>> > building a 64bit version of CsoundQT.
>>> >
>>> > On 8 February 2016 at 16:17, Victor Lazzarini 
>>> > wrote:
>>> > I think one of the main roadblocks is that we want to get a Windows64
>>> > package ready as well. Not sure
>>> > how that is at the moment.
>>> > ========================
>>> > Dr Victor Lazzarini
>>> > Dean of Arts, Celtic Studies and Philosophy,
>>> > Maynooth University,
>>> > Maynooth, Co Kildare, Ireland
>>> > Tel: 00 353 7086936
>>> > Fax: 00 353 1 7086952
>>> >
>>> > > On 8 Feb 2016, at 15:57, Rory Walsh  wrote:
>>> > >
>>> > > Soon is good enough for me.
>>> > >
>>> > > On 8 February 2016 at 14:26, jpff  wrote:
>>> > > No date as been suggested, other than "soon".  There is one outstading
>>> > > major issue we have not resolved -- 554//560 whic are aspets of the same
>>> > > deep issue.  Plus a few less important ones.
>>> > >
>>> > > ==John
>>> > >
>>> > >
>>> > >
>>> > > On Mon, 8 Feb 2016, Rory Walsh wrote:
>>> > >
>>> > > I think the last release was at the end of September.There have been
>>> > > some
>>> > > great improvements made since then!
>>> > >
>>> > >
>>> > >
>>> >
>>
>>
>
>
>
> --
>
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
>
> http://www.partikkelaudio.com/
> http://soundcloud.com/brandtsegg
> http://flyndresang.no/
> http://soundcloud.com/t-emp



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://flyndresang.no/