2.0.2 fixup release

There was an error in the source tarball for 2.0.1. This
error did NOT
affect the OS X DMG. 2.0.2 has been released as a correction
for the
error - it does not change any listed fixes for 2.0.1 in any
way.



_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, May 09, 2007 at 04:59:51PM -0400, Paul Davis wrote:
> There was an error in the source tarball for 2.0.1.
This error did NOT
> affect the OS X DMG. 2.0.2 has been released as a
correction for the
> error - it does not change any listed fixes for 2.0.1
in any way.

Just tried 2.0.2. The plugin control panels are working
again,
and everything else looks good so far.

John
_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Paul Davis wrote:
> There was an error in the source tarball for 2.0.1.
This error did NOT
> affect the OS X DMG. 2.0.2 has been released as a
correction for the
> error - it does not change any listed fixes for 2.0.1
in any way.
>
>
>
> _______________________________________________
> ardour-dev mailing list
> ardour-devlists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org
>   
Woooa Yeeeah!

-- 
Check out "The BlueWall Groove"  Myspace
http://www.mysp
ace.com/bluewallgroove

_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2007-05-09 at 16:59 -0400, Paul Davis wrote:
> There was an error in the source tarball for 2.0.1.
This error did NOT
> affect the OS X DMG. 2.0.2 has been released as a
correction for the
> error - it does not change any listed fixes for 2.0.1
in any way.

Has there been a change in how cpus are detected during the
build
process? With the same spec file I used with 2.0.0 for
building Planet
CCRMA packages I get this (on 32 bit fc6):

