XT Software

Compyfox · Post by **Compyfox** » Mon Mar 31, 2008 4:20 pm

brok landers wrote:... but to enhance the concept/uniqueness of xt1x ... which it doesn't ... it's not even right on par with xt1x on a lot of terms ... and i'm not talking about the modular approach, but aswell in the sequencerpart ...

I'm in on this with brok, though I'm greatly dissapointed by the modular matrix. I tried both XT1 and XT2 now, and I really tend to use XT1 - why? It has switches that can turn the plugins on and off, the plugins are listed on the left (unlike with XT2), I can use the right mouse button in the comp window in XT1, while that's not possible in XT2.

Granted, I get XT1 with a XT2 license, but seriously... I'd rather only shell out 20 bucks for XT1 than 50 for both, if I only need the modular host, which wasn't carefully ported in XT2.

It's like Cubase VST5 to Cubase SX up until SX3 - one of the most important part is missing - in case of Cubase, it was the hardware/MIDI integration, in case of XT2 it's the modular approach.

(btw: you're not alone with flames anymore, brok - I recently got my share since I said something "negative" about SE, and stick to my opinion)

jens · Post by **jens** » Mon Mar 31, 2008 4:26 pm

Compyfox wrote: (btw: you're not alone with flames anymore, brok - I recently got my share since I said something "negative" about SE)

You're a hero now.

D-Fusion · Post by **D-Fusion** » Mon Mar 31, 2008 4:52 pm

- Duplicate sequencer could sometimes cause a crash, now fixed
- Back space now works also as delete
- Fixed bug with Back space and delete key on MacOSX
- MIDI playback only worked on first arrangement in sequencer, now fixed

Ad0 · Post by **Ad0** » Mon Mar 31, 2008 5:02 pm

Kyran wrote: ext keeps them in memory for the undo. I actually posted your method as an improvement.

I thank you

hehe. It's a lie that it needs to be resident in memory because of that.
I am baffled that it is the undo's fault. Noone would be that crazy to keep the instance on purpose!

Do you know for certain that the reason for it to be in memory is truly because of undo? I find that hard to believe.

Don't we all love posts where speculation rules and nothing happens? (I am not saying that I don't speculate)

tibor · Post by **tibor** » Mon Mar 31, 2008 5:06 pm

personally i think it would be great if jorgen would take the time to start a thread here on the forum with both an outline of most of the additional features he's planning on implementing in XT2 until he considers "done" and a "production management" timetable with estimates on when he predicts they will be available.

these estimates need not even be actual dates... percentages would be ok...

if "x" amount of features (and no bugs) = 100%, then
.feature "a" (live mode?) = xx% of those 100%,
.feature "b" (midi out comparable to that of those sequencers that actually work well with hardware?) = xx% of those 100%,
.feature "c" (better audio handling in the sequencer?) = xx% of those 100%,
.feature "d" (a few "gimmebacks" from xt1.4 as options for those who want them?) = xx% of those 100%,
.debugging/beta testing = xx% of those 100%,
etc

as i said... since these would be estimates there would be less potential for embarrassment compared to target dates being missed for months. it would still give us users a picture on what to count on. personally, i have tons of pending work in fields other than music that i must get about doing, so it's not that bad for me to (mostly) put xt2 aside for a couple of months. other users might prefer to stick with other tools for a while as well until the functionalities they regularly need are properly in place.

i think there is sort of an emotional aspect to using xt, on account of 1.4 promising so much and xt2 looking like a sub-developed step in the right direction. people are clinging to it even when it crashes every time they glue midi parts, patiently waiting days or weeks for a fixed released. i believe this is called love.

does this make any sense?

edit:
the percentage approach even allows for margin of error... sounds like a sweet deal for everyone. pie charts

djsubject · Post by **djsubject** » Mon Mar 31, 2008 5:24 pm

Ad0 wrote:
Do you know for certain that the reason for it to be in memory is truly because of undo? I find that hard to believe.

well Jorgen said so!

so that's as close to knowing as we will get as only he has the source code to prove it

& he also said he will replace it with a option that just saves a fxp in memory

original flipper · Post by **original flipper** » Mon Mar 31, 2008 5:31 pm

HI

I don't expect (any time soon) to see Jorgen lay out his development calendar.

I have seen the development of a synth take months longer than anticipated: within a host - a bug fix or new feature can likewise take many moons to instigate.

It is a real shame that the development cycle has slowed to a crawl: unfortunately with all the platforms being covered it is hard to be upbeat about progress.

Flipper.

Ad0 · Post by **Ad0** » Mon Mar 31, 2008 5:32 pm

djsubject wrote:
Ad0 wrote:
Do you know for certain that the reason for it to be in memory is truly because of undo? I find that hard to believe.

well Jorgen said so!

so that's as close to knowing as we will get as only he has the source code to prove it

Haha OK

Then I withdraw my indirect accusations of speculations in shame and embarassement.

djsubject wrote: & he also said he will replace it with a option that just saves a fxp in memory

Cool. That's the "right way". Where's the thread he said this btw? can't find it anywhere

masstronaut · Post by **masstronaut** » Mon Mar 31, 2008 5:43 pm

Poor Jorgen must feel like he can't win - slated when nothing happens, and slated when 'coming next' is updated.

But I did think this was satire until I looked at the page.

lama2 wrote:I want "Midi out is now working properly"
not "Back space now works also as delete"

Kyran · Post by **Kyran** » Mon Mar 31, 2008 6:06 pm

Ad0 wrote:
Kyran wrote: ext keeps them in memory for the undo. I actually posted your method as an improvement.

I thank you
hehe. It's a lie that it needs to be resident in memory because of that.
I am baffled that it is the undo's fault. Noone would be that crazy to keep the instance on purpose!

If we're getting technical: I did not post that it needs to be, I just posted that it is implemented that way.

your aggressive reply was totally unwarrented and uncalled for. You basically posted and wanted the same thing as me.

djsubject · Post by **djsubject** » Mon Mar 31, 2008 7:10 pm

Ad0 wrote: Cool. That's the "right way". Where's the thread he said this btw? can't find it anywhere

not a clue

it was in one of the early "BR: Memory leak in XT2" threads,

Subz

SWTrex · Post by **SWTrex** » Mon Mar 31, 2008 9:30 pm

tibor wrote:personally i think it would be great if jorgen would take the time to start a thread here on the forum with both an outline of most of the additional features he's planning on implementing in XT2 until he considers "done" and a "production management" timetable with estimates on when he predicts they will be available.

masstronaut wrote:Poor Jorgen must feel like he can't win - slated when nothing happens, and slated when 'coming next' is updated.

Seems to me that there's been a lot of "damage" in the forum in the past few months as the development pace has slowed, and significant problems remain in the software.

I don't know what Jorgen is thinking, but it also seems to me that he could go a long ways to control the "damage" by posting and responding to conjecture, defending his development plan, asking for user input, and giving us a few teasers to keep us excited. Isn't this the way it used to be in the early days??

Trying to be patient,
SWTrex

fandango · Post by **fandango** » Mon Mar 31, 2008 9:45 pm

I just find it odd that there's usually a big gap of no news... and then things get added in dribs and drabs to the "Coming Next" over a period of hours. You'd think they'd be uploaded as one chunk.

Almost like jorgen's looked at his watch, thought "meh, that's been a couple of weeks", cracks his knuckles and starts typing away...

sinkmusic · Post by **sinkmusic** » Mon Mar 31, 2008 9:55 pm

I feel a bit the same, but, on the other hand, i think there is a quite a possibility that Jorgen may have been busy lately with public relation's stuff (the Behringer version, the German Keys version, being at Musikmesse, etc). If he's alone, he may have focused on that side of his job, and the collaboration with Behringer may mean that now he should focus again on coding to give to the new potential thousands of users a stable DAW (which Ext2 is not yet, at all).

As now Musikmesse is over, and as the Behringer thing was announced for the end of March (and as tomorrow April starts), i would keep confident for many bugfixes come soon (i hooooooope it so much !).

jens · Post by **jens** » Mon Mar 31, 2008 9:59 pm

sinkmusic wrote: As now Musikmesse is over, and as the Behringer thing was announced for the end of March (and as tomorrow April starts), i would keep confident for many bugfixes come soon (i hooooooope it so much !).

yeah, I would love to give the BR-thread a bump - alas I can't, since it's a sticky!