-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi!
I want to program my Motif Rack with the proprietary "Yamaha Studio
Manager". The editor software for the Motif is something like a plugin
for the "Studio Manager". As the setup.exe of both the "Studio Manager"
and the plugin breaks at the very beginning, I've copied all the files
from a windows machine. All the tricky stuff like finding the Motif's
MIDI ports work great -- but the "Studio Manager" doesn't find the
plugin. I assume that the setup.exe of the plugin does something to
register it.
Has anyone successfully run the "Studio Manager" with plugins? Is there
any registry setting I have to change? I've searched the registry on the
Windows machine, but there is nothing that links the plugin to the
"Studio Manager". Neither a path nor the name of a DLL -- not even a
string or a ID.
Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF5EP/uXdsp50C0vMRCFd8AKC7Vbb9tUtW0fvsOgj89j7TCFJ5UQCgzKo+
3AicL9sajLNDjGBLjbpAgs4=
=YuUh
-----END PGP SIGNATURE-----
http://www.emvg.net/esa/falseflagshow.ogg
The piano intro of "False Flag Show" was recorded last summer, and I spent many hours with this tune,
experimenting different kind of approaches and here's what came up. Maybe this ain't the last mix, maybe it is. The lyrics were influenced heavily by Alex Jones' radio show and his films.. Musically something
between power pop, hard rock, progressive rock ... or something else.
Recorded with:
Katar Jazzblaster el. bass
Epiphone Les Paul el. guitar
12-string acoustic guitar & 6-string ac. guitar
Millennium MD70 digital drums
Behringer GDi21 preamp for guitar and bass
Behringer Tube Ultragain MIC200 preamp for vocals
Beyerdynamic MC834 microphone
Behringer UB802 Eurorack mixer
Mandriva Linux 2007 and Ardour, Audacity , ZynAddSubFx, Qsynth, Hydrogen (with custom
kits), VST & LADSPA plugins...
-----------------------
http://www.emvg.net/esahttp://www.emvg.net
-----------------------
That's great news! So my M-audio Audiphile 24/94 is only 24-bit, which
means I can still keep using my favourite sound editor Audacity.
So I don't have to learn a new editor.
I'd much rather play guitar than fight with the computer.
Hello all,
I was looking for jack-fst and linuxsampler, and I can't seem to find
either site with google. Have these sites been taken down? If they
have moved, can someone point me to them? Forgive me if I have missed
something...
--
Josh Lawrence
http://www.hardbop200.com
OK, tried it. Worked like a charm.
I downloaded the ladspa2vst bridge from the site and compiled those to test
jost. Note: replace the vst directory with a symlink to your
vstsdk/source/common! The compile script then takes all the ladspas you have
and makes vst .so's for them.
As per the instructions, you copy jost with the name (without the .so) of the
plugin. Crude but does work. A little script to do this for a directory full
of .so's would be convenient (may try this if I can remember enough of my
Perl).
Note: jack-fst works (some of the time) for native Windows VSTs. Actually was
on Debian Sid for a while (in a sort of non-Debian-standard manner). Wondered
about compiling such a thing without WINE. See, it can be done. Now for ASIO?
Note: Such opensource packages based on "non-free" stuff like Steinberg's SDKs
go into a category "contrib" in Debian parlance (same would apply to Ubuntu).
Tim Orford:
>>>
>> I'll add an "Amen!" to that. The new GUI for Mammut is impressive, I'd
>> love to see more Linux audio apps use the JUCE framework.
>
> A few people have been saying nice things about JUCE gui toolkit recently,
> but I must somehow be missing its attractions.
>
> What gui problems does this toolkit solve? I can imagine that it is simpler
> to program for, but at what cost?
>
I chose Juce for the new Mammut because I like using a new gui set, and I
hadn't used juce before. The other reason is that juce is very
good looking.
In the start, I was very sceptical, because it was obviously not
completely mature on linux, so I had to spend some time fixing 16 bits
display and xshm. Juce's Alsa audio support is still not working
completely yet, but I added jack support to mammut as well, so its not a
big deal for me.
I was also sceptical to the widgets, because after playing
around with the gui builder program "jucer", it didn't seem to offer many
types of widgets or configuration of widgets. However, it quickly came
apparent that its the jucer that is limited, and not juce. But that
doesn't matter, because its very easy to customize the code that juce
produce.
Another nice thing about juce, which came very apparent after working with
it, is that its been made with the user in mind, thinking one step further
than whats normal about what the user normally wants to do. So therefore
code written with juce is very little verbose. Compared to qt and gtk
code, juce code is relatively (we're talking C++) small and pretty. Theres
also a bunch of nice classes for doing stuff you normally do in a program,
like preferences, warnings, timers, etc. And its all done in a way where
you can get a lot done by writing very little, while still being able to
configure things if you want.
> If an application has any pretension to actually having any users, it
> needs to respect the ui choices of the user, and utilise the system theme(s)
I don't see the point of that. Lets have anarchy. In radium, I use gtk,
qt, tk, xterm, and xlib, all simultaniously in the same program. I think
thats a cool way to do it. Pick the best gui kit for the task you are
about to do, and get the job done.
Greetings:
I was wondering if anyone has successfully used ChucK in a 64-bit
environment. I can build the app without any complaints from the
compiler, but it segfaults whenever I try running a script. Also, the
TAPESTREA program doesn't work x86_64, the GUI appears but no elements
are usable. They do look nice though. :)
I built and employed the JUCE library, it's the business behind the
popular Tracktion (Win/Mac only, afaik). I successfully built and
tested Kjetil's latest Mammut with it, and I must say that it's a very
attractive GUI. Beats the tar out of the old GTK1 look. Some changes to
the JUCE sources were needed, Jules knows about them, so hopefully the
lib will soon compile for 64-bits out of the box.
SuperCollider's sclang seems to be an utterly lost cause for pure 64-bit
environments. I've set up a chroot to try running sclang from within
that space, but I've yet to put together a complete development
environment in the chroot (I need to compile sclang there). What a PITA.
I built and tested some of the code from the EnergyXT2 site, including a
couple "native Linux VSTs" (the CMT Bitcrusher and the Destroy FX
Transverb). I could instantiate them within EnergyXT2, but no GUIs
appeared. Btw, it seems that the EnergyXT2 devels have been working on a
port of Steinberg's vstgui, it might be worth looking into. I'd be more
interested in pursuing tests with the program, but my enthusiasm is
tempered by the lack of source code. :(
Sun has released an AMD64-happy JDK 1.5, which I've been using to run
various Java-based music and sound apps. Not surprisingly, they work
nicely. I've tested MEAPsoft, ImproVisor, and a few other useful apps,
and I plan to see what can be done with jMusic and Phil Burk's jSyn
environment. Btw, jCollider worked well with SC3, but I'm loathe to
learn Java. Nothing against it, I'm just too busy to learn another language.
I tried to build transcode yesterday, I want to convert some AVI files
to DVD format. Alas, building the required mjpegtools failed, and I
wasn't up to chasing down the cause (more unhappiness with 64-bits, I'm
sure). Anyone have a better method for this project, maybe one that
doesn't require transcode ?
Okay, peace out, ciao for now.
Best,
dp
Michael Bohle:
>
> Am Montag, 26. Februar 2007 14:18 schrieb Michael Bohle:
>> Hi there,
>>
>> The italian DJ and Developer Lucio Asnaghi has made a first preview of
>> simple host for native VST on Linux. Native VST for Linux was founded first
>> by Jorgen Aase /EnergyXT2, but the communication is problematic (also other
>> devs reported that Jorgen didn't anwer to any mail), so Lucio decided to
>> make an own host, based on the framework JUCE , because he porting a lot of
>> VST Synths to Linux. (he also made a great port from ZynAdd Windows VST
>> back to Linux VST)
>
> Please read the website and the comments from Lucio, he made an article about
> this discussion and he pleased me not to make an ANN in this list about his
> apps anymore.
>
> See http://www.anticore.org/jucetice/index.php?entry=entry070226-191811
>
> I see cleary, there are the an old linuxaudio community, like represented
> with this list. The old community believes that there is the evil closed
> source and that open source heal all wounds and make an ideologic overhead
> about this.
>
I think you are too categorical and judgemental. I also think you are
wrong, in fact, the person I suspect you are addressing with this, Paul
Davis, is a guy who perhaps has devoted the most time making closed
source vst plugins work in linux.
It is provocating, however, that someone, without explaining why,
suddenly works a lot on making vst plugins more popular in linux, when we
already have descent well-licensed plugin formats like l2v, ladspa and
dssi, which most linux audio plugin hosts support.
And therefore, I also think you should have spent more time on the very
good argument for vst plugins on linux: There are a lot of great vst
plugins available, and many of them are even open source.
> The new community, often active musicians, have no problems to get in touch
> with "the evil" - The new community is pragmaticly use this what works for
> the musicans. And they want Linux, not because of the FSF, more because this
> can be an alternative for Windows.
>
You can't categorize people into a new and an old community. There are no
us and them here. I think the arguments against vst plugins on linux are
rational, at the same time as there are rational arguments for vst plugins
on linux.
This would be a far more constructive discussion if you spent time
fronting the rational arguments for vst plugins on linux instead of
initiating flame wars by constructing alternative realities. At least,
thats how it appears.
Quoting Michael Bohle <opendaw(a)jacklab.org>:
> Hello Paul,
> > native VST for linux has yet to produce anything concrete at all,
> > AFAICT. developers of VST plugins are *not* writing plugins for linux.
> > if you wanted to make native VST on linux easier, the sensible thing
> to
> > do is to implement VSTGUI on top of X11 and/or one or more
> contemporary
> > toolkits.
>
> Native VST on Linux is real! it works and needed 3 mounth (Dec, 1st was
> the
> first release of EnergyXT2/Linux)for around 50 plugins - Lucio is the one
> who
> made the first VSTgui working on Linux! See his website.
Yeah, it might work, cool - but do we need native VST's? You can do
everything a VST or VSTi do with an LV2. Just look at the AZR-3 VSTi Hammond
simulator which has been very successfully ported to LV2 by Lars Luthman -
even before LV2 has been "officially" released.
Are you aware of the licensing problems with VST? If Steinberg does not make
it's SDK license compatible with the GPL you will never get VST software,
not even linux-VST software, included in distributions. Ever. You will not
be able to distribute your software in binary form if you want to use GPL.
Ever. Every one of your users will need to build your software by
themselves, they need to navigate Steinbergs' website jungle to get the SDK.
The picture is not pretty.
Now, what would really be cool would be an alternative SDK for VST which
would turn existing VST sources into LV2 plugin sources, including the GUI.
This would probably make a lot more of the DSP in the existing VST plugins
(we're really interested in the DSP, right, not VST itself?) available for
the Linux users. But even then it's a question licensing, licensing,
licensing... Not many VST developers are interested in open source ideals.
my 0,01
Sampo
----- Forwarded message from Thomas Vecchione <seablaede(a)gmail.com> -----
>- Do you export once in the end, or do you do tests in
>between?
Both
>- Do you work with stereo and/or multi-channel?
Both again, though Multichannel more often
>- What are your targets: CD, DVD, Web?
Yes, as well as multichannel files, or multiple files making up a
multichannel mix(Will explain)
>- File-types: WAV, Flac, Ogg, MP3?
In general that covers it, though AAC and AIFF are not nessecarily bad
to look at. In general Wav and FLAC covers me.
>- Bits and sampling rates you need?
24/96 is as high as I go in general. Obviously your standard 16/44.1
16/48, etc. as well
>- Do you or would you like to export to several formats at
>once? If yes, which exactly?
Again Wav or FLAC and a compressed format for preview purposes would fit
nicely for me. Particularly for web distribution, so I can link to
download the full quality or preview it.
>- Do you know of outstanding solutions in any application?
Nothing I would call outstanding sorry.
>- What problems do you run into?
The ability to seperate multiple outputs over multiple files.
Explanation:
Since I work in Live theater, as a Sound Designer, often times i am
using a playback device or software for my playback. Not all of these
can understand multichannel files, but often at least with the software
I have the option of starting a playback of multiple stereo wav files at
once for the same effect. Thus the ability to with ease export to
multiple stereo wav files would be great.
>- Wishlist items?
>
See above, but give me enough time and I am sure I can come up with more;)
>- If you use Jamin, do you feed it with multitrack material
>or rather with mixdowns?
Don't use it so much, I really should dig into it. Sorry.
Seablade
----- End forwarded message -----
--
Thorsten Wilms