g++ -c -fPIC libs/ardour/sse_functions_64bit.s -o
libs/ardour/sse_functions_64bit.os
libs/ardour/sse_functions_64bit.s: Assembler messages:
libs/ardour/sse_functions_64bit.s:37: Error: bad register
name `%rbp'
libs/ardour/sse_functions_64bit.s:38: Error: bad register
name `%rsp'
libs/ardour/sse_functions_64bit.s:41: Error: bad register
name `%rbx'
libs/ardour/sse_functions_64bit.s:42: Error: bad register
name `%rdi'
libs/ardour/sse_functions_64bit.s:43: Error: bad register
name `%rsi'
libs/ardour/sse_functions_64bit.s:46: Error: bad register
name `%rdx'
libs/ardour/sse_functions_64bit.s:51: Error: bad register
name `%rdi'

(I did not get to try with 2.0.1... 
-- Fernando


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2007-05-09 at 18:42 -0700, Fernando Lopez-Lezcano
wrote:
> On Wed, 2007-05-09 at 16:59 -0400, Paul Davis wrote:
> > There was an error in the source tarball for
2.0.1. This error did NOT
> > affect the OS X DMG. 2.0.2 has been released as a
correction for the
> > error - it does not change any listed fixes for
2.0.1 in any way.
> 
> Has there been a change in how cpus are detected during
the build
> process? With the same spec file I used with 2.0.0 for
building Planet
> CCRMA packages I get this (on 32 bit fc6):
> 
> g++ -c -fPIC libs/ardour/sse_functions_64bit.s -o
> libs/ardour/sse_functions_64bit.os
> libs/ardour/sse_functions_64bit.s: Assembler messages:
> libs/ardour/sse_functions_64bit.s:37: Error: bad
register name `%rbp'
> libs/ardour/sse_functions_64bit.s:38: Error: bad
register name `%rsp'
> libs/ardour/sse_functions_64bit.s:41: Error: bad
register name `%rbx'
> libs/ardour/sse_functions_64bit.s:42: Error: bad
register name `%rdi'
> libs/ardour/sse_functions_64bit.s:43: Error: bad
register name `%rsi'
> libs/ardour/sse_functions_64bit.s:46: Error: bad
register name `%rdx'
> libs/ardour/sse_functions_64bit.s:51: Error: bad
register name `%rdi'
> 
> (I did not get to try with 2.0.1... 

there should be no change. it looks as if its picked the
wrong
sse_functions file. puzzling.


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2007-05-09 at 18:42 -0700, Fernando Lopez-Lezcano
wrote:
> On Wed, 2007-05-09 at 16:59 -0400, Paul Davis wrote:
> > There was an error in the source tarball for
2.0.1. This error did NOT
> > affect the OS X DMG. 2.0.2 has been released as a
correction for the
> > error - it does not change any listed fixes for
2.0.1 in any way.
> 
> Has there been a change in how cpus are detected during
the build
> process? With the same spec file I used with 2.0.0 for
building Planet
> CCRMA packages I get this (on 32 bit fc6):
> 
> g++ -c -fPIC libs/ardour/sse_functions_64bit.s -o
> libs/ardour/sse_functions_64bit.os
> libs/ardour/sse_functions_64bit.s: Assembler messages:
> libs/ardour/sse_functions_64bit.s:37: Error: bad
register name `%rbp'
> libs/ardour/sse_functions_64bit.s:38: Error: bad
register name `%rsp'
> libs/ardour/sse_functions_64bit.s:41: Error: bad
register name `%rbx'
> libs/ardour/sse_functions_64bit.s:42: Error: bad
register name `%rdi'
> libs/ardour/sse_functions_64bit.s:43: Error: bad
register name `%rsi'
> libs/ardour/sse_functions_64bit.s:46: Error: bad
register name `%rdx'
> libs/ardour/sse_functions_64bit.s:51: Error: bad
register name `%rdi'
> 
> (I did not get to try with 2.0.1... 

Never mind, DIST_TARGET is (I think) what I needed. 
Still, it did work on 2.0.0...
-- Fernando


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2007-05-09 at 18:50 -0700, Fernando Lopez-Lezcano
wrote:
> On Wed, 2007-05-09 at 18:42 -0700, Fernando
Lopez-Lezcano wrote:
> > On Wed, 2007-05-09 at 16:59 -0400, Paul Davis
wrote:
> > > There was an error in the source tarball for
2.0.1. This error did NOT
> > > affect the OS X DMG. 2.0.2 has been released
as a correction for the
> > > error - it does not change any listed fixes
for 2.0.1 in any way.
> > 
> > Has there been a change in how cpus are detected
during the build
> > process? With the same spec file I used with 2.0.0
for building Planet
> > CCRMA packages I get this (on 32 bit fc6):
> > 
> > g++ -c -fPIC libs/ardour/sse_functions_64bit.s -o
> > libs/ardour/sse_functions_64bit.os
> > libs/ardour/sse_functions_64bit.s: Assembler
messages:
> > libs/ardour/sse_functions_64bit.s:37: Error: bad
register name `%rbp'
> > libs/ardour/sse_functions_64bit.s:38: Error: bad
register name `%rsp'
> > libs/ardour/sse_functions_64bit.s:41: Error: bad
register name `%rbx'
> > libs/ardour/sse_functions_64bit.s:42: Error: bad
register name `%rdi'
> > libs/ardour/sse_functions_64bit.s:43: Error: bad
register name `%rsi'
> > libs/ardour/sse_functions_64bit.s:46: Error: bad
register name `%rdx'
> > libs/ardour/sse_functions_64bit.s:51: Error: bad
register name `%rdi'
> > 
> > (I did not get to try with 2.0.1... 
> 
> Never mind, DIST_TARGET is (I think) what I needed. 
> Still, it did work on 2.0.0...

One more question, I see that:

      USE_SSE_EVERYWHERE
      BUILD_SSE_OPTIMIZATIONS

are gone. What does this mean? Are all sse/3dnow
optimizations dynamic
by default? (meaning the proper routine is chosen at runtime
based on
the cpu ardour is running on?)

-- Fernando


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2007-05-09 at 19:01 -0700, Fernando Lopez-Lezcano
wrote:

> One more question, I see that:
> 
>       USE_SSE_EVERYWHERE

been gone for quite some time.

>       BUILD_SSE_OPTIMIZATIONS


that is still there.

> are gone. What does this mean? Are all sse/3dnow
optimizations dynamic
> by default? (meaning the proper routine is chosen at
runtime based on
> the cpu ardour is running on?)

they have been dynamic for some time. we default to SSE if
the runtime
CPU supports it and the user doesn't ask to *not* use it.

--p


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Ok... this is probably me or hopefully easy but I've been
banging my head 
against the wall and now I'm stuck.... :(

I made the classic mistake of changing two things.

1) I upgraded Jack from .101 to .103. It seemed to go fine
but I have to 
admit I haven't run anything before the next steps but I
have reason to 
believe it's part of my problem.

2) I upgraded from 2.0beta12 to 2.0.2.  Scons went
smoothly.

3) qjackctl now segfaults after it starts jackd (I didn't
change any 
settings.  It seems fine until I hit the start button and
then segfaults.

4) if I start jackd manually it starts fine however... when
I start 
ardour2.0.2 it segfaults after loading the bindings.

  I'm
lost.  Any thoughts?  I suppose trying to reinstall Jack
.101 
right?  But that seems so defeatist.

Best Regards,

Lawrence T. Levine
Direct: 434-531-5982


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Paul Davis wrote:
> There was an error in the source tarball for 2.0.1.
This error did NOT
> affect the OS X DMG. 2.0.2 has been released as a
correction for the
> error - it does not change any listed fixes for 2.0.1
in any way.
>   

Thanks!

I has a few issues compiling ardour2, but after upgrading my
64studio 
distro to 1.3.6 testing release, the build performs smoothly
(after I 
loaded a few dependencies)

2.0.2 works great! It does absolutely everything that I
normally use, 
and my work flow is now so much improved, I could finish a
project that 
normally took me up to a week (between my other -real- job)
in just two 
days.

If I take the pace at which stuff is improving in linux
audio nowadays, 
it is truly exciting to see what will be on the table even a
few months 
from now. Yes Paul, the revolution has finally started!

Thanks again,
Quentin
_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org