If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
mono to frame module question
11 posts
• Page 1 of 2 • 1, 2
mono to frame module question
I tried to deal with the mono to frame component module ( with number of samples to grab ), but without success...
So please post little example how to use it ( with ruby component desireble )!
So please post little example how to use it ( with ruby component desireble )!
- Dimmak01
- Posts: 12
- Joined: Mon Oct 19, 2009 11:38 am
Re: mono to frame module question
that's pretty cool mate.
Now you can process the frames.
What are you planning to do to them?
edit- can we build a direct to disk recorder?
Now you can process the frames.
What are you planning to do to them?
edit- can we build a direct to disk recorder?
-
nix - Posts: 817
- Joined: Tue Jul 13, 2010 10:51 am
Re: mono to frame module question
Dimmak01 wrote:Solved.
Good to hear!
Just wondering whether this Is a universal solution or only suited for your own equipment...
For instance: what happens if the soundcard's driver latency is 128 samples and one would request 192 samples at once? (or am I misinterpreting the "output 192"?)
T A D - since 2005
-
TheAudiophileDutchman - Posts: 46
- Joined: Tue Jul 13, 2010 1:36 pm
- Location: Apeldoorn, The Netherlands
Re: mono to frame module question
TheAudiophileDutchman wrote:Dimmak01 wrote:Solved.
Good to hear!
Just wondering whether this Is a universal solution or only suited for your own equipment...
For instance: what happens if the soundcard's driver latency is 128 samples and one would request 192 samples at once? (or am I misinterpreting the "output 192"?)
I guess you'll get 192 samples, each one with 128 samples delay
- TomC
- Posts: 13
- Joined: Fri Jul 16, 2010 10:38 pm
Re: mono to frame module question
Thanks for your swift response, TomC. Not sure if my message was formulated clearly enough though, so let me try to rephrase: In the given example I mean the case where the blocksize is 128 samples and then an unequal 192 samples are requested (i.e. not a multiple of 128). Would the total delay then become 256 samples
T A D - since 2005
-
TheAudiophileDutchman - Posts: 46
- Joined: Tue Jul 13, 2010 1:36 pm
- Location: Apeldoorn, The Netherlands
Re: mono to frame module question
If you're wanting to process all the samples that come on a Mono stream then the way to do it is as shown below. This implements a simple delay effect. I've attached the schematic for you as well.
The Mono to Frames component will give you each buffer as it comes.
Your solution using the Mono to Graph will work if your buffer size is 192 but if you change it then you will get anomalies in the audio. Let's take the example TAD has suggested. If your audio card is set up to work with 128 sample frames then each time one of these is requested at the ASIO Out, you're grabbing the last 192 samples instead of the last 128. The ASIO Out will still only use the first 128 of these but because you grabbed 192 the start sample will not be correct - it'll be shifted back by 64 samples, hence the anomalies.
The Mono To Graph can be used instead of the Mono to Frames in this scenario if you use the Frame Sync component to supply the buffer size.
Mainly the Mono To Graph is used for analysing signals. It allows you to grab samples at lower than sampling rate and specify exactly how many samples you want too.
The Mono to Frames component will give you each buffer as it comes.
Your solution using the Mono to Graph will work if your buffer size is 192 but if you change it then you will get anomalies in the audio. Let's take the example TAD has suggested. If your audio card is set up to work with 128 sample frames then each time one of these is requested at the ASIO Out, you're grabbing the last 192 samples instead of the last 128. The ASIO Out will still only use the first 128 of these but because you grabbed 192 the start sample will not be correct - it'll be shifted back by 64 samples, hence the anomalies.
The Mono To Graph can be used instead of the Mono to Frames in this scenario if you use the Frame Sync component to supply the buffer size.
Mainly the Mono To Graph is used for analysing signals. It allows you to grab samples at lower than sampling rate and specify exactly how many samples you want too.
- Attachments
-
- frames delay.fsm
- (6.76 KiB) Downloaded 1137 times
-
admin - Site Admin
- Posts: 231
- Joined: Tue May 11, 2010 6:30 pm
Re: mono to frame module question
Thank you very much for this clear explanation, admin.
T A D - since 2005
-
TheAudiophileDutchman - Posts: 46
- Joined: Tue Jul 13, 2010 1:36 pm
- Location: Apeldoorn, The Netherlands
Re: mono to frame module question
BTW: what is that init method in the example above? When is it called? There is no mention in the manuals.
- rlr
- Posts: 27
- Joined: Tue Jul 13, 2010 9:17 pm
Re: mono to frame module question
init is called when the file is opened AFAIK
-
nix - Posts: 817
- Joined: Tue Jul 13, 2010 10:51 am
11 posts
• Page 1 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 98 guests