Brainspawn User Community

sosKeys

Progress... removing three busses routed to the DAW and trimming the rack has resolved the issue. Having a single aux but target routed to my monitors is working fine so far, a couple of rehearsals. Once I am confident that the issue is resolved, I'll add back in one return to route to the DAW.

-andy

sosKeys

This is still an issue for me, so bad that I'm considering dropping the separate keyboard monitor mix and DAW sends and just using a single output. The crackling has gotten more prevalent in the last two years even though I have gone almost entirely x64. It is definitely most frequent on EHCo channe...

sosKeys

Hi guys,

I just came back to this after some significant downtime in my band

I'll load the device compatibility file and report any anomalies.

-andy

sosKeys

I have limited experience with the previous collection... I got it some months ago, but haven't had time to integrate it. I loaded a couple of the instruments and encountered no issues... they behaved like any other plugin. When they came out with the new suite, I (perhaps prematurely) got it on pro...

sosKeys

Confirmed on a different computer that loading a scene containing Prophet V3, at least the Mixer, Filter, and Amplifier settings are set to zero. Loading a different patch, then the original followed by changing scenes away and back again leaves the parameters intact.

sosKeys

I'm relatively new to V Collection, decided to get v5 when it was on promotion. I waited until the last couple of weeks to upgrade to Windows 10. When I did, NI Pro-53 stopped working, so I decided to go straight to Prophet V3 to replace it for the one scene where I was using Pro-53. In addition, I ...

sosKeys

Using 4.1.9, I have had repeated instances where the application would stop responding to ctrl-U (Update Scene), ctrl-P (toggle audio engine), and ctrl-S (Save). The application continues to respond to the UI buttons. AS far as I can tell, when one key binding goes away, they all do. Restarting fort...

sosKeys

My .02 on this is that I have infrequent but ongoing problems with Aux Bus Set mangling my sound with harsh crackling dropouts. This only occurs with EHCo to the best of my knowledge, but is unquestionably in Aux Bus Set as my main buss is unaffected (going to the PA mains) while my keyboard monitor...

sosKeys

This is similar to an issue I have had with other modules, primarily EHCo. When I first change to a scene, sometimes one (or perhaps two or all three) of my EHCo modules will be muted. ctrl-P, ctrl-P (toggling the audio engine play state off and back on) will usually bring the instrument back, but s...

sosKeys

sosKeys

Hi Dirk,

Good to hear from you after a long absence. Here's the link:

http://www.brainspawn.com/check-qualifying-discount/

Andy

sosKeys

The only thing I've done with mine is reduce the size of the list on the left and change the active scene highlight color to be able to distinguish it from the song/scene hierarchy. If that is interesting, I'll grab it next time I'm at rehearsal.

-andy

sosKeys

I have also had a lot of crashes working with setlists. In particular, changing the order of songs using drag and drop, in addition to seeming unpredictable, caused a couple of crashes. The functionality is a big improvement, but stability isn't quite where it should be.

sosKeys

No problem. Glad to be able to help.

sosKeys

Are you updating the scene, then saving the rack?

sosKeys

You can enter raw MIDI data from the instrument tab (on the left, default name is EHCo MIDI Output). Select Add, then MIDI from the dropdown. You can construct any MIDI string you want there.

sosKeys

Same OS version but I'm on a somewhat older quad core Xeon in a rack mount... I doubt that makes a difference. Have you tried fiddling with the plugin in the Plugin Manager? Try doing a rescan on it, particularly if it is in the ignored list.

-andy

sosKeys

I use Aftertouch to CC x64 on my dedicated music system and the computer I use at home to try things out. Both are Win7 x64 and neither has any problem running the plug-in as an instrument.

sosKeys

Unless I'm missing something, you should be able to map the controller onto the VST plugin parameter in Forte. EHCo is not required unless you are using an external device. In the MIDI Routing tab of the VST, select the From device that corresponds to the Keytar, then the MIDI channel (usually 1, bu...

sosKeys

The incompatibility between Reaktor and Ultranova Editor has returned. After making some edits to an effects insert on Ultranova (BlueCat Gain), Forte hung and refused to reload, even after a full restart. Disabling either Reaktor or Ultranova in a Safe Mode startup allowed the rack to load. Since R...

sosKeys

I'm not having any issues with jBridge on either of my systems, but both are running Win7 SP1 x64.

sosKeys

Hi Mike, A new problem tonight, never observed before. On some scene changes, audio processing sputters and stops with the output meters in the rack sticking at some high level (not max). The program doesn't crash, but I have to cycle the Audio button (fka Power) to get audio back. After cycling, th...

sosKeys

I'm not clear how you would get Pro-53 to load into Forte x64 without jBridge. To the best of my knowledge, NI ever released an x64 version as the plugin was EOL before they embraced x64 for Windows. Were you running 32 bit Forte 3, then switched to x64 with version 4? I did not try to load a new in...

sosKeys

I just experienced the same problem tonight except that it was all or nothing: either the tree labels are all there or all gone. Closing, then reopening the Options/Program Settings dialog with Cancel did not seem to change the tree, but selecting OK or opening the Rack Editor would make the labels ...

sosKeys

Same here. When Forte 4 was first released, there were problems with existing EHCo licenses but that was resolved in a couple of days.

sosKeys

J's MIDI Tools Atertouch to CC deals with one of these needs...

sosKeys

