The demo project thread

[telebunke]

Now, that we so many new users of SS2 and ST2 here, I wonder how many of them are using Cubase and? how many are using Sonar and other ones?
For a long time, I had this idea sitting in my mind to have users to "demo projects" for users, with using just
one VST Instrument only.
That these demo projects, let it be Cubase, Sonar, Logic and some other formats can be available for download,
so that one could study them and learn from it.
That would be nice. I always learn a lot, when looking at other people's projects. As a composer and technician, that is.

To avoid misunderstandings - I don't mean mp3 files(we got many of these), I mean the project files of the sequencer.

tele

[pricer]

Nice idea - it would be great to learn from other KvRians. Though as we'll all be using ST2 instruments, wouldn't a simpler method of doing things be through posting Combi patches and a midi file, or maybe just posting FXP/FXB files (is this a standard, or just Cubase).

It's a shame the ST2 engine doesn't support send/master FX section, that way, we could produce fully mixed/mastered pieces using just the onboard fx.

[telebunke]

Though as we'll all be using ST2 instruments, wouldn't a simpler method of doing things be through posting Combi patches and a midi file, or maybe just posting FXP/FXB files (is this a standard, or just Cubase).

Hmm, that might work as well, but the recepient of the MIDI file / Combi patch would have to set it up by himself, which makes it a little uncomfortable.
He would have to manually assign ST2 to all the MIDI tracks and so forth. Also, this way it would not be allowed for the song writer to use automation because that wouls get lost.

tele

[Kim Lajoie]

Cool idea! It'll be especially cool to see how others use ST2 "tricks" in layering and effects to achieve certain sounds.

I'm using Cubase SX2.2 by the way.

Forever,




Kim.

[tonio]

great idea, but there are so many "hosted" situations. different set ups and so forth. I think maybe usng 1 instrument within the context of a tune to pass the definition of that instrument maybe a recourse. Unless I miss what your saying.
T

[telebunke]

We could open a Yahoo group for that purpose

Yahoo groups have a file section, where one could load up project data.
We could have folders for projects with
- SS2 only
- ST2XL only
- SS2 plus ST2XL
- other combinations of SR products

Projects should be uploaded as zip files. A ZIP file can contain
- a sequencer project file (e.g. Cubase,Sonar, and so forth)
- MIDI export of that project
- Patches for the VSTI (FXB files in Cubase terminology)

Some technical issues have to be cleared up to give it structure.
One of the questions is: Is the fxb / fxp file format existant for other sequencers than Cubase?
Maybe Harmony can tell, I believe he's got Sonar. What's the file extension name when you save a bank of a virtual instrument?
I'd assume it's the same for all sequencers (fxb), since it's VST data, but you never know...

What would be a good name for the group?
- Sonic Reality users Example Projects?
- Sample Tank and Sonic Synth example projects?
- SR example community?
- squids fan club?
- friends of harmony gardens?

suggestions welcome

tele

[telebunke]

great idea, but there are so many "hosted" situations. different set ups and so forth. I think maybe usng 1 instrument within the context of a tune to pass the definition of that instrument maybe a recourse. Unless I miss what your saying.
T

Yes, that's true, even for Cubase users only.
Could be SE, SL1.x, SL 2.x, SL 3.x, or SX 1/2/3.
Opening an SL1 project with SX3 should be fine, but what about opening an
SX3 project with SX2.2? Steinberg did care for upwards compatibility, but not the
other way round I assume.
suggestions on how to deal with that?

tele

[pricer]

i believe you have to export as a Cubase Song File now, as opposed to saving as a Project file, which is the standard Cubase file format.

Great idea with the Yahoo Group idea, i think Squid's Fan Club would be the way to go.

[telebunke]

i believe you have to export as a Cubase Song File now, as opposed to saving as a Project file, which is the standard Cubase file format.

Yes that's what I meant, the file extention is .cpr, which stands for Cubase Project, I believe.
The advantadge of sequencer files as opposed to MIDI is that you not only have automation, but also have the possibility to use Cubases's effects, to make a more complete thing.

tele

[tonio]

great idea, but there are so many "hosted" situations. different set ups and so forth. I think maybe usng 1 instrument within the context of a tune to pass the definition of that instrument maybe a recourse. Unless I miss what your saying.
T

Yes, that's true, even for Cubase users only.
Could be SE, SL1.x, SL 2.x, SL 3.x, or SX 1/2/3.
Opening an SL1 project with SX3 should be fine, but what about opening an
SX3 project with SX2.2? Steinberg did care for upwards compatibility, but not the
other way round I assume.
suggestions on how to deal with that?

tele

Exactly, well at least within the same host you should be able to open a fold v.file within a nwere v. DAW app. Iguess you can make a previous version "session". I can do that with DP(Digital Performer), not sure about other apps.



sounds interesting, however.
T