Re: [Psychosynth-user] Re: Psychosynth-user Digest, Vol 1, Issue 1

[Juan Pedro Bolivar Puente]

> The thing that caught my eye was the config not installing the 3d client
> psynth3d. I didn't have this problem with version 1.1-1. The config runs
> just fine, and I even have the shortcut now. But psynth3d isn't installed! I
> have psynth, and I can run in server mode with no issues. But I am not able
> to lauch psynth3d because it's not on my computer! Help!!!
>

Have you installed CEGUI, Ogre and CeguiOgre?? Maybe you forgot the last
one (libceguiogre-dev on Debian and Ubuntu).

JP


> 
> Josh
> 
> On Mon, Feb 9, 2009 at 12:03 PM, <address@hidden>wrote:
> 
>> Send Psychosynth-user mailing list submissions to
>>        address@hidden
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        http://lists.nongnu.org/mailman/listinfo/psychosynth-user
>> or, via email, send a message with subject or body 'help' to
>>        address@hidden
>>
>> You can reach the person managing the list at
>>        address@hidden
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Psychosynth-user digest..."
>>
>>
>> Today's Topics:
>>
>>   1. New release: Psychosynth 0.1.2 (Juan Pedro Bolivar Puente)
>>   2. Re: [Psychosynth-devel] New release: Psychosynth  0.1.2
>>      (Aleksander Morgado)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 09 Feb 2009 07:22:05 +0100
>> From: Juan Pedro Bolivar Puente <address@hidden>
>> Subject: [Psychosynth-user] New release: Psychosynth 0.1.2
>> To: address@hidden, address@hidden
>> Message-ID: <address@hidden>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi,
>>
>> A new release has been made. It is far from including all features I had
>>  planned for this term, but I hope I'll have more time the starting one.
>>
>> Also, important design decisions are to me taken in a month or so. Any
>> help from experienced C++ programmers with previous experience in
>> template metaprogramming, software synthesis and sequencing -anyway, any
>> help is wellcome and very valuable, even if those "requisites" are not
>> matched :-)
>>
>> Despite there are not many people on the list, I'll try to send emails
>> to it periodically so there is a record for design discussions and
>> newcomers have an active mean of communication.
>>
>> @ALEX:
>>
>> You said that you could try to do a port for MacOsX. That means
>> implementing an output device based on Core Audio. I have never
>> programmed with Core Audio so, please, can you take a look at the Core
>> Audio API and see if the interface defined in psynth/output/output.hpp
>> is ok for it? As usage examples you can take a look at output_alsa.*
>> output_oss.* and output_jack.*. Note that those implementations are not
>> good -missing error handling (exceptions handling systems are to be
>> added in the future) and hardcoded values.
>>
>> I no longer think that postponing the ports till the refactorings is a
>> good idea. Probably taking them into account from the start and
>> maintaining them later is a better idea -despite the fact that it
>> requires more effort for the people maintaining the platform-specific
>> code :p Also, having the eyes of Mac/Win guys on the project is a good
>> idea and will probably help us get more help. What do you think?
>>
>> JP
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 09 Feb 2009 09:56:15 +0100
>> From: Aleksander Morgado <address@hidden>
>> Subject: [Psychosynth-user] Re: [Psychosynth-devel] New release:
>>        Psychosynth     0.1.2
>> To: Juan Pedro Bolivar Puente <address@hidden>
>> Cc: address@hidden, address@hidden
>> Message-ID: <address@hidden>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>>> @ALEX:
>>>
>>> You said that you could try to do a port for MacOsX. That means
>>> implementing an output device based on Core Audio. I have never
>>> programmed with Core Audio so, please, can you take a look at the Core
>>> Audio API and see if the interface defined in psynth/output/output.hpp
>>> is ok for it? As usage examples you can take a look at output_alsa.*
>>> output_oss.* and output_jack.*. Note that those implementations are not
>>> good -missing error handling (exceptions handling systems are to be
>>> added in the future) and hardcoded values.
>>>
>> I will take a look at the Core Audio stuff and keep you informed.
>>
>> Bye!
>> -Aleksander
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Psychosynth-user mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/psychosynth-user
>>
>>
>> End of Psychosynth-user Digest, Vol 1, Issue 1
>> **********************************************
>>
> 
> 
>