Hi Lucien, I had problems with a couple of plug-ins in F4 that worked in F3: Reaktor 5 and UltraNova Editor (UNE). The bridged version of UNE wouldn't run in F4 (whereas the x64 version wouldn't run in F3) and rack would crash with the x64 version where Reaktor was loaded first. I ended up fixing (w...

sosKeys

Maybe you need to cut back on the repertoire...

sosKeys

I'll check it next time I'm at my dedicated system. I have Pro-53 on that but not at home. I didn't notice any issue with it on an existing rack file, but this report will prompt me to check the scenes that use it.

-andy

sosKeys

The behavior should be similar to f3 with four tabs:
VST Scan Folders (to specify the location of your VSTs)
VST Plugins (successfully enumerated plugins available to the program)
Ignored Files
Crash Log

So far it has worked well on both of my systems.

-andy

sosKeys

I used it tonight at rehearsal... seems more stable than any previous version. I'm joining the chorus...

Thanks!

-andy

sosKeys

I see that there is no discount for upgrades to forte purchased before the beginning of this year and am ok with that given the huge amount of development work and the fairly small customer base.

What about EHCo? Will the previous license work, or is it required to buy a new license for v4?

-andy

sosKeys

Indeed. Very appealing to look at. It seems well organized after a little poking around.

sosKeys

In the Forte 3 menu, go to View/Setlist Manager/Scenes and Setlists/Basic Scene Automation, enable Change scene with MIDI Program Change. There are dropdown boxes to select a (MIDI) port and channel once the selection is enabled.

-andy

sosKeys

Here's my previous post on this topic:

viewtopic.php?f=2&t=4608

sosKeys

I use Aux Bus Set LE x64 in my rack and have had recurring, intermittent problems with what I can only describe as crunchy audio output from at least one bus when sending audio from EHCo. There are four Aux Bus Set returns, routed to four different audio pairs of my MOTU 828 Mk3 (Analog 1-2 for keyb...

sosKeys

I've had two instruments, Spark and Prism, running in separate instances of Reaktor 5. When I added the UltraNova editor, it would not run in x64 under Forte 3, so I used jBridge and the 32 bit version. Loading that rack into F4 resulted in the UltraNova editor being proxied; subsequent attempt to l...

sosKeys

Hi bigalminal,
I can't speak for others, but I respond if I have a similar experience. It might be helpful to add details about what plugins you are using as some are *much* more problematic than others. Also, including what version and whether you are running 32 or 64 bit may be useful.
-andy

sosKeys

I have the Kontakt pianos as part of Komplete, but Ivory is my main instrument. Coupled with a good controller (I use an S90ES) it is almost as satisfying as the real thing until things things get loud... then it's better.

-andy

sosKeys

Not here...

sosKeys

Hi Cormacmc, If you go to Options/General Options and set the Default Rack Save and Default Backup Rack Save locations, you should provide a basis for recovery from at least some of your issues. One thing that was difficult to learn was that, every time you make a change (to a scene), you have to FI...

sosKeys

Hi Jori, I have been using Ivory 2 with Forte 3 for a long time and have no issues. One thought is that I create separate instances of Ivory for each sample set (I use two) then just toggle the mutes to get the one I want. That, along with disabling per-scene configuration changes, makes for a stabl...

sosKeys

Just for grins, rather than closing and reopening, try cycling power on the rack (the virtual power button or <ctrl-P>). This seems to have a significant effect on the behavior of EHCo on my system. In general, though, EHCo is rock solid for me with four instances and has been for a number of years....

sosKeys

I learned something interesting tonight... the taper with FC-7 connected to the Supernova II was quite problematic. Tonight I connected the FC-7 to the S90ES instead and found the taper to be qualitatively linear. Now I need to change all of the scenes to use a different MIDI port, CC (Novation send...

sosKeys

Hi Julien, Thanks for the input. 1. I'm reluctant to add another layer of complexity by putting MIDIOX on the front end and filtering, but maybe that makes sense anyway; I merge volume (CC2, a ridiculous Novation quirk) and sustain from different keyboards as needed, so when overlaid with splits and...

sosKeys

Update on this behavior: I'm running four EHCo instances--Yamaha S90ES, Supernova II, Ultraproteus, and Ultranova. At least two of these (S90ES ands SuperNova II) exhibit repeatable crunchy noises when playing notes and moving the volume pedal. Cycling the rack "power" (<ctrl-P>) resolves ...

sosKeys

The French guy is probably Dirk.... only one step below a major deity around here. He's right, and it is simple: for any MIDI controller, you can enter an initial value in the MidiRouting/Device/Channel/Controllers tab.

sosKeys

Hi, I have a couple of odd behaviors with EHCo/Forte, not sure where to look. 1) Some patches on my Yamaha S90ES (Sweet Oboe in particular) have a crunchy sound (non-periodic, sub-audio rate popping sound overlaid on the normal audio), particularly when moving the volume pedal (MIDI from Supernova I...

sosKeys

Hi,

When does Forte (3.1.XX) read the MyControlSurfaceDefinitions.xml? Is it required to close and reopen the Forte after making changes?

Thanks,
-andy

sosKeys

Hi Dirk,

I'm curious about the MotionStrip, but there's nothing on the site and the link returns a 404.

I'll be making a contribution soon... my rack wouldn't function without AuxBus.

Thanks,
-andy

Search found 98 matches