Hi,
in the previous versions of Prophet V2 (all after 2.0) the Sysex import feature of Prophet V (for both the Prophet 5 and VS Sysex) seemed to be broken.
Also see this thread at the Arturia forum:
http://forum.arturia.com/index.php?topi ... #msg115673
Now i installed the new update that came with the release of the V-Collection 4 and the problem seems to be fixed but now there is a new one.
When a Sysex file is imported no longer the proper name (= name of the Sysex file) is displayed in the banks list at the GUI but only something like "_2", "_2.1", "2.2 etc.". This makes it hard to see which bank is which.
Ingo
Prophet V Sysex import problem
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
One solution for the problem could be changing the bank name manually after import. By clicking at the name of the currently loaded bank (left to the sub-bank + patch selection) you could edit the bank name...
Of course it would be nicer to automatically use the name of the Sysex file at the import.
I just sent an email reply to the support ticket i sent for the original problem (broken Sysex).
Of course it would be nicer to automatically use the name of the Sysex file at the import.
I just sent an email reply to the support ticket i sent for the original problem (broken Sysex).
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
