Dexed error opening midi ports

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

deadpahn opened this issue

Mar 6, 2016

· 3 comments

Comments

DAW: Renoise
INTERFACE: Native Instrument Komplete 6
SYNTH: Yamaha TX7

Won’t let me connect to the device. Tried it in VST HOST but I still get the error.

This usually occurs on Windows when the midi port is used by another program (e.g. renoise in your case). On windows, some midi drivers doesn’t support multiple program using the same midi port.

Confirm that no other software is using the same midi device and test it again to see if you have the same issue.

I got it to work by using «savihost». Thanks !

On Sun, Mar 6, 2016 at 11:40 PM, Pascal Gauthier notifications@github.com
wrote:

This usually occurs on Windows when the midi port is used by another
program (e.g. renoise in your case). On windows, some midi drivers doesn’t
support multiple program using the same midi port.

Confirm that no other software is using the same midi device and test it
again to see if you have the same issue.

—
Reply to this email directly or view it on GitHub
#57 (comment).

You have to check if the MIDI is activated also in an oher track. I had the dexed activeded in track 1 and 4. And the track 4 had this error because you can not activate the midi in morenthen one track at the same time

Источник

I have managed to load dexed and load hundreds of cartridges, But when i hit the parm button and vhoose my Roland UMONE as the DX7 Out it displays — Error opening midi ports, meaning I cannot use dexed to send these awesome sounds! no other programme is using my Roland midi interface and I just dont know what to do, anyone know what i can do to fix it?

level 1

Running dexed in a standalone plugin host, it only started working when i swapped the usb-to-din-midi adapter against a different one.

level 1

I use the free DAW MuLab for dexed. Don’t add the UMONE in the Parm setting in dexed, instead add it in the midi settings in Mulab (or whatever DAW is your preference)

Link for MuLab: http://www.mutools.com/

Edit: Didn’t realize this was posted 18 days ago lol. Hopfeully you got it sorted!

level 1

Literally had this problem yesterday with my new Volca FM. I don’t use the same DAW (I use Ableton), but I noticed that after I turned the track sync off in the settings I was able to connect Dexed to my Volca. So basically the issue was that Ableton’s midi out to my audio interface that the Volca was connected to had to be turned off so that Dexed could take control. Try seeing if this works for you.

level 1

I logged on to synthmata and my volca synced to the sites online editor then went back into dexed and it allowed me to add it as output, just worried I’ll never get it working with dexed again cause it was a total accident

level 1

I got it sorted but thank you

Источник

«Midi Interface: Error Opening Midi Ports»

DAW: Renoise
INTERFACE: Native Instrument Komplete 6
SYNTH: Yamaha TX7

Won’t let me connect to the device. Tried it in VST HOST but I still get the error.

asb2m10

This usually occurs on Windows when the midi port is used by another program (e.g. renoise in your case). On windows, some midi drivers doesn’t support multiple program using the same midi port.

Confirm that no other software is using the same midi device and test it again to see if you have the same issue.

I got it to work by using «savihost». Thanks !

On Sun, Mar 6, 2016 at 11:40 PM, Pascal Gauthier notifications@github.com
wrote:

This usually occurs on Windows when the midi port is used by another
program (e.g. renoise in your case). On windows, some midi drivers doesn’t
support multiple program using the same midi port.

Confirm that no other software is using the same midi device and test it
again to see if you have the same issue.

—
Reply to this email directly or view it on GitHub
#57 (comment).

Источник

