Vortex VSTi - Multi Timbral Groove Machine Beta

Official support for: hgsounds.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Thanks Mark,
Only on N track studio. But it doesn't record anything.
You mean it doesn't write anything to the log file?

The load scale button does work and does send info to the debug. Is it working because it is compiled for debug?

It only has writing to text file added, it's not a debug version in the standard sense, so it shouldn't make any difference really.

Post

Astralp wrote:
I hope Vortex will have a way to input the notes other than the mouse, in fact i have an FR relating to that.
It did use the same CCs as ARP but it was causing a conflict somewhere and so it's disabled for now, it needs work but it is on the list. I may need to try using RPNs for it, 32 is a lot of controllers to tie up... It will only edit the current sequence, but that should be enough?
It will only edit the current sequence in focus but will work across all sequences? :)

That would be great, i didn't realise there was something already in place, my fr was on the basis that there was no way to input notes other than via a mouse. 8)
Latest release and Socials: https://linktr.ee/ph.i.ltr3

Post

I'll try and get to work on it tomorrow, shouldn't take too long :)

Post

Astralp wrote:I think he means using vst synths inside maschine and routing the channels internally from Vortex. I don't have maschine and so only know what I've heard on this thread.

As for the direct outs, they generally appear as extra channels on the hosts internal mixer so that you can mix them using effects sends etc.. within the host.
Yeah exactly. It works multitimbrally with hardware, in that respect it's great but when it comes to routing internal instruments not so much. :|

@soundklink apparently someonew from NI hinted at Maschine becoming a daw so i assume all this kinda thing will be implemented but it's a case of when. Hopefully there will be an announcement around Messe. :)
Latest release and Socials: https://linktr.ee/ph.i.ltr3

Post

soundklinik wrote:I am glad you have a sense of humor :) of course it is meant in good nature.
Tell me, do you own maschine?
I do, and I don't need another DAW. I use it almost exclusively as a standalone! So advantage #1
I don't own it, I have messed with, I do understand it ... and using anything standalone can be an advantage ... but not necessarily. A far as Maschine goes, while it may work well for you standalone, it is actually it's ability to interact with a computer that gives it a relative advantage over a MPC, Command Station or ASR-X. Standalone is also a relative concept ... whether a laptop with decent interface and controller is standalone or not, could be debated.
Maschine: (Standalone<>VST combo, with a hardware midi controller).

8 x audio in, and 32 x audio out. MIDI in/out. It Can send midi out to other hardware/software

16 Groups/Channels A-H, with 16 tracks each=256 tracks in total .

256 bars per track, multiply by 64 scenes = 16 384 bar song max.

Each track=(1/16th of a group) can have its own FX- native or VST, Group can have FX and 15 channels can have master FX in 16th channel.
My laptop running Cubase and my Allen&Heath ZED R16 mixer with 18 channels of FW i/o can pretty much do all this ... although if you're saying that you have 32 channels of analog out, that sounds impressive. Are you saying there is something like 4 DB25 connectors? It's certainly difficult to imagine that many physical channels of i/o on that unit.

The whole tracks by groups is a little misleading. Sure, Vortex only has 24 multisequences of it's 12 sequencers ... but on the lap top those midi tracks are infinitely tweakable, copyable and on and on ... I mean we're not talking about songs longer than 6 or 7 minutes anyway, are we?
It hosts VSTs, it samples(re-samples) from inside and outside, you can load samples, you can record tweaks, into audio and bounce the result on another channel or track without even stopping Maschine...
Do I need to go on? Do you realize the difference?
Yes, actually I think you do. My premise was with my DAW ... even my portable rig ... and Vortex and the controllers I have, the only thing Maschine would add for me would be the sequencing ... and I can do all that and in the bigger picture more with my setup and Vortex.
Can we stop comparing different products with Vortex, so the forum does not degenerate into stupidity? :)
There you go again with your condescension. I'm glad you enjoy you rig. No one said Maschine was an inferior or useless piece of kit. However, you seem to have an unfortunate habit of demeaning others with whom you have a difference of opinion ... and I don't accept such treatment. You still haven't demonstrated anything you can do with Maschine, I can't do with my rigs and Vortex. Your snide, 'put down' comments are uncalled for and reflect an unsavory aspect of your character. It would be good for you and the world if you could learn to behave otherwise.

Como
Help! I've fallen up and can't get down!

Win7 x64 Dual Dualcore Xeon 3.0 Ghz 16 GB Ram. Cubase 6, RapidComposer, BIAB, Abelton 6, Acid Pro 6,Roland XV5080 & Super JD, E-Mu CS PX7, Korg Radias R and MI-EX R, ASR-X Turbo, UAD 2 Quads, stuff.

Post

Astralp wrote:Still no word on the Load Scale issue anyone?
Now it works perfectly... at least on my machine.

Janusz
Computer: rack PC, Windows 10 64bit, Intel i7 2700K, 16 GB RAM, 250 GB & 500 GB SSD disks, HDD 1 TB 7200 RPM
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,

Post

Thanks Janusz, it does seem that the logging cures it for people for some reason hmmmm... very odd.

Post

Astralp wrote:Thanks Janusz, it does seem that the logging cures it for people for some reason hmmmm... very odd.
So try disable logging in next build and I'll check it.

Janusz
Computer: rack PC, Windows 10 64bit, Intel i7 2700K, 16 GB RAM, 250 GB & 500 GB SSD disks, HDD 1 TB 7200 RPM
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,

Post

Janusz Grzybek wrote:
Astralp wrote:Thanks Janusz, it does seem that the logging cures it for people for some reason hmmmm... very odd.
So try disable logging in next build and I'll check it.

Janusz
The last one didn't have it, but I need the log to get closer to what is going on, it's frustrating! :)

Post

Astralp wrote:
Janusz Grzybek wrote:
Astralp wrote:Thanks Janusz, it does seem that the logging cures it for people for some reason hmmmm... very odd.
So try disable logging in next build and I'll check it.

Janusz
The last one didn't have it, but I need the log to get closer to what is going on, it's frustrating! :)
I updated to latest beta 28 from beta 26, while seem to me that it was enabled in beta 27, so I can't send log to you :(.

Janusz
Computer: rack PC, Windows 10 64bit, Intel i7 2700K, 16 GB RAM, 250 GB & 500 GB SSD disks, HDD 1 TB 7200 RPM
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,

Post

Actually I think it was 26 that the log was disabled and I re-added it to 27. I'll leave it in for a while just in case someone has the problem, fingers crossed!

Post

Hey Andy,
good news, no problem on Maschine, there is no longer volume readout jumping in two pots, and the volume-CC7 did not happen again.
I am running your latest beta version.
However I (alone?) seem to have a bug in TEMPO, the tempos are miss labeled, e.i. "1 bar" is actually 1/32, "2" is 1 bar, "4" is 1/2 etc, they all work but under different value.

Request: Is it possible to fit the whole midi keyboard on the VST so you can see which octave/note is active? I like how you can play the same pattern an octave up/down, but I don't see which octave I pressed, I see the "lit/active" note but not octave, once I am out of range.

Post

soundklinik wrote:Hey Andy,
good news, no problem on Maschine, there is no longer volume readout jumping in two pots, and the volume-CC7 did not happen again.
Great :)
However I (alone?) seem to have a bug in TEMPO, the tempos are miss labeled, e.i. "1 bar" is actually 1/32, "2" is 1 bar, "4" is 1/2 etc, they all work but under different value.
Really? Nobody else has reported that and it's definitely correct here. Is this just in maschine or in other hosts too?
Request: Is it possible to fit the whole midi keyboard on the VST so you can see which octave/note is active? I like how you can play the same pattern an octave up/down, but I don't see which octave I pressed, I see the "lit/active" note but not octave, once I am out of range.
Well there's room for another octave I suppose, which would you prefer higher or lower? At some point in the future the octave below the triggers will be used for more triggers though, so probably better off higher.

Post

Well there's room for another octave I suppose, which would you prefer higher or lower? At some point in the future the octave below the triggers will be used for more triggers though, so probably better off higher.
Another idea is if you can put << and >> to scroll?
Really? Nobody else has reported that and it's definitely correct here. Is this just in maschine or in other hosts too?
Yes in maschine it goes the way described above and in Chainer and BloXpander it goes in reverse: 1 bar actually stops the clock, 2 is 1bar, 1/4 is 1/2 etc.
CHAINER : http://www.xlutop.com/html/downloads.html
Bloxpander :http://www.kvraudio.com/product/bloxpander-by-eareckon

Post

The 1 bar issue is known, it's on my todo list.

I've just tried it in chainer and it appears to work correctly. Are you using the GUI to edit the tempo setting?

Post Reply

Return to “Homegrown Sounds”