OSS driver won't start due to wrong block size
When I try to start the OSS driver I get a pop-up with the message "Error starting audio driver". At the console I get:
[ERROR] OssDriver ERROR_IOCTL: unable to set BlockSize
[ERROR] Hydrogen [audioEngine_startAudioDrivers] Error starting audio driver [audioDriver::connect()]
[ERROR] Hydrogen [audioEngine_startAudioDrivers] Using the NULL output audio driver
[ERROR] Hydrogen [audioEngine_startAudioDrivers] m_pMainBuffer_L == NULL
[ERROR] Hydrogen [audioEngine_startAudioDrivers] m_pMainBuffer_R == NULL
[ERROR] Hydrogen [audioEngine_setupLadspaFX] nBufferSize=0
[ERROR] NullDriver [setBpm] not implemented yet
I found a report of an identical situation at http://72.32.12.210/archives/openbsd/2007-04/2109.html, where a patch with a simple workaround is also provided. I haven't tried this fix yet, although I assume it will work. However the ideal situation would be for Hydrogen to have the ability to choose its own block size for low-latency running under OSS, rather than letting OSS impose its default.
I am using Hydrogen 0.93 and OSS4 on Linux.
[ERROR] OssDriver ERROR_IOCTL: unable to set BlockSize
[ERROR] Hydrogen [audioEngine_startAudioDrivers] Error starting audio driver [audioDriver::connect()]
[ERROR] Hydrogen [audioEngine_startAudioDrivers] Using the NULL output audio driver
[ERROR] Hydrogen [audioEngine_startAudioDrivers] m_pMainBuffer_L == NULL
[ERROR] Hydrogen [audioEngine_startAudioDrivers] m_pMainBuffer_R == NULL
[ERROR] Hydrogen [audioEngine_setupLadspaFX] nBufferSize=0
[ERROR] NullDriver [setBpm] not implemented yet
I found a report of an identical situation at http://72.32.12.210/archives/openbsd/2007-04/2109.html, where a patch with a simple workaround is also provided. I haven't tried this fix yet, although I assume it will work. However the ideal situation would be for Hydrogen to have the ability to choose its own block size for low-latency running under OSS, rather than letting OSS impose its default.
I am using Hydrogen 0.93 and OSS4 on Linux.
Leave a comment
tested on 0.9.5 :
this seems to happen in a number of cases, mainly when you switch between audio drivers (something that you typically dont do very often)
i also saw it happen while i was playing around with ALSA settings, so i'm not sure if this is an OSS-only issue
in some cases i even got H2 to segfault (persistently) after changing buffer settings and switching to an other audio driver. I had to manually change my hydrogen.conf to fix this (changing 'ASLA' to 'OSS')
it looks as if there is no mechanism to check if the buffer settings are valid for a specific audio driver.
it also looks like there is no mechanism that ensures a smooth switch-over from audio river A to audio driver B
i will repeat my test on the 0.9.6 but on the 0.9.5 it seems quite easy to get H2 to crash if you mess with these settings
to be continued
this seems to happen in a number of cases, mainly when you switch between audio drivers (something that you typically dont do very often)
i also saw it happen while i was playing around with ALSA settings, so i'm not sure if this is an OSS-only issue
in some cases i even got H2 to segfault (persistently) after changing buffer settings and switching to an other audio driver. I had to manually change my hydrogen.conf to fix this (changing 'ASLA' to 'OSS')
it looks as if there is no mechanism to check if the buffer settings are valid for a specific audio driver.
it also looks like there is no mechanism that ensures a smooth switch-over from audio river A to audio driver B
i will repeat my test on the 0.9.6 but on the 0.9.5 it seems quite easy to get H2 to crash if you mess with these settings
to be continued
hi thijs,
i will check in the oss patch from the ticket creator. if you have some time and you like, please check if this ticket bug is fixed. because this bug and the patch are oss specific.
we/you can create a new ticket about problems you describe in your last comment.
greetings wolke
i will check in the oss patch from the ticket creator. if you have some time and you like, please check if this ticket bug is fixed. because this bug and the patch are oss specific.
we/you can create a new ticket about problems you describe in your last comment.
greetings wolke