Проблема в подключении, помогите (Проблема USB-MIDI в Win7 64) (1 онлайн

4ever

New Member

Добрый вечер, уважаемые форумчане.

Обладаю ноутбуком с системой Windows 7 — 64 бит. Также владею контроллером AKAI MPD 26.

Вот уже 3 дня я бьюсь над проблемой. При подключении контроллера к ноутбуку — ноутбук видит устройство, всё в порядке. При включении Standalone продуктов от Native Instruments (Kontakt, Battery, Massive) всё хорошо работает, MIDI- сообщения доставляются. Но стоит включить Nuendo/Cubase/FL (в общем, любой DAW), MIDI-сообщения не идут в секвенсор. То есть вообще не происходит доставка. Индикаторы MIDI молчат.

Установил программу Vyzex, которая идет в комплекте с MPD. При загрузке выпадает ошибка: «Can’t open MIDI Out Port AKAI MPD26. Driver may already be in use». То есть программа говорит, что кто-то уже использует порт MIDI.

Залез в мануал к Vyzex. В нем написано, что эта ошибка вылезает из-за того, что драйвер не может быть использован одновременно несколькими программами. Даны инструкции. В том числе: существует конфликт драйверов AKAI с Logitech. А также рекомендации изменить некоторые параметры в реестре. Все параметры изменил, все драйвера Logitech удалил. По-прежнему не работает ничего.

MIDI Monitor не видит сообщений MIDI. Вообще. При этом если смотреть монитор Windows (Команда perfmon — чтобы следить за отправкой сообщений на USB-порт с контроллера), то видно, что сообщения на порт поступают.

Первым делом, конечно же, проверял настройки MIDI- портов в секвенсорах. Всё стоит правильно.
Переустанавливал драйвера USB-портов, материнки (чипсета), всех аудиоустройств.
Удалил все фантомные драйвера (оставшиеся от прежних устройств).
Удалил все приложения типа Steinberg, NI, Sony и т.д. Реестр почистил от «хвостов».
Выставил контроллер MIDI-устройством по умолчанию в Windows (MidiOutId = 1).
Процессы в Windows убивал. Не понимаю, кто использует MIDI-порт..Все-равно не работает.

Уже не знаю что делать!! Помогите пожалуйста.

Источник

Error opening midi ports

Общие обсуждения

due to an advice that was given to move the discussion to the tech side of Microsoft, I would like to bring up a serious problem of the MIDI interface on Windows 10.

— «Microsoft GS Wavetable Synth» on Windows 10 not working with midiOutOpen

— Midi input ia the Win32 function «MidiInOpen» is extreme slow so that is useless

I hope bringing it up here helps to get more clarity and to get the problem resolved asap which have been reported since Dec. 2nd, 2014 and April, 13 2015 respectively.

Перемещено Brandon Records Moderator 24 июня 2015 г. 17:52 Moved to more appropriate forum.

Все ответы

In order to demontrate the issue I have created a little code snipset (same as what Notation Softare uses) in a little app to demonstrate the problem with midiOutOpen. Please download the app (Test_Midi_Ports.exe). The cpp code snipset is in file

You can also find the according VS2010 project file from here.

The «Microsoft GS Wavetable Synth» can be perfectly opened on Windows XP, 7, 8.1. But on Windows 10 you will see the issue that midiOutOpen brings the UNEXPECTED ERROR 1.

I have created the same app with VC6 and/or the MFC libraries. The results are the same.

It would be helpful if someone could check this app on his Windows environment and confirms my observations (and/or tell me what might be wrong in that code snipset).

Got these results on Win10 and WIN 8 using your test program:

(the Timidity stuff is not on my WIN8)

Windows 10 without VirtalMidiSynth

Cleck if MIDI Ports work
ID: 0, Portname: Microsoft GS Wavetable Synth
HMIDIOUT: 00000000
Result: Error opening MIDI Output. Error #: 1
ID: 1, Portname: Timidity++ Driver
HMIDIOUT: 009B3820
Opening: OK
Closing: OK
ENTER to quit

Windows 10 with VirtalMidiSynth installed

Cleck if MIDI Ports work
ID: 0, Portname: CoolSoft VirtualMIDISynth
HMIDIOUT: 0071A1C0
Opening: OK
Closing: OK
ID: 1, Portname: Microsoft GS Wavetable Synth
HMIDIOUT: 00000000
Result: Error opening MIDI Output. Error #: 1
ID: 2, Portname: Timidity++ Driver
HMIDIOUT: 00719BE8
Opening: OK
Closing: OK
ENTER to quit

Windows 8 with VirtalMidiSynth installed

Cleck if MIDI Ports work
ID: 0, Portname: CoolSoft VirtualMIDISynth
HMIDIOUT: 00E14998
Opening: OK
Closing: OK
ID: 1, Portname: Microsoft GS Wavetable Synth
HMIDIOUT: 00E66630
Opening: OK
Closing: OK
ENTER to quit

Thanks. Exactly what I see on my Windows PCs.

It demontrates the problem of midiOutOpen on Windows 10 with Microsoft GS Wavetable Synth.

The code snipset is so simple. I hope that now finally somebody from Microsoft take over responsibility and checks why there is a problem in Windows 10.

It is really annoying because I have reported the problem and delivered exactly the same code snipset on Dec. 2nd, 2014.

More testing: I translated the MidiOutOpen-test program of Reinhold to Pascal. Compiled with
Delphi, Delphi-XE and Lazarus. Compiled for both console and window. All six programs give the same result on WIN8 as Reinholds original program.

On WIN10 however the results are different. The problem is opening «Microsoft GS Wavetable Synth». In most cases (and all my console application programs) returns «unspecified error» (1).

In some cases running the window applications the Midi Device works (one or two times, then fails).

It makes no sense — there is no consistence in the results. This made me make some wrong conclusions. For example I thought that it worked after upgrade — but I had installed Timidity and Coolsofts Virtual Midi Synth Configurator. With Virtual Symth + the soundfont FluidR3_GM.sf2 it sounded great and I was happy for a short time.

It would be quite easy for Microsoft to solve the problem: Let Coolsoft do it — add it as a program in the Control Panel called «Soundfont Installer».

PS: The Lazarus window version even reports wrong number of Midi devices (if > 1). Lazarus is 64 bit and my program runs double as fast — I like that. If anybody could compile Reinholds original C++-program to 64 bit and test on WIN10 with CoolSoft Midi Synth Konfigurator, I would be glad.

Источник

Error opening midi ports

General discussion

due to an advice that was given to move the discussion to the tech side of Microsoft, I would like to bring up a serious problem of the MIDI interface on Windows 10.

— «Microsoft GS Wavetable Synth» on Windows 10 not working with midiOutOpen

— Midi input ia the Win32 function «MidiInOpen» is extreme slow so that is useless

I hope bringing it up here helps to get more clarity and to get the problem resolved asap which have been reported since Dec. 2nd, 2014 and April, 13 2015 respectively.

Moved by Brandon Records Moderator Wednesday, June 24, 2015 5:52 PM Moved to more appropriate forum.

All replies

You can also find the according VS2010 project file from here.

The «Microsoft GS Wavetable Synth» can be perfectly opened on Windows XP, 7, 8.1. But on Windows 10 you will see the issue that midiOutOpen brings the UNEXPECTED ERROR 1.

I have created the same app with VC6 and/or the MFC libraries. The results are the same.

It would be helpful if someone could check this app on his Windows environment and confirms my observations (and/or tell me what might be wrong in that code snipset).

Got these results on Win10 and WIN 8 using your test program:

(the Timidity stuff is not on my WIN8)

Windows 10 without VirtalMidiSynth

Windows 10 with VirtalMidiSynth installed

Windows 8 with VirtalMidiSynth installed

Thanks. Exactly what I see on my Windows PCs.

It demontrates the problem of midiOutOpen on Windows 10 with Microsoft GS Wavetable Synth.

The code snipset is so simple. I hope that now finally somebody from Microsoft take over responsibility and checks why there is a problem in Windows 10.

It is really annoying because I have reported the problem and delivered exactly the same code snipset on Dec. 2nd, 2014.

On WIN10 however the results are different. The problem is opening «Microsoft GS Wavetable Synth». In most cases (and all my console application programs) returns «unspecified error» (1).

In some cases running the window applications the Midi Device works (one or two times, then fails).

It would be quite easy for Microsoft to solve the problem: Let Coolsoft do it — add it as a program in the Control Panel called «Soundfont Installer».

Источник

MIDI Communication Issues

If you see the MIDI port names for your controller in the MIDI settings for your DAW or other music applications, it means that the controller is detected by your computer and it’s MIDI ports can transmit data to and from the controller.

If you find that the controller is listed in your DAW/music application but you cannot hear sound when you play the keys or you don’t see parameters move when you adjust the controls, there may be a communication issue.

If you find that is the case, there are tools available for OS X and Windows which can help you diagnose the problem.

Windows

After completing the installation process, close any applications you have open and start MIDI Ox.
Open the ‘Options’ menu.
Select ‘MIDI Devices’.
Activate each of the ports associated with your controller, under the ‘MIDI Inputs’ list.
5. Click ‘OK’.
* Note: If, at this point, you encounter a message which indicates that there is not enough memory for the task (see image 2 on the right), it actually means that another application is accessing one or more of the devices MIDI ports. In Windows only one application can access a devices MIDI ports at a time. See the troubleshooting section below for more details.
Press a key on the keyboard (if your controller has a keyboard). You should see Note On and Note Off data in the form of light green and dark green text, (as shown in image 3 on the right)
Move a control. You should see a stream of controller data in the form of blue (MIDI CC), pink (Pitch Bend) or light green (Aftertouch) text.

Image 1) MIDI Ox

