Simple projects

Michu · Post by **Michu** » Wed Dec 29, 2004 5:25 pm

I am happy that you are happy

Now I've swapped the analogue out and asio dest inputs so the asio dest take the mixer out put and and my speakers are routed from d1l&r

just want to remind you, that you don't have to swap them, you can have mixer outs feeding both analog outs and asio.
take care

Post by **garyb** » Wed Dec 29, 2004 5:35 pm

or with the stm2448, you could connect the control room out to the analog dest and then use a record bus or the main out to the asio dest.....

Kymeia · Post by **Kymeia** » Sat Jan 01, 2005 12:44 pm

I managed to get Logic 5.51 (windoze) working with my new system now. I'm very pleased about this as I was prepared for it not to (considering it has 2 gigs DDR2 RAM and a P4 3.6 with hyperthreading on). However I'm having the same problems recording into and tried the same approach as with Tracktion but there's no way I can stop it getting horrible feedback. Anyone got a simple was to play Logic instruments, process them with Scope FX then record in Logic?

[ This Message was edited by: Kymeia on 2005-01-01 12:45 ]

Post by **garyb** » Sat Jan 01, 2005 4:41 pm

TOTALLY doable. there is a io plugin in logic. use that in the insert and connect the scope effect to the proper asio channels. record the instrument by sending it to an asio output and then back in an asio input...
if you are experiencing feedback it is because you are monitoring thru the sequencer. turn off software monitoring!

Kymeia · Post by **Kymeia** » Sat Jan 01, 2005 7:47 pm

Thanks - that works pretty well. The only thing (forgive my probable stupidity) is that to record I have to select the audio track but then I can't hear the instrument I am playing. What I'm having to do at the moment is record an instrument track then record that to an audio track so it's taking two takes. Is there a way of recording the audio as I play? (I can do this in Tracktion using the method described above)

Also I can't seem to record Scopes own synths. I thought I'd be able to use the io plugin to do that too but it doesn't seem to work for that even though the output of the mixer is going to my asio dest.

[ This Message was edited by: Kymeia on 2005-01-01 20:05 ]

Post by **garyb** » Sat Jan 01, 2005 10:34 pm

to record a vst synth, before opening logic(or any other sequencer), make sure that you will have enough asio channels for what you would like to do. i like to start with 4 or 6 source and 10 dest. i use the stdm2448 mixer and everything connects to the mixer. 8 of 10 asio dest channels are connected to the mixers recording busses(or vice-versa), leaving me with 2 connections for unexpected things(like suddenly deciding to use the io plugin). the first 2 of the source connections go to a stereo input of the mixer for monitoring purposes, leaving 2 or four connections for unforseen(or forseen) uses. recording a vst instrument in realtime with effects is one of them. assign the outputs of the audio instrument to an unused asio port and connect the port(asio source) to an appropriate mono or stereo channel. assign the channel to a recording bus. on an open audio channel in logic, set the input to the recording bus chosen(connected to asio dest) and record enable. press record.

the previous epic has a clue to recording scope synths. on the mixer channel connected to the synth, assign a mix(recording) bus. on an open audio channel in logic, set the input to the recording bus chosen(connected to asio dest) and record enable. press record.

this is how i do it, but there are many other ways. the trick is to follow the signal path. the scope card allows you to do things that were one thought impossible or impractical in the computer, routing and monitoring-wise so i really don't like to think of it in terms of a sound card(which it is). the scope environment represents the world inside the computer as an analog of the real world. think of logic as a hardware multitrak/midi sequencer(like a super vs880). scope is the "room" that the device(logic) is sitting in. in the real world, in a studio, you monitor and route everything through the mixer, that's why i do it that way. the advantages are easy signal routing and control(eqs, effects, gain control, headphone monitor bus) and zero latency when overdubbing.

Kymeia · Post by **Kymeia** » Sat Jan 08, 2005 9:15 am

Thanks for the help.

