Return to “Public Betas — Plugins & Components”
Jump to:
New Topic
Post Reply
300 posts
- Previous
- 1
- 2
- 3
- 4
- 5
- 6
- Next
[You can only see part of this thread as you are not logged in to the forums]
-
Thomas Helzle
- Tue Aug 05, 2014 10:04 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Great that the modular only scan’s the custom VST folder now. Thanks!
I agree with the others here though: a separate VST list for 32 and 64 Bit versions would be needed. I keep separate folders for those and don’t want either version to scan the other architecture.
Cheers,
Tom
(Windows 8.1.u, x64, Bitwig Studio)
Top
-
Satak
- Tue Aug 05, 2014 12:34 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Is it now possible to launch from IL Remote pad…
Top
-
S0ulA55a551n
- Tue Aug 05, 2014 8:11 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Hi,
I can make it open as 32bit version in sta…
Top
-
reflex
- Site Admin
- Wed Aug 06, 2014 9:33 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
S0ulA55a551n wrote:I can make it open as 32bit …
Top
-
Dlorance
- Wed Aug 06, 2014 11:42 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
I didnt know this existed O.o I need to browse …
Top
-
Hydrofizzy Chump
- Wed Aug 06, 2014 3:19 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Please forgive me if this has already been addr…
You do not have the required permissions to view the files attached to this post.
Top
-
Sacco
- Thu Aug 07, 2014 8:21 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Logic is probably 64bit…..right? so what you …
Top
-
Hydrofizzy Chump
- Thu Aug 07, 2014 2:22 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Sacco wrote:Logic is probably 64bit…..right? …
Top
-
S0ulA55a551n
- Wed Aug 13, 2014 4:22 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
The only way you can get this to work in 32bit …
Top
-
c.a.p.
- Thu Aug 21, 2014 7:01 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
OSX 10.9.2
No changes for OSX version 1.5.7? C…
Top
-
TheSteven
- Sat Aug 23, 2014 6:45 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
As previously mentioned
I agree with the others…
Top
-
Reflected
- Mon Aug 25, 2014 6:55 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Is it possible to have output control parameter…
Top
-
banmier
- Wed Aug 27, 2014 12:50 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
I’m not sure if I have something setup incorrec…
Top
-
jtoyl
- Wed Aug 27, 2014 5:57 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Each time I restart the VST host (I use Renoise…
Top
-
sjs
- Thu Aug 28, 2014 10:06 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
I don’t seem to be able to get Minihost to outp…
Top
-
TimeFlight
- Sat Aug 30, 2014 9:35 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Let’s give this a spin! Great idea
Top
-
ILDan
- Thu Sep 04, 2014 11:49 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
user question wrote:Heres where im at, Ive been…
Top
-
ILDan
- Thu Sep 04, 2014 11:52 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Sacco wrote:Dan, can we have the internal names…
Top
-
reflex
- Site Admin
- Thu Sep 04, 2014 12:15 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
ILDan wrote:I wanted this too but I think Fred …
Top
-
vburel
- Wed Sep 10, 2014 7:30 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
just tested Minihost 1.5.8 (32bits) , it’s a ni…
Top
-
Siek Hondt
- Sun Sep 14, 2014 6:09 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Hi Scott,
Apologies if this has already been …
You do not have the required permissions to view the files attached to this post.
Top
-
audiosync
- Thu Sep 18, 2014 7:54 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Very great piece of software with high potentia…
You do not have the required permissions to view the files attached to this post.
Top
-
levendis
- Mon Sep 22, 2014 7:16 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 2
ILDan wrote:frankz00 wrote:Minihost needs to lo…
Top
-
Nowhk
- Sun Sep 28, 2014 2:43 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
How do you record score into Piano Roll module?…
Top
-
audiosync
- Wed Oct 01, 2014 12:08 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Does anyone take care of this thread?
is there…
Top
-
einfachfelix
- Wed Oct 29, 2014 4:48 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Problem:
— from time to time minihost deos not …
You do not have the required permissions to view the files attached to this post.
Top
-
fredrik
- Mon Nov 03, 2014 3:45 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Is it possible to set up a MIDI connection that…
Top
-
fredrik
- Mon Nov 03, 2014 3:52 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
audiosync wrote:Very great piece of software wi…
Top
-
Sacco
- Tue Nov 04, 2014 2:48 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
As of 1.5.8 I don’t seem to have success openin…
Top
-
Mysta187_
- Mon Nov 10, 2014 4:57 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Has this project been abandoned or shelved? Per…
Top
-
Dewdman42
- Thu Nov 13, 2014 8:45 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Tried to run windows version under wine in orde…
Top
-
Satak
- Sun Nov 16, 2014 6:59 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Satak wrote:Is it now possible to launch from I…
Top
-
dummyaccount
- Fri Nov 28, 2014 12:35 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Minihost is awesome. Is there an estimation for…
Top
-
reflex
- Site Admin
- Mon Dec 01, 2014 10:36 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
dummyaccount wrote:Minihost is awesome. Is ther…
Top
-
dummyaccount
- Mon Dec 01, 2014 5:00 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
reflex wrote:dummyaccount wrote:Minihost is awe…
Top
-
fredrik
- Fri Dec 12, 2014 5:32 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Anyone able to get the mouse wheel to work in t…
Top
-
DJ Trancestorm
- Sat Dec 13, 2014 5:20 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
how to use my pc keyboard to play a melody?
Top
-
fredrik
- Wed Dec 17, 2014 6:38 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
BUG: When using Minihost as a VST plugin, it do…
Top
-
audiosync
- Wed Dec 17, 2014 8:03 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
I would suggest IL to take some money for Minih…
Top
-
Thomas Helzle
- Tue Dec 23, 2014 2:48 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Happy holidays everybody!
I hope next year the…
Top
-
Mr. Ree Huss
- Wed Dec 31, 2014 6:15 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
If I wanted to automate a parameter via an LFO …
Top
-
c.a.p.
- Sat Jan 10, 2015 1:59 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Is anywhere/anywho talking about this…looks l…
Top
-
fredrik
- Mon Feb 16, 2015 3:28 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Scott wrote:
Last updated 24-April-2014
Almost …
Top
-
c.a.p.
- Fri Feb 20, 2015 9:55 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Because FL12 ? Maybe?
Top
-
varikusbrainz
- Sun Mar 01, 2015 6:56 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Has the windows version been removed, The linke…
Top
-
Nowhk
- Fri Mar 13, 2015 10:39 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
How is the state of this beast? Is this ever go…
Top
-
fredrik
- Wed Mar 18, 2015 8:57 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Nowhk wrote:How is the state of this beast? Is …
Top
-
alexfsu
- Sun Apr 12, 2015 5:28 pm
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
I’m having trouble getting this to work as an e…
Top
-
JC2008
- Fri May 15, 2015 12:45 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
Does anyone else have issues with this app usin…
Top
-
Dynaudio82
- Mon May 18, 2015 4:55 am
-
-
- Quote
-
x
Re: Minihost Modular Beta 3 (v1.5.8)
What happened with this??? still in beta from A…
Top
Display posts from previous:
Sort by
New Topic
Post Reply
300 posts
- Previous
- 1
- 2
- 3
- 4
- 5
- 6
- Next
Return to “Public Betas — Plugins & Components”
Jump to:
Platform (Hardware/OS):Rasbian v9 Stretch
Node version:10.10.0
MagicMirror version:2.4.1
Module version:Latest
Description of the issue: Error opening audio device plughw:0 for capture: Device or resource busy
FATAL: «continuous.c», line 245: Failed to open audio device
Hello,
I have been trying to run the module but it keeps saying Error Undefined when I do.
I am not sure if it is because I am using the Google AIY Voice Hat (It’s not USB) or if it’s something
else.
I have config set to 0 as cat /proc/asound/cards returns:
0 [sndrpigooglevoi]: snd_rpi_googlev - snd_rpi_googlevoicehat_soundcar snd_rpi_googlevoicehat_soundcard 1 [HD3000 ]: USB-Audio - Microsoft® LifeCam HD-3000 Microsoft Microsoft® LifeCam HD-3000 at usb-3f980000.usb-1.3, high speed
Note, the Google soundcard is what I wish to use although I get the same error when I put 1 in and try to use the Lifecam.
My Debug log is:
`INFO: pocketsphinx.c(153): Parsed model-specific feature parameters from /usr/local/share/pocketsphinx/model/en-us/en-us/feat.params
Current configuration:
[NAME] [DEFLT] [VALUE]
-agc none none
-agcthresh 2.0 2.000000e+00
-allphone
-allphone_ci yes yes
-alpha 0.97 9.700000e-01
-ascale 20.0 2.000000e+01
-aw 1 1
-backtrace no no
-beam 1e-48 1.000000e-48
-bestpath yes yes
-bestpathlw 9.5 9.500000e+00
-ceplen 13 13
-cmn live batch
-cmninit 40,3,-1 41.00,-5.29,-0.12,5.09,2.48,-4.07,-1.37,-1.78,-5.08,-2.05,-6.45,-1.42,1.17
-compallsen no no
-dict modules/MMM-voice/MMM-voice.dic
-dictcase no no
-dither no no
-doublebw no no
-ds 1 1
-fdict
-feat 1s_c_d_dd 1s_c_d_dd
-featparams
-fillprob 1e-8 1.000000e-08
-frate 100 100
-fsg
-fsgusealtpron yes yes
-fsgusefiller yes yes
-fwdflat yes yes
-fwdflatbeam 1e-64 1.000000e-64
-fwdflatefwid 4 4
-fwdflatlw 8.5 8.500000e+00
-fwdflatsfwin 25 25
-fwdflatwbeam 7e-29 7.000000e-29
-fwdtree yes yes
-hmm /usr/local/share/pocketsphinx/model/en-us/en-us
-input_endian little little
-jsgf
-keyphrase
-kws
-kws_delay 10 10
-kws_plp 1e-1 1.000000e-01
-kws_threshold 1e-30 1.000000e-30
-latsize 5000 5000
-lda
-ldadim 0 0
-lifter 0 22
-lm modules/MMM-voice/MMM-voice.lm
-lmctl
-lmname
-logbase 1.0001 1.000100e+00
-logfn
-logspec no no
-lowerf 133.33334 1.300000e+02
-lpbeam 1e-40 1.000000e-40
-lponlybeam 7e-29 7.000000e-29
-lw 6.5 6.500000e+00
-maxhmmpf 30000 30000
-maxwpf -1 -1
-mdef
-mean
-mfclogdir
-min_endfr 0 0
-mixw
-mixwfloor 0.0000001 1.000000e-07
-mllr
-mmap yes yes
-ncep 13 13
-nfft 512 512
-nfilt 40 25
-nwpen 1.0 1.000000e+00
-pbeam 1e-48 1.000000e-48
-pip 1.0 1.000000e+00
-pl_beam 1e-10 1.000000e-10
-pl_pbeam 1e-10 1.000000e-10
-pl_pip 1.0 1.000000e+00
-pl_weight 3.0 3.000000e+00
-pl_window 5 5
-rawlogdir
-remove_dc no no
-remove_noise yes yes
-remove_silence yes yes
-round_filters yes yes
-samprate 16000 1.600000e+04
-seed -1 -1
-sendump
-senlogdir
-senmgau
-silprob 0.005 5.000000e-03
-smoothspec no no
-svspec 0-12/13-25/26-38
-tmat
-tmatfloor 0.0001 1.000000e-04
-topn 4 4
-topn_beam 0 0
-toprule
-transform legacy dct
-unit_area yes yes
-upperf 6855.4976 6.800000e+03
-uw 1.0 1.000000e+00
-vad_postspeech 50 50
-vad_prespeech 20 20
-vad_startspeech 10 10
-vad_threshold 3.0 3.000000e+00
-var
-varfloor 0.0001 1.000000e-04
-varnorm no no
-verbose no no
-warp_params
-warp_type inverse_linear inverse_linear
-wbeam 7e-29 7.000000e-29
-wip 0.65 6.500000e-01
-wlen 0.025625 2.562500e-02
INFO: feat.c(715): Initializing feature stream to type: ‘1s_c_d_dd’, ceplen=13, CMN=’batch’, VARNORM=’no’, AGC=’none’
INFO: acmod.c(162): Using subvector specification 0-12/13-25/26-38
INFO: mdef.c(518): Reading model definition: /usr/local/share/pocketsphinx/model/en-us/en-us/mdef
INFO: mdef.c(531): Found byte-order mark BMDF, assuming this is a binary mdef file
INFO: bin_mdef.c(336): Reading binary model definition: /usr/local/share/pocketsphinx/model/en-us/en-us/mdef
INFO: bin_mdef.c(516): 42 CI-phone, 137053 CD-phone, 3 emitstate/phone, 126 CI-sen, 5126 Sen, 29324 Sen-Seq
INFO: tmat.c(149): Reading HMM transition probability matrices: /usr/local/share/pocketsphinx/model/en-us/en-us/transition_matrices
INFO: acmod.c(113): Attempting to use PTM computation module
INFO: ms_gauden.c(127): Reading mixture gaussian parameter: /usr/local/share/pocketsphinx/model/en-us/en-us/means
INFO: ms_gauden.c(242): 42 codebook, 3 feature, size:
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(127): Reading mixture gaussian parameter: /usr/local/share/pocketsphinx/model/en-us/en-us/variances
INFO: ms_gauden.c(242): 42 codebook, 3 feature, size:
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(244): 128×13
INFO: ms_gauden.c(304): 222 variance values floored
INFO: ptm_mgau.c(475): Loading senones from dump file /usr/local/share/pocketsphinx/model/en-us/en-us/sendump
INFO: ptm_mgau.c(499): BEGIN FILE FORMAT DESCRIPTION
INFO: ptm_mgau.c(562): Rows: 128, Columns: 5126
INFO: ptm_mgau.c(594): Using memory-mapped I/O for senones
INFO: ptm_mgau.c(837): Maximum top-N: 4
INFO: phone_loop_search.c(114): State beam -225 Phone exit beam -225 Insertion penalty 0
INFO: dict.c(320): Allocating 4130 * 20 bytes (80 KiB) for word entries
INFO: dict.c(333): Reading main dictionary: modules/MMM-voice/MMM-voice.dic
INFO: dict.c(213): Dictionary size 29, allocated 0 KiB for strings, 0 KiB for phones
INFO: dict.c(336): 29 words read
INFO: dict.c(358): Reading filler dictionary: /usr/local/share/pocketsphinx/model/en-us/en-us/noisedict
INFO: dict.c(213): Dictionary size 34, allocated 0 KiB for strings, 0 KiB for phones
INFO: dict.c(361): 5 words read
INFO: dict2pid.c(396): Building PID tables for dictionary
INFO: dict2pid.c(406): Allocating 42^3 * 2 bytes (144 KiB) for word-initial triphones
INFO: dict2pid.c(132): Allocated 21336 bytes (20 KiB) for word-final triphones
INFO: dict2pid.c(196): Allocated 21336 bytes (20 KiB) for single-phone word triphones
INFO: ngram_model_trie.c(354): Trying to read LM in trie binary format
INFO: ngram_model_trie.c(365): Header doesn’t match
INFO: ngram_model_trie.c(177): Trying to read LM in arpa format
INFO: ngram_model_trie.c(193): LM of order 3
INFO: ngram_model_trie.c(195): #1-grams: 25
INFO: ngram_model_trie.c(195): #2-grams: 46
INFO: ngram_model_trie.c(195): #3-grams: 23
INFO: lm_trie.c(474): Training quantizer
INFO: lm_trie.c(482): Building LM trie
INFO: ngram_search_fwdtree.c(74): Initializing search tree
INFO: ngram_search_fwdtree.c(101): 28 unique initial diphones
INFO: ngram_search_fwdtree.c(186): Creating search channels
INFO: ngram_search_fwdtree.c(323): Max nonroot chan increased to 157
INFO: ngram_search_fwdtree.c(333): Created 28 root, 29 non-root channels, 5 single-phone words
INFO: ngram_search_fwdflat.c(157): fwdflat: min_ef_width = 4, max_sf_win = 25
INFO: continuous.c(307): pocketsphinx_continuous COMPILED ON: Sep 19 2018, AT: 22:43:41
Error opening audio device plughw:0 for capture: Device or resource busy
FATAL: «continuous.c», line 245: Failed to open audio device
`
I tried doing:
LD_LIBRARY_PATH=/usr/local/lib PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
This helped with a different problem I was having before but I now have this issue which I can’t seem to find a fix for.
Please help and explain in steps and language that a beginner at raspberry Pi and indeed Linux can comprehend.
Thank you very much in advance.
Содержание
- 1. Что такое IL Minihost Modular.dll?
- 2. IL Minihost Modular.dll безопасный, или это вирус или вредоносная программа?
- 3. Могу ли я удалить или удалить IL Minihost Modular.dll?
- 4. Распространенные сообщения об ошибках в IL Minihost Modular.dll
- 4a. IL Minihost Modular.dll не найден
- 4b. IL Minihost Modular.dll отсутствует
- 5. Как исправить IL Minihost Modular.dll
- 6. Обновление за февраль 2023
Обновлено февраль 2023: Вот три шага к использованию инструмента восстановления для устранения проблем с dll на вашем компьютере: Получите его по адресу эту ссылку
- Скачайте и установите это программное обеспечение.
- Просканируйте свой компьютер на наличие проблем с dll.
- Исправьте ошибки dll с помощью программного инструмента
Ил Minihost Modular.dll это файл библиотеки динамических ссылок, который является частью разработанный Изображение-Line, Версия программного обеспечения: обычно о по размеру, но версия у вас может отличаться. Файлы DLL — это формат файлов для динамических библиотек, который используется для хранения нескольких кодов и процедур для программ Windows. Файлы DLL были созданы, чтобы позволить нескольким программам использовать их информацию одновременно, тем самым сохраняя память. Это также позволяет пользователю изменять кодировку нескольких приложений одновременно, не изменяя сами приложения. Библиотеки DLL могут быть преобразованы в статические библиотеки с помощью дизассемблирования MSIL или DLL в Lib 3.00. Формат файла .exe файлов аналогичен формату DLL. Файлы DLL, и оба типа файлов содержат код, данные и ресурсы.
Наиболее важные факты о IL Minihost Modular.dll:
- Имя: Ил Minihost Modular.dll
- Программного обеспечения: IL Minihost Модульный
- Издатель: Изображение-Line
- URL издателя: www.image-line.com
- Файл справки: www.image-line.com
- Известно, что до 27.05 MB по размеру на большинстве окон;
Рекомендуется: Выявление ошибок, связанных с IL Minihost Modular.dll.
(дополнительное предложение для Reimage — Cайт | Лицензионное соглашение | Персональные данные | Удалить)
IL Minihost Modular.dll безопасный, или это вирус или вредоносная программа?
Ответ — нет, сам по себе IL Minihost Modular.dll не должен повредить ваш компьютер.
В отличие от исполняемых программ, таких как программы с расширением EXE, файлы DLL не могут быть выполнены напрямую, но должны вызываться другим кодом, который уже выполнен. Тем не менее, DLL имеют тот же формат, что и EXE, и некоторые могут даже использовать расширение .EXE. В то время как большинство динамических библиотек заканчиваются расширением .DLL, другие могут использовать .OCX, .CPL или .DRV.
Файлы DLL полезны, потому что они позволяют программе разделять свои различные компоненты на отдельные модули, которые затем могут быть добавлены или удалены для включения или исключения определенных функций. Если программное обеспечение работает таким образом с библиотеками DLL, программа может использовать меньше памяти, поскольку ей не нужно загружать все одновременно.
С другой стороны, если файл .dll прикреплен к исполняемому файлу, который предназначен для повреждения вашего компьютера, возможно, это опасно. Мы рекомендуем вам запустить сканирование вашей системы с инструмент, подобный этому это может помочь выявить любые проблемы, которые могут существовать.
Вот почему обычно, когда вы видите новый файл .dll на вашем компьютере, где-то будет файл .exe.
Убедитесь, что вы сканируете оба вместе, чтобы вам не пришлось беспокоиться о заражении вашего компьютера чем-то плохим.
Могу ли я удалить или удалить IL Minihost Modular.dll?
Согласно различным источникам онлайн, 7% людей удаляют этот файл, поэтому он может быть безвредным, но рекомендуется проверить надежность этого исполняемого файла самостоятельно, чтобы определить, является ли он безопасным или вирусом.
Программные программы хранят файлы DLL в одной или нескольких папках во время установки. Эти файлы содержат код, который объясняет работу программ.
Если вы планируете удалить IL Minihost Modular.dll, лучше оставить его в покое. Причина этой логики заключается в том, что некоторые программы совместно используют эти файлы, поэтому удаление определенного файла DLL может непреднамеренно вызвать проблемы. Это означает, что удаление IL Minihost Modular.dll может привести к прекращению работы одной или нескольких других программ или только в ограниченной степени.
Некоторые программы также могут устанавливать файлы DLL в несколько папок вне папки Program Files (где установлено большинство программ). Поиск этих DLL-файлов может быть очень трудным, а удаление их может быть опасным.
Как уже упоминалось выше, если вы не уверены, что IL Minihost Modular.dll используется другой программой, мы рекомендуем оставить его в покое. Однако, если вам нужно удалить файл, мы рекомендуем сначала сделать копию. Если после этого у вас возникнут проблемы с другой программой, требующей использования недавно удаленного DLL-файла, вы можете восстановить файл из резервной копии.
Распространенные сообщения об ошибках в IL Minihost Modular.dll
Как вы можете себе представить, некоторые DLL появляются чаще в сообщениях об ошибках, чем другие. Вот некоторые из DLL, которые, как известно, вызывают проблемы.
- Не удалось запустить приложение, так как IL Minihost Modular.dll не был найден. Переустановка приложения может решить проблему.
- IL Minihost Modular.dll не найден
- Отсутствует IL Minihost Modular.dll
- Требуемая DLL IL Minihost Modular.dll не найдена
- Приложение или IL Minihost Modular.dll не является допустимым образом Windows
- IL Minihost Modular.dll отсутствует или поврежден
- Не удается найти IL Minihost Modular.dll
- Не удается запустить IL Minihost Modular.dll. Отсутствует необходимый компонент: IL Minihost Modular.dll. Пожалуйста, установите IL Minihost Modular.dll снова.
Как исправить IL Minihost Modular.dll
Обновлено февраль 2023:
Мы рекомендуем вам попробовать этот новый инструмент. Он исправляет множество компьютерных ошибок, а также защищает от таких вещей, как потеря файлов, вредоносное ПО, сбои оборудования и оптимизирует ваш компьютер для максимальной производительности. Это исправило наш компьютер быстрее, чем делать это вручную:
- Шаг 1: Скачать PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista — Microsoft Gold Certified).
- Шаг 2: Нажмите «Начать сканирование”, Чтобы найти проблемы реестра Windows, которые могут вызывать проблемы с ПК.
- Шаг 3: Нажмите «Починить все», Чтобы исправить все проблемы.
(опциональное предложение для Reimage — Cайт | Лицензионное соглашение | Персональные данные | Удалить)
Если IL Minihost Modular.dll отсутствует или поврежден, это может повлиять на многие приложения, включая операционную систему, что может помешать вам выполнять свою работу или использовать критические функции в критически важных программах.
Запустить SFC
Самый безопасный способ восстановить отсутствующий или поврежденный файл IL Minihost Modular.dll, вызванный вашей операционной системой Windows, — запустить встроенную проверку системных файлов, которая заменяет отсутствующие или поврежденные системные файлы.
Для этого щелкните правой кнопкой мыши кнопку «Пуск» на компьютере Windows 10, чтобы открыть меню WinX, и щелкните ссылку «Командная строка (администратор)».
В окне CMD скопируйте следующую команду и нажмите Enter:
ПФС / SCANNOW
Сканирование может занять 10 минут, и если оно успешно завершено, вы должны перезагрузить компьютер. Запуск sfc / scannow в безопасном режиме или при запуске может дать лучшие результаты.
Обновить драйверы
Иногда, при использовании аппаратного обеспечения, такого как принтер, вы получаете отсутствующую ошибку файла IL Minihost Modular.dll. Эта ошибка может быть связана с более старой версией драйвера, который не совместим с обновленным файлом DLL, поэтому принтер ищет неправильный файл DLL и не может его найти.
Обновите драйверы вашего устройства, чтобы увидеть, решит ли это проблему.
Восстановление при загрузке
Восстановление при загрузке — это еще один способ восстановить все DLL-файлы, такие как IL Minihost Modular.dll, до их первоначального рабочего состояния. Однако это исправление может вызвать проблемы в других программах, особенно если программа обновила файлы .dll.
Скачать или переустановить IL Minihost Modular.dll
В большинстве учебников и руководств авторы предупреждают своих читателей, чтобы они не загружали отсутствующие файлы IL Minihost Modular.dll со случайных и непригодных для использования веб-сайтов, которые могут предоставить им вредоносное ПО. Это не без причины, конечно. Правда состоит в том, что в Интернете полно сайтов, которые обещают пользователям решить их проблемы, открыв определенные приложения или программы как можно скорее. К сожалению, очень немногие могут действительно оправдать ваши ожидания.
Хотя эта проблема встречается реже, потенциально гораздо более серьезная проблема заключается в том, что библиотеки DLL, которые вы загружаете из источников, отличных от поставщика, иногда могут быть загружены вирусами или другими вредоносными программами, которые могут заразить ваш компьютер. Это особенно верно для веб-сайтов, которые не слишком заботятся о том, откуда берутся их файлы. И это не так, как будто эти сайты сделают что-нибудь, чтобы рассказать вам о своих источниках высокого риска.
К счастью, процесс установки IL Minihost Modular.dll довольно прост. Короче говоря, все, что вам нужно сделать, это скопировать оригинальный файл DLL в C: Windows System32. После копирования .DLL выполните следующую команду: regsvr32 IL Minihost Modular.dll и ваш .DLL будет успешно установлен.
Единственный способ убедиться, что вы получаете стабильный, современный и чистый IL Minihost Modular.dll, — это получить его из источника, из которого он поступил.
#1 2008-09-21 13:52:57
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
[SOLVED]Error opening PCM device hw:0,0
I am trying to use Jesusonic, but I get the following error:
mmanu > Desktop/jesusonic-0.991-linux-x86/jesusonic -mode ALSA -nbufs 2
Jesusonic v0.991 - Copyright (C) 2004-2005 Cockos Incorporated
Using output mode: 'ALSA'
Opening ALSA 'hw:0,0' for read
Opening ALSA 'hw:0,0' for write
Error opening PCM device hw:0,0
My audio card is an integrated Intel one:
Audio device: Intel Corporation module: snd-hda-intel
82801G (ICH7 Family) High Definition Audio Controller
I am not very expert with audio devices and functionality, so is there anything I can look up or do to solve this problem?
Thank you for your time
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#2 2008-09-21 14:34:00
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
What’s the output of cat /proc/asound/cards?
#3 2008-09-21 14:46:29
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Here you go:
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0580000 irq 16
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#4 2008-09-21 15:41:58
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
Hi again finferflu,
I downloaded the software and it’s working here, so bare with me while I guess (which I am doing). What about cat /proc/asound/devices?
#5 2008-09-21 15:49:39
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Thanks, skottish, for your effort
Here you go:
2: : timer
3: : sequencer
4: [ 0- 1]: digital audio playback
5: [ 0- 0]: digital audio playback
6: [ 0- 0]: digital audio capture
7: [ 0- 0]: hardware dependent
8: [ 0] : control
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#6 2008-09-21 16:06:22
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
My lack of understanding is really showing here…
The default format for alsa is implicitly defined like this:
jesusonic -mode ALSA -in hw:0,0 -out hw:0,0
I’m posting this in the hope that someone that knows hardware will be able to tell you how to identify the proper address. Of course another (very hackish) solution is to just try some other value like hw:0,1 on both. 0,0 and 0,1 work on my machine, but it fails with the same error you have on 0,2.
Last edited by skottish (2008-09-21 16:17:33)
#7 2008-09-21 20:34:01
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Thanks, skottish!
jesusonic -mode ALSA -nbuff 2 -in hw:0,0 -out hw:0,1
Was the way to go.
Now I just wonder: do you also get an empty effects menu? Last time I have used Jesusonic it was full of effects… I might be missing some other download perhaps…
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#8 2008-09-21 20:52:31
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
When I get to the first screen, it says «No effects active — hit A to add an effect». When I hit ‘a’, I get a list of effects: Delay, Guitar, Meters,… Is this what you’re missing?
Last edited by skottish (2008-09-21 20:54:48)
#9 2008-09-21 20:54:10
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Yes, that’s what I’m missing, I don’t see any list.
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#10 2008-09-21 20:55:53
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
finferflu wrote:
Yes, that’s what I’m missing, I don’t see any list.
I’m sort of stuck how much farther I can help. If I add anything to the list I get a segfault. It’s probably because I’m missing something; I’m on 64 bit and got lucky with the 32 bit libraries that I have.
#11 2008-09-21 21:01:42
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
I’m on a 32bit, but the app is recommended for usage on a 64bit machine (I know it works on 32bit because I have used it in the past on my previous 32bit machine).
EDIT:
Found out: my working directory wasn’t the one containing the jesusonic executable, so I guess the app follows a relative path. That’s it!
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#12 2008-09-21 21:16:09
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
The download that I found is without a doubt 32 bit. It’s the only one I found. Although, they do reference a 64 bit version of Reaper on the page which includes Jesusonic.
#13 2008-09-21 22:05:13
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Ok, I must have misread it…
Anyway, I found where the error was actually lying: Firefox was apparently using the playback device, so it was busy. Stupid me, not thinking about it before.
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- Multimedia Software
- [SOLVED] alsa cannot open audio device hw:1,0 [Input/output error] question
-
alsa cannot open audio device hw:1,0 [Input/output error] question
I found out last year an easy way to convert VHS to an mkv file with flac sound
but now I am getting an alsa problem everytime and have no idea whyNothing I can see has changed
Code:
cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf220000 irq 130 1 [Alpha ]: USB-Audio - Lexicon Alpha Lexicon Lexicon Alpha at usb-0000:00:14.0-6, full speed 2 [CAMERA ]: USB-Audio - USB2.0 PC CAMERA ARKMICRO USB2.0 PC CAMERA at usb-0000:00:14.0-3, high speed
Code:
ffmpeg -f v4l2 -standard PAL -thread_queue_size 1024 -i /dev/video0 -f alsa -thread_queue_size 1024 -i hw:1,0 -c:v libx264 -s 720x576 -b:v 2400k -vf eq=saturation=0.5 -r 25 -aspect 4:3 -c:a flac -channels 2 -ar 48000 outfile.mkv ffmpeg version 3.4.6-0ubuntu0.18.04.1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-16ubuntu3) configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared WARNING: library configuration mismatch avcodec configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc libavutil 55. 78.100 / 55. 78.100 libavcodec 57.107.100 / 57.107.100 libavformat 57. 83.100 / 57. 83.100 libavdevice 57. 10.100 / 57. 10.100 libavfilter 6.107.100 / 6.107.100 libavresample 3. 7. 0 / 3. 7. 0 libswscale 4. 8.100 / 4. 8.100 libswresample 2. 9.100 / 2. 9.100 libpostproc 54. 7.100 / 54. 7.100 [video4linux2,v4l2 @ 0x5561a6784bc0] This device does not support any standard [mjpeg @ 0x5561a6785f60] EOI missing, emulating Input #0, video4linux2,v4l2, from '/dev/video0': Duration: N/A, start: 3412.361590, bitrate: N/A Stream #0:0: Video: mjpeg, yuvj422p(pc, bt470bg/unknown/unknown), 640x480, 30 fps, 30 tbr, 1000k tbn, 1000k tbc [alsa @ 0x5561a678ba00] cannot open audio device hw:1,0 (Device or resource busy) BUT IT IS NOT BUSY WITH any process i can see hw:1,0: Input/output error
Last edited by shantiq; May 7th, 2020 at 08:09 AM.
Linux is Latin for off-the-beaten-track
what I like MOST about our Ubuntu … The Community
Playing with Slackware too now …
ShanArt
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
BUT IT IS NOT BUSY WITH any process i can see
So you looked at?:
Have you considered trying ‘-f pulse’ instead of ‘-f alsa’?
https://ffmpeg.org/ffmpeg-devices.html#pulse
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
thanx Pasque
➊ had looked at
which i take it shows processes still alive? and then to kill them with or I suppose?➋ As regards pulse yes that sounds good but requires a reconfig
Code:
To enable this output device you need to configure FFmpeg with --enable-libpulse.
There must a way to reset alsa so it does not glitch like this maybe here altho a tad loath to try those routes as many say they often worsen matters
PS =====
i used same command on an older PC I have got with Slackware installed and it is working with same ffmpeg command and fine there altho once it also gave me the
Code:
(Device or resource busy)
runaround
Sound is often a puzzle on Linux :]
Anyway many thanx you have provided food for thought here … will play further and see
Last edited by shantiq; May 9th, 2020 at 08:47 AM.
Linux is Latin for off-the-beaten-track
what I like MOST about our Ubuntu … The Community
Playing with Slackware too now …
ShanArt
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
Originally Posted by shantiq
To enable this output device you need to configure FFmpeg with —enable-libpulse.
You don’t have to worry about that. ffmpeg is already built with —enable-libpulse
There must a way to reset alsa so it does not glitch
Well, if something is really using the device, then it is not a «glitch». And no, I wouldn’t try random commands to fix it.
As for lsof, you’ll probably find that pulseaudio itself is responsible for «grabbing» the hw:x,y device. You don’t want to kill that. Are you sure that all applications using/playing audio are stopped before you attempt to use ffmpeg?
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
OK
so
does not appear on my ffmpeg installed on my system or do you mean it is there but not spelt out
Code:
--enable-gpl --enable-libaom --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-openssl --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
And as re: all audio turned off YES emphatically
Last edited by shantiq; May 9th, 2020 at 11:38 AM.
Linux is Latin for off-the-beaten-track
what I like MOST about our Ubuntu … The Community
Playing with Slackware too now …
ShanArt
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
Look at your ffmpeg configuration line:
configuration: —prefix=/usr —extra-version=0ubuntu0.18.04.1 —toolchain=hardened —libdir=/usr/lib/x86_64-linux-gnu —incdir=/usr/include/x86_64-linux-gnu —enable-gpl —disable-stripping —enable-avresample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libmp3lame —enable-libmysofa —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librubberband —enable-librsvg —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxml2 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libdrm —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libopencv —enable-libx264 —enable-shared
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
hi again if i choose pulse it does [as you can see in config not installed here]
Code:
ffmpeg -f v4l2 -standard PAL -thread_queue_size 1024 -i /dev/video0 -f pulse -thread_queue_size 1024 -i hw:1,0 -c:v libx264 -s 720x576 -b:v 2400k -vf eq=saturation=0.5 -r 25 -aspect 4:3 -c:a flac -channels 2 -ar 48000 ~/Desktop/floyd.mkvffmpeg version N-91586-g90dc584 Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-16ubuntu3) configuration: --prefix=/home/shan/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/shan/ffmpeg_build/include --extra-ldflags=-L/home/shan/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/shan/bin --enable-gpl --enable-libaom --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-openssl --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree libavutil 56. 18.102 / 56. 18.102 libavcodec 58. 22.101 / 58. 22.101 libavformat 58. 17.101 / 58. 17.101 libavdevice 58. 4.101 / 58. 4.101 libavfilter 7. 26.100 / 7. 26.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc 55. 2.100 / 55. 2.100 [video4linux2,v4l2 @ 0x55eefd7f5f00] This device does not support any standard [mjpeg @ 0x55eefd7f7500] EOI missing, emulating Input #0, video4linux2,v4l2, from '/dev/video0': Duration: N/A, start: 15065.860398, bitrate: N/A Stream #0:0: Video: mjpeg, yuvj422p(pc, bt470bg/unknown/unknown), 640x480, 30 fps, 30 tbr, 1000k tbn, 1000k tbc Unknown input format: 'pulse'
with
Code:
cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf220000 irq 130 1 [Alpha ]: USB-Audio - Lexicon Alpha Lexicon Lexicon Alpha at usb-0000:00:14.0-6, full speed 2 [CAMERA ]: USB-Audio - USB2.0 PC CAMERA ARKMICRO USB2.0 PC CAMERA at usb-0000:00:14.0-3, high speed
and
Code:
aplay -l**** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Alpha [Lexicon Alpha], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0
Last edited by shantiq; May 9th, 2020 at 12:01 PM.
Linux is Latin for off-the-beaten-track
what I like MOST about our Ubuntu … The Community
Playing with Slackware too now …
ShanArt
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
configuration: —prefix=/home/shan/ffmpeg_build —pkg-config-flags=—static —extra-cflags=-I/home/shan/ffmpeg_build/include
You seem to have two copies of ffmpeg installed, and your local/home copy looks like it’s missing libpulse (and a bunch of other dependencies) for some reason. I honestly don’t know what you’re doing there.
Also, if you’re going to use ‘-f pulse’, you need to use a pulse device (not hw:x,y).
https://ffmpeg.org/ffmpeg-devices.html#pulse
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
ok so pulse not an option as no wish to reinstall ffmpeg if avoidable
was really more wanting to get alsa to «behave»here as it thinks there is a process going on
so my question really is how to prod deeper into alsa so that it reveals where it thinks it is «busy»
Anyone knows of ways of doing this ? I have read around a lot and far come up empty as to a way to «see» what it is doingThank you so much for your help thus far
I know the command is fine as is as it used to work and works on my Slackware oldie so the kink is with alsa here
Last edited by shantiq; May 9th, 2020 at 02:29 PM.
Linux is Latin for off-the-beaten-track
what I like MOST about our Ubuntu … The Community
Playing with Slackware too now …
ShanArt
-
Re: alsa cannot open audio device hw:1,0 [Input/output error] question
so my question really is how to prod deeper into alsa so that it reveals where it thinks it is «busy»
Again,
Please give the output!ok so pulse not an option as no wish to reinstall ffmpeg if avoidable
There is no need to reinstall ffmpeg to use pulse. However, you do need to make sure you’re using the system copy of ffmpeg (like you did in your initial post) and not the copy of ffmpeg you have in your /home.
Tags for this Thread
Bookmarks
Bookmarks
![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%200%200'%3E%3C/svg%3E)
Posting Permissions
Audacity is a free virtual studio software for Windows computers and it’s a great tool to edit music files for free. However, some users have reported having problems when trying to record or play their files using Audacity. The error message read “Error opening sound device” and it has bugged users all over the world.
There are a couple of causes and methods which can be used to solve the problem and we recommend you follow through the rest of the article to find out just what to do to solve the problem.
What Causes Audacity “Error opening sound device” Error?
It’s usually a permissions issue which started to appear after a specific Windows Update because it has reset some permissions settings for apps which are allowed to use your microphone.
Solution 1: Let Apps Use Your Microphone
This little option may have always been turned on before but it might have been changed by new programs being installed or by a Windows Update which might have turned it off for various security reasons. This solution is the simplest and it can save you hours of pain so make sure you don’t skip this method.
Windows 10 Users:
- Click the gear icon in the lower left section of the Start menu in order to open the Settings app. You can also search for it.
- Scroll down until you see the Privacy section and make sure you click on it. At the left side of the window, you should see the App permissions section. Scroll down until you reach Microphone and click on this option.
- First of all, check if the Microphone access for this device option is on. If it’s not, click on Change and set the slider to on.
- After that, switch the slider under the “Allow apps to access your microphone” option to On and scroll down in the list of installed apps on your computer to locate Skype. Switch the slider next to the Skype entry on the list to on.
- Reopen Audacity and check to see if the problem persists.
Further Troubleshooting for Windows 10 and Older Versions of Windows
It’s possible that one of your core sound devices may have been disabled by a program or by a new Windows Update. Also, this can fix the problem if there are other similar tools installed on your computer which might try to access sound devices at the same time as Audacity.
- Right-click on the volume icon located at your taskbar and choose the Sounds option. If this icon is not located at your taskbar, you can locate Sound settings by opening Control Panel, switching the view to Category and selecting Hardware and Sound >> Sound.
- Check to see if your microphone is enabled under the Recording tab. Switch to this tab by clicking at the top of the window and locate the Microphone you are using. It should be located at the top and be selected.
- Click on it once and click the Properties button at the lower right part of the window. In the Properties window which opens, check under Device usage and set the option to Use this device (enable) if it wasn’t already and apply the changes.
- Navigate to the Advanced tab in the same properties window and check under Exclusive mode.
- Uncheck the boxes next to the “Allow applications to take exclusive control of this device” and “Give exclusive mode applications priority”. Apply these changes as well and repeat the same process for your Speaker device in the Playback tab before you close these windows. Reopen Audacity and check to see if the error persists.
Note: Even if you are a Windows 10 user, you should still try out the second set of steps as they managed to solve the problem for some Windows 10 users when the above has failed.
Solution 2: Use the Built-in Voice Recorder and Switch to Audacity
It’s quite possible that a third party app is hogging one of your sound devices and it’s almost impossible to take ownership of it once more. The reason why opening Voice Recorder which is built into your Windows OS might work is because this app is verified by Microsoft and it has better permissions than any third-party app.
The Voice Recorder is available on all versions of Windows so make sure you use it to solve the Audacity “Error opening sound device” error!
- Search for Voice Recorder’s shortcut on the Desktop and double-click it, or search for it in the Start menu. If you struggle finding it, you can use the command below.
- Search for “Command Prompt” by typing it either right in the Start menu or by pressing the search button right next to it. Right-click the first entry which will pop up as a search result and select the “Run as administrator” context menu entry.
- Type in the command below in the window and make sure you press Enter after typing each one. Wait for the Voice Recorder window to open to know that the command worked
explorer.exe shell:appsFolderMicrosoft.WindowsSoundRecorder_8wekyb3d8bbwe!App
- Click the microphone button in order to start a recording. Close Voice Recorder and reopen Audacity to see if the problem still appears.
Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.
Back to top button