Image 2) MIDI Ox Error

Image 3) MIDI Ox Data

Audio MIDI Setup
There is a utility called Audio MIDI Setup (AMS) built into OS X. This utility has a basic test tool which can detect some types of incoming MIDI messages.

Open a Finder window.
Open your Applications directory or open the ‘Go’ menu at the top of your screen.
Select ‘Utilities’.
In Utilities, double-click on ‘Audio MIDI Setup’ (the icon looks like a controller keyboard).
In Audio MIDI Setup, open the ‘Window’ menu.
If you see the option to ‘Show MIDI Studio’, click on it. If you see an option to ‘Hide MIDI Studio’, the MIDI Studio window should already be visible.
In the MIDI Studio window, check if you see an icon associated with your controller. If you have had a number of MIDI devices connected to your computer, you may need to expand the window to see all of the icons.
If you see an icon for your controller, click the ‘Test Setup’ button (see Image 4)
Press a key on your controller and then release it.

When you release the key, you will hear a small noise which indicates that a Note Off message has been received. You will also see an arrow flash blue, under the port which the Note Data was transmitted on. Note: If you are using a controller which doesn’t have keys, follow the instructions for using MIDI Monitor, below.

MIDI Monitor (download link)
MIDI Monitor is very useful if you need to test a controller without keys or if you need to see more information about the data which your controller is transmitting.

