From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: Fwd: Re: Fwd: Re: merging mono files
Date: Wed, 14 Dec 2016 12:40:40 +0000 [thread overview]
Message-ID: <8094f4057fdc38ae9d7aa3bbbbcff37b@wingsandbeaks.org.uk> (raw)
In-Reply-To: <a4a8dbad-f841-8395-c3d1-7cda4d99d7a1@gmail.com>
On 2016-12-14 07:22, Dr. Mark Bugeja MD wrote:
> Hi,
>
> I can only test the files in GrandOrgue when I build the organ in
> question. I cannot test individual files on the software. I did check
> files with iZotope and they look good visually, sound well when
> played, they are in 24 bit and 48kHz sample rate, they load up on
> LoopAuditioneer so I could add pitch information and loops.
>
> The only other software that issued a warning was Sony's Soundforge...
> though I can't get this warning again for some reason. What I am
> noticing just now is that Soundforge gives a detail (property) when
> opening up a file, something that I did not observe before, not that
> it means anything to me:
>
> * Rgns/Play/Cmd: No/No/No
>
> A file that is known to work with GrandOrgue gives _*
> *_
>
> * Rgns/Play/Cmd:_*Yes*_/No/No.
>
> Could my answer lie with this difference?
I've no idea what that means. However: http://www.magix-audio.com who
took over the
Sony products do have technical support (I know this because I emailed
them several
times fairly recently about one of their other products), so you could
email them and
ask what that means.
--
Jeremy Nicoll - my opinions are my own
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2016-12-14 12:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5ed1e52-d9ed-f3e9-3295-05d2e00549b5@gmail.com>
2016-12-12 20:07 ` Fwd: Re: Fwd: Re: merging mono files Dr. Mark Bugeja MD
2016-12-13 1:40 ` Jeremy Nicoll - ml sox users
2016-12-13 18:39 ` Dr. Mark Bugeja MD
2016-12-13 23:48 ` Jeremy Nicoll - ml sox users
2016-12-14 7:22 ` Dr. Mark Bugeja MD
2016-12-14 12:40 ` Jeremy Nicoll - ml sox users [this message]
2016-12-14 9:50 ` Dr. Mark Bugeja MD
2016-12-14 12:44 ` Jeremy Nicoll - ml sox users
2016-12-15 9:31 ` Jeremy Nicoll - ml sox users
2016-12-15 10:18 ` Dr. Mark Bugeja MD
2016-12-15 11:31 ` Jeremy Nicoll - ml sox users
2016-12-15 14:20 ` Dr. Mark Bugeja MD
2016-12-15 16:46 ` Dr. Mark Bugeja MD
2016-12-15 17:42 ` Jeremy Nicoll - ml sox users
2016-12-15 17:59 ` Dr. Mark Bugeja MD
2016-12-16 2:47 ` Dr. Mark Bugeja MD
2016-12-16 9:46 ` Jeremy Nicoll - ml sox users
2016-12-16 10:31 ` Dr. Mark Bugeja MD
2016-12-14 13:02 ` Dr. Mark Bugeja MD
2016-12-14 13:29 ` Jeremy Nicoll - ml sox users
2016-12-14 14:05 ` Dr. Mark Bugeja MD
2016-12-14 14:50 ` Jeremy Nicoll - ml sox users
2016-12-14 13:58 ` Dr. Mark Bugeja MD
2016-12-14 14:56 ` Jeremy Nicoll - ml sox users
2016-12-14 17:03 ` Dr. Mark Bugeja MD
2016-12-14 19:21 ` fmiser
2016-12-14 14:21 ` Dr. Mark Bugeja MD
2016-12-14 14:53 ` Jeremy Nicoll - ml sox users
2016-12-14 15:27 ` Dr. Mark Bugeja MD
2016-12-15 8:56 ` Jeremy Nicoll - ml sox users
2016-12-15 8:48 ` Jeremy Nicoll - ml sox users
2016-12-15 8:32 ` Jeremy Nicoll - ml sox users
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8094f4057fdc38ae9d7aa3bbbbcff37b@wingsandbeaks.org.uk \
--to=sox-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).