Consolidated bug thread

[ohm]

Can't reproduce this here, tried with a few combinations of plugins. Doesn't seem like the sort of bug that would be system specific though, curious.

I forgot to mention: I was running energy xt standalone with the window maximized

[adam standring]

Bug:(1.3.6)
When you delete a VST from its root folder, eXT still remembers it in the 'recent' list, and although it gives the correct 'not found' error when you try to instance the VST, it then goes on to open a blank VST module on the workspace when perhaps it ought to not try and load anything.

[adam standring]

Incompatibility issue: (Fxpansion VST2RTAS wrapper 1.06 and VST2RTAS v2 beta versions)

Hi - I wonder if anybody can help on this issue? Sorry for cross-posting it.
eXT is the ideal solution to Protools' lack of MIDI functions (even the latest version 7). I was overjoyed to find that I could wrap the eXT VST with the FXpansion wrapper and that it receives MIDI and audio from Protools as well as sending it back. eXT is a musical swiss army knife!
However, I get 'access violation' messages every time I switch focus from the Protools window to Internet Explorer , irrespective of wether or not the wrapper/plugin window is being displayed. Weird....

" Exception EAccess Violation in energyXTE.dll at 0001364D "
and " Access Violation at address 16F03640, read of address 00000008 " or "00000009" to be precise!
Do it a few times and Protools crashes flat on its face with a fatal error. Bummer

Is it a problem with the VST implementation of eXT? The wrapper has never generated this with other VSTs in Protools.

[adam standring]

(1.3.6 standalone)
- Switching focus of VSTi's and stuck notes:
If I switch focus from one VSTi to another by selecting the MIDI track in the sequencer, the previous VSTi gives a stuck note. This also happens when I select in the modular workspace.

- Changes in the output for sequencer MIDI tracks not reflected in the main mixer pane in the main workspace:
If I reroute to another VSTi and disable the old one, another tab is added in the main mixer for my new synth but the old one remains. Would it not be better to replace the old with the new?

[robenestobenz]

With the FXPansion bug, I suggest you make a new topic in the main forum, try and initiate a dialogue with Jorgen - maybe he can ascertain where the fault lies here (although it does sound like eXT is causing the problem).

Nasty bug you found there with the MIDI track switching. Surprised it hasn't been noticed before. How exactly do you reproduce it by selecting VSTis in the main window though? Or are you talking about switching MIDI tracks in the sequencer that are routed to VSTis in the main window?

As for the final point, I think there's probably certain cases where a synth may be used by more than one track.

Thanks for the reports.

[adam standring]

The stuck notes bug happens in the sequencer when it is running in playback mode and you start deleting tracks that are playing (the synth itself isnt deleted from the main window - only the MIDI track, even though you instantiated the synth with the track).
It also occurs in the main window/modular workspace when you have tracks playing off of a MIDI part and you unhook the part and route it to another synth. The note hangs on the disconnected synth until you send it a few more MIDI notes again.

[lunik]

- Create a midi part in an arrangement, in the sequencer, loop area set to one bar
- Go into live mode
- Add the arragement to the live trigger list, and set the arrangment playing (and looping)
- You should see the loop area indicator at the top
of the parts window has shrunk to smaller than a bar.
- left click on this to make it dissappear
- eXT now hangs and maxes out CPU (if arr. is playing). Otherwise trigger arrangement.

Expected: no hanging of app. If loop points are not relavent in live mode, suggest not displaying at all.

[robenestobenz]

- Create a midi part in an arrangement, in the sequencer, loop area set to one bar
- Go into live mode
- Add the arragement to the live trigger list, and set the arrangment playing (and looping)
- You should see the loop area indicator at the top
of the parts window has shrunk to smaller than a bar.
- left click on this to make it dissappear
- eXT now hangs and maxes out CPU (if arr. is playing). Otherwise trigger arrangement.

Expected: no hanging of app. If loop points are not relavent in live mode, suggest not displaying at all.

Confirmed. That was nasty.

[jorgen]

- You should see the loop area indicator at the top
of the parts window has shrunk to smaller than a bar.
- left click on this to make it dissappear

this I dont understand. please explain

cheers
jorgen

[lunik]

I just emailed you via your support email with screengrab to clarify the issue.

There is a related issue in that loop area changes to 1 beat long in Live mode, whereas it was a different length in Single mode, in the arrangement view.

Also, I think the fact the loop dissappears in live mode with a left click is a bug in and of itself.

thanks
Lunik

- You should see the loop area indicator at the top
of the parts window has shrunk to smaller than a bar.
- left click on this to make it dissappear

this I dont understand. please explain

cheers
jorgen

[jorgen]

thanks

There are spearate loop settings for live and single mode. This way you can switch between single/live without messing up the live loop settings.

When you left click I guess you set the left and right locator to the same position. This will lock the playback, setting a valid loop are will make it play again. Will fix this.

cheers
jorgen

[flippya2000]

Hi jorgen,

Certain midi files do not play properly when imported - they either skip the first note, or keep reloading the preset of the output vsti. I think this may have something to do with extra midi information contained within these files.


UPDATE (31.12.05):-

jorgen has replied & indeed it was a problem with my midi file - NOT eXT - The midi file in question was created inside FLStudio502, with the notes drawn in the piano roll with a mouse. It is very odd, extra info is being added (program changes, etc) on midi export..Anways I've contacted the people at imageline abt this, and will edit this post if/when they reply.

Also, would like to thank jorgen for his speedy reply, I am really loving eXT and think he should be given a medal for his programming genius-ness!


UPDATE:-

gol (main programmer of FLS) says that it is limitation of FL to add this extra information to all midi files made in FLS & there is no way round it, except to edit the midi files after export. Of course a simpler solution: use a host that exports midi files correctly in the 1st place! (Like eXT!) Hope this info helps..

[soma]

thanks

There are spearate loop settings for live and single mode. This way you can switch between single/live without messing up the live loop settings.

When you left click I guess you set the left and right locator to the same position. This will lock the playback, setting a valid loop are will make it play again. Will fix this.

cheers
jorgen

I see what you are saying but if you make a loop of length 0 you can crash XT if the cursor is outside the loop. I think that's how I just crashed it.

BTW I didn't realize I could have seperate loop setting for live mode until just now! Nice one!

[soma]

Problem with ulinked audio in/from sequencer

http://www.kvraudio.com/forum/viewtopic ... 26#1536826

Bump-
Bothing more people here:
http://www.kvraudio.com/forum/viewtopic ... highlight=

Also that copy and paste audio from one seq to another crash is holding me back a bit.

[robenestobenz]

Both already in - except I had the unlinking sequencer outputs in the main window section. Thanks, sorting out now.