Drag MIDI Monitor to your Applications folder (or some place you can find it).
Start MIDI Monitor.
Press a key on your controller and release it. You will see Note On and Note Off data appear in the monitor window.
Move a control. You will see a stream of controller data appear in the controller window. (see image 5 for an example).

Источник

Добрый вечер, уважаемые форумчане.

Обладаю ноутбуком с системой Windows 7 — 64 бит. Также владею контроллером AKAI MPD 26.

Уже не знаю что делать!! Помогите пожалуйста!!!

P.S. У супруги на Win7 64 все работает хорошо….

Последнее редактирование: 30 Янв 2015

Так и знал, что никто не ответит.

Поскольку потратил 3 дня на решение этой проблемы, поделюсь что я сделал, чтобы ее решить. Пусть решение лежит здесь, может кто-то наткнется на него и будет мне благодарен:laugh:

Итак, проблема решена следующим образом:

— Пуск — выполнить — вводим команду regedit (или прямо в поисковой строке пуска)
— Идем по адресу HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionDrivers32
— Удаляем все файлы с названиями «midi», «midi 1» и т.д.
— Идем по адресу HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Class/4D36E96C-E325-11CE-BFC1-08002BE10318
— Удаляем файл UpperFilters (если есть)
— Правой кнопкой мыши под файликами — Вручную выбираем Создать мультистроковую переменную — вводим ее имя «UpperFilters» — вводим значение «ksthunk».
— Устанавливаем устройство в систему.
— Насладжаемся.

