DLR-RM / DLR-RM/BlenderProc

Generating a dataset on a cluster: -> ALSA lib confmisc.c: 767: (parse_card) cannot find card 'g° ALSA lib conf.c: 4568: (_snd_config_evaluate) function sd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c: 392:

Open
#1,027 2 comments 0 reactions 0 assignees View on GitHub
first answer provided question
Dominant language
Python
Stars
3.7k
Forks
518
PR merge metrics
No merged PRs in 30d

Description

### Describe the issue

Hi, thanks for your excellent work!
I am generating a dataset on a cluster. It doesn't have a sound card or drivers.
I had an error before: `ALSA lib confmisc.c: 767: (parse_card) cannot find card 'g° ALSA lib conf.c: 4568: (_snd_config_evaluate) function sd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c: 392:`
Now I have an error: `xcb_connection_has_error () returned true
Failed to create secure directory (/run/user/16934/pulse): No such file or directory xb_connection_has_error) returned true`

This warning or error does not fundamentally affect the data set generation process.
However, when blender tries to connect to the audio card, it takes a lot of time. Moreover, the more parallel processes are called for generation, the more time is required.

I'm using my own scene config file, but it's based on the `coco_annotation` script.
I run the script via `blenderproc run`.

### Minimal code example

_No response_

### Files required to run the code

_No response_

### Expected behavior

Please tell me how to bypass this warning. I want to speed up the process of starting dataset generation.

### BlenderProc version

v2.6.1

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the cluster run through `blenderproc run` with the custom scene config based on `coco_annotation`, noting where Blender initializes audio or X11. Compare startup time and dataset output with and without the cluster's sound-card and display environment. Done means the ALSA/XCB warnings no longer impose the reported delay while dataset generation remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
blender, python
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.