[PlanetCCRMA] Planet CCRMA x86_64 and Adour/Ardour2 XRuns

[Beepo / Vanguard]

I continued a little bit testing with other audio software and had
Rosegarden4, Hydrogen running synchronized via jack transport. Tried
with several example projects using for example Hexter.

I recorded several tracks of audio in rosegarden and played back them
with no problems all of the above running together.

At least this leads to a thought that the xrun problem might be somehow
Ardour related.

BR:
  Aapo

On Sat, 2007-03-10 at 13:54 +0200, Beepo / Vanguard wrote:
> Hi and thanks for the answer
> 
> I updated from the yum the new planetccrma-core package and forced back
> the original pam package. I'm not sure if that was the right way to do
> it or should I try a fresh install again?
> 
> The xruns are still there and I'm not sure what is causing them. I tried
> to lower the latency by increasing the periods in qjackctl and went as
> up as 2048 giving the latency of 85.3ms that did not help the situation.
> Still when the playback is stopped from ardour the xruns start to flow
> and ardour is taking up all of the processor. That happens only after
> the first stop of the playback and goes away when I exit Ardour.
> 
> The snd-via82xx module is reappeared in the modules.conf so I'll have to
> figure out how the disable the integrated card for good since I really
> don't need it. It is already disabled in the BIOS but that does not
> help. For some reason the FC5 didn't detect it that was fine.
> 
> Thank you again!-)
> 
> BR:
>   Aapo
> 
> On Fri, 2007-03-09 at 16:12 -0800, Fernando Lopez-Lezcano wrote:
> > On Fri, 2007-03-09 at 15:37 -0800, Fernando Lopez-Lezcano wrote:
> > > On Fri, 2007-03-09 at 23:22 +0200, Beepo / Vanguard wrote:
> > > > Hi,
> > > > 
> > > > Forgive me writing such a long version, but it includes the whole path
> > > > of the upgrade. The actual questions can be found at the very end of
> > > > this message ;) Anyway thanks again for all that have been there for me
> > > > earlier and especially for Fernando for the hard work.
> > > > 
> > > > I've just installed the x86_64 version of Planet CCRMA on a fresh FC6
> > > > installation. I knew I would be taking a bit of a risk since I had
> > > > perfectly working 32bit version on FC5 but the temptation was too big.
> > > > 
> > > > The installation was almost a walk in the park. I did a completelly
> > > > fresh install of FC6 and updated it with yum before the Planet CCRMA
> > > > installation. Only thing that I had to do when installing the
> > > > planetccrma-core package was to force the pam to install. For that I
> > > > downloaded the CCRMA pam package and installed it manually by issuing
> > > > command: rpm -Uhv --force pam-0.99.6.2-3.16.1.fc6.ccrma.x86_64.rpm
> > > 
> > > Hmmm, why was it not installing? "--force" is _always_ a bad idea, it
> > > means there's something wrong with the package database. Do you remember
> > > what the error was? (I don't have an x86_64 machine to test this on). 
> > 
> > Hmmm, I pulled the x86_64 package from the repo for now till I can
> > figure this out (turns out there's a version skew with fc6 i386 and both
> > i386 and x86_64 builds are needed for x86_64), and updated
> > planetccrma-core to not require it. Will take a look at this asap. 
> > 
> > For now I recommend you reinstall the original x86_64 pam package from
> > the fc6 updates repo...
> > 
> > -- Fernando
> > 
> > 
>