Community: Message List

Re: Input-output audio latency?

support@line6.com — Sat, 11 Jun 2011 19:15:16 GMT

(2nd edit, but hey as long as no one else responded yet I may as well correct my original post and pretend I didn't answer it in a hurry the first time.)

The TCDDK software and hardware guide with specifications are downloadable ( http://line6.com/software/readeula.html?rid=2432 ). The codec ( http://www.asahi-kasei.co.jp/akm/en/product/ak4552/ak4552_f01e.pdf ) analog filter group delay is 32 sample periods, then there's transmission time to and from the codec, 1 sample period each way, and buffered i/o copy time. Let's call it 36 sample periods total latency (if I'm way off someone should say so.) At 39.0625 kHz this is 0.92 ms, so it's right on the edge for your application.

Of course, you can increase the sample rate by modifying the clock division settings from the Line 6 template code, for lower latency but fewer compute cycles per sample.

Extremely low latency for realtime playing is one reason I prefer the ToneCore platform to writing DAW plugins, where you can easily encounter OS-incurred latencies of hundreds of samples.

New ToneCore Programmable Modules for sale

support@line6.com — Fri, 03 Dec 2010 01:38:58 GMT

I have a large surplus of modules, new in their original unopened boxes. As they are currently unavailable at the online store, and not available at all outside the US, I am offering some for sale, simply to recover my investment in them. Will ship them anywhere in the world USPS will deliver. Payment by PayPal only. Contact me to make arrangements.

Rane Pro Audio Reference

support@line6.com — Sat, 05 Jun 2010 21:28:58 GMT

Just thought I'd share this resource, I've found it very useful over the years:

http://www.rane.com/digi-dic.html

Re: Interested in developing, but have some questions

support@line6.com — Wed, 14 Apr 2010 08:41:01 GMT

Thanks Curt for mentioning those devices, they're interesting. I'd add that TCDDK and SoundBite use exactly the same DSP development tools, you can work with both.

Bryan it's pretty simple. If you just want to experiment with DSP you have a lot of options, but if you want to code your own real music performance stompboxes then TCDDK is the only option. You can produce professional-grade gear with it because that's what it is, the only thing missing is your professional-grade code. So deal with the knobs, they're noisy anyway and effectively quantize to six bits. Figure out how to make them work for you. Line 6 isn't going to change anything, but a larger community of TCDDK developers might help keep the product line going. So just jump in and do something, it's not expensive because you're just buying a stompbox. You have to figure out how to make it worth more than the hardware.

Re: Using Symphony Studio to debug on-target?

support@line6.com — Fri, 05 Mar 2010 20:30:46 GMT

Debugging the pedal, eh?

Be aware that reverse engineering anyone else's code is an international criminal copyright violation.

Re: Module broken by code ?

support@line6.com — Thu, 04 Mar 2010 03:51:51 GMT

What you are describing happens if you are using a USB hub between the pedal and the computer. If so, try it without the USB hub. It also happens if you are trying to use the TCDDK GUI software from within a virtual Windows environment under Parallels or VMWare on the Mac. If so, try it from an actual Windows PC.

Re: Expandability of Buttons/Inputs?

support@line6.com — Fri, 26 Feb 2010 07:42:51 GMT

If you download the free tools provided by Line 6, all of your questions will be answered. There are schematic diagrams, internal photos, and sample code. You can modify the programmable modules any way you like, they even discuss that in the documentation. Here's the link to the tools from the product page: Looking for the tools?Click here

Re: DSP Code Size Limitations?

support@line6.com — Sun, 07 Feb 2010 10:40:00 GMT

Hi Christian,

Sounds like you have a plan. No offense intended on the engineering advice, nor was it intended to solve your problem. I'm uncertain how much anyone here can help you, though, without having access to every file of your project (no I'm not asking for them) because, and excuse the general advice, when there is a contradiction, at least one of your assumptions must be false. Since $500 word programs do run fine, then there logically must be a false assumption involved, when the conclusion is that the size of the program alone is causing it to fail (one possible assumption is that the hardware is not malfunctioning.)

Good luck, I'll be interested in hearing what you determine is happening.

Re: DSP Code Size Limitations?

support@line6.com — Thu, 04 Feb 2010 22:02:51 GMT

I can corroborate Angelo's assertion that a $500 word program works fine.

Two things come to mind when reading and thinking about your approach:

1) If at any point in your DSP assembly code you skip even a single memory location, not having it filled with code or data, the tools will stop there and not load your whole program.

Look at the assembler output listing, any addresses with no contents listed will do this.

2) I would recommend approaching the device slowly and carefully, building up your program, testing and confirming functionality as you grow it. I have been programming a long time,

on all kinds of devices and platforms, and often I see coders who write a long program and then try to debug it. If you start with just the example startup code provided, and a null ISR doing nothing, then proceed to develop your code slowly and carefully, testing as you go, you can't go wrong, and won't end up with a large mess where the smallest unnoticed detail can break it. Forgive me for being pedantic, for any coders reading this to whom it is obvious, but the tendency to not test-as-you-write is way too common in inexperienced programmers, from my observations.

You don't need good luck, you need good methodology.

Re: Availability of ToneCore Programmable Modules

support@line6.com — Thu, 09 Jul 2009 18:15:56 GMT

Line6Miller:

Can you please find out exactly when you expect new modules to be in stock?

Some of us, me in particular, are planning an imminent commercial product release, and absolutely need to know about availability.

"please keep checking in periodically." is not a viable option. Please find out and reply with specific information.

This is not a hobbyist's inquiry, I am risking a lot on going into business doing this, and I'm sure others are as well.

Thanks.