Recent Posts

Pages: [1] 2 3 ... 10
1
This is not the mod for QCON, sorry.
Primary advantages of mentioned mod was re-assignable buttons and modified fader ranges.
From what I have observed about the topic, firmware updates have made the device really mackie compatible. So check if you have the last one.
2
And does it also work for the icon qcon xs. The extenders
3
is this the costume mackie controll dll for Icon qcon pro x on sonar? cause the download link doesnt work anymore and i really need to use my icon qcon pro x .if not could you please make another link with this dll .and thank you so much for your great work your the best here is the old link http://forum.cakewalk.com/Custom-Version-of-Mackie-Control-Surface-Plugin-to-use-the-QCON-m3092979.aspx#3092979
4
Presets / Re: [MarKo] BCR2000
« Last post by Bassman on July 24, 2018, 09:49:42 AM »
Hi Alexey:)

Ich versuche es im Laufe der Woche, bin noch im Stress bis zum Urlaub....... danke;)

Heinz.


P.S. Es funktioniert, vielen Dank dafür:)
5
Presets / Re: [MarKo] BCR2000
« Last post by azslow3 on July 21, 2018, 10:02:36 AM »
Versuch mit b393

Ich hatte mit eine Virtuele Machine Tests gemacht, dort funktionierte es ohne Änderungen, auf normale doch nicht.
Aber jetzt macht es was es soll auf alle meine Rechner.
6
Presets / Re: [MarKo] BCR2000
« Last post by Bassman on July 15, 2018, 08:49:03 PM »
@Alexey

Mach dir bitte keinen Stress! Wenn es nicht geht dann ist es halt so:) 

Liebe Grüsse,
Heinz.
7
Presets / Re: [MarKo] BCR2000
« Last post by azslow3 on July 15, 2018, 09:56:05 AM »
Das Problem ist tief... Es betrifft nur bestimmte Kombinationen,  z.b. Up/Down/Left/Right mit Shift.
Ich benutze Sonar API und damit kann ich nicht das Problem umgehen. Ich muss dann auf Windows API umschalten, das probiere ich nächste Woche.
 
8
Discussions / Re: AZ: Not a Mouse (a mouse as a dedicated REAPER controller)
« Last post by azslow3 on July 05, 2018, 08:52:39 PM »
.
9
Discussions / Re: AZ: Not a Mouse (a mouse as a dedicated REAPER controller)
« Last post by azslow3 on July 05, 2018, 08:15:45 PM »
Configuration for Mouse
  • In the REAPER preferences, Control Surfaces/OSC, add "AZ: Not a Mouse"
  • Select the mouse (only switched in Zadig devices will be shown, so you can not make mistake here)
  • Choose MIDI channel the messages will be sent to (useful for several "Not Mouses" with different bindings)
  • Use usual for MIDI surfaces procedure for Actions binding. For Wheel, select "Relative 1" mode

Configuration for Keyboard
  • In the REAPER preferences, Control Surfaces/OSC, add "AZ: Not a Keyboard"
  • Select the keyboard (only switched in Zadig devices will be shown, so you can not make mistake here)
  • Choose MIDI channel the messages will be sent to (useful for several devices with different bindings)
  • Use usual for MIDI surfaces procedure for Actions binding


In case you like my projects in Control Surfaces area, here is Donation link
Please note that you do not buy a license nor any special service.
10
Discussions / Re: AZ: Not a Mouse (a mouse as a dedicated REAPER controller)
« Last post by azslow3 on July 05, 2018, 08:02:00 PM »
Installation
AZ: Not a ...
The procedure is standard for REAPER extension.
  • Download the latest version from: http://www.azslow.com/index.php?action=downloads;sa=view;down=64
  • Start REAPER. Select "Options"/"Show REAPER resource path..."
  • Close REAPER (important especially when upgrading)
  • In the downloaded archive select the folder with correct  fro your REAPER version number of bits (32/64) any copy "reaper_aznot.dll" into "UserPlugins" sub-folder of your REAPER resources.if you had reaper_aznm.dll installed, delete it. reaper_aznot.dll is the new name for the same plug-in
Declaring your mouse/keyboard as "not a mouse"/"not a keyboard"
Note: that is not a "hack", the device will just use another standard Microsoft driver.
The following procedure is for Windows 7-10.
WARNING: Do NOT randomly click in this application! You will not break your computer doing that and you can easily revert the change, but the result can be confusing...
  • Download Zadig application from https://zadig.akeo.ie/ . Note that on the right side of the site are Ads... Direct link to the current version: https://zadig.akeo.ie/downloads/zadig-2.3.exe This version is for Windows 7-10, for XP-Vista download older version
  • Disconnect the mouse/keyboard you want to use for REAPER from the computer
  • Start Zadig (no installation required). It should be digitally signed. I repeat: do not randomly click in it! Read the following first! It will ask about online update check, that is up to you what to answer.
  • In the "Options" menu select "List All Devices". For keyboard, un-check "Ignore Hubs or Composite Parents"
  • Open drop-down list of the devices, notice what you see here, you DO NOT want to modify any of them!
  • Connect the mouse/keyboard in question. You should see new choice in the list now. If not sure, disconnect/check/connect again.
  • Once you are sure which mouse/keyboard is right...
  • First select "normal" mouse/keyboard, which you do not want to modify. Write on paper USB ID (2 numbers). Now select your "Not a Mouse/Keyboard". Compare its USB ID with IDs of your normal mouse/keyboard. Are they the same (both numbers)? If yes, do not continue and find another device for the purpose. Windows will have problems using absolutely identical devices with different drivers
  • If USB ID is different, select the device which (sure?) is "Not a Mouse". For keyboards, select "Composite" if you see it (there will be also "Interface 0"/"Interface 1" in this case, but you need the whole device)
  • "HidUsb -> WinUSB" should be already pre-selected. Press "Replace Driver" and confirm the decision. Sometimes it can take a while, but it should report "Success" at the end.
  • Close Zadig. You may need to use it again after major Windows 10 upgrades
Pages: [1] 2 3 ... 10