Так и знал, что никто не ответит.

Поскольку потратил 3 дня на решение этой проблемы, поделюсь что я сделал, чтобы ее решить. Пусть решение лежит здесь, может кто-то наткнется на него и будет мне благодарен:laugh:

Итак, проблема решена следующим образом:

— Пуск — выполнить — вводим команду regedit (или прямо в поисковой строке пуска)
— Идем по адресу HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionDrivers32
— Удаляем все файлы с названиями «midi», «midi 1» и т.д.
— Идем по адресу HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Class/4D36E96C-E325-11CE-BFC1-08002BE10318
— Удаляем файл UpperFilters (если есть)
— Правой кнопкой мыши под файликами — Вручную выбираем Создать мультистроковую переменную — вводим ее имя «UpperFilters» — вводим значение «ksthunk».
— Устанавливаем устройство в систему.
— Насладжаемся.

Спасибо тебе, дорогой человек! Пишу тебе из будущего, в котором столкнулся с точно такой же проблемой, что ты описал (даже спецом зарегался на этом форуме чтобы тебе ответить). И так, расскажу как было у меня. Я отключил внутри Cubase 10.5 клавиатуру M-audio Keystation49 в Windows 10 64, потом снова её включил внутри того же кубейса. Он её обнаружил, но миди сигнал не шёл. Винда так же видела клавиатуру. Долго я плясал с бубном прежде чем наткнуться на твоё сообщение. Ты спас меня! Спасибо огромное! Всё заработало! Ура!

Источник

Old
08-17-2012, 07:42 PM

Human being with feelings

Join Date: Nov 2010

Location: Cleveland, Ohio

Posts: 7

Default
Control Surface Error Opening MIDI Ports

I have a Tascam FW-1884 programmed and formatted in the Mackie Control mode in the control surface in Reaper, however, every time I open my projects, the error reports an error in opening the midi ports.

Old
08-17-2012, 08:02 PM

Human being with feelings

Join Date: Sep 2007

Posts: 1,116

Default

Disable your Tascam Midi Ports in & out in Preferences — Audio — Midi Devices.

Old
08-17-2012, 10:16 PM

Human being with feelings

Join Date: Jun 2011

Posts: 68

Default

Disable fw1884 control under midi devices, only use it in mackie control midi input and output in control sufaces

Old
08-18-2012, 03:25 AM

Human being with feelings

Join Date: Oct 2010

Location: Charleston, SC

Posts: 10,902

Default

How did a Cubase sneak in here ? Hehehe

Источник

Moderators: MattKingUSA, khz

Frank Carvalho: Established Member; Posts: 363; Joined: Sat Nov 17, 2012 3:36 pm

Dexed MIDI output?

I read that Dexed would work as an editor for the DX7. However, when I start it in Carla — or in any other way — the patchbay shows only a MIDI in, and no MIDI out to connect to the MIDI interface. Anyone knows how to activate MIDI out on dexed.
Is there any other usable DX7 patch editor I can use?

/Frank

Vox, Selmer, Yamaha and Leslie amplifiers. Rickenbacker, Epiphone, Ibanez, Washburn, Segovia, Yamaha and Fender guitars. Hammond, Moog, Roland, Korg, Yamaha, Crumar, Ensoniq and Mellotron keyboards. Xubuntu+KXStudio recording setup.

StudioDave: Established Member; Posts: 753; Joined: Sat Nov 01, 2008 1:12 pm

Re: Dexed MIDI output?

Post

by StudioDave » Fri May 15, 2015 4:35 pm

Frank Carvalho wrote:
I read that Dexed would work as an editor for the DX7. However, when I start it in Carla — or in any other way — the patchbay shows only a MIDI in, and no MIDI out to connect to the MIDI interface. Anyone knows how to activate MIDI out on dexed.
Is there any other usable DX7 patch editor I can use?

Hexter

http://dssi.sourceforge.net/hexter.html

Best,

Frank Carvalho: Established Member; Posts: 363; Joined: Sat Nov 17, 2012 3:36 pm

