I like the "Open in Explorer" feature
Cheers
Dennis
As so often, we first want to get some experience. Thing is, multithreading can degrade performance on older systems with a north bridge (or whatever was before that). Even my 8 core Mac Pro - ancient 5 years old - happily chokes with 2 instances in multicore mode.penguinfromdeep wrote:Great stuff! Is there a possibility to enable the multithreading by default?
Sounds fun. We'll check this out too!Shifrin wrote:Small bug-ette, the LED Colour knob is behaving erratically when I use it. Appearing to move smoothly at first then jumping about like crazy!!
(Running Diva 1.1b x32 in Reaper 4.22 x32 on Windows 7 x64)
Well, Nehalem's were the first processors with on-board memory controller or so, which made the North Bridge surplus. I'm by far not an expert though. We just observed that e.g. Core2Duos, old Mac Pros etc obviously have a memory bottleneck.EvilDragon wrote:I think you mean CPUs predating Nehalem, perhaps, Urs (that would be the first Core CPUs, prior to Core2)? "North bridge" is a part of motherboard chipset.
Hmmm, MidiLearn on patch buttons never worked, because one can't do file access upon a MIDI event. That's why patches in MIDI Programs are pre-loaded into memory.mbncp wrote:I can't get midi learn for next/prev patch to work (osx 10.7.3). Is there some trick ?
And, Reveal in Finder doesn't work here.
Sounds brilliant, very wide-eyed right now. Cheeeers!Urs wrote:(I wasn't sure if Fine Select worked even... in future you can have a visual focus ring around the knob and even use keyboard input directly to select knobs/type values... but this needs a few more weeks of work and testing)
Aha - I didn't know that! On my Mac it's like this:xh3rv wrote:Drag and drop is working, and multi-select is.
Would just be nice to change preset when I'm not near the pc. What about some flag and a timer, it doesn't need to switch right away and to respond after each cc value change.Urs wrote:Hmmm, MidiLearn on patch buttons never worked, because one can't do file access upon a MIDI event. That's why patches in MIDI Programs are pre-loaded into memory.mbncp wrote:I can't get midi learn for next/prev patch to work (osx 10.7.3). Is there some trick ?
And, Reveal in Finder doesn't work here.
You can however step through presets with the cursor keys once you click the preset selector.
Reveal in Finder doesn't (yet) work in the Carbon layer, unfortunately... I'll try to get that done (mostly for Mac VST), or I'll take it out till VST3 (next thing after Diva 1.1). Are you using VST? If not, which host are you in (might still require Carbon... hmmm)
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026