Group Admins

  • Profile picture of bouchereau
  • Profile picture of daubresse
  • Profile picture of esling

Orchids

Public Group active 2 days, 9 hours ago

Welcome to the Orchids user group.

This user group is devoted to the Orchids orchestration system and its users, but also on the topic of computer-aided orchestration and generic sound mixture optimization. In order to facilitate the exchange of bug reports, idea and collaborative thinking, we encourage any kind of report on errors, bad or good results, desired features, ideas, remarks and any other topic.

Please report any unsolved problem, ideas or even cool sounds to this group and we will be glad to discuss it. If you want to start using the software, please read the full documentation, which provides turnarounds to known issues: http://repmus.ircam.fr/_media/esling/orchids-documentation.pdf

http://forumnet.ircam.fr/user-groups/orchids/
http://forumnet.ircam.fr/product/orchids/

empty search space.

Author 2 Subscribed Users |
Profile photo of benjamin
benjamin

“Production: empty search space, search space is empty!check filter and orchestra.”
Hello
I am a beginner. I’ve had several problems in the installation that I am solving.
At the moment the error that more occurs is ::::. “Production: empty search space, search space is empty!check filter and orchestra.”
On the other hand, in another computer, in a mac book air, has not given any problem, neither in the installation nor in the operation. It offers solutions and works well (for now!). The steps given in the two computers have been the same (The same sample, the same filter, the same orchestra).
The office computer is an imac OSX yosemite 10.10.5, the Air is OSX10.10.2
Any ideas?
Thanks.

August 25, 2017 at 18:39 #23444
Profile photo of Carmine Emanuele Cella
Carmine Emanuele Cella

Hallo Benjamin,

this message can be generated by several circumstances. Two possible reasons are the following:
1. the SOL database is not correctly installed or you didn’t perform all required configuration steps (for example pressing the button “Parse database and build explorer”) on the explorer page
2. the filters you put in your orchestration are too strict: for example is you reduce the allowed dynamics, playing styles and instruments you could end up on a search space that is too small for your problem
3. the sound you use as target has a complex nature that is difficult to describe with partials and low-level descriptors that you used; this in combination with filters that are too strict could be a problem
4. the parameters for the search algorithm are not sound (I suggest to use the default configuration to start)

Many other reasons could be at the origin of that message, anyway. Try to simplify your orchestration at the beginning using stationary sounds, no onsets, harmonic filtering and mean descriptors. Eventually, increase the level of the complexity by changing targets and descriptors as long as you understand more the software.
Regards
Carmine

October 6, 2017 at 16:49 #24019

You must be logged in to reply to this topic.

Log in now