I've just realised the simplest method for recording anything that comes out of the mixer is just to add a wave in and out to the project and use an audio editor to do it (just trying a demo of Audition at the mo which is lovely). I get everything this way and as it uses direct sound I can run it alongside my asio apps as well.

Post by **garyb** » Sat Jan 08, 2005 1:34 pm

sure, you can do that if that's how you like it(flexibility is a scope strong point). i kinda think that is a bit of an extra step, but if it works....i think that method might make overdubs and punch-ins tricky...

[ This Message was edited by: garyb on 2005-01-08 13:36 ]

rounser · Post by **rounser** » Tue Jan 11, 2005 2:07 am

I like to keep things simple because mostly I freely improvise in realtime so what I really need is just a way of recording as I play that is relatively hassle free and records the whole sound (inc effects etc) without disrupting my creative flow.

I had this problem too...I'd do something cool and then wish I had had record on.

In the Tips and Tricks forum there's a thread called "Background recording" with a link to a piece of software called Silent-Bob which records into RAM minutes before you hit record - very useful to have this running in the background if you're mucking around with SCOPE, so if you do something cool, you can hit record then and it's not lost. The demo does the job. A possible downside is that it can only record at 44K.

astroman · Post by **astroman** » Tue Jan 11, 2005 4:51 am

you can easily do that with VDAT - just keep it lurking in your signal pass and push RECORD when you get close to something.
Any # of tracks and resolution, almost no DSP load

Later just cut the good pieces from the recorded files.

cheers, Tom

rounser · Post by **rounser** » Tue Jan 11, 2005 6:07 pm

you can easily do that with VDAT - just keep it lurking in your signal pass and push RECORD when you get close to something.

But won't it only start recording from the point at which you press record?

If so, then the whole point is that that's back-to-front creatively speaking - you want to press record to save something you've already played which is cool, not predict that you're about to play something cool and press record then. That's why I'm so fond of Silent-Bob.

astroman · Post by **astroman** » Tue Jan 11, 2005 6:38 pm

well, in that case follow instructions on page 17 of the VDAT manual (it's part of the regular SFP docs)

You set 2 'outer' locators to constantly loop, and in between those you place 2 'inner' locators for punch-in and punch-out, so the thing is constantly recording.

cheers, Tom

rounser · Post by **rounser** » Tue Jan 11, 2005 6:44 pm

Fair enough, but to RAM or the hard drive? It would be a pity to burn out the hard drive after doing that continually, because it's a lot of data to be constantly writing...

[ This Message was edited by: rounser on 2005-01-11 18:46 ]

astroman · Post by **astroman** » Tue Jan 11, 2005 6:55 pm

to hard drive of course, but you're free to supply a solid state disk...

I might be missing the point, but do you really assume that a record loop (like described above) is a load for a HD.
That's holiday for the disk, it can do it for 6 month or longer non stop - no kidding, it's the best job an average HD will get in it's life

See it this way: the files are created ('tape formatted'), the record starts, the head steps one block after the other, at the end the head is moved to the start again and slowly steps one block after the other...
No back and forward, no wild seeking, step by step.

cheers, Tom

rounser · Post by **rounser** » Tue Jan 11, 2005 7:08 pm

True...which reminds me, mine could probably do with a defrag about now...

at0m · Post by **at0m** » Wed Jan 12, 2005 12:43 am

I do strongly suggest against defragmenting drives with multi-track recordings, especially VDAT audio files! During recording, these files are layed out interleaved. Upon playback, that's also how they will be read. Defragmenting this will give your harddrive another good job to do, plus the head will be jumping back and forward during multi-track playback later.

valis · Post by **valis** » Wed Jan 12, 2005 2:23 am

Sounds like a market for a multitrack-aware utility to defrag audio data from within your host app...

Alternatively many people use an extra drive specifically for each new project and format or defrag before beginning (empty drive). Of course that's less necessary these days than it was 4+ years ago...