|
|
Tascam Us-122, Review of new USB device |
|
|
|
Fri 24 Oct 2003, 16:36
|
Newbie
Group: Members
Posts: 4
Joined: 24-Oct 03
From: Cardiff - UK
Member No.: 27,414
|
I thought the purpose of OS Classic was to enable Mac users with newer machines to use older programmes. Why won't Cubasis work in Classic and is there anything that can be done to remedy the problem? I currently have a us 122 on order and don't want to be lumbered with a piece of kit that isn't going to work on my machine. Any advice will be greatly appreciated.
|
|
|
|
|
Fri 24 Oct 2003, 16:50
|
Newbie
Group: Members
Posts: 8
Joined: 10-Oct 03
From: Chicago - US
Member No.: 26,452
|
I got a suggestion yesterday from a friend that seems to aliviate the OSX compatability problem. I was unable to open protools free in classic because my computer would ask for OMS settings and then it would crash.If you go to the start up disk option for your computer prefrences, you can set your computer to boot up in OS 9.2, at least thats what mine did, and my computers new so I'm assuming that's a standard thing. I was able to run protools just fine then, so I'm assuming Cubase will work the same. You can reset the start up disk if you want to go back to OSX. Does anyone know if there's any reason why this would be a bad way of doing things. It's a little time consuming, but if you want to use older sound programs, I don't see any other option.
|
|
|
|
|
Fri 24 Oct 2003, 17:15
|
Junior Member
Group: Members
Posts: 132
Joined: 13-Sep 03
From: - US
Member No.: 24,676
|
huwthom and jebbels- booting into 9.2 (whether by holding the option key at startup or using the System Prefs method as J describes) is totally fine- not a 'bad way of doing things'. the two quick things i wanted to say is that booting into 9.2 is not the same as running Classic from within OSX (just in case this isn't obvious to somebody new who's reading this thread).
also, while you make a valid point that classic's purpose is to run older apps, the truth is that classic is not as robust as osx or a regular booting os9. it's best to think of it as OS9Lite or something- use it for a simple util or a fairly small program that isn't all that realtime processor dependant and it's okay, but don't expect to launch launch Cubasis in it and track audio or you'll be disappointed.
--------------------
Kit: Dual Ghz G4, Vaio 2.6ghz GRV670 notebook. Software: Reaktor, Reason, Ableton Live. Leanings: Laptop performance, jazz guitar, singing.
|
|
|
|
|
Fri 24 Oct 2003, 19:21
|
Senior Member
Group: Members
Posts: 235
Joined: 25-Jul 02
From: Strongsville - US
Member No.: 6,217
|
QUOTE (jebbels @ Oct 24 2003, 10:50) at least thats what mine did, and my computers new so I'm assuming that's a standard thing. Actually, new Macs lost the ability to boot into OS9 as of January 2003. You must have bought a computer from some older inventory. Not that that's a bad thing! At least now you can run Cubasis if you get that 122. The only downside is really the limitations of that program, but depending on your needs, it might suit you just fine. Huwthom - if your Mac doesn't boot into OS9, I think you'll have to consider one of the free/cheaper options mentioned in my previous reply, as I'm not aware of any bundled OSX-native DAW apps - at least not with interfaces this cheap.
|
|
|
|
|
Thu 30 Oct 2003, 11:03
|
Newbie
Group: Members
Posts: 2
Joined: 30-Oct 03
From: OSLO - NO
Member No.: 27,830
|
Hi. I just got my Tascam U-122. I'm a PC user, but got the same problems with the "fuzzy" audio signal. When I try to record from a Microphone, using the XLR input, I get a fuzzy signal that's no good at all. I experience small pauses in the input signal. When i don't record, it sounds well using the audio output or headphones. Any suggestions to eliminate the fuzz ???? (Recording is done in Cubase sx)
|
|
|
|
|
Fri 21 Nov 2003, 22:41
|
Newbie
Group: Members
Posts: 1
Joined: 21-Nov 03
From: Cave Creek - US
Member No.: 29,412
|
QUOTE (rickenbacker @ Oct 15 2003, 15:38) The summed input issue is basically that - a mic and line in don't play nicely together inside the US-122, although it's not a total disaster. If you're a kind of one-man-band in your bedroom, or you want to build up a song one track at a time, or you want to record something live using two mics or a stereo feed or whatever, the 122 is fine. If you want to get some kind of Bob Dylan vocal mic, guitar and harmonica thing going on, it's not best suited for that. I, too, thought it seemed from the manual that the summed input issue was only a problem when you tried to use line and mic/guitar on the same channel. Has anyone actually tried mic on one and guitar on the other, or a similar mixed combination, and did it work? This will be the primary application for me.. Thx!
|
|
|
|
|
Sat 29 Nov 2003, 20:37
|
Newbie
Group: Members
Posts: 1
Joined: 29-Nov 03
From: London - UK
Member No.: 29,961
|
Is there somebody also having problems with latency (with MIDI) using the tascam us-122 in cubase SX. Basically the problem is the following: when I hit a note in the keyboard editor in cubase, the response when I have the tascam us-122 connected is quite long, and definitely longer than when I play on the soundcard of my laptop. I would expect the latency of my laptop's soundcard to be worse than the latency of the tascam us-122, and not the other way around. Is there somebody who can give me some suggestions for resolving this. Many thanks in advance
|
|
|
|
|
Sat 13 Dec 2003, 00:40
|
Newbie
Group: Members
Posts: 18
Joined: 01-Sep 03
From: Clovis - US
Member No.: 23,979
|
I have been watching this thread for awhile. Although Tascams forums never reappeared after the OSX fizzle and drop-out problems were first reported, I have read here and there that Mac users are having better luck now with the US series.
Anybody out there who is using the drivers for Panther? I would love to hear more before I buy. Thanks.
Also, regarding the latency question concerning internal vs. external soundcards: The onboard card should have the least latency, especially if you are using core audio and MIDI. It's the roundtrip from your instrument to your interface, via your computer, that causes the latency.
This post has been edited by Oakland Stroke: Sat 13 Dec 2003, 00:43
|
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
|
|