Re: Dexed MIDI output?

Post

by Frank Carvalho » Fri May 15, 2015 4:53 pm

falkTX wrote:I don’t think dexed does MIDI out.

Hmm. Odd, because the project page says:

Using as a DX7 editor

You can use this plugin to edit your real DX7 patchs. Since midi sysex send/receive are quirky for the majority of VST hosts, any sysex messages (editor messages) must be send or received with the external Dexed midi interface. This is configurable in the «PARM» panel. By setting a DX7 in / DX7 out midi interface, Dexed will listen to specific program/cartridge changes from your DX7 and send controller/program/cartridge you edit.
Prerequisite

Before you use this interface, your DX7 must be configured to send or receive sysex messages. Do this by hitting [FUNCTION] and [8] button
Check the midi channel. By reading some of DX7 literature, most DX7 are supposed to support only 1 channel. Unless you are running a cluster of DX7, you should keep this to 1.
Press [8] again and you should see: «SYS INFO AVAIL» or «SYS INFO UNAVAIL». Keep it to «SYS INFO AVAIL» to be able to receive sysex messages. This step is not required on a TX7.
You need to remove MEMORY PROTECT on the internal or cartridge memory to be able to receive a Dexed 32 voice bulk dump. This is done by using the [MEMORY PROTECT] button and then by pushing [NO].

To send to your DX7

If the midi out port is configured, any parameter change will be sent to your DX7.
If the midi out port is configured, you should see the [SEND] button, if not this button won’t be available.
You can use this [SEND] button on Dexed to send program or cartridge changes to your DX7. Be sure you have set [MEMORY PROTECT] is set to NO so the cartridge (internal or external one) on the DX7 can be overridden.

But I don’t know what they mean by «the external Dexed midi interface». Sure enough, the editor has a «param» button, to configure DX7 in and out, but the only choice is «None». So something must be missing form the equation.

I also noticed that Hexter wouldn’t work either. So do I really have to use a Windows editor under Wine???
/Frank

Frank Carvalho: Established Member; Posts: 363; Joined: Sat Nov 17, 2012 3:36 pm

Re: Dexed MIDI output?

Post

by Frank Carvalho » Fri May 15, 2015 6:22 pm

so the midi ports it will supposedly show are hardware alsa-midi ones.

What does that mean? Forgive my lack of knowledge about the workings of ALSA, but even an external device would have to show up as a device in ALSA, would it not?
I was trying to use this with my newly working (recently, see another thread) Quattro USB card — which should appear as an external MIDI interface. I can send sysex to the DX7, through the Quattro with a command like

Code: Select all

amidi -p hw:1,0,0 -s mydx7patch.syx

… that is, if JACK is not running. So I assume I am communicating MIDI through ALSA this way, with a MIDI device called hw:1,0,0. So are you saying I could communicate from dexed with hw:1,0,0 then?
That would be OK for programming, except it prevents me from running JACK at the same time. Unless there’s a JACK-ALSA-bridge that would do the job?

/Frank

Frank Carvalho: Established Member; Posts: 363; Joined: Sat Nov 17, 2012 3:36 pm

Re: Dexed MIDI output?

Post

by Frank Carvalho » Fri May 15, 2015 7:53 pm

Thanks, I’ll give them a try.

/Frank

Источник

Join the conversation

You can post now and register later.

If you have an account, sign in now to post with your account.

Note: Your post will require moderator approval before it will be visible.

Источник

Comments

«Midi Interface: Error Opening Midi Ports»

Проблема в подключении, помогите (Проблема USB-MIDI в Win7 64) (1 онлайн

4ever

New Member

Error opening midi ports

Общие обсуждения

Все ответы

Error opening midi ports

General discussion

All replies

MIDI Communication Issues

Windows

Image 1) MIDI Ox

Image 2) MIDI Ox Error

Image 3) MIDI Ox Data

Dexed MIDI output?

Re: Dexed MIDI output?

Re: Dexed MIDI output?

Re: Dexed MIDI output?

Re: Dexed MIDI output?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Читайте также: