Bug Report

[FireUponDeep2]

Hey there,

first of all, these plugins are great! They make the synths so much more useful. But I have a few problems here. First things first, hard & software:

Synths:
Roland JX8P
DSI Evolver (Desktop Version)
Moog Little Phatty Stage II

Computer:
iMac 20", core 2 duo, 2.4GHz, 2GB Ram

Software:
OSX 10.6.4
Logic Pro 9.1.1 (run in 32bit Mode)

Problem 1:
After starting Logic Pro, whichever ctrlr plugin is loaded first, will work.
Subsequently loaded ctrlr plugins will come up with the GUI area completely blank/white (to be exact: GUI is shown for a split second, and then replaced with a blank/white area, no controls at all shown).

Example:
If I load the JX8P plug first, it will work. Phatty & Evolver will not work.
If I load the Evolver plug first, it will work, JX8P and Phatty won’t.
If I load the Phatty plug first, it will work, JX8P and Evolver won’t.

This is true when used on the same track, and also on a new created track. Only when Logic Pro is quitted and re-started will another of those plugs work. But only the first one used.

Problem 2:
Plugins don’t seem to remember the MIDI device selection from the preferences.

Problem 3:
Saving Programs and reloading them has no effect…. to be more exact: It doesn’t reflect the GUI settings, instead, plugin stops working entirely.

If there’s ANYTHING that I can do to help and contribute, please let me know, I’m more than happy to help get these things working. It’s just, I’m not a programmer, I can do thorough testing, but not go into the code.

Cheers
FireUponDeep

PS: The other FireUponDeep is also me, but I never got the registration mail to the e-mail address I used there. So you can delete the first FireUponDeep.

[FireUponDeep2]

Okay, even though nobody is responding… here’s some more testing:

1. Inside Logic, the three Ctrls I’m using — Evo, Phatty, JX8P — seem to share their preference settings dialog. Changing e.g. the MIDI channel on one, will have the same MIDI channel selected on the next.
2. The MIDI device setting will not be remembered (reported before).
3. Getting the device state or any programm doesn’t work at all, on none of the crtrls, neither in AU, nor in standalone. MIDI in/out of synths are correctly connected.
4. Preference settings always open behind plugin window.
5. The audio input options (available in the standalone) are missing, but sometimes a feedback loop is created that suggests they’re actually active.
6. Phatty editor misses many of the synth’s features (specifically all of those that were added with newer Phatty OS versions in 2008/2009 and are selectable via the LCD menu).
7. As reported before, the GUI goes away for the 2nd ctrlr opened. I’ve found a way to get it back: In the AU Window there’s a "view" button (upper left). Put it to "slider" and back to "GUI". (I’m on the German version of Logic, so the actual words in your version may differ).

That’s all so far. Again, if there’s anything I can do besides coding, let me know. I really want those things to work.

FireUponDeep

[atom]

I’m reading all posts don’t worry, i’m doing the new engine and the work is progressing, all bug reports are welcome.

Some of theese will be fixed definetly. For the Phatty i’ll need a MIDI Specs if there are new parameters to add.

[FireUponDeep2]

"atom":122itmd6 wrote:

For the Phatty i’ll need a MIDI Specs if there are new parameters to add.[/quote:122itmd6]

Yes, many advanced parameters were added, e.g. additional modulation sources, noise as modulation, per-patch filter pole selection, arpeggiator, etc.

But the sysex specs are not in the manual. Can I somehow grab them from the synth directly? I have the standalone Phatty Editor from Soundtower; it does save banks of course, but as far as I can tell, not in human readable/xml format.

FireUponDeep

[atom]

well if it’s sysex then i don’t think that phatty will send those, you can hook up MIDI OX to the soundtower editor instead of the actual phatty and see what sort of data is going on the wire, or post a link to some trial/demo version, i’ll have a look.

[FireUponDeep2]

The editor is here, I think it does run in demo mode if not registered:

http://www.soundtower.com/moog/littlephatty/index.htm

They also have an editor for the Evolver. They are quite good, except that they do not run as a plugin, only standalone.

I’ll take a look at MIDI OX, perhaps I can figure something out.

FireUponDeep

[FireUponDeep2]

Hello there ” title=”Smile” />

Checked the latest versions today, only quickly though. Many of the bugs I mentioned earlier are gone. Remaining & new Problems:

JX8P ctrlr does not send changes to the synth at all, but works otherwise.
Little Phatty ctrlr uses 8bit resolution for the knobs (cutoff, resonance, etc.) but they should be 14bit (or even 16?)
Little Phatty ctrlr does not reflect the 2008 Phatty OS with its many extended preset features.
EVO ctrlr seems to be working, although I’ve not looked at the sequencer window yet.

All of the ctrlrs:
– Menus don’t work properly, open only once, and then the itmes are greyed out.
– Configs are not remembered
– Feature to receive or send a patch/bank to and from machine missing (or not working @JX8P ctrlr)
– In Logic, if two synths share the same MIDI bus, they sometimes play together, even if on different MIDI channels. Using VST Output, MIDI Through, setting input to Capslock keyboard, and the receiving MIDI channel (instead of All) in the Logic track solves the problem. Took some time to figure that one out, tho.

Cheers
FireUponDeep

[atom]

What i can say without looking at any code

LittlePhatty changes for some newer OS, post a link to a manual, i’m afraid i don’t track changes to OSes to all Ctrlrs.

– menu bug is still there yes, use the toolbar to access all options
– that’s weird, but i need to make new OSX builds cause i think they’re old compared to Windows and there was a bug like that
– that does not work, and will not work anytime soon (you can only send the current Ctrlr send as a snapshot to the device, sysex patch send/receive is not an option at the moment)

[atom]

What i can say without looking at any code

LittlePhatty changes for some newer OS, post a link to a manual, i’m afraid i don’t track changes to OSes to all Ctrlrs.

– menu bug is still there yes, use the toolbar to access all options
– that’s weird, but i need to make new OSX builds cause i think they’re old compared to Windows and there was a bug like that
– that does not work, and will not work anytime soon (you can only send the current Ctrlr send as a snapshot to the device, sysex patch send/receive is not an option at the moment)

[acatcalledanarchy]

Hi guys

Just thought I’d chip in here with a list of new CC’s for Little Phatty

[b:31tcu37p][u:31tcu37p]OS 2.0:[/u:31tcu37p][/b:31tcu37p]

Mod Wheel
MSB = 1, LSB = 33

Filter Cutoff:
MSB = 19, LSB = 51

[b:31tcu37p][u:31tcu37p]OS 2.2:[/u:31tcu37p][/b:31tcu37p]

LFO Sync Source CC 102
LFO Sync Clock Divisions CC 103
Mod Source 5 Select CC 104
Mod Source 6 Select CC 105
Mod Destination 2 CC 106
Pitch Bend Down Amount CC 107
Pitch Bend Up Amount CC 108
Filter Poles CC 109
Filter Velocity Sensitivity CC 110
EG Release On/Off CC 111
EG Legato On/Off/Reset CC 112
Arpeggiator Enable On/Off CC 113
Arpeggiator Clock Rate[b:31tcu37p]**[/b:31tcu37p] CC 4, CC 36
Arpeggiator Clock Source CC 114
Arpeggiator Clock Divisions CC 115
Arp. Range (octaves) CC 116
Arp. Pattern CC 117
Arp. Mode CC 118
Arp. Latch Enable CC 119
Arp. Run/Stop CC 90
Arp Latch/Unlatch CC 91
KB Note Priority CC 88

[b:31tcu37p]**[/b:31tcu37p] Arpeggiator Clock Rate is set by CC 4 in increments of 3BPM over a range of 21 – 320 BPM. You can fine adjust this with CC 36 in increments of 0.1 BPM, which is added to the value set by CC 4. So to set any BPM range 21-320, take your target BPM and divide by three. The resulting integer (while number) is your CC4 value. However many "extra" BPM you need to reach your target, multiply this remiander by 10 and this is your CC 36 value.

Example: we want to set the Arp Clock rate to 121.7 BPM.
121.7 / 3 = 40.566…
CC 4 value = 40
LP displays: 120BPB
we need to add 1.7 BPM to get 121.7
1.7 * 10 = 17
CC 36 value = 17
LP displays: 121.7BPM

[b:31tcu37p]Reminder: Arpeggiator must be ON and Arp Clock set to Internal in order to show the internal BPM on the LP display.[/b:31tcu37p]

Below are some tables of MIDI CC values corresponding to LP parameter values for the newly-implemented MIDI CCs:

[b:31tcu37p]Mod 2 Destination:[/b:31tcu37p]
0-24 = Off
25 – 49 = Pitch
50 – 74 = Filter
75 – 99 = Wave
100 – 127 = Osc 2

[b:31tcu37p]LFO Clock Divisions[/b:31tcu37p]
[i:31tcu37p](same for ARP Clock Divisions)[/i:31tcu37p]

0-7 = 1/32
8-15 = 1/32 dot
16-23 = 1/16
24-31 = 1/16 dot
32-39 = 1/8
40-47 = 1/8 dot
48-55 = 1/4
56-63 = 1/4 dot
64-71 = 1/2
72-79 = 1/2 dot
80-87 = Wh
88-95 = Wh + 1/4
96-103 = Wh + 1/2
104-111 = Wh + 1/2 dot
112-127 = Wh + Wh

[b:31tcu37p]Gate Modes:[/b:31tcu37p]
0-42: Legato On
43-85: Legato Off
86-127: Legato Reset

[b:31tcu37p]Arp Pattern:[/b:31tcu37p]
0-42: Up
45-85: Down
86-127: Order

[b:31tcu37p]Arp Mode:[/b:31tcu37p]
0-42: Loop
43-85: Back/forth
86-127: Once

[b:31tcu37p]Arp Clock Source:[/b:31tcu37p]
0-42: Internal
43-85: LFO
86-127: MIDI

[b:31tcu37p]Arp Octave Range:[/b:31tcu37p]
0-18: -3
19-37: -2
38-56: -1
57-70: 0
71-89: 2
90-108: 2
109-127: 3

[b:31tcu37p]Filter Sensitivity:[/b:31tcu37p]
0-11: -8
12-18: -7
19-25: -6
26-32: -5
33-39: -4
40-46: -3
47-53: -2
54-60: -1
61-67: 0
68-74: +1
75-81: +2
82-88: +3
89-95: +4
96-102: +5
103-109: +6
110-116: +7
117-127: +8

[b:31tcu37p]Filter Poles:[/b:31tcu37p]
0-31: 1
32-63: 2
64-95: 3
96-127: 4

[Author]

Posts